#Mystery Conflict
5 messages in this thread
Fortunately, this question is now academic. Nevertheless, I have
two SCSI drives attached to my Always IN-2000 SCSI card, along with a Texel
DM-3024. I also have an IDE drive. This setup worked fine. I was able to
use all of the drives, as well as the CD-ROM, without a hitch. After a
week, it started locking up whenever I tried to access the CD-ROM. After
pulling my remaining hair for another week, I discovered that the problem
went away if I modified QEMM to exclude the address C800-CC00, the bios
area for the Always. My question is this: if there was an address
conflict, why did this setup work for a week?
Paul Green
The reason it might work for a week is because the memory that has been
excluded (not excluded) was not overwritten by another program thinking it
is memory. Once this are was overwritten (it corrupts) the memory used by
the host adapter that it needs to run. Since it is corrupted (all garbage)
it attempts to execute a command on garbage and since you can't execute
garbage it locks up (crashes).
Also if you run windows enchanced mode you have to exclude that area in
your windows.ini or system.ini. Forgot which one.
So your thesus is that there must be some program that I did not
use for a week, and that I must have begun using after a week? Not that I
recall, but I suppose it's possible.
Paul
Did you make any changes in drivers or TSR's or other configuration?
Are you running Stealth? If so try excluding the IN-2000 BIOS.
I run with QEMM all the time. Before excluding the BIOS, was did you have
it shadowed (ROM option)? Or as available RAM. Make sure that if it was
shadowed, that the whole range was allocated (C800-CBFF).
I'll check with Quarterdeck in the mornin, see if they have any other
suggestions.
By the way, are you using the stand alone Always CD driver, or the ASPI and
Corel drivers?
Let me know what happens.
–rick
I am not using the ASPI driver, only the IN-2000 directly, with
Always' CD-ROM driver. Adding a few more facts, I had been using my
IN-2000 for about a year-and-a-half. In preparation for adding the CD-ROM
(and running it under OS/2), I upgraded to the latest bios and firmware,
and got the Columbia Data Products OS/2 .ADD driver. Although it took me a
while to figure out how to use the driver (CDS' instructions omit certain
critical directions–like all of the necessary software switches), it
worked under DOS–for a week. Excluding the memory area from QEMM seems to
have resolved the DOS problem entirely, so no more solution is required.
Only my curiosity remains to be satisfied.
Paul