Recently I used moderator Wengier's ROM-DOS boot disk to try whether The Legend of Sword and Fairy could run, and ran into some problems.
First I booted with moderator Wengier's original autoexec.bat and config.sys. After booting, there were 567KB of conventional memory left. To run The Legend of Sword and Fairy, conventional memory basically needs 570KB. Obviously, I had to modify the two files autoexec.bat and config.sys, deleting some programs that didn't need to be loaded into memory at startup, because I was mainly just testing whether The Legend of Sword and Fairy could run~~ I modified autoexec.bat and config.sys about four times in total.
I'll first post the original autoexec.bat and config.sys written by moderator Wengier for reference.
The original autoexec.bat and config.sys written by moderator Wengier
autoexec.bat:
@echo off
break on
lfnfor on
verify on
set dircmd=/OGN /4
set comspec=a:\command.com
path=a:\;..
mode con rate=32 delay=1
killer.exe
doskey.com
mscdex.exe /D:CDROM1 /K
ctmouse.exe /r3
mousclip.exe /m
set ramdrive=
xmsdsk 1024 /y
findramd>nul
if %ramdrive%#==# goto noram
copy command.com %ramdrive%\>nul
path=%ramdrive%\;%path%
set comspec=%ramdrive%\command.com
:noram
escape.exe
echo.
echo Now you're in ROM-DOS 7.10 prompt.
echo.
config.sys:
device=fdxxms.sys
device=emm386.exe quiet
device=vide-cdd.sys /d:CDROM1
device=cloaking.exe
shell=command.com /p /e:640
dos=high,umb
numlock=off
files=30
buffers=20,0
stacks=9,256
lastdrive=n
The first time, I added the LoadHigh command in autoexec.bat and added the DeviceHigh command in config.sys. After rebooting, conventional memory was still 567KB. Looks like those commands seem useless for ROM-DOS, so I tried a second round of modifications.
The second time I deleted some unnecessary programs from autoexec.bat and some driver programs from config.sys. I'll post them here for everyone to take a look.
autoexec.bat:
@echo off
break on
lfnfor on
verify on
set dircmd=/OGN /4
set comspec=a:\command.com
path=a:\;..
mode con rate=32 delay=1
mscdex.exe /D:CDROM1 /K
ctmouse.exe /r3
set ramdrive=
xmsdsk 1024 /y
findramd>nul
if %ramdrive%#==# goto noram
copy command.com %ramdrive%\>nul
path=%ramdrive%\;%path%
set comspec=%ramdrive%\command.com
:noram
echo.
echo Now you're in ROM-DOS 7.10 prompt.
echo.
config.sys:
device=fdxxms.sys
device=emm386.exe quiet
device=vide-cdd.sys /d:CDROM1
shell=command.com /p /e:640
dos=high,umb
numlock=off
files=30
buffers=20,0
stacks=9,256
lastdrive=n
After rebooting, dizzy.... it was actually even less than before, only about 548KB. I guessed it should be a problem in config.sys, so I added the line device=cloaking.exe back in. After rebooting, my guess was indeed right. Adding this line back made conventional memory 4KB more than the basic requirement for The Legend of Sword and Fairy. I immediately tried running it. After running it, it hung. The opening animation didn't come out. I guessed again that maybe memory still wasn't quite enough, so I deleted the two lines buffers=20,0 and stacks=9,256 in config..sys, and changed files=30 to 40. After rebooting, it was even worse. ROM-DOS said something about a stacks error, and then hung, so I added stacks=9,256 back. This time it booted normally, and conventional memory also increased to 584KB. I immediately tried running The Legend of Sword and Fairy, but it was the same as the previous run: it hung, and the opening animation wouldn't come out. Below are a few questions I'd like to ask. Please, experts familiar with ROM-DOS, help me see what's going on here~~
1. Moderator Wengier said ROM-DOS is very compatible with MS-DOS. In theory it should be able to run The Legend of Sword and Fairy on it, but I tried and it really can't run (though I don't know whether it's related to xmsdsk)
2. What exactly is ROM-DOS's cloaking.exe used for??
3. Does ROM-DOS have very strict requirements for stack(s)??
First I booted with moderator Wengier's original autoexec.bat and config.sys. After booting, there were 567KB of conventional memory left. To run The Legend of Sword and Fairy, conventional memory basically needs 570KB. Obviously, I had to modify the two files autoexec.bat and config.sys, deleting some programs that didn't need to be loaded into memory at startup, because I was mainly just testing whether The Legend of Sword and Fairy could run~~ I modified autoexec.bat and config.sys about four times in total.
I'll first post the original autoexec.bat and config.sys written by moderator Wengier for reference.
The original autoexec.bat and config.sys written by moderator Wengier
autoexec.bat:
@echo off
break on
lfnfor on
verify on
set dircmd=/OGN /4
set comspec=a:\command.com
path=a:\;..
mode con rate=32 delay=1
killer.exe
doskey.com
mscdex.exe /D:CDROM1 /K
ctmouse.exe /r3
mousclip.exe /m
set ramdrive=
xmsdsk 1024 /y
findramd>nul
if %ramdrive%#==# goto noram
copy command.com %ramdrive%\>nul
path=%ramdrive%\;%path%
set comspec=%ramdrive%\command.com
:noram
escape.exe
echo.
echo Now you're in ROM-DOS 7.10 prompt.
echo.
config.sys:
device=fdxxms.sys
device=emm386.exe quiet
device=vide-cdd.sys /d:CDROM1
device=cloaking.exe
shell=command.com /p /e:640
dos=high,umb
numlock=off
files=30
buffers=20,0
stacks=9,256
lastdrive=n
The first time, I added the LoadHigh command in autoexec.bat and added the DeviceHigh command in config.sys. After rebooting, conventional memory was still 567KB. Looks like those commands seem useless for ROM-DOS, so I tried a second round of modifications.
The second time I deleted some unnecessary programs from autoexec.bat and some driver programs from config.sys. I'll post them here for everyone to take a look.
autoexec.bat:
@echo off
break on
lfnfor on
verify on
set dircmd=/OGN /4
set comspec=a:\command.com
path=a:\;..
mode con rate=32 delay=1
mscdex.exe /D:CDROM1 /K
ctmouse.exe /r3
set ramdrive=
xmsdsk 1024 /y
findramd>nul
if %ramdrive%#==# goto noram
copy command.com %ramdrive%\>nul
path=%ramdrive%\;%path%
set comspec=%ramdrive%\command.com
:noram
echo.
echo Now you're in ROM-DOS 7.10 prompt.
echo.
config.sys:
device=fdxxms.sys
device=emm386.exe quiet
device=vide-cdd.sys /d:CDROM1
shell=command.com /p /e:640
dos=high,umb
numlock=off
files=30
buffers=20,0
stacks=9,256
lastdrive=n
After rebooting, dizzy.... it was actually even less than before, only about 548KB. I guessed it should be a problem in config.sys, so I added the line device=cloaking.exe back in. After rebooting, my guess was indeed right. Adding this line back made conventional memory 4KB more than the basic requirement for The Legend of Sword and Fairy. I immediately tried running it. After running it, it hung. The opening animation didn't come out. I guessed again that maybe memory still wasn't quite enough, so I deleted the two lines buffers=20,0 and stacks=9,256 in config..sys, and changed files=30 to 40. After rebooting, it was even worse. ROM-DOS said something about a stacks error, and then hung, so I added stacks=9,256 back. This time it booted normally, and conventional memory also increased to 584KB. I immediately tried running The Legend of Sword and Fairy, but it was the same as the previous run: it hung, and the opening animation wouldn't come out. Below are a few questions I'd like to ask. Please, experts familiar with ROM-DOS, help me see what's going on here~~
1. Moderator Wengier said ROM-DOS is very compatible with MS-DOS. In theory it should be able to run The Legend of Sword and Fairy on it, but I tried and it really can't run (though I don't know whether it's related to xmsdsk)
2. What exactly is ROM-DOS's cloaking.exe used for??
3. Does ROM-DOS have very strict requirements for stack(s)??
MSN:tiqit2@hotmail.com



