#Memory conflicts.
3 messages in this thread
Ted,
I hope you don't mind, but I have some rather mundane but frustrating memory
conflicts going on that I really don't know how to solve. If this stuff is not
your forte' please refer me to the right person. Here is the pertinent
information:
Hardware:
486-DX-33-EISA
16MB-RAM
SONY 2X-CD-ROM Drive
DPS-PAR System
Software used (listed most often to least often):
3D Studio r4
AutoCAD r12 (DOS)
DPS-PAR
Windows 3.1 (Windows stuff only)
PCTools ver. 7.1(DOS)
I'm getting alot of memory error msgs. in Windows and PCTools. Everything else
seems to be OK.
Here is my autoexec.bat and config.sys. Could you please edit them the way you
think they should be? Sorry for asking such a tedious favor. Thanks.
Tim
autoexec.bat
C:\WINDOWS\SMARTDRV.EXE
SET CPAV=C:\CPAV\CPAV.INI
SET PCTOOLS=C:\PCTOOLS\DATA
PROMPT $P$G
PATH = C:\PCTOOLS;C:\;C:\DOS;C:\BATCH
SET TEMP=C:\WINDOWS\TEMP
VGADIM
C:\DOS\SHARE.EXE /L:500 /F:5100
C:\DPS_PAR\parinit /P=C:\DPS_PAR /l:e
C:\DPS_PAR\pardrv
\bin\MSCDEX.EXE /E:mscd000 /m:10 /l:e
config.sys
LASTDRIVE=Z
DOS=umb
FILES=40
BUFFERS=35
STACKS=9,256
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE 7168 M9 X=B000-B7FF
device=moustrak.sys /kc /y
SHELL=c:\COMMAND.COM /p /e:512
DEVICE=\DEV\SLCD.SYS /E:SONY_000 /B:340 /M:P /V /C
Tim
I'm really not much at diagnosing memory problems and I use NovellDos, which
is slightly different than MSDOS, ie, it has it's own set of problems<G>.
The best bet would be to note the error messages when a crash occurs and note
what you are doing and pass ask the question to ALL on the forum. If it's
mostly windows problems you might have to go to the Microsoft forum for a final
answer.
Good luck
TedB
!^NavFont01F0007MGHHH4D9383
Tim,
To diagnose memory conflicts, follow the instructions below.
-Brian
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is rebooted
without terminate and stay resident (TSR) programs nor device drivers that are
not absolutely necessary for the operation of the operating system and
computer. The Autodesk program should also be configured for VGA display if
possible, to rule out display driver conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy for this
trouble-shooting exercise and place these simplified system files on the
diskette. Or, you may edit the existing CONFIG.SYS and AUTOEXEC.BAT files
currently on the hard disk (make back-up copies first). Make sure you have a
bootable DOS floppy on hand, just in case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track down memory
conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.