From: jdashiel AT eagle1 DOT eaglenet DOT com Date: Mon, 24 Feb 1997 19:15:59 -0500 (EST) To: opendos AT mail DOT tacoma DOT net Subject: [opendos] opendos and provox mixed 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 As some of you may be aware, provox is one of the screen review packages which is freeware used by print disabled computer users. I've been successful running provox from an opendos created boot disk and am doing that right now. There was a failure however once opendos was installed on my hard drive however. Provox managed to load in config.sys but it appeared the computer hung after that. I loaded provox after dpms.exe and emm386.exe. I have more hacking to do on this end as things stand. Load order may be having some kind of impact, and emm386.exe may have to be run with pic=on option in autoexec.bat file. One thing that was very surprising to me this morning when I tried this installation for the first time using the fixed opendos (2nd release) was that partly through my boot up my printer which is an epson fx on lpt1 started printing. I have to check the print out since some intelligible material might be on that papger. The printer printed over a page and showed no signs of stopping so I turned it off. There were two or three intermittent double beeps that came from the computer while the printing was happening. Finally, I left the installation alone at 2 o'clock and got back to it about 9 o'clock. by that time even with no disk action happening any key I hit on the keyboard beeped like the keyboard was already overflowed. So I hit the reset button and started on this second adventure. A note about edit.com is that it doesn't honor newui=off or the /n parameter on the command line. In fact any attempt to use /n on that command line gets an error message.. Finally, possibly that newui statement might be in more than one file, since only part of install.exe honored it. The last statement you hear before you have to force speech is reading taskmgr.ini. This isn't impossible, it's just not yet ready yet. jude