China DOS Union

When was VPC 5.2 released? I'm currently using version 5.1.

My boot disk works fine in VPC 5.1, but the EMM386 settings don't have as good an effect as UMBPCI.

I'll also say a few words about virtual machines. Don't trust them too much because after all, it's not a real environment, and there are bugs in itself, often giving false positives. The so-called compatibility is not to be compatible with the virtual machine. Instead, it's to be compatible with the real system. Because the virtual machine itself has compatibility issues, because its hardware devices are virtual (so there are many errors). If you rely on them, then many good software won't work. For example, HWINFO can't run under VPC, but it can run in VMware. And HD-COPY can't run in VMware but can run in VPC. But in the real environment, these can all run. Also, in the WENGIER disk, CLOAKIN + MSCDEX is much better than Microsoft's MSCDEX, but CLOAKING can't run in VPC. If you want full compatibility with the virtual machine, then you can only use those old and memory-consuming tools from Microsoft.

It's precisely because VPC often has problems that it has wasted me a lot of time, often making me mistakenly think it's the problem with the boot disk.

VPC5.2 has been out for more than three months, and the Chinese version has been out for a long time.

The latest version of MVW is the 4.0 Chinese version.

What the brother said makes some sense. Virtual machines do have certain drawbacks~~~

But I wonder if the brother thinks that the test environment of virtual machines is more neutral? It is not limited to a certain type of machine, but adopts a general-purpose design, that is to say, its compatibility is better than that of real machines to some extent, otherwise it would lose the meaning of virtualization~~~ For example, some Linux systems have compatibility problems on some machines, but can be installed smoothly in virtual machines, which just shows that its compatibility is stronger~~~

What the brother said about HWINFO indeed cannot be used in virtual machines. In fact, it's not just it. Most system testing software cannot run in virtual machines because they require a fixed test type. All tests are based on the database carried by the software, and virtual machines cannot make them locate specific hardware data, so deadlocks or overflows and other failures will occur, which is inevitable~~~


In addition, the "CLOAKIN + MSCDEX" problem mentioned by the brother, I think this is completely understandable. In the eyes of programmers, the quality of software is the simplicity of its algorithm and the optimization of code. In our eyes, the quality of software is its occupation of system resources and functions. When it comes to users, the quality of software becomes the problem of stability and compatibility. They don't care how it is made or how powerful the function is~~~ So the advantages of "CLOAKIN + MSCDEX" are recognized by us all, but from the feedback of so many people, it does have compatibility problems with some machines!

Here I want to give an opinion on a sentence by WENGIER, and I hope WENGIER doesn't mind~~~ WENGIER said in a reply that "you can call the motherboard manufacturer to modify their bugs" (something like that). I personally think such words should not be said. The production of hardware cannot change because of our wishes (unless market demand). With our ability, we can only try to be compatible with hardware, not let hardware be compatible with our software. Moreover, from the perspective of implementation, software changes are simpler and faster than hardware. So if we can't solve the problem, we should admit it and face it, not escape it~~~

This is just my personal view. I just hope to learn technology with everyone, and there is no other meaning. If there is anything wrong, please correct me. Thank you~~~

After I made it into a CD, the overall feeling is very good, but it seems that Norton's hard disk scan is not easy to use; selecting the fourth item usp in the interface also seems unable to drive, maybe I haven't mastered it yet?

Hehe~ I've always been using vpc52. Actually, there are also problems, just relatively fewer.

The following is the speech of qian_012 on 2003-6-28 14:26:52:
After I made it into a CD, I generally felt very good, but it seems that the Norton hard disk scan is not easy to use; selecting the fourth item usp in the interface also seems unable to drive, maybe I haven't mastered it yet?

NOTON's scan should be usable. Specifically, tell me where it's not easy to use. Is "the fourth item usp in the interface" referring to UNDO?

After entering the interface, press the space key to select the drive letter, and then pressing Enter does not execute well (sometimes it works). The second question is that I made a mistake. I thought that selecting the fourth item meant booting from the flash drive or being able to call files from the flash drive in DOS, but you mean an external USB optical drive driver, right?

I thought you were talking about the fourth item of Norton, but it turns out you were talking about the fourth item of the boot main menu. There is an explanation in this README, but since I don't have a USB device, I can't guarantee that the USB will be driven. Flash memory, heh, it's not possible at present.

Oh! I see. Thanks.

My computer is under DOS, and it stops for a long time and freezes when extracting CAB1. I want to make a CD version. It's best to extract CAB1, CAB2, zipdata, and CAB3 and put them in the CD folder. May I ask the moderator how to modify it?

What kind of startup did you use, floppy disk, CD - ROM, or virtual machine? Specifically, tell us about it.

Bamboo yiyesong, I made it to boot from a floppy disk, selected the first item. When I selected the second item, it froze when extracting CAB1. The third item works, but it's too slow.
I want to make a CD version, put the files that need to be extracted from CAB1.CAB2.CAB3 and ZIPDATA in a directory on the CD, so that the boot speed is much faster. Just don't know how to modify the AUTOEXEC.bat and files in CAB0? Also, what compression software is used for.CAB? Please, bamboo, give an explanation.....

If you make it boot from a floppy disk and it crashes, it's a problem with the quality of your floppy disk.
If you make it from a CD, it will be very fast without decompressing the CAB1, CAB2 and other compressed packages. The speed of the CD is much faster than that of the floppy disk. qian_012 has already done it, and according to his feedback, it's okay.
If you want to decompress the files like CAB1.CAB2.CAB3, you not only need to modify AUTOEXEC.bat, but also modify many batch files. So it's very troublesome to make. A few words can't make it clear.
There are many software for making CAB under DOS. You can search and you will know. I recommend a tool for making CAB packages under WIN here: cab manager. It's simple and convenient to operate, and you can choose the compression level.
If you need it, I can upload it.

How to modify and add some menus?

After repeated tests: Norton Disk Doctor 2002 can only scan the floppy drive, and cannot scan the drives of each drive letter on the hard disk, and prompts: "Cannot read from drive C: Determine that a disk is in the drive and the configuration driver is installed and available." I don't know why. Please help.

"Rain waves drifting" is indeed very good, thank you!

And regarding this boot disk (especially the floppy disk version), I strongly suggest adding some prompt information when booting, so as to avoid making users mistakenly think the system has crashed when waiting for a long time without any prompts. Like when I tested it for the first time, I actually waited for 10 minutes with no response at all, and then I realized it had really crashed. Although later it was found that it was the problem of the floppy disk itself, the boot process of this boot disk should preferably have enough prompts to let users judge whether the system is still booting, so as to avoid unnecessary losses.