#3DS AND SUPERSTORE
10 messages in this thread
Hi folks. a friend of mine purchased 3DS (V.2), and is having some
problems with it. He uses SUSPERSTORE on-the-file compression on his
system, and I told him this may be the problem. He also has some video
capture and output cards, as well as a sound card, which may be
contributing to the problem. Essentially, the program takes a long time
to boot, the mouse is quirky & jumpy, and I don't think he can even do
anything.
Under the assumption that he CAN run 3DS with SUPERSTORE, plus the
additional hardware, I told him I'd post his AUTOEXEC & CONFIG files
here, in hopes that he just needs to alter it, or at least make a
custom set for 3DS. He runs an old Gateway DX2-50, with 4 megs of ram.
Below are the boot files from his virtual "C" drive, and from his "D"
drive (true C). Thanks for any help with this.
VIRTUAL "C"
oadhigh C:\DOS\SHARE.EXE /l:500 /f:5100
echo off
PROMPT $p$g
c:\windows\smartdrv.exe
PATH= C:\DOS;c:\windows;c:\util;c:\nu;c:\ndw;c:\aldus;c:\pm4;c:\;C:\ADDSTOR;c:\ mouse
*lh MOUSE CENHANCE
lh c:\mouse\mouse.com
rem ********************************************************
rem loadhigh c:\ndw\smartcan /on /skiphigh
SET TEMP=C:\windows\temp
set sound=c:\sb
set blaster=a220 i7 d1 t3
c:\ndw\image
DEVICE=C:\HIMEM.SYS
DEVICE=C:\EMM386.EXE ram auto
DOS=HIGH,UMB
DEVICEhigh=\SSTORDRV.SYS
DEVICEhigh=\DEVSWAP.COM
REM DEVICEhigh=C:\NDW\NAV&.SYS /B
STACKS=9,256
FCBS=20,0
FILES=40
BUFFERS=32
"D" DRIVE (TRUE C)
oadhigh C:\DOS\SHARE.EXE /l:500 /f:5100
echo off
PROMPT $p$g
c:\windows\smartdrv.exe
PATH= C:\DOS;c:\windows;c:\util;c:\nu;c:\ndw;c:\aldus;c:\pm4;c:\;C:\ADDSTO
R;c:\mouse
*lh MOUSE CENHANCE
lh c:\mouse\mouse.com
rem ********************************************************
rem loadhigh c:\ndw\smartcan /on /skiphigh
SET TEMP=C:\windows\temp
set sound=c:\sb
set blaster=a220 i7 d1 t3
c:\ndw\image
DEVICE=C:\HIMEM.SYS
DEVICE=C:\EMM386.EXE ram auto
DOS=HIGH,UMB
DEVICEhigh=\SSTORDRV.SYS
DEVICEhigh=\DEVSWAP.COM
REM DEVICEhigh=C:\NDW\NAV&.SYS /B
STACKS=9,256
FCBS=20,0
FILES=40
BUFFERS=32
Apparently, CIM didn't like my message. Let's try that again.
VIRTUAL "C"
oadhigh C:\DOS\SHARE.EXE /l:500 /f:5100
echo off
PROMPT $p$g
c:\windows\smartdrv.exe
PATH= C:\DOS;c:\windows;c:\util;c:\nu;c:\ndw;c:\aldus;c:\pm4;c:\
;C:\ADDSTOR;c:\mouse (Note: I put this here to fit this message)
*lh MOUSE CENHANCE
lh c:\mouse\mouse.com
rem ********************************************************
rem loadhigh c:\ndw\smartcan /on /skiphigh
SET TEMP=C:\windows\temp
set sound=c:\sb
set blaster=a220 i7 d1 t3
c:\ndw\image
DEVICE=C:\HIMEM.SYS
DEVICE=C:\EMM386.EXE ram auto
DOS=HIGH,UMB
DEVICEhigh=\SSTORDRV.SYS
DEVICEhigh=\DEVSWAP.COM
REM DEVICEhigh=C:\NDW\NAV&.SYS /B
STACKS=9,256
FCBS=20,0
FILES=40
BUFFERS=32
(Continued next message)
And here's the "D" DRIVE (TRUE C). [Note:CIM keeps dropping the first
two letters from the previous AUTOEXEC. They are
]
D DRIVE (TRUE C)
echo off
PROMPT $p$g
c:\windows\smartdrv.exe
PATH= C:\DOS;c:\windows;c:\util;c:\nu;c:\wp51;c:\ndw;c:\aldus;c:\pm4;c:\
;C:\ADDSTOR;c:\mouse (Note:I put this here to fit this message)
*lh MOUSE CENHANCE
lh c:\mouse\mouse.com
rem ********************************************************
rem loadhigh c:\ndw\smartcan /on /skiphigh
SET TEMP=C:\windows\temp
set sound=c:\sb
set blaster=a220 i7 d1 t3
c:\ndw\image
chirp 3
DEVICE=C:\HIMEM.SYS
DEVICE=C:\EMM386.EXE ram auto
DOS=HIGH,UMB
DEVICEhigh=\SSTORDRV.SYS
DEVICEhigh=\DEVSWAP.COM
REM DEVICEhigh=C:\NDW\NAV&.SYS /B
STACKS=9,256
FCBS=20,0
FILES=40
BUFFERS=32
Again, thaks for any help with all this.
I just want to add that CIM really sucks.
Phil,
<< CIM isn't enjoyable..>>
you need another front end to CIS. some forum members
have favorites for easy navigating, downloading and viewing
on your $time$, some have steeper learning curves. I use
WInCim which isn't the most economical but allows me to
be live while reading.
jonas[adesk]
Yeah, I was just getting a little annoyed that CIM kept distorting the
message I was making, apparently because I was importing text from the
different AUTOEXEC, and CONFIG files.
Phil,
<< r2 not quite right… >>
The first thing that popped out at me was that you said he had 4 meg
of ram total. 3ds r2 requires 4 meg for itself. It looks like you
are taking a meg for dos, then you're giving some away for
smartdrive. You are not using a robust memory manager, like qemm.
With video cards, sound cards, etc. since they use use memory mapped
io, you must exclude regions of memory which map to specific
addresses. 3DS will try to take over all of the memory it can find.
Managers like qemm allow you to exclude a section which then protects
it from 3ds.
jonas[adesk]
Can you suggest some modifications to his boot files, that may be of
help. I guess he'll just have to deal with multiple boot files in order to roll
with 3DS. Thanks.
Phil,
Like Jonas said, 3DS wants more than 4 megs, especially as SMARTDRV itself, (as
installed), is taking 1 meg.
I've run 3DS r2 & r3 under both SuperStor and Stacker with no problems
whatsoever.
John
Can you suggest an AUTOEXEC, and CONFIG file that he may use in his
system when he runs 3DS? Also, are the changes made to his virtual "C" drive or
his "D" drive, or both? Thanks.