CompuServe Thread

Memory config questions

9 messages in this thread
#31733From: Aaron WeintraubJan 12, 1993 4:21 PM
Hi. I have what has been turning out for me to be a configuration nightmare. I'm really hoping I can get some hard advice on what to do from the people here on the forum. Here's the situation, nothing too complex, yet complicated nonetheless: I just got a new system, 66 Mhz IBM PS/VP 486DX2 with 32 megs of RAM. I also have a Targa 64+ and Windows. I have Qualitas' 386-to-the-MAX as my memory manager. How should I have everything configured for everything to work to it's full abililty? I'm using the Targa in a 2 monitor setup. Basically, I need config.sys, autoexec.bat and Targa information. I'm not sure how to set up the memory manager either. What interrupts should be set? What about excluding areas of RAM? I know I can't run 3DS from Windows, but do I have to reboot with a different autoexec and config.sys to change between running windows and 3ds? I'd really appreciate it if someone could help me out. Just ask if you need some more information, or if I forgot to mention something. Thanks.. Aaron
#31860From: Ted BoardmanJan 13, 1993 9:42 AM
Aaron I had trouble with 386max and 32megs a while back. Getting out of any Adesk product would take 2-3 minutes until returning C:>. Switching to Qemm took care of the problem. Just for your information. TedB
#31917From: Aaron WeintraubJan 13, 1993 3:35 PM
Hmm… interesting to note that. I had problems with QEMM a while back, it rebooted my system when it came to the QEMM line in CONFIG.SYS. My system just went in an endless rebooting loop and I had to stick a DOS disk in to stop it. That's why I decided to try 386max. Aaron
#31973From: CARL SMITHJan 13, 1993 11:14 PM
Aaron- Qemm is a very good product and in some way even worked along side the Yost people in writing of 3ds, see installation and performance manual. Qemm is very tricky and technical to get working "correctly", if you can get it to work on your system I highly recommend it. From my experience it takes a lot of diligence to tweek it out correctly. Qemm has a forum on CIS you can get help from. I think its GO QEMM. Any way thats my two bits, two cents or two what ever economic structure you like to use. Carl-
#32378From: Peter KrokoJan 17, 1993 3:22 PM
Its me again, I had zero trouble getting qemm to work on any of my systems. In fact, until recently, I had absolutly no idea what I was doing…Just typed "install"… no brain-no pain. Regards, Peter Kroko
#32421From: CARL SMITHJan 17, 1993 9:59 PM
Peter- Don't get me wrong. I think Qemm is great, I said it takes some time, at least in my case, to get it "tweeked out". When I first install it all by it self, I just typed install, I had a good running system with only 476k of mem left. After a lot of reading and help I got it up to 600k, playing with exclude statements, stealth parameters, re-arranging the order of TSR programs and so on.
#32487From: David TaffetJan 18, 1993 12:14 PM
Seems odd, Carl. When I installed QEMM, I got 633K, 1st time on about 10 machines. How many TSRs have you got? Our machines have mouse drivers, network drivers, doskey and PC Support drivers. Totals about 150-200K and all are loaded high. I usually run QEMMs OPTIMIZE/q (/q=quick, blows past all the prompts) and get the above result….FWIW David Taffet
#32502From: CARL SMITHJan 18, 1993 1:18 PM
David- Hey thanks for the tip on \q I never saw that in the manual. Anyway, I had to exclude some high memory for the Herc. board to work, C000-CFFF, otherwise I kept getting hangups, plus I had to use a DiskBuffer of 7 for the SCSI drive to work and my Aspikern.sys will not run in high mem, don't ask why I only know that is the way the computer whats it or else, its hang-em high time.
#32691From: David TaffetJan 19, 1993 4:22 PM
Yeah, the /q isn't in the manual. One of Quarterdeck's tech personages told me about it. DT