VOGONS


First post, by Unregistered

User metadata

I try to get a DOS Flight Simulator called Airline Simulator 2 to run with XP Pro. VDMSound 2.04 + Update + Launchpad are installed. Even if "Activate EMS memory" is checked and I have activated EMS and XMS in the Advanced/Compatibility tab, the Program (needs 1538 KB EMS) keeps telling me "No EMS available".
I tried to set EMM=RAM in config.nt, but that didn't help.

Any ideas ?

Michael

Reply 2 of 8, by Unregistered

User metadata

Ok, here are my system specs :

IBM Thinkpad A31p, MoBo ?, Pentium 2 GHz, Phoenix BIOS 4.0 Rel 6.0, 512 MB, ATI Fire GL 7800, Soundmax Integrated Digital Audio, Win XP Pro.

It seems something is located in the UMB that blocks to free up continuous 64 KB. From what we found it's a ROM (DOS debug says DC00:0000 55 AA ...) and it has to do with USB because I find stuff like USBKVLIB-1.28 shortly after that, but I have no idea how to change that yet.
The developer of Airline Simulator 2 does a great job to help, but it seems to be a difficult task.

Michael

Reply 5 of 8, by Nicht Sehr Gut

User metadata
Rank l33t
Rank
l33t

It's quite possible that your PC has no capacity for EMS. It all depends on your motherboard and the various bits of hardware you have plugged into it.

Create a file named GO.BAT and edit it to contain the single command MEM /C, the run it with VDMSound (right-click and choose Run with VDMS), it should report something like the following:

Conventional Memory :

Name Size in Decimal Size in Hex
------------- --------------------- -------------
MSDOS 13184 ( 12.9K) 3380
KBD 3296 ( 3.2K) CE0
EMM 176 ( 0.2K) B0
HIMEM 1248 ( 1.2K) 4E0
COMMAND 3152 ( 3.1K) C50
FREE 112 ( 0.1K) 70
FREE 633984 (619.1K) 9AC80

Total FREE : 634096 (619.2K)

Upper Memory :

Name Size in Decimal Size in Hex
------------- --------------------- -------------
SYSTEM 180208 (176.0K) 2BFF0
MOUSE 12528 ( 12.2K) 30F0
DOSX 34720 ( 33.9K) 87A0
FREE 256 ( 0.3K) 100
FREE 34336 ( 33.5K) 8620

Total FREE : 34592 ( 33.8K)

Total bytes available to programs (Conventional+Upper) : 668688 (653.0K)
Largest executable program size : 633712 (618.9K)
Largest available upper memory block : 34336 ( 33.5K)

4194304 bytes total EMS memory
4194304 bytes free EMS memory

20971520 bytes total contiguous extended memory
0 bytes available contiguous extended memory
16628736 bytes available XMS memory
MS-DOS resident in High Memory Area

Cut and paste your results from your command prompt, here.

Reply 6 of 8, by Groxx

User metadata
Rank Newbie
Rank
Newbie

I'm a different person than the one that started this thread, but I have a question for Nicht Sehr Gut.

What does that DO? I've got the same problems, and I want to know what it does before I do it. Also, when it's done, what do you do with that info?

Reply 7 of 8, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

it simply tells us all the details about your memory we might need helping you.

(when vdmsound is being used)

nothing harmfull in it (unless if you use your memory size as passwd 😉

Water flows down the stream
How to ask questions the smart way!

Reply 8 of 8, by James Nix

User metadata
Rank Newbie
Rank
Newbie

From a late night forum browser:

This is an excerpt from a problem solution I had to deal with re: XP/Home and the DOS environment (Tomb Raider+Glidos+VDMSound). You may have already tried this, if not I hope it might help.

START EXCERPT:

For future reference to debug MSDOS/XP environment variable conflicts:

1) Go to C:\WINDOWS\SYSTEM32.

2) Edit the CONFIG.NT file and unREMark the ECHOCONFIG statement.

3) Edit the AUTOEXEC.NT file:

a) Change the "@echo off" statement to "@echo on".

b) Add a "SET" and a "PAUSE" statement to the bottom
of the file.

4) Execute the MSDOS program. When the DOS window opens the CONFIG.NT and the AUTOEXEC.NT will execute and pause before starting the MSDOS program. You should now be able to scroll up through the output and check for errors/conflicts.

This is not only needed in OS upgrades as programs such as VDMSound also edit these files (AUTOEXEC.NT specifically) and one program may conflict with another.

(Don't forget to change the AUTOEXEC.NT and CONFIG.NT files back!)

END OF EXCERPT.

Good luck,

Muad Dib