CompuServe Messages

I have had similar problems, and continue to have problems with the 2090. A few weeks ago, my hard drive crashed after trying to copy and run Interceptor. The hard drive was completely resistent to being reformated, despite low level formating the thing on another system (different controller). I was having no trouble with the hard disk at all until this moment of failure. Now I have another drive (Miniscribe 8425F ? – the same as before except with the "F".) and another 2090 controller. I used mount res0:, and prep res0: with the same mountlist, etc. as before, and nothing. I had to low-level format the drive several times, and it seemed that all worked best when the machine was cool. Anyway, it finally prep'ed and and formated, but now many problems -I have not been able to use the same s/startup-sequence. The thing seems to hang the first time I turn the machine on when executing: "newcli con:0/0/640/200/MyCLI from dh0:s/hdstart" If I warm re-boot, it seems to get past this most of the time, but then very often gets going and then I have a visit from the Guru with the # being: 00000003.00c09578 or 00000004.00c09578, or other things to the right of the decimal with 00000003., 00000004., or 0000000B.. IF I get past these, which it sometimes will do, I continue to Guru after running CLI or a while, or at time, the screen will go to clear blue or lockup after a command such as dir or type. It does not seem to be consistent when this occurs. I am using 3 partitions, and also at times get a "read/write error" from the hard disk or "not a dos disk". I am not sure, but it seems to work better if I do not run s/startup-sequence, b but enter the commands individually. I have tried putting "wait" in the s/ startup-sequence, but not helped. I have not had any such problems before, and do not have problems when running from a floppy disk. **Rich**