CompuServe Messages

> If you use GVPSCSICTRL to rescan the bus before trying to access the > CD-ROM, you should not get those error messages. Copy GVPSCSICTRL into > your C: directory and add the following just before the line that tries > to call the CD-ROM: > > GVPSCSICTRL -r I _did_ this, it is in fact why I'm posting the complaint here, instead of bothering CPR or ASIM. > driver. It probably came from the CD-ROM software you are using. > Secondly, most of the error codes that WE would give are for > engineering purposes only. In ALL cases, our messages merely refer to > some type of error communicating on the SCSI bus, usually because of > improper cabling or termination, unless a real hardware problem exists. Given that the drives system worked perfectly with a 3000's somewhat less than perfect SCSI interface, I don't think this is an issue. > Again, the GVPSCSICTRL program was written specifically for this > purpose. In a worst case scenario, you will have to add a WAIT > statement before the rescan. I hope this has cleared up your issues. I can try moving the gvpscsictrl command to the end of my user-startup, but I don't think this will work on a CD-ROM drive — no RDB after all. As far as adding the wait…. Well, I got the error when I turned my 4000 on today, and the CD-ROM isn't there — as is normal if I don't 3-key-salute my 4000 after turning it on. Well I _just_ tried "GVPSCSICTRL -r 3 DCOFF" and I get "Error 33 while opening SCSI unit 3." Also, why did it take one message _and_ a flame to get a GVP response? Brian — Cruising on AutoPilot…..