Steve McCrystal wrote in a message to David Calafrancesco:

 SM> ;
 SM> In a msg of , David Calafrancesco
 SM> writes to Will Honea:
 SM> ;
 SM> David,

 DC> What torqued me the most was that all I did was put the driver
 DC> into place in config.sys, shut down, rebooted and it instant
 DC> trapped. Tried rebooting to go to the command prompt and it traps
 DC> instantly after hitting Alt-F1. Then I fired up the install
 DC> disks, and they trap on bootup. I removed the drive and put a
 DC> different drive in as primary and everything boots fine. Haven't
 DC> dared try the DANIS driver a second time.

 SM> I couldn't help but notice several instances of "instant" in
 SM> the quote above. If the traps are indeed 'instant' do you
 SM> think Dani's driver really caused them?  Isn't it more
 SM> likely that the problem lies somewhere else, especially
 SM> given you machine wouldn't boot from floppies, which would
 SM> NEVER load Dani's driver? 

One of the first driver loaded, even before the recovery choices loads is the
IDE drivers. The other is the HPFS drivers. I think something caused the MBR
to get corrupted beyond all saving. If something corrupted the MBR or the HPFS 
tables thoroughly, then it is possible that every other boot that tried
bringing the HPFS drivers online would have trapped. 

 SM> Were you able to fix the problem with the original drive?
 SM> How? 

Deleted all partitions, and rewrote the MBR while the drive was in a different 
system as a secondary drive under WIN95. This was a brand new install and the
only thing I had done was apply all the recomended upgrades from the Warp-Up
CD. 

 SM> What switches did you use when you tried the DANIS506
 SM> driver? 

None if I recall correctly. 

Dave Calafrancesco, Team OS/2
dave@drakkar.org

... They got the library at Alexandria, they're not getting mine! 
---