It's a FIGHT! 3.5 versus SCSI!

[mark@trillian.jsc.nasa.gov (Mark Manning)]

Ok - I already know why this is happening (or at least I'm pretty
sure why this is happening) but I was wondering WHY it is happening.

I am still working on getting CP/M up and running decently on the //gs.
I downloaded a program called ANYDISK.COM from oak.oakland.edu.  A very
nice program too. :)  Anyway, it would not read the smart port.  So I
had this 3.5 disk controller card in my //e and I decided to plug it
into the //gs.  Just to see if ANYDISK.COM would _then_ be able to read
the 3.5".

Well, not only would ANYDISK.COM not read the disk, but the SCSI disk
drive would no longer boot.  I even went so far as to remove all of the
other cards from the //gs and then to put them back one by one until
I had found which one was causing the problem.  It seems that the SCSI
disk drive controller card is using more than one of the memory areas
reserved for it.  It also seems that the 3.5" disk drive controller
card does the same.  This makes them dump on each other and die.

So, you go, "Who makes the cards?" and "Why didn't they stick with the
guidelines Apple put out?"  Well, these are both Apple products.  It is
the Apple SCSI disk drive interface card (a fairly new card) and an
Apple 3.5" disk drive card.  Can anyone explain _why_ this was done?
Other than - "we needed the memory in order to make it work" - answer
that is.

Thanks guys and gals! :)

----------------------------------------------------------------------------
Welfare is the art of taking the money you've earned and giving it to
someone who hasn't.

mark@trillian.jsc.nasa.gov