Does it crash without the highscan option?

There are replacement drivers for MSCDEX from the FreeDos project which use less memory.

I've never even heard of Highscan before. What makes you think it is necessary?

Google appears to bring up the official Microsoft Help page for EMM386:

HIGHSCAN Specifies that EMM386 use an additional check to determine the availablity of upper memory for use as UMBs or E […]
Show full quote

HIGHSCAN
Specifies that EMM386 use an additional check to determine the
availablity of upper memory for use as UMBs or EMS windows. On some
computers, specifying this switch may have no effect or cause EMM386 to
identify upper memory areas as available when they are not. As a
result, your computer might stop responding.

Why don't you post what you have in your config.sys and autoexec.bat so far? There may be other ways to achieve the result you seek. There are lots of other threads here about ways to achieve more conventional memory; as suggested, there are superior alternatives to MSCDEX, you may not need UniVBE, and you probably don't need smartdrv. There are even alternatives to EMM386.

How much conventional memory do you need, anyway? Is there something you are trying to run that requires an unusual amount of conventional memory?

Nope only with it. I want to use built in drivers to be as compatible as possible. On my other PC using the highscan option gives me a lot more memory. Is there some way to find out what areas of memory are reserved so I can manually exclude them and include all others?

Soupdragon wrote:

Nope only with it. I want to use built in drivers to be as compatible as possible.

Because built-in drivers won't make your computer crash? 🤣

Is there some way to find out what areas of memory are reserved so I can manually exclude them and include all others?

The other Google hit for <emm386 highscan> is http://support.microsoft.com/kb/96522 .

There might be a memory viewer you can use to check which areas of upper memory are in use (I think msd has one), but you'll probably have to resort to trial-and-error.

You might want to try looking in your computer's BIOS and turning off the various BIOS "shadow" options that might be there; it might solve the locking-up problem, but it also might affect your system performance.

You say it gives you "a lot more memory" on your other PC, but really, don't you just need enough memory for smartdrv, mscdex, univbe and cute mouse ?

I've never found one autoexec/config set that enabled me to run all my games...

Its a dell pc there are next to no bios options. With out highscan I have under 500k free so a lot of old stuff wont run. I was able to setup my others PC with the highscan option to play all my dos games with one set of start up files. Is anyone able to point me to a guide on how to use msd to set-up emm386?

Try something more modern like JEMM
http://www.japheth.de/

autoexec.bat

@ECHO OFF LH C:\DOS\SMARTDRV.EXE /X LH C:\DOS\MSCDEX.EXE /D:MSCD000 /V LH C:\DRIVERS\UNIVBE\UNIVBE.EXE LH KEYB UK,,C:\DOS\KEYBOA […]
Show full quote

@ECHO OFF
LH C:\DOS\SMARTDRV.EXE /X
LH C:\DOS\MSCDEX.EXE /D:MSCD000 /V
LH C:\DRIVERS\UNIVBE\UNIVBE.EXE
LH KEYB UK,,C:\DOS\KEYBOARD.SYS
LH C:\DRIVERS\CTMOUSE\CTMOUSE.EXE
PROMPT $p$g
SET PATH=C:\DOS
SET TEMP=C:\TEMP
SET DIRCMD=/O
SET SOUND=C:\DRIVERS\SB16
SET BLASTER=A220 I5 D1 H5 P330 T6
SET MIDI=SYNTH:1 MAP:E
C:\DRIVERS\SB16\DIAGNOSE /S
C:\DRIVERS\SB16\MIXERSET /P /Q

config.sys

DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE RAM AUTO REM DEVICE=C:\DOS\EMM386.EXE RAM AUTO HIGHSCAN I=B000-B7FF BUFFERS=10, […]
Show full quote

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE RAM AUTO
REM DEVICE=C:\DOS\EMM386.EXE RAM AUTO HIGHSCAN I=B000-B7FF
BUFFERS=10,0
FILES=40
DOS=UMB
LASTDRIVE=G
FCBS=10,0
DEVICEHIGH=C:\DRIVERS\CDROM\OAKCDROM.SYS /D:MSCD000
DOS=HIGH
STACKS=9,256
COUNTRY=044,,C:\DOS\COUNTRY.SYS

Mem /c /p

Modules using memory below 1 MB: […]
Show full quote

Modules using memory below 1 MB:

Name Total = Conventional + Upper Memory
-------- ---------------- ---------------- ----------------
MSDOS 16,829 (16K) 16,829 (16K) 0 (0K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
EMM386 3,120 (3K) 3,120 (3K) 0 (0K)
COMMAND 2,928 (3K) 2,928 (3K) 0 (0K)
OAKCDROM 36,096 (35K) 0 (0K) 36,096 (35K)
SMARTDRV 29,040 (28K) 0 (0K) 29,040 (28K)
MSCDEX 25,888 (25K) 0 (0K) 25,888 (25K)
KEYB 6,944 (7K) 0 (0K) 6,944 (7K)
CTMOUSE 3,328 (3K) 0 (0K) 3,328 (3K)
Free 588,032 (574K) 498,032 (486K) 90,000 (88K)

Memory Summary:

Type of Memory Total = Used + Free
---------------- ---------- ---------- ----------
Conventional 522,240 24,208 498,032
Upper 191,296 101,296 90,000
Reserved 0 0 0
Extended (XMS)* 65,868,992 2,675,904 63,193,088
Press any key to continue . . .
---------------- ---------- ---------- ----------
Total memory 66,582,528 2,801,408 63,781,120

Total under 1 MB 713,536 125,504 588,032

Total Expanded (EMS) 33,947,648 (33,152K
Free Expanded (EMS)* 33,554,432 (32,768K

* 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 497,936 (486K)
Largest free upper memory block 49,120 (48K)
MS-DOS is resident in the high memory area.

thanks ill checkout jemm

The CD driver, MSCDEX and SMARTDRV are the big ones. There are good alternatives for the CD driver like one from Toshiba. MSCDEX can also be replaced.

There are previous threads with more info, just got to find them 😀

The other thing you can do is try running MEMMAKER and see what it finds. But get rid of any fancy stuff like highscan, LH, DEVICEHIGH and things like that.

You have two DOS= lines in your config.sys. You should only have one:
DOS=HIGH,UMB
and it should be before your EMM386 line (but after HIMEM).

That ought to help.

EDIT: I've never heard of FCBS before, and a little Googling suggests that if you have it at all, it ought to be FCBS=1,0 . I'm not sure you need anything more than STACKS=0,0 as well.

I have no idea why it's saying you have a total of 522k of conventional RAM, but that fix I mentioned above might fix it.

Ok, here are some tips:

A. Increasing available conventional memory without altering your EMM386 statement:

1. Remove Smartdrv.

- It dramatically improves system speed which is quite apparent. But it's not required to run games, unless the game frequently accesses the hard disk or cd-rom.

- It is useful while working with file managers.

- Otherwise it's not needed. Even more so on a PII system, where the absence of Smartdrv is not missed.

- This will free up 30k of memory if loaded low.

2. Change the CDROM driver to QCDROM.SYS

- Takes up only 2k. (Compare this with the OAKCDROM driver - 35k!!)

- It does have some limitations will work with majority of drives out there. I've never faced any problems using it with my 4X drives upto the latest DVD writers.

(Even if the former drivers do not occupy conventional memory when loaded into the UMB, using more efficient drivers will leave the UMB with more space to load even more drivers into the UMB.)

3. Change the cdrom redirector MSCDEX with SHCDX33E.

- Takes up only about 6k. (Compare this with MSCDEX - 25k!)

- I've not seen any cd read errors when using this instead of using the MSCDEX.

B. Use newer extended memory managers like QHIMEM.SYS:

- QHIMEM removes some limitations with memory management, like breaking through the 64MB barrier, added some minoor enhancements, and is basically, more friendly with faster and newer systems.

- For instance, in one of my systems, which has 512MB, I've created a RAM drive of 384MB - which is not possible with HIMEM. (This is a Win2K/Win98SE/Dos/Wiin3 combo system.)

C. Manually identify memory regions:

- If you have DOS6+, you can use the MSD.EXE (MicroSoft Diagnostics) to identify free memory regions. On boot-up, bypass the startup files and load MSD directly and see.

- Or any other similar utilities will help.

- Most of the time, I end up manually doing this instead of relying on MEMMAKER - I can squeeze out even more conventional memory by doing this way.

- But don't underestimate MEMMAKER. It's very helpful, and usually I use this first. Only when I'm not happy, I go manual.

D. Other options :

1. There are many third party utilities like the JEMM as DosFreak said.

2. Get FreeDOS if you want automated installation processes. The OS will leave you with about 615kb at the end of install. It has a list of bootable options created for you.

E. Not many programs require very high Free Conventional Memory requirements

- There are few notorious games which will cry if there's less than 600k of free conventional memory. In my experience, Falcon 3.0 comes to mind.

- I remember Wing Commander II came with a big readme file with information to help free up space. It requires 580kb or 588kb free.

- Most games should run fine at your current 574kb free conv. mem.

F. Resources:

SHCDX33E

QCDROM.SYS

UMBPCI.SYS - Alternate UMB provider.

JEMM

DOSMAX - moves BUFFERS, FILES, FCBS, STACKS, LASTDRIVE + COMMAND.COM environment to upper memory, freeing up to 100 KB of conventional memory.

QHIMEM.SYS

Malik wrote:

- Most games should run fine at your current 574kb free conv. mem.

Look again. That's 574kb total. Free conventional is only at 486k for some strange reason, unless I'm misreading that completely.

Hmm...then, maybe try with different memory modules(sticks)?

I did find some indications that a Dell might do funny things with conventional memory, but nothing definitive.
http://marc.info/?l=linux-kernel&m=120423337406116
http://www.tomshardware.com/forum/259620-45-c … -memory-windows

Hmmm.... Looking at the Memory Summary above, the Total Conventional Memory is given as 522,240. That comes to (522,240 / 1024) = 510kb.

So, does the figure 510 ring anything to anyone?

I can't think of any instance which has this figure. All I can think of is that the BIOS is using up some meomry in some way, (maybe corrupted?), or something wrong with the memory sticks/modules. It looks like something is eating up a whole chunk of the border of the conventional-high memory region.

Or there might not be anything wong at all. Maybe you guys can help.

(Also, will it be helpful if we have more information, like motherboard/system series name and total installed RAM? And maybe some pictures of the BIOS screens too?)

And some additional queries :

How about the mem/c and mem/f command outputs when autoexec.bat and config.sys are bypassed?

Dominus wrote:

I've never found one autoexec/config set that enabled me to run all my games...

100% true. You need to have different configs for different games to maximize available base memory. DOS 6 or higher addressed this need with MENU commands that allowed you to choose which drivers to load at startup.

Some things JUST CAN'T BE LOADED HIGH. Period. You will never achieve the 'one config for all' in DOS except in your dreams. That's just the way DOS is, deal with it.

You can get far with umbpci but as soon as one game wants ems and another can't run with it (ultima 7) you need to have different configs ...

IIRC there are 512kb/640kb BIOS options for conventional memory in some old computers.

Originally it was 512kb for conventional and 512kb for option rom.
Later it was changed to 640kb conventional and 384kb

OK the problem was a memory hole setting in the BIOS that I missed (It was late at night). I then tested with and without smart drive and your right its not needed on a P2 system. I also swapped out the Oak CD-ROM driver for the correct NEC one from the dell site which is smaller. Now I have enough conventional memory to run all my old games.

Modules using memory below 1 MB: […]
Show full quote

Modules using memory below 1 MB:

Name Total = Conventional + Upper Memory
-------- ---------------- ---------------- ----------------
MSDOS 16,829 (16K) 16,829 (16K) 0 (0K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
EMM386 3,120 (3K) 3,120 (3K) 0 (0K)
COMMAND 2,928 (3K) 2,928 (3K) 0 (0K)
UNIVBE 18,224 (18K) 18,144 (18K) 80 (0K)
NECATAPI 8,576 (8K) 0 (0K) 8,576 (8K)
MSCDEX 27,952 (27K) 0 (0K) 27,952 (27K)
KEYB 6,944 (7K) 0 (0K) 6,944 (7K)
CTMOUSE 3,328 (3K) 0 (0K) 3,328 (3K)
Free 624,352 (610K) 610,960 (597K) 13,392 (13K)

Memory Summary:

Type of Memory Total = Used + Free
---------------- ---------- ---------- ----------
Conventional 653,312 42,352 610,960
Upper 60,272 46,880 13,392
Reserved 0 0 0
Extended (XMS)* 66,000,016 578,704 65,421,312
Press any key to continue . . .
---------------- ---------- ---------- ----------
Total memory 66,713,600 667,936 66,045,664

Total under 1 MB 713,584 89,232 624,352

Total Expanded (EMS) 33,947,648 (33,152K
Free Expanded (EMS)* 33,554,432 (32,768K

* 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 610,864 (597K)
Largest free upper memory block 13,184 (13K)
MS-DOS is resident in the high memory area.

Thanks for the help everyone.😀