Path: utzoo!news-server.csri.toronto.edu!rutgers!usc!trwind!venice!press From: press@venice.SEDD.TRW.COM (Barry Press) Newsgroups: comp.windows.ms Subject: Re: Paradox 3.5 and WIN 3.0 help Message-ID: <1035@venice.SEDD.TRW.COM> Date: 9 Mar 91 06:17:00 GMT References: <1991Mar07.013042.26527@vpnet.chi.il.us> <1991Mar8.234630.20522@bronze.ucs.indiana.edu> Reply-To: press@venice.sedd.trw.com (Barry Press) Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA Lines: 37 In article <1991Mar8.234630.20522@bronze.ucs.indiana.edu> hanj@bronze.ucs.indiana.edu (Jining Han) writes: >In article <1991Mar07.013042.26527@vpnet.chi.il.us> kji@vpnet.chi.il.us (Ken Isacson) writes: >>I am currently running WIN 3.0 on a 386 in the ENHANCED mode. >> >>I looking for tips on how to run Paradox 3.5 from WIN 3.0 in this >>mode. Currently WINDOWS is complaining about Paradox being a >bound to be contention and conflict. So if you want to run Paradox in the >PROTECTED mode, you need to run it from DOS, just as you have >installed it from DOS. I tried to do this a while ago, and while I wasn't completely successful, I think I know why by now. First, there are a couple of parameters in the paradox command line you need, one of which (I think) was -real, which shuts down the protected mode slop. ANother may have been -share, but I'm not sure. I seem to recall something in a readme file or in one of the manuals. Borland themselves were somewhere between helpful and clueless. Once you get past the protected mode trouble, however, you're not home free. At that point I had paradox complaining about not enough DOS files/buffers. I of course ran them to very high numbers in config.sys but with no effect. What I have since seen, but never tried due to lack of further interest in forcing paradox to run, is a setting in the [386enh] section of system.ini that lets you put in a line like this (ta da): PerVMFiles=dd The default is 10, which works for most apps, but not for paradox. Presumably, bumping this past the paradox minimum will do the trick. (Actually, there is an amazing trove of things in the sysini*.txt files. DualDisplay was also a major fix for UAE's and such in my VGA/MDA setup, automatic display detection notwithstanding). -- Barry Press Internet: press@venice.sedd.trw.com