China DOS Union

1. Why do I get an error when copying files? It says I need to specify some filename. I actually already did, but it shows *.*. WHY??

2. Where can I change the startup screen?

If you want to avoid the copy problem, when it prompts “Enable Long File Names?” at boot, just choose “No”.

The following is quoted from Wengier's post at 2003-9-19 22:35:05:
If you want to avoid the copy problem, when it prompts “Enable Long File Names?” at boot, just choose “No”.

I saw this explanation you gave, but if I choose NO, I can't see any files at all, while the disk is actually a FAT32 partition, so there shouldn't be any problem.

The following is quoted from annabel's post at 2003-9-19 23:52:23:
I saw this explanation you gave, but if I choose NO, I can't see any files at all, while the disk is actually a FAT32 partition, so there shouldn't be any problem.

Then could it be an operational problem? I've tried it N times, but I haven't run into the “can't see any files” situation at all.

I'll try again tomorrow, thanks for the prompt reply.

Also, is it impossible to test successfully with VIRTUAL PC? It restarts as soon as it reaches the startup screen.

As for the issue of “not being able to see any files after choosing NO,” this actually reminded me that there really was a small potential bug in there (but it would only happen under special circumstances). I just fixed it, so download it again and give it a try. There shouldn't be any problem this time:
http://newdos.yginfo.net/dosware/pmwin3.zip

As for Virtual PC, that's VPC's own BUG, nothing can be done about it. Roy said that VPC 5.x has too many BUGs, so MiniWin3.2 can't run under it, while under VPC 4.x there is no problem.

The following is quoted from Wengier's post at 2003-9-20 1:30:19:
As for the issue of “not being able to see any files after choosing NO,” this actually reminded me that there really was a small potential bug in there (but it would only happen under special circumstances). I just fixed it, so download it again and give it a try. There shouldn't be any problem this time:
http://newdos.yginfo.net/dosware/pmwin3.zip

As for VirtualPC, that's VPC's own BUG, nothing can be done about it. Roy said that VPC5.x has too many BUGs, so MiniWin3.2 can't run under it, while under VPC4.x there is no problem。

Thanks, retry succeeded.

A few more questions --->

1. The WIN 3.2 interface font is SYSTEM, size 12. Can it be changed to Song 9? This may involve adding fonts, but if it's burned onto a CD I don't think size would be a problem. I just don't know how to modify it.

2. If I burn this image onto a CD to make a multi-boot disc, how can I obtain the CD-ROM path? Because I want to make a simple menu to run some tools on the CD.

3. Is there a driver for a USB mouse? How should it be set up?

Enable the USB mouse driver in the BIOS/CMOS, I guess... As for getting the path, actually if you're putting it on a CD, using ELORITE.SYS instead of VIDE-CDD.SYS will be OK.

The following is quoted from Wengier's post at 2003-9-21 21:18:56:
Enable the USB mouse driver in the BIOS/CMOS, I guess... As for getting the path, actually if you're putting it on a CD, using ELORITE.SYS instead of VIDE-CDD.SYS will be OK.

Forget the USB mouse...

For finding the path I used findcd.com, and it works okay.

I had been using VIRTUAL PC to test IMG files all along. Now I installed VMware station, and the effect is very good when testing ISO, but it seems it can't directly mount floppy IMG? It requires fld image format. I wonder what you all are using.

FINDCD is of course better, it's just that if there are multiple CD-ROM drives, you need to add another check.

FLP is just IMG format (only renamed). But VMWare can't directly support 1.68MB IMG images.

FLP is just IMG, ah~~~~~~ what the hell is VMWARE doing %^&*()_

Just now when testing NTFSDOS I found that I had to enter the directory containing its main program for it to run properly, otherwise it would say unauthorized. That made me reinstall it N times. Strange : (

That refers to NTFSPro 5.0, right? In the same folder as NTFSPRO.EXE there must be a file with some name or other (I forgot the exact name), and then it'll be fine.