China DOS Union

If everyone positions the boot disk as a repair disk, please use the boot files of ROM-DOS. The three boot files are: COMMAND.COM 44K; IBMBIO.COM 74K; IBMDOS.COM 1K. I just used it to repair a friend's computer that was infected with a hard disk logical lock. The ROM-DOS boot files are not only small, only 119K. And they have excellent compatibility. Most MS-DOS software works smoothly under it.

After booting with a ROM-DOS boot disk, if you run software like NetResq for repair, you can directly remove the "hard drive logical lock" without losing data on the hard disk.

Mine is a dual-boot from CD. There are both MS7.1 (2.88M) and ROMDOS (1.44M). The CD also has 98SE, some necessary drivers. NORTON ANTIVIRUS corporate version DOS module... If there is only ROMDOS, I still feel it's not enough.

Excuse me, since the bootable CD-ROM can be virtualized into a 2.88M bootable floppy disk, can it be virtualized to be larger, such as 5.76M and so on?

Haven't tried it, should be okay. Let's try.

It is not possible. The CD bootable disk image must take the standard 1.2/1.44/2.88 floppy disk image. If you want to exceed this limit, you can only use the hard disk image. But now it seems that using the hard disk image is of little significance, because you can put those tools that can't fit and are used infrequently on the CD and load the CD drive and then use them. After using the hard disk image, the C drive will become the one in the image, and the original C drive will be shifted to D. This will bring many unnecessary troubles in use.

If the image disk really becomes the C drive, you can only use software like LETASSIGN to exchange the drive letters.

The MINI WIN3.X proposed by Wengier some time ago is actually very promising in loading on a CD, at least the capacity is not a problem. The interface of WIN3.X is higher than most current DOS GUIs. It has network functions and does not have the PNP function of 9X, which is a very good platform for making a general-purpose DOS toolset.

I agree with this view.

Good idea. Then I can make more practical MiniWin3.x, but there need to be viewers, otherwise I won't have confidence.

Then start doing it. On one hand, continue to make the optimal 1.44M DOS bootable floppy disk, and on the other hand, make a bootable disk exceeding the 1.44 even 2.88 boundary (based on CD bootable disk). The purpose is to have stronger functions and better interface.

What specific functions are needed?

As far as the problems I think of at present are concerned.
1. If booting WIN3.X based on MS7.1, MS7.1 has restrictions on 3.X. This needs to be overcome. I have tried ROMDOS. Booting WIN3.X is no problem. However, I am still not at ease about the compatibility of ROMDOS.
2. Because it is loaded from the CD - ROM drive, the situation without a hard disk must be considered. At this time, a memory virtual disk must be created for the disk swap/cache of WIN3.X.
3. Although the capacity of the CD - ROM is very large, I hope to minimize the size of WIN3.X as much as possible to improve the loading and running speed. (The most difficult to handle)
4. The others are secondary. For example, whether there are general - purpose SVGA drivers similar to the standard, as well as network functions and so on.

What restrictions did MS-DOS 7.1 impose on Win3.x? (Note: not a 98 boot disk) Anyway, the MS-DOS 7.10 boot disk I made has always worked fine with booting Win3.x. The last time I made MiniWin 3.x also used MS-DOS 7.1, and there were also memory disks and so on.

I remember it wasn't allowed to run at that time. My DOS version is win98