Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!mimsy!dftsrv!oneel From: oneel@heawk1.gsfc.nasa.gov ( Bruce Oneel ) Newsgroups: comp.windows.ms Subject: Re: Paradox under Windows 3 Message-ID: Date: 4 Jun 91 14:24:14 GMT References: <1991Jun3.212209.21014@ibmpcug.co.uk> <37140025@hpopd.pwd.hp.com> Sender: news@dftsrv.gsfc.nasa.gov Organization: STX/GSFC Nasa Lines: 25 In-reply-to: dcc@hpopd.pwd.hp.com's message of 4 Jun 91 09:53:36 GMT In article <37140025@hpopd.pwd.hp.com> dcc@hpopd.pwd.hp.com (Daniel Creswell) writes: This is a nasty I'm afraid we've got a customer with the same problems you describe. Your best bet is to load the PIF editor and configure memory requirements (KB Required/Desired to -1). In the advanced options goto memory options and set both KB Requireds to 0. Then set the limits to -1. Select both 'locked's and the uses HMA and Lock App. memory. If that doesn't sort it your stuck I'm afraid. Paradox is a nasty and I don't know that you'll be able to run even with this. If your running a mem. manager such as EMM386 or QEMM remove it and see if that helps. Thats all I have, Dan C. I believe that paradox runs in three modes under dos. Real, 286, and 386. Try running it in real mode. Slow, but should run under windows. bruce -- Bruce O'Neel oneel@heasfs.gsfc.nasa.gov NASA/GSFC/STX/Code 664