From: jdashiel AT eagle1 DOT eaglenet DOT com Date: Fri, 31 Jan 1997 02:31:30 -0500 (EST) To: opendos AT mail DOT tacoma DOT net Subject: [opendos] pic=on results Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-opendos AT mail DOT tacoma DOT net Precedence: bulk In short, no cigar. The longer version goes like: With an ami bios 386 you can't run the opendos emm386.exe driver as anything other than a device driver without having your system hung. opendos was able to load much of creative labs sb16 files and drivers until it got to the driver that had: /unit=0 /blaster=a 220 ... in its line. Now, creative labs requires both of those slashes but both generate an error under opendos 7.01. Everything in the config.sys file loaded with that exception so I decided to remove all references to that technology from my files and try again. That also failed. provox still does lots of what's now high short beeps when run and tinytalk does nthing. Btw, tinytalk was written in pascal. Most likely burbopascal too. Something else that I found interesting, I have a utility called syscap.exe which is one of those pcmag utilities capable of capturing what happens in the config.sys file and saving that to syscap.txt. When ansi.sys from the opendos directory was loaded, there was no message that showed up in the capture file for it. This system has 640k conventional memory and 3072 extended on it. I'm not trying to run the netware stuff, though I have another computer that's an xt with 512k memory on it. jude