中国DOS联盟

Originally posted by fastslz at 2006-6-12 22:29:
config.sys configuration 1
SHELL=COMMAND.COM /E:640 /P /F
DEVICE=DOS\QHMBOOT.SYS
DOS=HIGH,UMB
DEVICE=DOS\UMBPCI.SYS I=C800-EFFF NOEMS
DEVICEHIGH=DOS\QHIMEM.SYS /N48
DEVICE=DOS\QCDROM.SYS /D:IDE-CD01 ...

Don't understand the meaning of !???

Last edited by ITU on 2006-6-13 at 23:25 ]

Sorry, I can't come to see every day.

There are still places that can be improved in the configuration:

config.sys Configuration 1 (I am used to putting non-Device in the front, so it can be seen more clearly)
-----
DOS=HIGH,UMB
LASTDRIVE=Z
FCBSHIGH=4,0
**If there is a problem, don't load FCSB High first. It's not too late to add it after solving the problem**
FILESHIGH=30
**Same as above**
BUFFERSHIGH=20,0
**Same as above**
STACKSHIGH=9,256
**Same as above**
SHELL=COMMAND.COM /E:640 /P /F

DEVICE=DOS\QHMBOOT.SYS /t7
DEVICE=DOS\QDBOOT.SYS
**Friend, are you using S-ATA? Why are there no QDBOOT and QDMA?**
DEVICE=DOS\UMBPCI.SYS
DEVICEHIGH=DOS\QHIMEM.SYS /t7
**The above /t7 is an improved hardware testing method. Some motherboards must have it. For details, you can refer to README.TXT in QHIMEM**
DEVICEHIGH=DOS\QCDROM.SYS /D:IDE-CD01 /UF /L
DEVICEHIGH=DOS\RAMDRIVE.SYS /E 6144
**It is recommended to use SRDISK v2.09 (Resizeable RAM Disk), which is very stable!**

This configuration shows QHMBOOT V2.5, 6-04-2006, and freezes after 32 XMS handles available
After changing this configuration to DEVICE=DOS\QHIMEM.SYS /N48, it still freezes after showing QHMBOOT V2.5, 6-04-2006, and 32 XMS handles available

It should have nothing to do with the number of /N (handles), but that after setting up XMS, the memory conflicts with something

config.sys Configuration 2 (Old method, uses a bit more memory)
-----
DOS=HIGH,UMB
FCBS=1,0
**If using FreeDOS, FCBS will be ignored**
FILES=30
BUFFERS=20,0
STACKS=9,256
LASTDRIVE=Z
SHELL=COMMAND.COM /E:640 /P /F

DEVICE=DOS\QHIMEM.SYS /t7
DEVICE=DOS\UMBPCI.SYS
DEVICEHIGH=DOS\QCDROM.SYS /D:IDE-CD01 /UF /L
DEVICEHIGH=DOS\RAMDRIVE.SYS /E 6144
===

Please try again and see if the result is the same.

Thanks to Johnsonlam for the detailed explanation. I tested the above two configuration methods, as detailed below:

DOS=HIGH,UMB
LASTDRIVE=Z
FCBS=4,0
FILES=30
BUFFERS=20,0
STACKS=9,256
SHELL=COMMAND.COM /E:640 /P /F
DEVICE=DOS\QHMBOOT.SYS /t7
DEVICE=DOS\UMBPCI.SYS
DEVICEHIGH=DOS\QHIMEM.SYS /t7
DEVICEHIGH=DOS\QCDROM.SYS /D:IDE-CD01 /UF /L
DEVICEHIGH=DOS\RAMDRIVE.SYS /E 6144
Shows QHMBOOT V2.5, 6-04-2006, 32 XMS handles available and then freezes.

============================================
DOS=HIGH,UMB
FCBS=1,0
FILES=30
BUFFERS=20,0
STACKS=9,256
LASTDRIVE=Z
SHELL=COMMAND.COM /E:640 /P /F
DEVICE=DOS\QHIMEM.SYS /t7
DEVICE=DOS\UMBPCI.SYS
DEVICEHIGH=DOS\QCDROM.SYS /D:IDE-CD01 /UF /L
DEVICEHIGH=DOS\RAMDRIVE.SYS /E 6144
Shows QHIMEM V2.5, 6-04-2006, 64 XMS handles available Use /Nnn with nn=32/48/64/96/128 and then freezes.

Operating environment: MS-DOS 7.1 (ATA133 hard drive, ATA100 motherboard)
As for not using QDMA, it's because it didn't load successfully, so I gave up. Using XDMA 3.3 and UDMA2 V8.2 can both load UltraDMA 5. Because I have often helped friends maintain computers and once found that with XDMA 3.3 on an 865EP motherboard, the running speed was extremely slow, so now I don't use several DMA drivers or configure multiple methods in config to load. I hope QDMA has a compromise loading method. Even if it can't load, don't freeze. If it can't run on UltraDMA 5~6, ignore it (QDMA loading method is in post 7). Also, I want to ask about the configuration method of QDMA in autoexec.
For example:
DEVLOAD /H /Q /A DOS\QDMA.SYS /O /D /F
IF NOT EXIST ????? GOTO Second configuration
Or use IF NOT ERRORLEVEL ? to judge whether it is loaded successfully

Maybe this idea is relatively naive ^_^

Originally posted by fastslz at 2006-6-14 09:45 AM:
Operating environment MS-DOS 7.1 (ATA133 hard disk ATA100 motherboard)

I suspect that the ATA133 hard disk may be returning some QDMA incomprehensible responses, so QDMA cannot be loaded.

As for not using QDMA, it's because it wasn't loaded successfully, so I gave up. Using XDMA 3.3 and UDMA2 V8.2 can both load UltraDMA 5. Because I often help friends maintain computers, I once found that the running speed was extremely slow with XDMA 3.3 on an 865EP motherboard, so now I don't use several DMA drivers or use multiple configuration methods in config to load. I hope QDMA has a compromise loading method. Even if it can't load, don't have a system crash. If it can't run in UltraDMA 5~6, just ignore it (QDMA loading method is in post 7)

Also, UDMA and XDMA lack a lot of things. The author Jack once said in his email to me...

A) "Fast" boundary-crossing DMA.
B) Dual XMS buffers for simultaneous primary/secondary IDE I-O.
C) XMS buffer "sharing" between it and XCDROM (XCDROM uses no XMS).
D) The ability to load and run in UMBPCI upper-memory, i.e. issuing its UltraDMA commands from XMS memory.
E) Support for QDBOOT and its "diskette catcher" logic.
F) No "Int 13h links" between it and QCDROM, so EMM386 can be used.
G) Sector caching, yet to come, but I believe "almost there"!

Translating all of it is a bit difficult and will take time, so I'll skip it for now. If you're interested, I can help you translate what you don't understand.

In addition, I would like to ask about the configuration method of QDMA in autoexec, such as:

DEVLOAD /H /Q /A DOS\QDMA.SYS /O /D /F
IF NOT EXIST ？？？？ GOTO 第2配置
Or use IF NOT ERRORLEVEL ？ to judge whether it is loaded successfully

Maybe this idea is relatively naive^_^

I haven't tried loading it this way because I'm concerned that QDMA must "take into account" the drivers below it, so its order is only below QHIMEM/UMBPCI. If there are some poorly written drivers or some programs that change memory in front of it, it is very likely to damage the written data, which is very dangerous. So it's not recommended to load it in AUTOEXEC.BAT or after that.

If it weren't a driver, your suggestion is not naive at all, but very good, because AUTOEXEC.BAT loading is more flexible, but this situation is not suitable.

Sorry, almost forgot.

Tried so many times and it still freezes after QHIMEM. It might be that QHIMEM exits and freezes or freezes right after loading UMBPCI. But it's certain that the motherboard or BIOS has non-standard strange codes, which causes the freeze.

I've received many emails from abroad, all thanking me. I also ran Q-series drivers on a strange IBM eServer without any problems at all. So sorry I can't help.

If possible, could you provide your machine model? If you have another PC, please help test, thanks!

I tested it, and qdma was loaded successfully, but the computer crashed when loading qcdrom. My motherboard is an ASUS K8N

Thanks johnsonlam
Learned a lot again
My computer configuration is as follows

Physical memory
DIMM1: 128 MB PC2100 DDR SDRAM
DIMM2: 128 MB PC2100 DDR SDRAM
================================================
Mainboard
Mainboard ID 10/24/2001-P4X266-8233-6A6LW00BC-00
Mainboard name VIA P4X266 VL33-S / VIARAMA P047/P147
================================================
Device description
North bridge: VIA VT8753 Apollo P4X266
South bridge: VIA VT8233C
================================================
Award BIOS type Award Modular BIOS v6.00PG
Award BIOS information 10/24/2001 For Apollo P4X266 Chipset
(EE)PROM size 256kB (2Mbit)
Supported standards DMI, APM, ACPI, ESCD, PnP
================================================
Hard drive Maxtor 6L080P0
================================================
Processor
Model : Intel(R) Pentium(R) 4 CPU 1600MHz
Package : OOI PGA423
Rated speed/FSB : 1600MHz / 4x 100MHz
Name : P4W (Willamette) Pentium 4 1.3-2GHz 1.7-1.75V
================================================
Environment monitor 1
Model : Winbond W83697HF ISA
Version : 6.00
Support mainboard specifications : No
================================================

Originally posted by SXBG at 2006-6-15 11:00 PM:
Tested it, qdma was loaded successfully, but it froze when loading qcdrom. My motherboard is Asus K8N

Really, really strange. Why do domestic users' computers always have problems?
Does the QCDROM driver display any special messages?

Originally posted by fastslz at 2006-6-16 01:04 AM:
Thanks johnsonlam
Learned a lot more

Sorry, can't help.

Just found your motherboard using Google, BIOS was updated in 2001, almost no updates:

http://www.opendrivers.com/driver/212438/via-p4x266-vl33-s-mainboard-bios-04b-free-download.html

If your BIOS is older than 04B, you might as well give it a try, be careful when upgrading!

I will put the information on the webpage to see if other users can run QHIMEM on this motherboard.

Thanks for taking the trouble to help me find the BIOS.
The BIOS has been upgraded, and there is no change except an additional VIA logo. I also have 5 different versions of the BIOS, all from 2001, 10, 25, just changing the OEM logo.
The QCDROM driver shows that the CD - ROM ATA - 33 mode is normal, and there are no error messages.
Oh, does it have something to do with overclocking? The computer performs well under Windows, so I haven't been willing to淘汰 it so far.

Originally posted by johnsonlam at 2006-6-16 09:34:


Really, really strange. Why are there always problems with domestic users' computers?
Does the QCDROM driver display any special messages?

This is not strange. For a long time, many companies have had a sales strategy: high-quality products are sold abroad, and defective products are sold domestically.

Originally posted by fastslz at 2006-6-16 11:54 AM:
Thanks for taking the trouble to help me find the BIOS.
The BIOS has been upgraded, and there is no change except an additional VIA logo. I also have 5 different versions of the BIOS, all from 2001, 10, 25, only changing the OEM logo.

Oh, does it have anything to do with overclocking? The machine performs well under Windows, so I haven't been willing to淘汰 it yet.

It's a pity, but no matter how cheap it is, it still costs money!

Overclocking may lead to instability. In DOS, to cool the CPU, you must have the DOSIDLE program; otherwise, the CPU may be at 100%. PG author BAHCL said that his IBM laptop gets特别 hot when running DOS.

It may be the last resort...

I mentioned it to author Jack, and he said we can try QHIMEM /t4 (QHMBOOT also needs /t4). That is to call the BIOS to use the oldest method to use XMS. If the /t4 line is okay, we can also try /t2 or /t1. The following is the explanation of /t:

/Tn Specifies the BIOS requests to try in getting extended memory as follows:

/T1 "E820h" requests only.
/T2 "E801h" request only.
/T3 "E820h" requests first, then an "E801h" request.
/T4 Old 64-Megabyte request only.
/T5 "E820h" requests, then an old 64-MB request.
/T6 "E801h" requests, then an old 64-MB request.
/T7 "E820h", then "E801h", then an old 64-MB request.

/T can usually be omitted. This causes /T6 to be assumed and the drivers will run the same as past QHIMEM versions.

For details on BIOS memory requests and when /T is needed, see section 7 below. If QHMBOOT loads QHIMEM and /T will be used, the same /T value must be given for both drivers!

Originally posted by SXBG at 2006-6-17 08:22 PM:

This is not strange. For a long time, many companies have had a sales strategy: high-quality products are sold to foreign countries, and substandard products are sold to the mainland.

This is really extremely foolish. They will regret losing the trust of domestic customers. Now the domestic economy is taking off, and people have relatively high demands for high-quality products. Using substandard products to insult their compatriots will have retribution!

Please ask Brother ITU if he has tried that modified CONFIG.SYS? Will QDMA or QCDROM still crash? When testing, first remove or REM irrelevant drivers, otherwise it may affect the result.

Let's replace UMBPCI with EMM386...