Article 7217 of comp.sys.ibm.pc.soundcard: Date: Fri, 22 Jan 1993 17:00:07 EST From: Matthew E. Bernold Subject: Re: Daretro demo and OS/2 > > Can anyone confirm or deny whether Daretro will actually cause your >OS/2 system to stop booting, as was stated in a post a day or two ago? I'm >not going to run it if there's a chance it will, but maybe the problem was >just a one-of-a-kind type of thing. > Note: This is NOT a definate answer to your question, only an educated guess. I've run Daretro, and it runs in Protected mode, so I had to edit out the QEMM (or EMM386) line from my config.sys to run it. I ran it before doing this, and the demo said that it couldn't run because the computer was running in real mode, and it asked me if I wanted to attempt a clean boot. I said no, and it exited. Then I modified my system, and it ran no problem. It is my guess that what is harmful to an OS/2 system is letting the demo attempt to make a clean boot. It probably makes modifications to the system files (autoexec.bat and config.sys) and tries to reboot the system, which might cause problems with OS/2. If you boot your machine with DOS and only himem and your sound drivers loaded, there shouldn't be a problem running it on an OS/2 machine. You might just want to take a DOS formatted floppy, and make a bootup disk for Daretro. The demo is less than 200K... Just my opinion, Matthew E. Bernold MEB117@PSUVM.PSU.EDU <> meb@haydn.psu.edu ----> Article 7216 of comp.sys.ibm.pc.soundcard: From: dhumphre@comanche.ess.harris.com (David Humphreys) Subject: Re: Daretro demo and OS/2 > Can anyone confirm or deny whether Daretro will actually cause your >OS/2 system to stop booting, as was stated in a post a day or two ago? I'm >not going to run it if there's a chance it will, but maybe the problem was >just a one-of-a-kind type of thing. > Well, first of all, Daretro uses 386 protected mode, but it is NOT a DPMI program so it will not run under OS/2 period. But, if you do try to run it, it will bring up a message saying that the system is already in protected mode and therefore cannot run and will ask you if you want to try a clean boot. The dangerous part of this is that is replaces your config.sys thinking that your running under DOS (This is stupid even under real DOS, what happens if my command.com is not in my root directory). Once it kills your OS/2 config.sys, then of course OS/2 will not boot anymore and you'll have to go and boot off the OS/2 install disks. Therefore, if you do try to run it under OS/2, answer NO to the question about performing a clean boot. David Humphreys