China DOS Union

The following is the speech of aruner on 2003-11-5 18:49:27:
Or you can also start normally by using DeviceHigh for other devices without loading DUSE

This is a problem with DUSE itself. You can simply delete DUSE directly.

Hello Brother wengier, I downloaded your latest boot disk file and made a boot disk using the floppy disk from the Netac dual-boot USB flash drive. After booting (with another Netac 64M dual-boot USB flash drive inserted), choosing options 2 and 4 causes a system crash (when displaying MS-DOS V7.10), with no response. Options 1, 5, and 6 can boot normally. When choosing option 3 (which I need most), it says there are errors in lines 50-53 and 59-60 of the config file, and also reports errors with IFSHLP.sys file and C:\windows\command.com file. Then it shows the "A>" symbol, and I can't perform other operations. Entering the C drive letter or the dir command both prompt "e.g., C:\windows\command.com file error". What should I do? Looking forward to your answer, thank you very much!!!

Hello, administrator!
I have downloaded the new version of the 710 boot disk. May I replace the simplified page number table with the traditional Chinese page number table? Because my file name is in traditional Chinese,
And I extremely need the xcopy command. Can you remove some unnecessary.com files in the cab package and replace them with XCOPY.com? Or do I need to import several.com files? Does this need to modify some files?
Can you provide the download of the traditional Chinese page number table?
Thank you!

Ask a question.
After I use XZL, when I do Dir, except for the last few lines, the lines above are all unreadable ====
It is suggested to add Pinyin input (don't tell me to use the area code to input Chinese characters -_-!)
The XZL Pinyin is very small (since XZL is already used, why not add XZLpy?)

Come on!

There is a problem with the 7.10 super boot disk.

For the SIS630 board, it stops at the LOGO. Removing LOGO.SYS can make it enter. Both the 630 board and the 845PE board stop at USB when selecting items 3 and 4. Manually loading USB can find the active hard disk of 2.0 (showing the hard disk name and model), but there is no drive letter appearing, it seems there is a problem. The last sentence of text is not understandable "treiber nicht ins...". Please give advice on how to overcome these problems? In addition, I want to know how to operate under DOS to use the active hard disk of USB2.0. Thanks!

Administrator:
Why can't the boot disk made with winimage under XP boot the system? It always prompts "remove disks or other media, press any key to restart". But when making it with makeboot under DOS, it can boot. However, it freezes when loading the USB devices in the 2nd, 3rd, and 4th items. Why is that?

I saw that there is a boot directory in the file list of the bootable disk, and there is probably a stage2 file inside. If we use grub.exe, we can avoid using stage2. I think there should be tools to compress grub.exe. In this way, it may occupy less space. Of course, it is assumed here that the approach of entering DOS first and then using grub.exe will not affect the entire system.

The following is a quote from Budian on 2003-11-22 4:39:25:
I saw that there is a boot directory in the file list of the boot disk, and there is probably a stage2 file in it. If you use grub.exe, you can avoid using stage2. I think there should be a tool to compress grub.exe. In this way, it may occupy less space. Of course, it is assumed here that the practice of entering DOS first and then using grub.exe will not affect the entire system.

Yes, GRUB.EXE can be compressed to more than 50KB with UPX compression (I don't know if there is a way to compress the stage2 file), but it has several disadvantages:

1: Once you enter GRUB for DOS from DOS, you can't return to DOS and continue booting. And if you use GRUB.EXE to reload the boot disk and use the boot command to start, it will cause a loop (that is, start from the boot disk again, and GRUB.EXE usually can't reload itself repeatedly, otherwise it will cause an error or crash. I don't know if this counts as a bug?);

2: If you want to add menu items in CONFIG.SYS (at least two lines, namely booting from the hard disk and from the CD-ROM) to load, on the one hand, it may cause too many and messy options. More importantly, GRUB for DOS has this bug: it can't use the config-file option in CONFIG.SYS to specify the corresponding menu.lst file to be loaded, because the contents of the two menu.lst files needed are different, and when loading GRUB.EXE in CONFIG.SYS, it can't be done (because of that lowercase letter reason. I don't know if GRUB.EXE can be modified so that a capital letter option can also achieve the function of --config-file, such as -C);

3: If you want to use a self-built menu to call GRUB.EXE to select the project to be started during or after the operation of AUTOEXEC.BAT, it is also impossible, because at this time programs like EMM386 may have been loaded in CONFIG.SYS, but GRUB.EXE can't run in this environment;

4: If you want to load GRUB.EXE before DOS starts, it is also impossible unless there is a special boot sector file for guiding GRUB.EXE to call GRUB.EXE (just like the stage1 file for guiding stage2 in GNU GRUB, or like the VLOADER.BIN file for guiding VMEMDSK.BIN file in vfloppy).

Because of these reasons, GRUB for DOS currently seems to be unable to be actually applied to the DOS boot disk for selecting whether to boot from a floppy disk, hard disk or CD-ROM, but GNU GRUB can.

I still don't quite understand the boot method of this bootable disk. I just said it casually just now.

In addition, regarding the issue of uppercase letters in the config you mentioned, I also knew about this problem. At that time, I didn't think someone would use this function, so I didn't pay attention to it. After hearing what you said, I think it is very necessary to support it.

Well, after we finish this grub_test this time, we plan to support the uppercase --CONFIG-FILE at the same time.

I found after using it that when loading the USB driver and booting the USB CD-ROM to install the system, there was insufficient memory and it couldn't be installed. I saw that the memory was only 510K. What should I do? Please help everyone.

The latest version (2003.10.12) of "Super Universal MS-DOS 7.10 Boot Disk" cannot boot the Netac OnlyDisk USB flash drive, while the Super Universal MS-DOS 7.10 Boot Disk from 2003.10.8 can boot the Netac OnlyDisk USB flash drive smoothly.
???

The following is a quote from Goldream at 12:05:01 on November 18, 2003:
Ask a question
After I use the pocket dragon, when I do Dir, I can't see anything clearly except the last few lines ====
It is suggested to add Pinyin input (don't tell me to use the locale to input Chinese characters -_-!)
The xzl Pinyin is very small (since xzl has been used, why not add xzlpy?)

Agreed!

The compatibility of the general MS-DOS 7.10 boot disk needs to be improved!
1. The MAXBLAST and POWERMAX (hard disk maintenance tools provided by Maxtor's original factory, with a graphical interface and support for PS/2 mice. Personally, I think it is better than the general version of DM and also supports hard disks of other manufacturers) could be used after the previous (April 24th) boot disk was started, but the current (October 12th) boot disk is completely not working.
2. In addition, I don't know if the problem of not accelerating the installation when installing Win2K and WinXP after booting to DOS and then loading SMARTDRV has been solved! (For related problems, see previous posts).
There are still improvements in this time's boot disk (October 12th): The previous (April 24th) boot disk had poor support for USB flash drives (ON_DATA 32MB), and it would crash when loading the USB driver, but now it doesn't crash. Using "FINDCD /S" closely next to the CD-ROM added two more drive letters (my computer is connected to two USB devices, one USB ADSL MODEN, and one ON_DATA USB 32MB flash drive). I don't know if the other two drive letters are provided for USB devices, but neither can be accessed.
Machine configuration: KT133A (EPOX) + Athlon850 MHz + 256MB SDRAM + 40GB (5400) + 52X CD-ROM + 24x10x40x CD-RW (LITE-ON);
OS: MSDOS710 + Win2000 + RedHat Linux 9.0.

My Newsmy USB 2.0 mobile hard disk has never started successfully. It often freezes during loading. Motherboard: SL-85DR3-C.