The copy I have was being thrown away at the place I worked almost 2 decades ago. I fooled around with it back then, experimenting with the various configurations that are possible with DESQview, but never found any real use for it that couldn't be done more flexibly with other choices. This current installation was just done by starting with basic config.sys and autoexec.bat files (like what you get with the default DOS installation) and then running the QEMM and DESQview installation program, which creates new config.sys and autoexec.bat files. This setup the DESQview 386 configuration which uses Expanded Memory to page the multiple DOS programs back and forth from the program memory area (first 640KB). It initially worked with QEMM just fine, but when I started trying to load the IBM hardware drivers the computer wouldn't boot. So, I used the MS DOS memory management (which is the same as IBM's PC DOS) and didn't have any problems.
It really didn't take any "guru-type" savvy to get it working, but it can make it more tedious to make farther changes to the start-up configuration files. Providing you have enough memory, the program doesn't seem to have any trouble juggling up to 4 DOS real-mode programs (programs that will run in ~512KB ram). It's sort of like running command-line Linux with 4 virtual terminals open. On 7/15/13, john s wolter <johnswol...@wolterworks.com> wrote: > I have a license and have used this. I see it as a wonder you've gotten > this far. > > Cheers, > John S Wolter > ------------------------ > LinkedIn: johnswolter <http://www.linkedin.com/in/johnswolter> > johnswol...@wolterworks.com > USA, Eastern Standard Time, -5 GMT, -4 GMT DST > > > > On Mon, Jul 15, 2013 at 10:55 AM, <mcelha...@usnetizen.com> wrote: > >> I have a retail box copy of DESQview version 2.42 with all the >> accompanying manuals. In the error messages appendix says the >> following about this error: >> >> "The DESQview command you performed tried to read the indicated >> DESQview file, but couldn't." >> >> "If you decide the indicated file is bad, delete it and then reinstall >> DESQview. There is no harm in reinstalling DESQview over the same >> version of an existing system." >> >> In addition, it says: >> >> "Sometimes, loading memory-resident programs prior to starting up >> DESQview, or allocating too few DOS file handles (by the FILES command >> in your CONFIG.SYS file), can cause this error. Also, if DESQview >> cannot find the .DVO (Open Window Menu) file this message will appear >> as a Startup Message." >> >> On an installation of this program that I have on an old computer, the >> DESQVIEW.DVO file is 249 bytes. You are correct that QEMM is not >> required (at least for the version I have) because I am running >> DESQview 386 using MS HIMEM.SYS and EMM386.EXE without problems. This >> is because some IBM drivers I have for this old computer would not >> work with QEMM. >> >> I don't know if this is of any help, but it's all I know about the >> problem. Good luck. >> >> > ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
