jcmorris@mwunix.mitre.org (Joe Morris) (07/05/90)
At the risk of being flamed for posting a "how to set up" question... Has anyone successfully installed Windows 3 with a CD-ROM? I'm trying to run on a PS/2-70-121 with both Bernoulli boxes and a Denon CD-ROM. The Bernoulli interface is the normal MicroChannel (tm and all that) IOMEGA card; the Denon interface is a Future Domain unit. Both the Bernoulli and Denon boxes are SCSI. The Denon/Future Domain pair came from Microsoft as the "Programmer Bundle". The Bernoulli boxes work fine, but any attempt to access the CD-ROM is aborted with an error message that the device isn't ready, has an I/O error, or that MSCDEX hasn't been installed. (The problem occurs only in /386 enhanced mode.) File Manager knows that it's a CD-ROM; the button for the drive is properly marked. IAW the README file I've added lines to the SYSTEM.INI file: [386enh] device=lanman10.386 <--- yes, I used 'expand' to load this file! VirtualHDIRQ=FALSE Nothing seems to help. I've been talking to uSoft support, but they tell me that many of them have been thrown onto the front support lines with only initial training on WIN3, and that nobody in the support (read: talks to users) front line has a CD-ROM. (One tech asked me if it was attached just to play music!) The techs have no idea what's happening. [pilot light on] I was promised a call back from development before last week. Nobody called, and I couldn't even get to the support desk to complain! [pilot light off] Has anyone been successful in running WIN3 with a CD-ROM (especially using a Future Domain card) in '386 enhanced mode? Joe Morris PS: One rather disturbing item surfaced while I was experimenting with the system.ini file: parameter values apparently aren't checked for switch settings, and nobody verifies that a switch named in the file exists. None of the following lines resulted in any error messages: VirtualHDIRQ=dumbstuff DumbStuff=FALSE FileSysChange=foobar AnyThing=AnyThing In other words, there is no protection against a typo in a switch setting. The only way I know that Windows is reading the copy of system.ini which I changed was that I made a typo in the name of the device driver line; Windows (correctly) complained that it couldn't fine 'lanman.386'. That's scary.