中国DOS联盟

Excuse me, everyone. Who has the COMMAND.HLP file of ROM-DOS? It is sometimes needed when using ROM-DOS. Please help.

Thank you!

I originally searched for a long time and didn't find it. Finally, I only found the COMMAND.HLP file in an old version of ROM-DOS, but it's not compatible with the 7.10 version.

The size of command.com in Rom-dos 7.1 is only 44K. It is very suitable to replace the Command.com in Ms-dos 7.1, and it has good compatibility, only occupying 4K memory, and all ms-dos programs can run normally. However, there is one problem, that is, it is necessary to add the line shell=command.com /p in CONFIG.SYS, otherwise the system cannot automatically load COMMAND.COM. I wonder if you all have any solutions.

The COMMAND.COM of MS-DOS cannot be directly compressed, but it can be used after being compressed into a ZIP or CAB package. Just expand it to the memory disk in CONFIG.SYS and it can be used. I have tried it and it can be used like this, but there are still one or two problems. Also, I found that after replacing the COMMAND.COM of MS-DOS with the COMMAND.COM of ROM-DOS, long filenames cannot be used normally under DOSLFN.

It doesn't work. Mine can be used normally. You can have a try.

My Chinese boot disk 144v030330:
Open attachment

I have tested and found that long filenames can only be displayed if DOSLFN is loaded before COMMAND.COM in ROM-DOS is loaded. For example:

:
INSTALLHIGH=DOSLFN.COM
SHELL=COMMAND.ROM /P (My system's C:\COMMAND.ROM is COMMAND.COM of ROM-DOS 7.10, to distinguish it from COMMAND.COM of MS-DOS 7.10.

However, I found in actual use that after using COMMAND.COM of ROM-DOS 7.10, commands like DIR are obviously slower when displaying long filenames compared with COMMAND.COM of MS-DOS 7.10, and programs also run slower.

Also, I want to ask what the R.BAT file in your DOS boot disk is for? If you really want to boot the Win9x interface from the MS-DOS 7.10 boot disk, you just need to set winbootdir=. in MSDOS.SYS. In this way, no matter where Win9x is installed (whether it's C:\WINDOWS or D:\WIN98, etc.), after booting with the DOS boot disk, as long as you enter the Win9x folder and type the WIN command, you can enter the Win9x interface (and this setting will not affect the boot of the DOS boot disk at all. My latest MS-DOS 7.10 boot disk is set this way). For example:

A:\>D:
D:\>CD \WIN98
D:\WIN98>WIN
You can start the Win98 GUI in the D:\WIN98 folder.

Note: The permanent download address of my latest MS-DOS 7.10 boot disk (currently the 2003-3-27 version) is:
http://newdos.yginfo.net/dosware/mdos71bd.zip

Also, the "ATTRIB -S -H -R -A xxx" in the R.BAT file is actually not necessary to be so complicated. You can directly use "ATTRIB , xxx" or "ATTRIB -SHRA xxx".

The following is the speech of lydong on 2003-3-31 23:33:05:
It won't. Mine can be used normally, you can give it a try.

My Chinese boot disk 144v030330:
Open the attachment

Strange........
Why is COMMAND.COM only 44K??
And what is ASCII.COM? Where did MORE.EXE, CHOICE.COM and XCOPY.EXE come from?

That COMMAND.COM is naturally from ROM-DOS 7.10, and ASCII.COM I saw was downloaded from newdos.de, and XCOPY is RXCOPY 1.1 from FreeDOS.

o......
Got it!!
Then what is the use of ASCII.COM?

Thanks to wengier for the guidance. Using your method to switch between DOS and Win9x interfaces is really a bit more convenient. ASCII.COM is an ASCII code program, which is actually useless. I removed it.

MS-DOS 7.10 has the best compatibility with Windows, as it can boot both Windows 2.x, 3.x and Windows 9x. However, I don't know if MS-DOS 7.10 can directly boot Windows ME (it's also okay to first use commands like DOSVER or SETVER to set the DOS version number to 8.0 and then run it). Has anyone tried it?