VOGONS


Microcosm

Topic actions

First post, by Theboss

User metadata
Rank Newbie
Rank
Newbie

Recently I got my hands on this old classic (cd release, 1993 unopned) as I was interested in checking how it compared to the Amiga CD32 release.

But I cannot get it to run on dosbox 😒
It constantly crashes when it tries to load the game.
If I set the speed to low cycles like 1000 it gives me a "Abnormal Program Termination: Page Fault before it crashes.

Anyone with the game can get it to run? 😐

An MS artical on old games running under win95 says about Microcosm:
"Microcosm uses a memory model that is not compatible with Windows 95. It must be run in MS-DOS mode"

Reply 1 of 19, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Try to disable ems and xms, or only one of them (this might be
enough "change of memory model" 😉 ).
Also you could try to disable sound and things like that, or use loadfix
(odd but true...)

Reply 3 of 19, by keropi

User metadata
Rank l33t++
Rank
l33t++

Then I guess that this game is simply not working on DOSBOX... if u tampered with memory and sound options and got nothing, then it won't work...
although I am not a dosbox expert, I prefer real dos machines 😁

Reply 6 of 19, by red_avatar

User metadata
Rank Oldbie
Rank
Oldbie

I have the same problem. I tried to install it on Qemu running Windows 95 but got similar issues. This game is one mean bitch to run. Nearly any game that won't run in DOSBOX will run in Qemu but this one gives the exact same errors. Theboss, where did you get the iso ?

Reply 9 of 19, by collector

User metadata
Rank l33t
Rank
l33t

TheBoss said that he got it unopened, not downloaded an ISO. I have this CD and tried it in DOSBox -- .65, CVS, gulikoza's build and ykhwong's. All four crash on the setup and the game's executable with:

Exit to error: Pagefault didn't correct table.

VDMS gives:

Error TNT.20074: Can't use -REALBREAK under this version of DPMI

Under VirtualPC in MS DOS:

Abnormal program termination: Memory fault
CS:EIP = 000Ch:0006C9C5h

Reply 11 of 19, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Pharlap is generally more tricky, try with a debugger-enabled version
and keep an eye on open failures. Also be sure that some directory
is mounted as c: as it might store a swap file there.
And, as already said, always play with the core and ems/xms settings.

Reply 12 of 19, by red_avatar

User metadata
Rank Oldbie
Rank
Oldbie

I played with those settings quite a lot 😜 with little to no result. I managed to get install.exe working (you're supposed to type install c:\mc or something like that). Maybe the actual exe needs something like that too.

Reply 13 of 19, by collector

User metadata
Rank l33t
Rank
l33t

I didn't have too much trouble with the installation, just the setup and the main executable. I tried to call a list of parameters or switches, but could find nothing.

The Sierra Help Pages -- New Sierra Game Installers -- Sierra Game Patches -- New Non-Sierra Game Installers

Reply 15 of 19, by LoneLines

User metadata
Rank Member
Rank
Member

If anyone cares for the last lines from a debug build before it crashes:

91840800: DOSMISC:DOS:65:Extended country information call 6507
91840927: FILES:file open command 0 file C:\MC\SETUP.EXE
91852879: DOSMISC:DOS:65:Extended country information call 6507
91856704: BIOS:INT15:Unknown call 2403
91856793: DOSMISC:DOS:Multiplex Unhandled call 160A
91856800: DOSMISC:DOS:Multiplex Unhandled call 1600
91856807: DOSMISC:DOS:Multiplex Unhandled call 4680
91856859: DOSMISC:DOS:Multiplex Unhandled call ED00
91856867: DOSMISC:DOS:Multiplex Unhandled call ED00
91856875: DOSMISC:DOS:Multiplex Unhandled call ED00
91856883: DOSMISC:DOS:Multiplex Unhandled call ED00
91856891: BIOS:INT15:Unknown call BF02
91856903: DOSMISC:DOS:Multiplex Unhandled call A1FE
91856915: DOSMISC:DOS:Multiplex Unhandled call FBA1
91856924: DOSMISC:DOS:Multiplex Unhandled call F100
91856954: DOSMISC:DOS:Multiplex Unhandled call 4300
91856981: FILES:file open command 0 file EMMXXXX0
91857007: FILES:file open command 0 file 386MAX$$
91857036: FILES:file open command 0 file $MMXXXX0
91857059: FILES:file open command 0 file QEMM386$
91857082: FILES:file open command 0 file EMMQXXX0
91857125: DOSMISC:DOS:Multiplex Unhandled call 1687
91857155: DOSMISC:DOS:Multiplex Unhandled call ED00
91857163: DOSMISC:DOS:Multiplex Unhandled call ED00
91857418: FILES:Special file open command 80 file C:\MC\SETUP.EXE
91887312: KEYBOARD:Port 64 write with val 255
91889003: BIOS:INT15:Function 0x88 Remaining 3C00 kb
91889428: BIOS:INT15:Function 0x88 Remaining 3C00 kb
91889635: KEYBOARD:Port 64 write with val 255
98701502: FILES:file open command 0 file setup.exe
98936739: PAGING:NP Table
98936739: PAGING:PageFault at A5F66990 type [0:0] queue 1
98946828: KEYBOARD:Port 64 write with val 255
98946912: PAGING:Left PageFault for a5f66990 queue 0
98946912: SBLASTER:DSP:Reset

After that, DosBOX crashes...
I wasn't aware DOS had paging even...

LoneLines list of workarounds for various games in DOSBox:
http://ADogsBox.jellofishi.com

Reply 18 of 19, by LoneLines

User metadata
Rank Member
Rank
Member

wd:
I meant I didn't know DOS supported it (I always figured DOS accessed memory through physical addresses not virtual addresses... guess I have some reading to do)

LoneLines list of workarounds for various games in DOSBox:
http://ADogsBox.jellofishi.com

Reply 19 of 19, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Still dos doesn't really have to do anything with paging, it doesn't use
it or prevent it or something. If you wanted to use it you had to switch
to pmode (mostly using some existing extenders) and enable paging.

The reason why extenders provide paging is to make memory handling
easier for programs, they just allocate how much they want without
caring how much memory is in the system.