China DOS Union

You've been quite active this month!!! Still, do pay attention to your health!

Can the landlord explain what are the benefits and advantages of XMGR compared to HIMEM.SYS of DOS 7.0?

9-Jun-09 UIDE/UIDEJR /N3 switch added for no XMS memory. Override of /D: name with UIDE$/UIDEJR$ added if no CD/DVD drives are found. XMGR/RDISK unchanged (re-dated only).

1-Jun-09 UIDE optimized for JEMM386, UIDE /K switch added. JEMM386 is now recommended with UIDE. See the README "Technical Notes" for full details. Other drivers unchanged.

Is it possible to add the function of customizing the drive number for RDISK.SYS? This will facilitate using INSTALL= to operate the RAM disk in CONFIG.SYS (such as extracting command.com to the RAM disk).

SHCDX33 has also been updated to a cracked version...
V3.03D 2009-06-01 SHCDX33D drive not-ready stack ERROR fixed.
By the way, can SHCDX33 add back the /i parameter?
This will be convenient to cooperate with SHSUCDHD to load ISO files again in the environment where the CD drive has been loaded...

1) Up to 4-GB of XMS memory
2) Comply with V3.0 XMS Specifications
3) XMGR has direct support for V3.70+ UMBPCI by Uwe Sieber
4) Avoid DMA problems with UMBPCI "Shadow RAM"
5) XMGR can load without the /B switch, copy all its "boot" data, and take over XMS work. Only its XMS "Handles" table remains in low memory
6) Super small, only occupies a small amount of memory, and can be loaded high (#5)
7) Correct EMM386 possible bugs (memory relocation) for new CPU characteristics
Sorry, anyone help translate, been a bit busy recently.


[ Last edited by johnsonlam on 2009-6-12 at 06:43 ]

Originally posted by Roy at 2009-6-11 12:13 PM:
Is it possible for RDISK.SYS to have the function of customizing the drive number?
This is convenient to use INSTALL= in CONFIG.SYS to operate the RAM disk (such as extracting command.com to the RAM disk).

I'm asking again, although someone has already asked...

Can you list the CONFIG.SYS you want here?
How to extract COMMAND.COM to the RAM disk?
Let Brother Jack see directly, saving time for explanation.


[ Last edited by Roy on 2009-6-12 at 08:35 ]

Originally posted by VeDe at 2009-6-11 01:29 PM:
SHCDX33 has also been updated to the D version...
V3.03D 2009-06-01 SHCDX33D drive not-ready stack ERROR fixed.
By the way, can SHCDX33 re-add the /i parameter?
This is convenient to cooperate with SHSUCDHD to load ISO files again in the environment where the CD-ROM is already loaded...

Please refer to my reply in post 7, and please give me an example, thank you!

Originally posted by wang0115 at 2009-5-30 10:38 PM:
You've been very active this month!!! Still, do take care of your health!

Recently, Brother Jack has had no major health issues, thanks for your concern.

Originally posted by johnsonlam at 2009-6-12 06:38:


I ask again, although someone has asked...

Can you list the CONFIG.SYS you want here?
How to extract COMMAND.COM to RAM disk?
For Brother Jack...

Excerpted from netbootddisk 6.4:

install=NetBoot\SHSURDRV.EXE 8192k,D480,N: /Q

install=NetBoot\tunz.com -o NetBoot\boot.zip N:\

SHELL=N:\COMMAND.COM /E:4096 /P 

This will create an N: RAM Disk, use tunz (or pkunzjr) to extract command.com from the zip to N:\, and then specify SHELL as N:\COMMAND.COM

Originally posted by johnsonlam at 2009-6-12 06:39:



Refer to my reply in floor 7, please give me an example, thanks!

Very glad to see your reply so soon, thank you!
Actually, this problem doesn't need to attach any example. It's just the question of whether SHCDX33 can be loaded multiple times and retained in memory. As long as this question is described clearly!

Example:
When executing
DEVLOAD UIDE.SYS /D:UIDE-CD
SHCDX33D /D:UIDE-CD
After success, it's impossible to mount MyISO.ISO to drive O:
SHSUCDHD /F:MyISO.ISO
SHCDX33D /D:SHSU-CDH,O

While using SHSUCDX can:
When executing
DEVLOAD UIDE.SYS /D:UIDE-CD
SHSUCDX /D:UIDE-CD
Then you can execute the following command to mount MyISO.ISO to drive O:
SHSUCDHD /F:MyISO.ISO
SHSUCDX /D:SHSU-CDH,O /I

From the above example:
SHSUCDX has an additional /I parameter compared to SHSUCDX33D. I remember that the explanation of this /I parameter for SHSUCDX is: Ignore that SHSUCDX has been loaded, reload one (time)...

Originally posted by johnsonlam at 2009-6-12 06:34:

Sorry, does anyone help translate? I've been a bit busy recently.

1) Up to 4GB of XMS memory
2) Written in accordance with XMS V3.0 specifications
3) XMGR can directly support UMBPCI (version 3.70 and later) written by Uwe Sieber
4) Avoid DMA issues with UMBPCI "Shadow RAM"
5) XMGR can be loaded without /B, copy all its "boot" data, and take over the management of XMS. Only its XMS handle table remains in conventional memory.

Just received a reply from Brother Jack. He said that under normal circumstances, DOS will assign the first available drive letter to .SYS. To specify, you must switch to using .COM and load RDISK in AUTOEXEC.BAT...

Do you mind using .COM?

Also, Brother Jack is considering whether there will be other issues with this, so... it will take some patience.



[ Last edited by johnsonlam on 2009-6-16 at 00:49 ]

Originally posted by johnsonlam at 2009-6-16 00:45:

Just received Brother Jack's reply. He said that under normal circumstances, DOS will assign the first available drive letter to .SYS. To specify, you must switch to using .COM and in AUTOEXEC.BA...

It's okay.
It's just changing DEVICE= to INSTALL= that's all.

Of course, it depends on Brother Jack being willing to do it.

Originally posted by johnsonlam at 2009-6-16 00:45:

Just received a reply from Brother Jack. He said that under normal circumstances, DOS will assign the first available drive letter to .SYS. To specify, one must switch to using .COM and in AUTOEXEC.BA...

It feels that making it into .COM is more flexible for on-demand loading. No need to use other tools for loading under BAT, which is very clever...
Also: Learned that XMSDSK.EXE fails when using the /T parameter to load RamDrive to the upper memory under environments with machine memory greater than 4G. Hope that RDISK can avoid this problem when considering adding similar parameters...