ACB-2322B-8 and ISC

Bill Kennedy bill at ssbn.WLK.COM
Mon Nov 13 03:24:38 AEST 1989


In article <319 at abhg.UUCP> misko at abhg.UUCP (William Miskovetz) writes:
>
>> adaptec!neese writes:
[ Adaptec testing goals ... ]
>
>I have to wish you luck in getting a 2322B-8 working with ISC.  4 months
>ago I sent my ACB-2322B-8 controller and my Maxtor 8760E drive to ISC.

Lemme be sure I have this straight...  FOUR MONTHS???  I can certainly
sympathize with ISC's predicament trying to support all things for all
combinations and they should be grateful for your generous loan of
cutting edge hardware, but FOUR MONTHS???  That's ungrateful, unprofessional,
and borders (IMHO) on criminal!

>They still have it.  They have been unable to get me a system that works
>with the drive and controller.  They claim that version 2.2 will support

Now I get it, after four months, since a fix isn't available they keep
the equipment.  I guess it's no good to you anyway since you can't have
the fix.  If they have a fix and know that it works, why can't you have
it?  How do you, they, or anyone else know it works?  It seems to me
that if you were generous enough to let them enhance their product with
your equipment, it would be professional courtesy to let you have the
fix, not to mention returning the equipment.  Is there someone from
support at ism780c.ISC.COM who can offer a rational explanation for this?
Please post a follow up if so, I doubt that I'm alone in my curiosity.

>a 60MB drive has made me a little sour.  That and I have owned ISC versions
>1.0.5, 1.0.6, and 2.0.2 and have never had ISC running on my system.  That
>is well over a year of owning ISC without ever being able to use it.

I'll concede that 15MHz ESDI and a 760Mb drive aren't necessarily mainstream
'386 ware, but it would seem that if they wanted to support the drive and
controller combination it could be done with a phone call or so to Maxtor
and Adaptec.  Surely there's some incredibly complex technical problem here,
or might they just be inept/rude?  They must have had some confidence that
they could solve the problem before agreeing to borrow the stuff.

>I do have to thank ISC support.  At least they offered to try to get it
>running rather than just telling me I was out of luck, but this was after
>months of telling me "it's fixed in 2.0.2".

Thank them for WHAT, not charging for storage?  For not sending you their
telephone and electric bills?  Sounds like you're not only out of luck,
but also out of a drive and controller...

>Bill Miskovetz.
>{uunet!lll-winken, daver, pyramid}!abhg!misko
>misko at mathworks.com
>abhg!misko at lll-lcc.llnl.gov

I hadn't intended to be so lengthy, but what Bill Miskovetz is pointing out
here is symptomatic of a larger problem than just a busted device driver
(if it was ever intended to work in the first place).  There are the usual
"fixed in the next release" canards, we're all used to that.  There's also
the fact that it wasn't fixed, at least in the three releases he bought.
What disturbs me is that ISC, a Kodak company, seems to think that his
equipment was donated equally "as-is" as their OS.  They don't let him have
the fix (if there is one) and don't return his stuff.  I'm incredulous...
Or I guess I would be if it wasn't true.  This IMHO deserves an official
ISC response.  If they are conducting their business this way, their
customers are entitled to an explanation.
-- 
Bill Kennedy  usenet      {attctc,att,cs.utexas.edu,sun!daver}!ssbn!bill
              internet    bill at ssbn.WLK.COM   or attmail!ssbn!bill



More information about the Comp.unix.i386 mailing list