CompuServe Thread

#Rel. 3 Install Help!

7 messages in this thread
#62974From: Stan Kalisher (Impulse)Oct 23, 1993 7:48 AM
Help! I'm trying to get Rel. 3 up and running and I get the following message when the program attempts to boot: Abnormal program termination: Memory Protection Fault CS:EIP = 000Fh:000A676Ch I've tried stripping everything out of my autoexec and config files, I've monkeyed around with Cfig386 and the message is always the same! Any help will be sincerely appreciated. –Rick Rodriguez
#63061From: John TissavaryOct 24, 1993 12:05 AM
Make sure you've got %100 conflict free hardware. R3 is very unforgiving in that area. You'll want to exclude all of the memory blocks that your hardware uses, without exception. If you need further assistance, upload more info on your system (hardware, config files, software problems, etc…) and I'll try to help. I just went through a mammoth hardware/software chase to get things going on my system, too and learned a couple of things on the way.
#63071From: Stan Kalisher (Impulse)Oct 24, 1993 6:04 AM
John, shouldn't remming out all lines referring to hardware in the autoexec and config.sys temporarily beat those conflicts? I booted up with a very vanilla system and I still get the same message. –Rick Rodriguez
#63205From: John TissavaryOct 25, 1993 2:38 AM
You're remming out device drivers and tsr's but not the rom (I think it's rom; I get confused) that the hardware itself uses in the upper memory area. You want to check your hardware and make sure that no two devices are trying to use the same space, plus take out any and all memory managment if you haven't already. Then, if that works, you can start adding stuff back in. It may even come down to physically removing/replacing hardware in your system untill 3ds works. That way you can track down the evil-doer and punish it appropriately <g>. Good luck, John Tissavary PS: If you list your hardware and config files I, or someone else (there are plenty of people on this forum WAY more qualified than me) can give you specific advice.
#63149From: Robert C. SeiwertOct 24, 1993 8:42 PM
Since you completely removed your config and autoexec I would suggest looking into your advanced CMOS setup. Also funky advanced disk controllers will cause problems. Do you have a SCSI or caching IDE disk controller. You may simply have to disable shadowing your system and/or video BIOS. Also you might try QEMM 7.xx to solve your problems. Although QEMM is mostly obsolete these days it can correct for compatibility problems. Have you tried calling your dealer for help? That is what they are there for.
#63185From: James M. MurphyOct 24, 1993 11:28 PM
Robert, PMJI, >> Although QEMM is mostly obsolete these days it can correct for compatibility problems << Could you explain what you meant by this? I've been using QEMM in all our Autodesk 3D Studio Installations the past year and a half and for our AutoCAD installations going back another 3 years and found it in general to solve many problems. The only caveat here is that one has to keep up with the ideosyncratic changes Mr. Gates deceides to throw in to each of his latest versions of DOS as well as certain hardware issues such as coexistance with bus-mastering devices and the VDS requirement. So what do you find obsolete? James M. Murphy
#63341From: Robert C. SeiwertOct 25, 1993 8:12 PM
Who uses Expanded Memory. Even VCPI is going away. Why waste memory supporting outdated standards. If you are still running Tips or Ani Pro then QEMM is still needed. BTW, I recomend QEMM to all my clients. I feel it is needed for compatability sakes. It is still much simpler to use a common memory standard. .