China DOS Union

This SHSUCDX.EXE file has a lot of problems:
1: If there is no system installed on drive C, then it cannot be loaded no matter what.
2: If you use lh SHSUCDX.EXE /d:cd001, although it can load, under the mem /c command this file cannot be found.
You can only use SHSUCDX.EXE /d:cd001.
3: An image file made with this file can only load if the image file is run by itself. If the image file is added into
an ISO file, then it still cannot always load. It seems that extract has to be run first in autoexec.bat before it can load.
It's simply baffling.
I replaced it with a 16k SHSUCDX.EXE, and then none of the above problems existed.

Also, the xzl in the super universal MS-DOS 7.10 boot disk always has problems too. Sometimes it can run normally, sometimes it's like
an old ox pulling a broken cart, and I thought it had hung.

All of the above problems were found in testing under VPC5.2; in a real environment it is unknown!

Testing in a virtual machine is fundamentally very hard to use to explain problems. When I was making boot disks I suffered a lot because of virtual machines too.... a lot of things that have no problem on real machines often behave inexplicably in virtual machines; now I always test with both real machines and virtual machines....

Mainly because there are still quite a few things in the ISO file I made that are not yet perfected, and I don't want to burn it to CD-ROM for testing in a real environment. So I can only use a virtual machine to test.
Anything that cannot run in the virtual machine I replace across the board.
I use the virtual machine as the standard.

Use a CDRW...........
If you use the virtual machine as the standard you'll end up badly off. I've tried it twice where the virtual machine passed but the real machine failed.......... Hehe

The virtual machine passes but the real machine fails? There's actually such a thing? This time it really is "nothing but darkness ahead."

"The virtual machine passes but the real machine fails" is true indeed... I've seen it too...

The one above is a BUG in Shsucdx 2.0. With this latest Shsucdx 2.1 there should be no problem:
http://users.tpg.com.au/jmhood/shsucdx/shcdx21.zip

Many thanks, Mr. Moderator. This file is very easy to use, can also load into upper memory, and only takes up 7k of space.

My boot disk does have some problems when tested in VPC52. But they are not the problems the OP mentioned. The main one is that using EMM386 together with Tianhui in VPC5.2 will show a white screen. But using UMBPCI together with Tianhui does not have this problem. The main reason is still a BUG in VPC5.2 itself.
The phenomena 1 and 3 mentioned by the OP cannot exist. Because I already tested them in VPC before, and the situations you mentioned would not appear. As for the second phenomenon: SHSUCDX2.0 cannot use the LH command, otherwise UMB confusion will occur. Because SHSUCDX will automatically load into UMB. Using LH again is unnecessary. I already said this long ago in a related post. So my boot disk does not use LH at all.
About SHSUCDX, let me say this. Version 2.0 does indeed have some BUGs, while 1.4b is very mature. It's just that it takes up 11K of memory. In version 2.0 the author reduced the memory usage to 7K, but because of that some problems were produced. As for how compatible the newly released version 2.1 is, that still needs verification. So in terms of compatibility, 1.4b is still the best.

Maybe my title caused you some misunderstanding. I extracted SHSUCDX.EXE, io.sys, command.com, msdos and some other files separately from your image file, then added Wengier's super universal MS-DOS 7.10 to make an image file myself. That is to say, aside from a few batch files and config.sys, not a single file in the image file I made was added from outside those two image files. These three phenomena I mentioned appeared repeatedly on my machine. I even specifically tested the first phenomenon just now, and it really does exist. Of course, it is also possible that it is a problem with my VPC5.2.

I just tried starting with UMBPCI (that is the third item in the menu), and this was the result


Not sure whether it's a problem with my VPC.