How does the MaxDOS 5.5s version achieve support for memory larger than 2GB? - China DOS Union Forum

Boss, hello, I've been using the MAXDOS 5.5S version all the time, and I've been using it for several years. But this version can only support up to 2GB of memory at most. I don't like the latest version of V8 yet. May I ask Boss, which file should I modify to make this version support more than 2GB of memory? Thank you Boss for your reply!
ERROR 29: Selected item cannot fit into memory
Press any key to continue........

The prompt is this. I can use it by pulling out one memory stick or having less than 2GB!

Is there any friend here? I can send you DOS to have a look.

Hehe, please post the autoexec.bat file for us to take a look.

@echo off
if "%config%" == "NDIS" goto _NDIS
if "%config%" == "nFx" goto _nFx
if "%config%" == "GH" goto _GH
if "%config%" == "USB" goto _USB
if "%config%" == "help" goto _help
set EXPAND=YES
LH CTMOUSE >NUL
xmsdsk 4096 /y >NUL
findramd >NUL
md %ramdrive%\Tmp >nul
set temp=%ramdrive%\Tmp
set tmp=%ramdrive%\Tmp
path=%RAMDRIVE%\;a:\;%RAMDRIVE%\lan;
lh doskey > NUL
lh escape.exe > NUL
lh KILLER.exe > NUL
lh a:\shsucd.exe /D:mscd001 >NUL
pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL
pkzip -O A:\PKTBAT.zip %RAMDRIVE%\ >NUL
cls
findcd
findcdx /S
echo RAMDRIVE=%ramdrive%
goto _end

:_NDIS
prompt $p$g >nul
findramd.exe >nul
path=a:\;a:\drv;%ramdrive%;%ramdrive%\drv >nul
lh doskey.com >nul
md %ramdrive%\drv >nul
md %ramdrive%\Tmp >nul
set temp=%ramdrive%\TMP >nul
pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL
copy \drv\*.* %ramdrive%\drv >nul
copy a:\PROTMAN.EXE %ramdrive%\Drv\PROTMAN.EXE >nul
copy a:\NETBIND.COM %ramdrive%\Drv\NETBIND.COM >nul
%ramdrive% >nul
cls
call \drv\maxs.bat >nul
cd drv >nul
netbind >nul
cd\
echo.
findcd
echo.
a: >nul
goto _end

:_nFx
prompt $p$g >nul
findramd.exe >nul
path=a:\;a:\drv;%ramdrive%;%ramdrive%\drv >nul
lh doskey.com >nul
md %ramdrive%\drv >nul
md %ramdrive%\Tmp >nul
set temp=%ramdrive%\TMP >nul
pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL
netbind >nul
echo.
findcd
echo.
goto _end

:_GH
GHOST -clone,mode=pload,src=1:3\bak\sys.gho:1,dst=1:1 -sure -rb
goto _end

:_usb
set EXPAND=YES
set temp=c:\
set tmp=c:\
xmsdsk 4096 /y >NUL
findramd >NUL
path=%RAMDRIVE%\;a:\;%RAMDRIVE%\lan;
lh doskey > NUL
lh escape.exe > NUL
lh KILLER.exe > NUL
pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL
cls
echo.
findcd
echo.
goto _end

:_help
xmsdsk 4096 /y >NUL
findramd >NUL
path=%RAMDRIVE%\;a:\;%RAMDRIVE%\lan;
pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL
call help.bat
goto _end

:_end

According to reason, himem.sys of DOS 7.1 supports 3.25G memory. I have tried it on a machine with more than 4G and it's all right, except that like XP, it can only recognize 3.25G.

Hello, boss. The key is that it hasn't reached that step yet. It just reports the above errors when loading to the IMG image file, and hasn't entered DOS at all. Is there a relationship between grldr and this file?

timeout 15
default 0
fallback 1
fontfile (hd0,0)/boot/maxs/fonts.gz
splashimage (hd0,0)/boot/maxs/maxlinux.gz
password --md5 $1$5$tVHk8H1dcQF4dx4IMQZy10
title Run All-Chinese DOS Boot Disk!
root (hd0,0)
kernel (hd0,0)/boot/maxs/memdisk.gz c=60 h=4 s=36 floppy
initrd (hd0,0)/boot/maxs/pzzcn.gz c=60 h=4 s=36 floppy
#####
password --md5 $1$9$dL1c9RnwewzBSUaUdKxY8/
#####
title Call Boot System from CD!
scdrom --bootcd
title Return Windows Boot Menu!
rootnoverify (hd0,0)
makeactive
chainloader +1

kernel (hd0,0)/boot/maxs/memdisk.gz c=60 h=4 s=36 floppy
initrd (hd0,0)/boot/maxs/pzzcn.gz c=60 h=4 s=36 floppy
Just got stuck at this one! The above error is reported!

Hope there are experts to help me solve it. I uploaded the DOS package, and everyone can study it.

Hehe, after looking at the autoexec.bat provided by 5#, no problems were found. From the information provided by 8#, it is very likely a problem with the bootloader. It is advisable to try booting with the new version of grub4dos.

The method is as follows:
Find the c:\boot\maxs\pzzcn.gz file on the hard disk where maxdos_5.5s is installed, and rename pzzcn.gz to pzzcn.img. This file is the real body of maxdos. Try booting with the new version of grub4dos. I tested the startup with pzzcn.img on the computer at hand and it was okay, but unfortunately this computer only has 2G of memory, and the office computer has 4G.

It has been tested on the 4G computer in the office, confirming that using the new version of g4d to directly boot pzzcn.img can start normally. At the same time, a test of only replacing memdisk for booting was carried out (grub was not replaced, still using the original version), and the result was a boot failure with the prompt message: Selected item cannot fit into memory

[ Last edited by bc12060101 on 2010-9-5 at 13:52 ]

It seems that it might be an issue with the version of memdisk. Try using the latest version of memdisk.

It should not be the problem of the memdisk version. I have changed several ones but it still doesn't work!

I know the reason, this is an issue with xmsdsk, that is, the error occurred when executing the following line:

xmsdsk 4096 /y >NUL

The reason is that xmsdsk is a very old program, it only supports up to 2GB of memory at most, and an error will occur if it exceeds 2GB. For the time being, there is no possibility to modify xmsdsk. My solution is to replace xmsdsk with Microsoft's ramdisk.sys. Although ramdisk.sys is not as easy to use as xmsdsk, it has no memory limit problem.

Originally posted by Climbing at 2010-9-10 01:37 AM:
I know the reason. This is an issue with xmsdsk, that is, the error occurs when executing the following line:

The reason is that xmsdsk is a very old program. It only supports a maximum of 2GB of memory. An error will occur if it exceeds 2GB, ...

Support this explanation. xmsdsk indeed cannot exceed 2GB of memory

Heheh, I already said in post #10 that "tested on a 4G computer in the office, and confirmed that using the new version of g4d to directly boot pzzcn.img can start normally." How can brothers Climbing and fujianabc still come to the conclusion that "xmsdsk is a too old program, it only supports up to 2G of memory at most"?

When using the xmsdsk program, as long as the parameter /T (which locates the memory disk at the top of XMS memory) is not used, there will be no problem when using it in 4G of memory.

I discovered this problem because the old version of MicroPE by brother chenall could not load the extended driver support module EXT_DRV.IMG normally on my new office computer (4G memory). Later, removing the /t in its xmsdsk %ramdrv% 10240 /t /y allowed it to run normally.

[ Last edited by bc12060101 on 2010-9-11 at 12:31 ]

Floor1　liuluanjun	Posted 2010-08-25 09:44
初级用户　Posts 11　Credits 26
Boss, hello, I've been using the MAXDOS 5.5S version all the time, and I've been using it for several years. But this version can only support up to 2GB of memory at most. I don't like the latest version of V8 yet. May I ask Boss, which file should I modify to make this version support more than 2GB of memory? Thank you Boss for your reply! ERROR 29: Selected item cannot fit into memory Press any key to continue........ The prompt is this. I can use it by pulling out one memory stick or having less than 2GB!

Floor2　liuluanjun	Posted 2010-08-25 16:44
初级用户　Posts 11　Credits 26
Is there any friend here? I can send you DOS to have a look.

Floor3　bc12060101	Posted 2010-08-25 22:05
银牌会员　Posts 712　Credits 1,455
Hehe, please post the autoexec.bat file for us to take a look.

Floor4　liuluanjun	Posted 2010-08-26 09:38
初级用户　Posts 11　Credits 26
Okay, now send it!

Floor5　liuluanjun	Posted 2010-08-26 09:40
初级用户　Posts 11　Credits 26
@echo off if "%config%" == "NDIS" goto _NDIS if "%config%" == "nFx" goto _nFx if "%config%" == "GH" goto _GH if "%config%" == "USB" goto _USB if "%config%" == "help" goto _help set EXPAND=YES LH CTMOUSE >NUL xmsdsk 4096 /y >NUL findramd >NUL md %ramdrive%\Tmp >nul set temp=%ramdrive%\Tmp set tmp=%ramdrive%\Tmp path=%RAMDRIVE%\;a:\;%RAMDRIVE%\lan; lh doskey > NUL lh escape.exe > NUL lh KILLER.exe > NUL lh a:\shsucd.exe /D:mscd001 >NUL pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL pkzip -O A:\PKTBAT.zip %RAMDRIVE%\ >NUL cls findcd findcdx /S echo RAMDRIVE=%ramdrive% goto _end :_NDIS prompt $p$g >nul findramd.exe >nul path=a:\;a:\drv;%ramdrive%;%ramdrive%\drv >nul lh doskey.com >nul md %ramdrive%\drv >nul md %ramdrive%\Tmp >nul set temp=%ramdrive%\TMP >nul pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL copy \drv\. %ramdrive%\drv >nul copy a:\PROTMAN.EXE %ramdrive%\Drv\PROTMAN.EXE >nul copy a:\NETBIND.COM %ramdrive%\Drv\NETBIND.COM >nul %ramdrive% >nul cls call \drv\maxs.bat >nul cd drv >nul netbind >nul cd\ echo. findcd echo. a: >nul goto _end :_nFx prompt $p$g >nul findramd.exe >nul path=a:\;a:\drv;%ramdrive%;%ramdrive%\drv >nul lh doskey.com >nul md %ramdrive%\drv >nul md %ramdrive%\Tmp >nul set temp=%ramdrive%\TMP >nul pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL netbind >nul echo. findcd echo. goto _end :_GH GHOST -clone,mode=pload,src=1:3\bak\sys.gho:1,dst=1:1 -sure -rb goto _end :_usb set EXPAND=YES set temp=c:\ set tmp=c:\ xmsdsk 4096 /y >NUL findramd >NUL path=%RAMDRIVE%\;a:\;%RAMDRIVE%\lan; lh doskey > NUL lh escape.exe > NUL lh KILLER.exe > NUL pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL cls echo. findcd echo. goto _end :_help xmsdsk 4096 /y >NUL findramd >NUL path=%RAMDRIVE%\;a:\;%RAMDRIVE%\lan; pkzip -O A:\MAX.zip %RAMDRIVE%\ >NUL call help.bat goto _end :_end

Floor6　fujianabc	Posted 2010-08-26 10:26
金牌会员　Posts 1,616　Credits 3,467
According to reason, himem.sys of DOS 7.1 supports 3.25G memory. I have tried it on a machine with more than 4G and it's all right, except that like XP, it can only recognize 3.25G.

Floor7　liuluanjun	Posted 2010-08-26 10:41
初级用户　Posts 11　Credits 26
Hello, boss. The key is that it hasn't reached that step yet. It just reports the above errors when loading to the IMG image file, and hasn't entered DOS at all. Is there a relationship between grldr and this file?

Floor8　liuluanjun	Posted 2010-08-26 10:50
初级用户　Posts 11　Credits 26
timeout 15 default 0 fallback 1 fontfile (hd0,0)/boot/maxs/fonts.gz splashimage (hd0,0)/boot/maxs/maxlinux.gz password --md5 $1$5$tVHk8H1dcQF4dx4IMQZy10 title Run All-Chinese DOS Boot Disk! root (hd0,0) kernel (hd0,0)/boot/maxs/memdisk.gz c=60 h=4 s=36 floppy initrd (hd0,0)/boot/maxs/pzzcn.gz c=60 h=4 s=36 floppy ##### password --md5 $1$9$dL1c9RnwewzBSUaUdKxY8/ ##### title Call Boot System from CD! scdrom --bootcd title Return Windows Boot Menu! rootnoverify (hd0,0) makeactive chainloader +1 kernel (hd0,0)/boot/maxs/memdisk.gz c=60 h=4 s=36 floppy initrd (hd0,0)/boot/maxs/pzzcn.gz c=60 h=4 s=36 floppy Just got stuck at this one! The above error is reported!

Floor9　liuluanjun	Posted 2010-09-04 18:31
初级用户　Posts 11　Credits 26
Hope there are experts to help me solve it. I uploaded the DOS package, and everyone can study it.

Floor10　bc12060101	Posted 2010-09-04 20:56
银牌会员　Posts 712　Credits 1,455
Hehe, after looking at the autoexec.bat provided by 5#, no problems were found. From the information provided by 8#, it is very likely a problem with the bootloader. It is advisable to try booting with the new version of grub4dos. The method is as follows: Find the c:\boot\maxs\pzzcn.gz file on the hard disk where maxdos_5.5s is installed, and rename pzzcn.gz to pzzcn.img. This file is the real body of maxdos. Try booting with the new version of grub4dos. I tested the startup with pzzcn.img on the computer at hand and it was okay, but unfortunately this computer only has 2G of memory, and the office computer has 4G. It has been tested on the 4G computer in the office, confirming that using the new version of g4d to directly boot pzzcn.img can start normally. At the same time, a test of only replacing memdisk for booting was carried out (grub was not replaced, still using the original version), and the result was a boot failure with the prompt message: Selected item cannot fit into memory [ Last edited by bc12060101 on 2010-9-5 at 13:52 ]

Floor11　fujianabc	Posted 2010-09-04 21:49
金牌会员　Posts 1,616　Credits 3,467
It seems that it might be an issue with the version of memdisk. Try using the latest version of memdisk.

Floor12　liuluanjun	Posted 2010-09-06 09:52
初级用户　Posts 11　Credits 26
It should not be the problem of the memdisk version. I have changed several ones but it still doesn't work!

Floor13　Climbing	Posted 2010-09-10 01:37
铂金会员　Posts 2,753　Credits 6,962　From 河北保定
I know the reason, this is an issue with xmsdsk, that is, the error occurred when executing the following line: xmsdsk 4096 /y >NUL The reason is that xmsdsk is a very old program, it only supports up to 2GB of memory at most, and an error will occur if it exceeds 2GB. For the time being, there is no possibility to modify xmsdsk. My solution is to replace xmsdsk with Microsoft's ramdisk.sys. Although ramdisk.sys is not as easy to use as xmsdsk, it has no memory limit problem.

Floor14　fujianabc	Posted 2010-09-10 09:27
金牌会员　Posts 1,616　Credits 3,467
Originally posted by Climbing at 2010-9-10 01:37 AM: I know the reason. This is an issue with xmsdsk, that is, the error occurs when executing the following line: The reason is that xmsdsk is a very old program. It only supports a maximum of 2GB of memory. An error will occur if it exceeds 2GB, ... Support this explanation. xmsdsk indeed cannot exceed 2GB of memory

Floor15　bc12060101	Posted 2010-09-11 12:23
银牌会员　Posts 712　Credits 1,455
Heheh, I already said in post #10 that "tested on a 4G computer in the office, and confirmed that using the new version of g4d to directly boot pzzcn.img can start normally." How can brothers Climbing and fujianabc still come to the conclusion that "xmsdsk is a too old program, it only supports up to 2G of memory at most"? When using the xmsdsk program, as long as the parameter /T (which locates the memory disk at the top of XMS memory) is not used, there will be no problem when using it in 4G of memory. I discovered this problem because the old version of MicroPE by brother chenall could not load the extended driver support module EXT_DRV.IMG normally on my new office computer (4G memory). Later, removing the /t in its xmsdsk %ramdrv% 10240 /t /y allowed it to run normally. [ Last edited by bc12060101 on 2010-9-11 at 12:31 ]