China DOS Union

: :o When saying sometimes, it refers to on the computers of some motherboards.
Why is that?
Content of MSDOS.sys:
;SPDOSHDD
[Options]
AutoScan=0
DisableLog=1
SystemReg=0
Logo=0
DBLSpace=0
DRVSpace=0
DoubleBuffer=0
BootGUI=0
;BootGUI=1
;BootMulti=1
BootKeys=1
BootDelay=0

Content of Config.sys
[menu]
menuitem=GSB,GHOST Script Batch Menu
menudefault=GSB,0
menucolor=2,0
[GSB]
device=\dos\sys\himem.sys /testmem:off
;device=\dos\sys\ifshlp.sys
device=\dos\sys\emm386.exe noems
devicehigh=\dos\sys\qdboot.sys
devicehigh=\dos\sys\qdma.sys /F /L /X
devicehigh=\dos\sys\qcdrom.sys /L /UF
devicehigh=\dos\sys\qcache.sys

[COMMON]
devicehigh=\dos\sys\vide-cdd.sys /D:IDE-CD
devicehigh=\dos\sys\ramdrive.sys 16192 /E
dos=umb
files=70
buffers=30,0
stacks=9,256
lastdrive=z
shell=command.com /f

And when using the configuration files msdos.sys and config.sys for one-click GHOST to start, Autoexec.bat still cannot be executed, while the one-click GHOST can.
Could you please explain it, moderator?

Because qdboot.sys, qdma.sys, qcache.sys are incompatible with some motherboards.

Compromise configuration:

menuitem=GSB2,Boot with QDMA (GHOST Script Batch Menu)

menuitem=GSB,(GHOST Script Batch Menu)

menudefault=GSB2,5

menucolor=2,0



device=\dos\sys\himem.sys /testmem:off

;device=\dos\sys\ifshlp.sys

device=\dos\sys\emm386.exe noems

devicehigh=\dos\sys\qcdrom.sys  /D:IDE-CD /L /UF



include GSB

devicehigh=\dos\sys\qdboot.sys

devicehigh=\dos\sys\qdma.sys /F /L /X

devicehigh=\dos\sys\qcache.sys





devicehigh=\dos\sys\ramdrive.sys 16192 /E

dos=umb

files=40

buffers=30,0

stacks=9,256

lastdrive=z

shell=command.com /f

Remarks: files= has no special use, 30~40 is enough. You can choose either vide-cdd.sys or qcdrom.sys. The above code has removed vide-cdd.sys.

[ Last edited by fastslz on 2006-10-11 at 11:49 ]

I didn't say qcdrom.sys ^_^
It's qdboot.sys, qdma.sys, qcache.sys

Let me rephrase the problem: Autoexec.bat can be executed when some computers start up, but not on others. How to solve it?

Post the Autoexec.bat again

@ECHO OFF
CLS
SET EXPAND=YES
SET DIRCMD=/O:N
PROMPT $p$g
SET LglDrv=27 * 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15
SET LglDrv=%LglDrv% O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C
PATH DOS;DOS\SYS;
CALL Setramd.bat %LglDrv%>NUL

:END
DOS\SPDOS.BAT

In fact, the reason there is shell=command.com /f in config.sys
is because there was an error in call Setramd.bat
But on a computer where Autoexec.bat cannot be executed (it will automatically fall back to DOS), manually entering Autoexec.bat
can run.
I have no way...

I modified it and need to restart for a test.

1: Missing CD drive letter
2: Whether Setramd.bat is complete (findramd.exe is also necessary)
As for shell=command.com /f, the recommended parameter is shell=command.com /e:640 /p /f
@ECHO OFF
CLS
SET EXPAND=YES
SET DIRCMD=/O:N
PROMPT $p$g
SET LglDrv=27 * 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15
SET LglDrv=%LglDrv% O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C
PATH=.\DOS;.\DOS\SYS;%RAMD%:\
CALL Setramd.bat %LglDrv%
COPY COMMAND.COM %RAMD%:\ >NUL
SET COMSPEC=%RAMD%:\COMMAND.COM
SHCDX33A.COM /D:?IDE-CD /C

SHCDX33A.COM download addresshttp://johnson.tmfc.net/dos/

[ Last edited by fastslz on 2006-10-11 at 12:40 ]

All necessary programs include findramd, shsucdx, setramd from Jiangmin's DOS antivirus disk. It is guaranteed to be okay.

Oh, maybe you didn't understand: But on computers where Autoexec.bat cannot be executed (it will automatically return to DOS), manually entering Autoexec.bat can run and everything is normal. It just needs to be entered manually once.

Oh, the autoexec.bat isn't pasted completely? Maybe it's because of the command.com /f parameter. The /f means ignoring parameters. For example, when if exist %cdrom%:\*.* ....., if there's no CD in the drive, it executes by ignoring the parameter and automatically drops to DOS. So with the /f parameter, batch processing parameters are relatively stricter, and any unstable parameter will automatically drop to DOS. To verify if this is the reason, check the difference between having no CD and having a CD in the drive.

It is not excluded that you use if exist X:\*.gho and there is no X drive. You don't post the complete autoexec.bat, so it can only be guessed.

Thank You! Solved
Initially judged that ramdrive.sys has issues on some computers.
Because during step tracing, an error occurred when copying files, and when... retry, fail was selected and f was pressed, it returned to DOS.
Replaced with xmsdsk, hehe, solved. Thank goodness!

If you are relatively curious, you can enter my network disk to download, the "Software Release" directory has spdos0.25final.rar
http://free5.ys168.com/?nhccrgd

spdos.rar is exactly one of the problematic series versions.

Hehe, a trouble caused by the /f parameter of command.com!
In addition, the way you express the virtual path \dos\ is not stable enough under pure DOS!

Although I haven't tested your spdos, I found a problem with gsldr. I'm sure that if you modified that gsldr, it will most likely not boot on an NTFS formatted drive.

[ Last edited by fastslz on 2006-10-12 at 12:03 ]