China DOS Union

I only tested according to the examples in readme.txt:

rem config.sys
SHELL=DOS\COMMAND.COM /E:512 /P
DEVICE=BIN\QHMBOOT.SYS
DOS=HIGH,UMB
DEVICE=BIN\QDBOOT.SYS
DEVICE=BIN\UMBPCI.SYS I=C800-EFFF NOEMS
DEVICEHIGH=QHIMEM.SYS /N48
DEVICEHIGH=BIN\QDMA.SYS /O /D /F /L
DEVICEHIGH=BIN\QCDROM.SYS /D:MYCDROM /UF /L

The computer froze during the test.
The screen prompts as follows:
QHMBOOT V2.1, 5-1-2006.
NOTE A20 line found ON!
16 XMS handles available.
The above is the prompt in Virtual PC. The prompt in Vmware has no middle line.

[ Last edited by zhangxue on 2006-5-4 at 13:33 ]

Originally posted by johnsonlam at 2006-5-4 09:56:

QDMA is not allowed for being "more strict" in checking. If data is damaged, no one can recover it.

UDMA is a very "early" work, and there are many...

It's really frustrating that QDMA can be used but is classified as ordinary transfer mode due to "strictness"! Being stricter is good, but can you provide a parameter to force it to be enabled? Of course, the user will bear the consequences. ~_~

Still using udma.sys for the time being, and waiting to see how it develops.

[ Last edited by zhangxue on 2006-5-4 at 13:31 ]

Originally posted by zhangxue at 2006-5-4 01:17 PM:
I only tested according to the example in readme.txt:
rem config.sys
SHELL=DOS\COMMAND.COM /E:512 /P
DEVICE=BIN\QHMBOOT.SYS
DOS=HIGH,UMB
DEVICE=BIN\QDBOOT.SYS
DEVICE=BIN\UMBPCI.SYS I=C800-EFFF NOEMS
...

Now QHIMEM's A20 uses the standard ones. It so happens that VirtualPC may not accept them, so the A20 problem occurs.

Need to ask what kind of A20 in VirtualPC is KBC A20 or something... Need to add new code, but first need to know what method to use to start that A20

Originally posted by zhangxue at 2006-5-4 01:17 PM:
I only tested according to the example in readme.txt:
rem config.sys
SHELL=DOS\COMMAND.COM /E:512 /P
DEVICE=BIN\QHMBOOT.SYS
DOS=HIGH,UMB
DEVICE=BIN\QDBOOT.SYS
DEVICE=BIN\UMBPCI.SYS I=C800-EFFF NOEMS
...

This example doesn't seem to cause a crash in VPC? I just tried it, only changing the above virtual path to the actual path, and no crash was found. However, when running to QDBOOT/QDMA, it prompts that UltraDMA is not found, so it is not loaded and skips directly. Let me add that my VPC is version 2004 SP1.

Virtual PC or VMware may be different from a real PC, or try Bochs.

Originally posted by johnsonlam at 2006-5-9 12:59 PM:
Virtual PC or VMware may be different from a real PC, or try Bochs.

VPC does not support UltraDMA mode, so QDMA cannot be used. However, VMWare does support it, and it works normally here.

Today, I used a bootable disk with QCDROM to boot the computer. After loading the QCDROM driver, I couldn't read the disc. The CD-ROM model is "LITEON CD-ROM LTN485S", while using Vide-cdd works normally. Therefore, the compatibility of QCDROM may be inferior to Vide-cdd, but the advantage of QCDROM is that it occupies less memory...

QDBOOT/QDMA may cause the computer to freeze on some computers. It would be better if it could skip directly when not supported to avoid freezing...

[ Last edited by ITU on 2006-6-19 at 23:49 ]

Originally posted by ITU at 2006-6-19 11:42 PM:
Boot the computer with a bootable disk with QCDROM today, and after loading the QCDROM driver, the disk cannot be read. The CD-ROM model is "LITEON CD-ROM LTN485S", while using Vide-cdd is normal. Therefore, the compatibility of QCDROM may be inferior to ...

Prove that many computer BIOS support UDMA have problems, especially the VIA chip is the worst.

Why not use UIDE.SYS?

Originally posted by Wengier at 2006-5-9 01:58 PM:

VPC does not support UltraDMA mode, so QDMA cannot be used. However, VMWare does support it, and it works normally here.

Under VMWare Fusion on Mac OSX 10.5.1, UIDE.SYS works perfectly fine!

Where can I download this QDMA???

Please provide the specific context or relevant information related to the email address you need, as just "Give me the email address" without any additional context is too vague.