CompuServe Messages

Brian, I'm not sure about the area you mention, but here are answers to your queries: >>>Annoyance #1: I am not able to use my CD-ROM drive without having to >>>warmstart immediately after first powering up my 4000. I get "Error 33 >>>accessing scsi ID 3" (or some such nonsense, the unit ID and error number >>>are accurate.) 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 >>>Annoyance #2: Why do you not publish a list of the farging error codes in >>>the manual? If you return them, you should _DESCRIBE_ them! First of all, the error code you describe above did NOT come from our 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. >>>Annoyance #3: The card prevents _any_ SCSI device from coming "on-line" >>>until the 4000 itself is powered on. This is NOT good when dealing with >>>relatively slow-to-spin-up drives like the Syquest and CD-ROM drive I >>>bought the thing to access. A FastLane ZIII or A4091 here would be like >>>using a sledgehammer to drive thumbtacks. 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.