Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Does anyone know if there is a limit on the amount of ram that MSDOS 6.22 can use? If so is there a work around which will allow me to use my entire 256Mb of ram?
I have created a bootable CD that contains the files from an installation of 6.22/ Win3.1 . When the CD boots, I use (in config.sys)XMSDSK.exe to create a ram drive. Next (autoexec.bat) xxcopy16/clone to copy the Dos, Windows, and MSoffice directories to the ram disk. The trouble is that my ram disk is not big enough due to the fact that MSDOS 6.22 cannot more that 64Mb?
Quite correct 64MB is the limit.
Look at the following site for a better option:
http://newdos.yginfo.net/msdos71/index.htm
0 
What does the load line for xmsdsk look like?
Example;
X:\folder\XMSDSK 262144 I: /T /YXMSDSK is capable of using 2Gb. If the bios sees it, xmsdsk should too.
0
Dan Penny,
"XMSDSK is capable of using 2Gb. If the bios sees it, xmsdsk should too."
I'm sorry, but this is not correct. XMSDSK can't be capable of using that much of memory if the XMS memory manager has such limitation. MS-DOS 6.x is so old that it can't support memory larger than 64MB.
Try MS-DOS 7.10 instead; this will also provide you with many more useful features, such as Long File Names (LFN) support, FAT16X/32 drives support, full Win3.x/9x support.
0
From the Readme.txt which comes with XMSDSK "package";
Quote
From version 1.9g up is included some of my tools to report a brief status of
EMS and XMS managers (EMSTAT.exe and XMSTAT.EXE). Is included too SETXMSTO.exe
which tries to convince old versions of HIMEM.SYS (from MSDOS 6.x) of managing
more than 64MB.
Run SETXMSTO, it displays a little usage and how much memory BIOS knows of.
If it displays that func. 15E801 is not supported and you try to set an XMS
size then you're on your own: USE AT YOUR OWN RISK.End quote
0
As well, from the same Readme.txt;
v1.9 (Sep 96) Supports up to 64 Mbytes. Adds option u to remove driver from memory. EMSDSK and EMSDSK86 can be used in place of each other safely. :-)
v1.9a (Sep 96) Supports up to 2 Gbytes. This should stop the question about "could it support more than xxxKb?". :)
0
Here is a copy of the config.sys I am using.
---------
DEVICE=C:\DOS\HIMEM.SYS
DEVICEHIGH=C:\XMSDSK.exe 475338
DEVICEHIGH=C:\teac_cdi.sys /D:mscd000
DOS=HIGH
FILES=30
BUFFERS=30,0
LASTDRIVE=ZSTACKS=9,256
-------------Am I correct in understanding that I can run Win 3.1 with MSDOS 7.1? I haven't checked the links in the above posts yet, but will I need some sort of patch to make Win 3.1 work with this newer version of DOS? Also, I do have a copy of PCDOS 2000, does anyone know if this ver will work for my project? Thanks in advance for any advice.
0
Dan Penny,
I haven't tested that "converter", but I think it's not necessary at all. MS-DOS 7.10 will solve any problem that may exist about it.
upal_2,
As we have said before for a couple of times, MS-DOS 7.10 from that page is fully compatible with Windows 3.x and Windows 9x without any sort of patch! Have you ever read the following knowledge base article?
0
Read the publishers own notes:
http://www.simtel.net/product.php?url_fb_product_page=4825
or to download XMSDSK
0
Yes, XMSDSK is a great tool that I have used for a few years. I don't know why there is no new versions of it any more.
Nevertheless, SETTOXMS is of no use if DOS supports large XMS memory already (MS-DOS 7.10 supports XMS memory up to 4GB). On the other hand, it's very nice if there is any tool that can modify the EMS handle table to support more than 32MB EMS, since no version of MS-DOS's EMS memory manager can support that much of EMS memory directly!
0
Wengier,
Thanks for the info on the compatibility of Win 3.1 and DOS 7.10. I read something a while back which caused me to (falsely) believe that 3.1 was not compatible with newer versions of DOS.
Also, the one of the reasons why I wanted to use MSDOS 6.22 is due to the fact that my primary partition on my hard drive is fat32. I wanted this to be invisible to the OS running in the ramdisk. Just a thought, but could I use the assign command within the Autoexec.bat file to hide the fat32 partition from the ramdisk? Maybe something like
assign C: Nul
0
upal_2,
"Just a thought, but could I use the assign command within the Autoexec.bat file to hide the fat32 partition from the ramdisk?"
Sure, you can hide/unhide that FAT32 partition by using ASSIGN or SUBST command (or similar) at any time.
For example (via SUBST):
To hide:
SUBST C: <path> (where <path> is any available path you want to point Drive C: to)
To unhide:
SUBST C: /D
Good luck!
0
Thanks for the info on the compatibility of Win 3.1 and DOS 7.10. I read something a while back which caused me to (falsely) believe that 3.1 was not compatible with newer versions of DOS.
You were not informed falsely! MS-DOS 7.10 as supplied with Windows 98/98se will not run Windows 3.1 it needs to be patched with 3XSTART to do so. Wengiers version of 7.10 has been patched already for you. MS-DOS 8.0 (from Windows Me) is not recomended at all for standalone use.
0
In short, the version of DOS shipped with full Win9x distribution (a.k.a. "WinDOS 7.1") does need some patches (3xStart is one of them, for example).
The MS-DOS 7.10 from that page (standalone version) is compatible with Win3.x & Win9x already without any patches or changes.
The version of DOS shipped with full WinME distribution is completely useless except the fact that WinME GUI can only be started from MS-DOS 8.0.
0
Just a question,
Sure, MS-DOS 7.10 can. And it even has the dual-boot ability with old MS-DOS 6.22. You can look at this page for more information:
http://groups.yahoo.com/group/classicwin3x/message/37
0  |
 help on older computer
|
Long Filename Null modem ...
|
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
