#Config help?
11 messages in this thread
I realize this may not be the place to post a question about AUTOEXEC.BAT and
CONFIG.SYS files, but since I am using 3-D Studio, I thought maybe someone
could offer advice, I don't know if this looks right. Here is what they look
like, if anyone would like to take a stab at what may be wrong with them, let
me know. Thanks.
I have an IBM clone, 486DX 33 with 500 meg HD and 32 meg RAM
AUTOEXEC.BAT=
C:\QEMM\LOADHI /R:2 C:\SB16\DRV\MSCDEX.EXE /D:MSCD001 /V /M:15
C:\QEMM\LOADHI /R:2 C:\WINDOWS\SMARTDRV.EXE
C:\NAV\NAV C:\
PATH=C:\;C:\WINDOWS;C:\WIN;C:\QEMM
set mouse=C:\Mouse
c:\qemm\loadhi /r:1 /lo C:\Mouse\mouse.exe
C:\QEMM\LOADHI /R:2 PANEL
SET SOUND=C:\SB16
SET BLASTER=A220 I5 D1 H5 P330 T6
REM ** By Creative ** rem C:\SB16\DRV\MSCDEX.EXE /D:MSCD001 /V /M:15
C:\SB16\SB16SET /M:220 /VOC:220 /CD:220 /MIDI:220 /LINE:220 /TREBLE:0
C:\SB16\SBCONFIG.EXE /S
@ECHO OFF
PROMPT $p$g
PATH=C:\;C:\QEMM;C:\DOS
PATH=C:\;C:\NAV;%PATH%
PATH C:\NU;%PATH%
SET SYMANTEC=C:\SYMANTEC
SET NU=C:\NU
SET TEMP=C:\windows\temp
REM C:\UNIVESA
SET RCPADI=C:\3DS3\DRIVERS\RCPVESA.EXP
rem SET RHPADI=C:\windows\system\deskjetc.drv
debug < fixcom.deb > nul
rem C:\DOS\DOSSHELL
rem c:\windows\win
rem SET COMPSPEC=C:\DOS\COMMAND.COM
C:\NU\NDD C:/Q
C:\NU\IMAGE C:
scrnsave
SET SCREENGRAB=YES
MENU
——————————————————————————-
——————————–
CONFIG.SYS=
DEVICE=C:\QEMM\DOSDATA.SYS
DEVICE=C:\QEMM\QEMM386.SYS RAM SH:N ST:M R:2
DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=8592 C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
FILES=60
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=14192 C:\SB16\DRV\SBCD.SYS /P:220 /S:A0
/D:MSCD001
DEVICE=C:\QEMM\LOADHI.SYS /R:1 /SIZE=14032 C:\DOS\SETVER.EXE
DOS=HIGH
REM ** FILES=30
REM By NAV: DEVICE = C:\NAV\NAVTSR.EXE
REM By NAV: DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=142368 C:\NAV\NAVTSR.EXE
STACKS=0,0
SHELL=C:\QEMM\LOADHI.COM /R:2 C:\COMMAND.COM C:\ /P
rem (advised by 3ds)SHELL=C:\QEMM\LOADHI.COM /R:2 C:\COMMAND.COM C:\ /E:1024 /P
buffers=30
rem DEVICE=C:\SBCD\SBCD.SYS /D:MSCD001 /P:250 /T:2 /S:A0
rem DEVICE=C:\VIP\EIMPCS.SYS
James,
What's the problem? You've certainly got a lot of stuff crammed in those files.
<g>
-JE
John Hi
I didn't know if there would be a problem, except that I seem to be having
a memory conflict when trying to view a few flics from within 3-D Studio, was
wondering if these conflicts would be visible in my files.
James,
>> I seem to be having a memory conflict when trying to view a few flics. <<
That sounds more like a configuration problem with your video display.
Try typing 3DS VIBCFG and check out how your FLIC drivers are set up. Then
trying running the FLC's in VIBRANT display mode. Its more than likely
something in this setup.
-JE
John Hi
>>Try typing 3DS VIBCFG and check out how your FLIC drivers are set up.<<
I typed it and this is the message I received:
Phar Lap err 74: can't use -REALBREAK under this version of DPMI
What do I need to do to fix this? Thank you.
James,
>> Phar Lap err 74: can't use -REALBREAK under this version of DPMI
You have a line in your config.sys file which reads:
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=8592 C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
This looks to me like a swap file for Windows that is using a DPMI form of
memory management which is incompatible with 3DS.
The thing to do is make a backup of your autoexec.bat and config.sys and then
go through and delete and lines which are not directly related to 3DS. For now
however rem out that line and see if it will work. Obviously you'll have
problems with Windows if you do, so you may want to think about how to
structure your auto/config files so that both will run.
Personally I would set up one set for Windows and one for 3DS but then I have
multiple systems networked so I can be in Windows on one system and 3DS on
another as needed.
-JE
Thanks John for the advice. It seems easier to just stay with going over to
Animator Pro to view the Flics I can't in 3-D Studio, so I think I'll do that
🙂
>> It seems easier to just stay with going over to Animator Pro. <<
That's what I do, mostly because you can load the thing in memory instead of
run it off the H.D.
-JE
James, advice from a wise man once on this forum was to simply ditch the
QDPMI.SYS line. Worked for me. JKJ
Thank you JKJ, I will try ditching that file.
>>will try ditching that file…
Er, try remarking out the line in the CONFIG.SYS instead.