Subj : Os/2 Evolution
To   : Matt Bedynek
From : David Bowerman
Date : Wed May 24 2000 02:56 pm

Matt Bedynek wrote in a message to David Bowerman:

 DB> Manufacturers dealing with issues in a timely manner?  Those
 DB> experiences have been few and far between.

 MB> Do tell.

 MB> What companies have you have extremely good and/or extremely bad
 MB> experiences with?

Hmmm... I'll limit this to recent (last couple of months) bad experiences to 
avoid rehashing old history.  The five good experiences go back over the last 
couple of years.

IBM.
   Excellent response to problems with one of their 5500 servers and a DLT tape 
unit.

HP.
   Problems with a HP4050 and networked Macintoshes.  An updated printer 
description file was supplied which solved the problems.

Seagate.
   Problems with using their 9.1GB SCSI drives with a RAID controller were 
acknowledged and a firmware update for the drives was supplied.

ATI.
   Problems with using VGA and TV output simultaneously under Windows NT 4.0 
were addressed in a timely fashion.  Not very helpful but at least the response 
was quick.

RedHat.
   A problem with an install on a Sparc was solved within 24 hours.

Creative.
   Problems with a Creative PCI sound card under Windows 98.  Their response 
was to query if we actually had a problem.

   Problems with a Creative CDROM which kept disappearing during bootup.  The 
response was nothing.  Not even an acknowledgement that the message had been 
received.

HP.
   Problems with a HP2100TN printer.  While a decent printer, it is NOT a 
printer suited for networked use despite the builtin Jetdirect unit.  HP seems 
disinterested at best.

Microsoft.
   A couple of our techs who just completed their MCSE/NT 4.0 are informed that 
their certification is being expired.

   A problem with an Access database was handled by constant reference to a KB 
article.  Unfortunately, the suggestions in that article didn't help and the 
help desk never seemed to get that idea through their head.

AOpen/Acer.
   Problems with the drivers supplied on CD with a clone using an AOpen MB. 
Finally solved by using drivers supplied by other manufacturers in the best 
pray and try again tradition.

Visio.
   Bug in Visio Pro 5.  The bug was acknowledged but no fix or workaround was 
suggested.  Current suggestion is to purchase Visio 2000 EE.  Admittedly, 
Microsoft purchased Visio so the lack of interest in supporting previous 
versions is understandable.

Regards,
       David

--- timEd/2 1.10.y2k+
 * Origin:  Frog Hollow -- a scenic backroad off the Infobahn (1:153/290)

.