China DOS Union

win95 osr2, removed IE3, installed DCOM95 and WINSOCK2, successfully ran
But the CRASH phenomenon on the second page of GOOGLE still exists, probably related to VPC.

Originally posted by glfdos at 2008-2-12 09:39 PM:
No installation file, directly drive in the display options, reporting no driver file. Unlike the driver under win3.x, which can directly setup the driver.

Didn't I say above? In the "Display Properties" of the Control Panel, enter the path where the universal graphics card driver is located, that is, the VBEMP directory in the enhancement package downloaded at the top of the building. The driver does not need an installation file, only the oemsetup.inf installation information file is needed.

Didn't I say earlier? In the "Display Properties" of the Control Panel, enter the path where the general graphics card driver is located, that is, the VBEMP directory in the enhancement package downloaded at the top of the thread. The driver program doesn't need an installation file, just the oemsetup.inf installation information file. That's how I did it, but it still doesn't work.

The most unfortunate thing is that when installing the system under VM6, after restarting, it cannot be directly booted. I then activated C: as the boot partition, and it directly prompted that the boot file is corrupted...

Isn't it good to upload files to FS2YOU? I download here at about 2K per second....

This has poor support for core and core2. I also get disk controller errors when using VPC and VMWare on new machines.

That seems to require certain VESA support.

"Driver programs do not need installation files, only the oemsetup.inf installation information file is required."
That's how I installed it, but it showed - You are running a low-version installation floppy disk, it is recommended to request a new version of the driver program from the manufacturer. What's the reason?

Okay, it's already driven. It turns out that you just need to ignore the warning and continue the installation directly!

Originally posted by yksoft1 at 2008-2-13 16:09:
This has poor support for core and core2. I also get disk controller errors when using VPC or VMWare on new machines.

Haven't encountered it. Maybe the version of VPC/VMWare you're using is too old?

The VPC version is 2007.
You find a T60 to try. There must be the same result.
On the contrary, the old 5.2 can be installed successfully.

Originally posted by yksoft1 at 2008-2-14 02:00 AM:
VPC version is 2007.
Try finding a T60 to test. There must be the same result.
Instead, the old 5.2 can be successfully installed.

VPC 2007 has many problems, and it has no advantages except supporting "hardware virtualization".

Originally posted by fujianabc at 2008-2-14 11:13 AM:

VPC 2007 has many problems. Besides supporting "hardware virtualization", it has no other advantages.

Of course, there is another advantage, which is being free (compared with version 5.2, which costs $229). Of course, if you are used to using pirated versions, it basically doesn't matter, but for formal places, it still has superiority and is conducive to popularization.

By the way, post a screenshot of Firefox 2.0 running under WinNT 3.51 (taken by Roy):