VOGONS


Dos 6 conventional memory tricks

Topic actions

Reply 260 of 273, by dr_st

User metadata
Rank l33t
Rank
l33t
Joseph_Joestar wrote on 2021-09-27, 07:29:

BTW, for testing purposes, I just reverted all of the tweaks that I added manually (including the EMM386 line listed previously) and let MEMMAKER.EXE work its magic on the unmodified AUTOEXEC.BAT and CONFIG.SYS. Surprisingly, it achieved an even better result, giving me 614 KB of free conventional memory. And this is without using any of those memory ranges and without HIGHSCAN.

I think I'm good with that and will likely keep this setup.

Could you share your current Config/Autoexec? I'm curious what exactly MemMaker did here. Others can learn from it too, I'm sure. 😀

https://cloakedthargoid.wordpress.com/ - Random content on hardware, software, games and toys

Reply 261 of 273, by Joseph_Joestar

User metadata
Rank l33t
Rank
l33t
dr_st wrote on 2021-09-27, 08:05:

Could you share your current Config/Autoexec? I'm curious what exactly MemMaker did here. Others can learn from it too, I'm sure. 😀

Sure thing. For reference, the files are from this rig running DOS 6.22 + Win 3.11. Note that I'm deliberately using the bloated Microsoft mouse driver v9 because of this issue with my BIOS, but MEMMAKER somehow manages to load it high.

AUTOEXEC.BAT

@ECHO OFF
SET SOUND16=C:\OPTI930
C:\OPTI930\sndinit /b
SET BLASTER=A220 I5 D1 H5 P300 E620 T6
SET SOUND=C:\SB16
SET MIDI=SYNTH:1 MAP:E MODE:0
SET CTCM=C:\CTCM
C:\SB16\DIAGNOSE /S
C:\SB16\AWEUTIL /S
C:\SB16\MIXERSET /P /Q
C:\CTCM\CTCU /S
LH /L:1,23024 C:\DOS\MSCDEX.EXE /E /D:OPTICAL /L:D
LH /L:0;1,25168 /S C:\DOS\MSM9\MOUSE.EXE
PROMPT $p$g
PATH C:\DOS;C:\DOS\BAT;C:\WINDOWS;C:\OPTI930
SET TEMP=C:\TEMP
SET DIRCMD=/A/O:GEN
SET SST_RGAMMA=1.0
SET SST_GGAMMA=1.0
SET SST_BGAMMA=1.0
SET SST_SCREENREFRESH=85
SET SST_FX_GLIDE_SWAPINTERVAL=0
SET SST_GRXCLK=50

CONFIG.SYS

DEVICE=C:\DOS\HIMEM.SYS /TESTMEM:OFF
DEVICE=C:\DOS\EMM386.EXE RAM
BUFFERS=40,0
FILES=60
DOS=UMB
LASTDRIVE=E
FCBS=4,0
SHELL=C:\DOS\COMMAND.COM /P /E:512
DEVICE=C:\OPTI930\cdsetup.sys /T:X
DEVICE=C:\CTCM\CTCM.EXE
DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
DOS=HIGH
DEVICEHIGH /L:1,11360 =C:\DOS\VIDECDD.SYS /D:OPTICAL
STACKS=9,256

MEM.EXE /a /c /p

Modules using memory below 1 MB:

Name Total = Conventional + Upper Memory
-------- ---------------- ---------------- ----------------
MSDOS 17,213 (17K) 17,213 (17K) 0 (0K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
EMM386 4,144 (4K) 4,144 (4K) 0 (0K)
COMMAND 3,184 (3K) 3,184 (3K) 0 (0K)
MOUSE 25,440 (25K) 272 (0K) 25,168 (25K)
SETVER 512 (1K) 0 (0K) 512 (1K)
VIDECDD 5,056 (5K) 0 (0K) 5,056 (5K)
MSCDEX 15,712 (15K) 0 (0K) 15,712 (15K)
Free 675,616 (660K) 629,008 (614K) 46,608 (46K)

Memory Summary:

Type of Memory Total = Used + Free
---------------- ---------- ---------- ----------
Conventional 655,360 26,352 629,008
Upper 93,056 46,448 46,608
Reserved 393,216 393,216 0
Extended (XMS)* 65,967,232 578,688 65,388,544
---------------- ---------- ---------- ----------
Press any key to continue . . .
Total memory 67,108,864 1,044,704 66,064,160

Total under 1 MB 748,416 72,800 675,616

Total Expanded (EMS) 33,947,648 (33,152K
Free Expanded (EMS)* 33,538,048 (32,752K

* EMM386 is using XMS memory to simulate EMS memory as needed.
Free EMS memory may change as free XMS memory changes.

Largest executable program size 628,704 (614K)
Largest free upper memory block 46,400 (45K)
Available space in High Memory Area 928 (1K)
MS-DOS is resident in the high memory area.

PC#1: Pentium MMX 166 / Soyo SY-5BT / S3 Trio64V+ / Voodoo1 / OPTi 82C930 / AWE64 Gold / SC-155
PC#2: AthlonXP 1700+ / Abit KT7A / Voodoo3 / SBLive / Vortex2
PC#3: Athlon64 3000+ / Asus K8V-MX / GeForce4 / Audigy1
PC#4: i5-3550P / MSI Z77A-G43 / GTX 650Ti / X-Fi

Reply 262 of 273, by dr_st

User metadata
Rank l33t
Rank
l33t
Joseph_Joestar wrote on 2021-09-27, 08:32:

Sure thing. For reference, the files are from this rig running DOS 6.22 + Win 3.11. Note that I'm deliberately using the bloated Microsoft mouse driver v9 because of this issue with my BIOS, but MEMMAKER somehow manages to load it high.

Thanks! I was going to ask about that MOUSE thing. 😁

Comparing to my startup files over there, it seems like the difference with all these EMM386 switches only amounts to ~8K of UMBs on my system. I guess EMM's default heuristics do a pretty good job finding free UMBs, while MEMMAKER does a great job utilizing them. Your free UMBs are all in one 46K chunk, thanks to the /L /S switches. You could even fit SMARTDRV in there, and a few other goodies, like DOSKEY.

I see the main difference in free conventional memory is that on my setup, COMMAND and parts of DOS are loaded in the high memory, while on your system they are all loaded low according to MEM/C/P. Part of it is probably due to DOS 7 vs DOS 6 (DOS 7 can load more stuff HIGH by default), but maybe it also has to do with the relatively late positioning of DOS=HIGH in your CONFIG.SYS? I don't remember if it has any effect.

https://cloakedthargoid.wordpress.com/ - Random content on hardware, software, games and toys

Reply 263 of 273, by Joseph_Joestar

User metadata
Rank l33t
Rank
l33t
dr_st wrote on 2021-09-27, 18:07:

You could even fit SMARTDRV in there, and a few other goodies, like DOSKEY.

I do use SMARTDRV on physical hard disks, but I don't see much benefit from it on a CF card, which is what my DOS 6.22 system is running on.

but maybe it also has to do with the relatively late positioning of DOS=HIGH in your CONFIG.SYS? I don't remember if it has any effect.

Originally, I had a single line with DOS=HIGH,UMB near the top of my CONFIG.SYS. For some reason, MEMMAKER split that into two lines and changed the position. I have no idea why.

PC#1: Pentium MMX 166 / Soyo SY-5BT / S3 Trio64V+ / Voodoo1 / OPTi 82C930 / AWE64 Gold / SC-155
PC#2: AthlonXP 1700+ / Abit KT7A / Voodoo3 / SBLive / Vortex2
PC#3: Athlon64 3000+ / Asus K8V-MX / GeForce4 / Audigy1
PC#4: i5-3550P / MSI Z77A-G43 / GTX 650Ti / X-Fi

Reply 264 of 273, by Rawit

User metadata
Rank Member
Rank
Member
Joseph_Joestar wrote on 2021-09-27, 08:32:

Note that I'm deliberately using the bloated Microsoft mouse driver v9 because of this issue with my BIOS, but MEMMAKER somehow manages to load it high.

I came here for memory tricks but ended up with a new mouse driver. The Microsoft mouse driver v9 fixes a few things on my Cyrix MediaGX1 system. I noticed with CuteMouse Windows wouldn't load and only version 2 gave me what I thought was OK performance. Apparently some delays in software (for example FastTracker 2 not keeping tempo) were caused by CuteMouse and are now solved!

YouTube

Reply 265 of 273, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
Rawit wrote on 2021-12-15, 08:25:
Joseph_Joestar wrote on 2021-09-27, 08:32:

Note that I'm deliberately using the bloated Microsoft mouse driver v9 because of this issue with my BIOS, but MEMMAKER somehow manages to load it high.

I came here for memory tricks but ended up with a new mouse driver. The Microsoft mouse driver v9 fixes a few things on my Cyrix MediaGX1 system. I noticed with CuteMouse Windows wouldn't load and only version 2 gave me what I thought was OK performance. Apparently some delays in software (for example FastTracker 2 not keeping tempo) were caused by CuteMouse and are now solved!

That's interesting, did you try to load windows without cutemouse? A boot menu with multiple voices it's the best thing.

Reply 267 of 273, by Nemo1985

User metadata
Rank Oldbie
Rank
Oldbie
Rawit wrote on 2021-12-15, 14:51:

Yes, I made a bat to unload CuteMouse on start of Windows 3.11 to circumvent this issue. With CuteMouse loaded it wouldn't start or would start without a mouse.

Sorry, I thought you were talking about windows 98.

I use cutemouse and windows 3.11 on my 486 build, but I haven't those issues.

Reply 268 of 273, by servicepack2

User metadata
Rank Newbie
Rank
Newbie
Joseph_Joestar wrote on 2021-09-27, 18:26:

You could even fit SMARTDRV in there, and a few other goodies, like DOSKEY.

Could you correct me ? And does "set RAM=" actually work ?

DEVICE=HImem.SYS DEVICE=emm386.EXE set ram=104528 BUFFERS=20,0 FILES=40 DOS=UMB lastdrive=Y FCBS=1,0 DOS=HIGH devicehigh=gcdro […]
Show full quote

DEVICE=HImem.SYS
DEVICE=emm386.EXE
set ram=104528
BUFFERS=20,0
FILES=40
DOS=UMB
lastdrive=Y
FCBS=1,0
DOS=HIGH
devicehigh=gcdrom.sys /d:dvdram

Reply 269 of 273, by Joseph_Joestar

User metadata
Rank l33t
Rank
l33t
servicepack2 wrote on 2022-02-13, 17:13:

Could you correct me ? And does "set RAM=" actually work ?

Do you mean the RAM parameter of EMM386.EXE? That specifies a range of segment addresses to be used for UMBs and is not invoked with SET.

Regarding your setup, I'm not that knowledgeable about manually tweaking DOS conventional memory settings. The last time I tried, I barely got around 590 KB free. Reverting all of my tweaks and then letting MEMMAKER.EXE do its job gave me a much better result. Maybe someone who's more familiar with the subject can give you some tips for manual adjustments.

PC#1: Pentium MMX 166 / Soyo SY-5BT / S3 Trio64V+ / Voodoo1 / OPTi 82C930 / AWE64 Gold / SC-155
PC#2: AthlonXP 1700+ / Abit KT7A / Voodoo3 / SBLive / Vortex2
PC#3: Athlon64 3000+ / Asus K8V-MX / GeForce4 / Audigy1
PC#4: i5-3550P / MSI Z77A-G43 / GTX 650Ti / X-Fi

Reply 272 of 273, by jheronimus

User metadata
Rank Oldbie
Rank
Oldbie

I've had an issue with CuteMouse where Win 3.11 tried to set it up as a Logitech mouse by default (and it wouldn't boot with that). Switching to Microsoft in Windows setup fixed that.

It happened on an ISA8 PS/2 adapter, the mouse is actually a Microsoft Intellimouse using PS/2 to USB converter dongle