China DOS Union

The version of qhimem.sys I tested is 3.7. Himem is 3.26 (released by FreeDOS). The situation is like this: When using qhimem to boot with grub4dos, the computer will die. When using the boot made by vfloppy, when only loading qhimem or qhimem + emm386, running ghost will automatically restart. But when using FreeDOS's himem.exe, such a situation does not occur.

config.sys (qhimem)

menuitem=M01, Clean Boot with QHIMEM support

menuitem=M02, Clean Boot with EMM386 support

menuitem=M03, Clean Boot with JEMM386 support

menuitem=M04, Clean Boot with UMBPCI support

menudefault=M02,5

menucolor=2,0





device=drv\qhimem.sys /N32 /B





include M01

device=drv\emm386.exe I=B000-B7FF NOEMS





include S01

device=drv\jemm386.exe I=B000-B7FF NOEMS





include M01

device=drv\umbpci.sys





devicehigh=drv\qcache.sys /F /L

shell=drv\command.com /E:2048 /P=drv\autoexec.bat

dos=high,umb,auto

numlock=on

fcbshigh=4,0

fileshigh=30

buffershigh=20,0

lastdrivehigh=32

stackshigh=9,256

config.sys (himem.exe)

menuitem=M01, Clean Boot with HIMEM support

menuitem=M02, Clean Boot with EMM386 support

menuitem=M03, Clean Boot with JEMM386 support

menuitem=M04, Clean Boot with UMBPCI support

menudefault=M02,5

menucolor=2,0





device=drv\himem.exe





include M01

device=drv\emm386.exe I=B000-B7FF NOEMS





include S01

device=drv\jemm386.exe I=B000-B7FF NOEMS





include M01

device=drv\umbpci.sys





devicehigh=drv\qcache.sys /F /L

shell=drv\command.com /E:2048 /P=drv\autoexec.bat

dos=high,umb,auto

numlock=on

fcbshigh=4,0

fileshigh=30

buffershigh=20,0

lastdrivehigh=32

stackshigh=9,256

Originally posted by store88 at 2007-1-16 06:40 AM:
The version of qhimem.sys I tested is 3.7
Himem is 3.26 (released by freedos)
Without changing any configuration, except
Just replacing himem and qhimem
The situation is like this
When using qhimem to start with grub4dos, the computer will die...

Very busy, but still need to reply...
Please don't be too quick to judge that QHIMEM is not good...

Please read the README, please!
I'm sorry I don't have time to translate it into Chinese, but please take the trouble to look it up in the dictionary, okay?

The CONFIG.SYS is wrong...

SHELL=C:\DOS\COMMAND.COM C:\DOS /E:512 /P
DEVICE=C:\BIN\QHIMEM.SYS /N32 /B <-- boot
DOS=HIGH,UMB
DEVICE=C:\BIN\QDBOOT.SYS /R /W
DEVICE=C:\DOS\EMM386.EXE I=B000-B7FF NOEMS
DEVICEHIGH=C:\BIN\QDREL.SYS
DEVICEHIGH=C:\BIN\QHIMEM.SYS <-- Actual configuration
DEVICEHIGH=C:\BIN\QDMA.SYS /F /X /L
DEVICEHIGH=C:\BIN\QCDROM.SYS /D:CDROM1 /UF /L
DEVICEHIGH=C:\BIN\QCACHE.SYS /N


[ Last edited by johnsonlam on 2007-1-16 at 12:41 PM ]

I have seen it. Why put SHELL=C:\DOS\COMMAND.COM C:\DOS /E:512 /P at the front? It used to be put at the back. I'm sorry. It seems I need to try more.

shell= The key is not whether it is placed before or after

To be honest, I also find that the compatibility of QHIMEM is not ideal. I am a technician in the computer city, and I come into contact with many types of computers every day. Some computers (such as some Lenovo Tianjiao machines and some NF4 motherboards) have memory errors at startup and then crash. When I replace it with HIMEM (the version of about 11k), everything is normal.

Originally posted by zihan at 2007-1-18 12:19 AM:
To be honest, I also feel that the compatibility of QHIMEM is not ideal. I am a technician in a computer city, and I come into contact with many types of computers every day. There are some computers (such as: some machines of Lenovo Tianjiao and some mainboards of NF4...

Welcome to speak the truth, don't hide problems!

The answer is both yes and no...

Yes is that QHIMEM did not fully accommodate old machines with HIMEM (HIMEM is mostly for old machines such as AST 386, COMPAQ, GATEWAY and some non-existent manufacturer compatibilities), so some that do not follow the standard (Brother Jack refers to the XMS standard) are not supported, which is also the reason for the small size of QHIMEM.

Brother Jack has seen many BIOSes. These editors and hardware designers like to use some methods that work but are non-standard. These motherboards are not many abroad, but according to the feedback of some domestic technicians, it was originally quite serious. My feeling is... Alas, the quality of foreign brands has declined a lot, why are there so many problems with domestic motherboards....

Please help all technicians, try to switch the /T /M parameters and see if the problem can be solved?

The Gigabyte, IBM factory machines and HP I use have no problems. There is no Lenovo sold here, and there is no brand like NF4 (NForce4?), so I can't find a machine to test.

If there is a programming problem, Brother Jack is happy to correct it.


[ Last edited by johnsonlam on 2007-1-18 at 11:11 AM ]

Originally posted by store88 at 2007-1-17 10:17 AM:
I have seen it
Why put SHELL=C:\DOS\COMMAND.COM C:\DOS /E:512 /P
at the front
It used to be put at the back
I'm sorry. It seems I need to try more

SHELL and DOS=HIGH,UMB can be placed before or after, but the DEVICE order is very important, especially the QHIMEM /B -> JEMM386 -> QHIMEM to complete XMS configuration is the most important, and you can also put QHIMEM on the UMB to save 640K traditional memory.

```
shell=drv\command.com /E:2048 /P=drv\autoexec.bat
device=drv\qhimem.sys /N32 /B
dos=high,umb,auto
device=drv\emm386.exe I=B000-B7FF NOEMS
device=drv\qhimem.sys
devicehigh=drv\qcache.sys /F

shell=drv\command.com /E:2048 /P=drv\autoexec.bat
device=drv\umbpci.sys
device=drv\qhimem.sys /N32 /W
dos=high,umb,auto
device=drv\emm386.exe I=B000-B7FF X=C400-EFFF NOEMS
devicehigh=drv\qcache.sys /F /L

shell=drv\command.com /E:2048 /P=drv\autoexec.bat
device=drv\qhimem.sys /N32
dos=high,umb,auto
device=drv\emm386.exe I=B000-B7FF NOEMS

I tried all three and they all crashed.
I will try combootf.
Try again.

My mainboard is MainBoard Foxconn 400M01-G-6L
BIOS is Phoenix Technologies, LTD 6.00 PG (09/01/2004)
The motherboard is not good, no way.

[ Last edited by store88 on 2007-1-18 at 11:44 PM ]
```

I=B000-B7FF is an advanced option.

When testing, do not first use the parameter I=B000-B7FF. After confirming there are no issues, add I=B000-B7FF

I tried COMBOOTF.EXE in Lucho's Boot Disks, and the result is the same. My computer has no fate with qhimem. But I still support senior johnsonlam. Thanks for providing good things like qcache, qcdrom, etc.

Originally posted by store88 at 2007-1-21 02:07 AM:
I tried Lucho's Boot Disks' COMBOOTF.EXE
The result is the same
My computer is not compatible with qhimem
But still support前辈 johnsonlam
Thank you for providing good things like qcache qcdrom

So可惜!
Can you give me the model number of the motherboard and BIOS version that doesn't work?
Publish this information on the webpage so that everyone can avoid buying this incompatible motherboard and waste money.


[ Last edited by johnsonlam on 2007-1-22 at 07:12 AM ]

Originally posted by darkradx at 2007-1-18 11:55 PM:
I=B000-B7FF is an advanced option..

Just taking the Monochrome area for use, modern motherboards rarely use this location...

Originally posted by johnsonlam at 2007-1-22 07:10 AM:



What a pity!
Can you give me the incompatible motherboard model and BIOS version?
Post these details on the webpage so that everyone can avoid buying such incompatible...

MainBoard Foxconn 400M01-G-6L
bios Phoenix Technologies, LTD 6.00 PG (09/01/2004)