中国DOS联盟

Tested QHIMEM2.6 immediately, but the /T1~ /T7 configurations didn't work. Please, Mr. johnsonlam, pass this on to author Jack.

Next, try QCDMA2.3, hope this works....
Great! QCDROM2.1:D

DEVICE=DOS\QDMA.SYS /O /D /F
DEVICE=DOS\QDMA.SYS /L
DEVICE=DOS\QDMA.SYS
DEVICEHIGH=DOS\QDMA.SYS /O /D /F
DEVICEHIGH=DOS\QDMA.SYS /O /C /D /F /L

Great, all 5 loading methods were successful... It shows it's more stable now

Version 2.2 prompt:
QDMA ERROR AAH, DISK=0 LBA=00000D027E80H

Version 2.3 prompt:
QDMA ERROR AAH, DISK=0 LBA=000000000051H

What is the specific reason?

QDMA runs as a "BIOS driver" and reports errors in the normal BIOS way.
On exit from a successful I-O request, the AH-register is zero, and the
carry flag is reset. When an I-O error occurs, the carry flag is SET,
and the AH-register returns an error code, as follows:

Code 08h - DMA timeout. CCh - Disk FAULT.
0Fh - DMA error. E0h - Hard I-O error.
20h - Controller busy. FFh - XMS memory error.
AAh - Disk not ready.

When QDMA output overlap is enabled, a run-time output error will cause
the following message to be displayed, along with a short "beep" sound:

QDMA Error eeh! Disk=d LBA=aaaaaaaaaaaah.

where eeh is one of the return codes listed above, d is the disk number
(0 for primary-master, 1 if primary-slave, 2 if secondary-master, and 3
for secondary-slave), and aaaaaaaaaaaah is the starting disk address of
the output request, shown as a 12-digit "logical block address". QDMA
handles only BIOS Int 13h calls ( not DOS "file I-O" ), so it is NOT told
and cannot display the DOS file/directory for an output overlap error..

Does this help you? I'm basically a complete English illiterate and just guessing; the hard drive is not ready. It may be related to BIOS settings, check if the BIOS Access mode is set to AUTO

Originally posted by SXBG at 2006-6-23 11:19 PM:
Version 2.2 prompt:
QDMA ERROR AAH, DISK=0 LBA=00000D027E80H

Version 2.3 prompt:
QDMA ERROR AAH, DISK=0 LBA=000000000051H

What is the specific reason?

It means there is a DMA issue. The problematic sectors are LBA sectors 00000D027E80 and 000000000051 (H is hexadecimal). AAH means the disk is not ready (QDMA waits for the disk to send a "ready" signal). It seems your hard drive may have an issue. I guess it's mostly a seek error, a mechanical problem, and the hard drive is probably very old.

See if this helps you? I'm basically an English illiterate guessing: The hard disk is not ready. It may be related to BIOS settings, check if BIOS Access mode is set to AUTO

Thanks for listing it out, it's very helpful (no need to look for it), what you translated is very correct, but the problem is likely the hard disk itself.

Originally posted by fastslz at 2006-6-23 07:01 PM:
Tested QHIMEM2.6 in the first time, and the configurations /T1~/T7 didn't work. Please let Mr. johnsonlam inform author Jack.

It proves that it's not a problem of setting XMS memory, but just that there is insufficient information for the crash...
I'm asking if there's a way.

The new - hard - disk of 110G has been used for less than one year, and it is possible to be a water - damaged product. Moreover, it is not that any program execution will cause those prompts. There is no problem when using the acronis command - line program to clone/restore the system. Currently, it is only found that after loading HX DOS - Extender and then using cabarc to extract files from SP2.cab, this prompt appears. In addition, both SP2.cab and the target directory for extraction are located in the NTFS drive, so Datapol NTFS4DOS 1.8 is also loaded.

Originally posted by SXBG at 2006-6-29 10:44 PM:
The new 110G hard drive has been used for less than a year, so it might be a水货. Moreover, not every program will cause those prompts. Using the acronis command-line program to clone/restore the system has no problems. Currently, it is only found that after loading HX DOS-Extender and then extracting files from SP2.cab with cabarc, this prompt appears. Also, SP2.cab and the extraction target directory are both located in the NTFS drive, so Datapol NTFS4DOS 1.8 is also loaded.

First, try removing HX Extender and NTFS4DOS 1.8, then add them one by one to see where the problem occurs. It is very likely there is a conflict between drivers.

This CabExtract is for DOS, no need to load HX:

http://blairdude.googlepages.com/cabextract

Can't this cabext extract a single or several files from the cab alone? That's not good. If the entire system driver.cab is extracted, it's more than 300 megabytes. And although the extract that comes with MS-DOS can do it, the speed is unbearably slow, simply a torture.

Moreover, although those prompts appeared, it didn't affect the actual execution result.

Last edited by SXBG on 2006-7-1 at 15:11 ]

Originally posted by SXBG at 2006-7-1 03:03 PM:
Can this cabext not extract one or several files alone from the cab? That's not good. If you extract the entire system driver.cab, it's more than 300 MB. And the ms-dos built-in extract can do it, but it's extremely slow...

cabextract automatically searches files for embedded cabinets, and extracts all of them. If any multi-part cabinets are present, cabextract automatically searches for those parts and links them in. To suppress this behaviour, use the --single option.