VOGONS


First post, by kolano

User metadata
Rank Oldbie
Rank
Oldbie

I have a few DOS programs (old eyecandy stuff) I'd like to put more muscle behind than I can via DOSBox's emulated CPU cores. I had thought the PC virtualizers (Virtual PC, VirtualBox, VMWare, etc.) would enable such, but...

VirtualBox (/w DOS 6.22 command prompt):
kPlasma: Immediate crash, Runtime error 200 at OD24:0091. Corrected via TPPatch. Seems to auto scale the image from 320x200 to 640x480, fullscreen produces a non-fullscreen centered output.

Pyche: Starts, hangs up part way through displaying initial resolution selection screen. I'm guessing it's related to limited VESA support in the VM.

Virtual PC (/w Windows ME command prompt):
kPlasma: Starts, runs very quickly. Unfortunately, without vsync support, there's lots of image tearing. I also eventually crash out with a stack overflow error. The stack overflows seem to occur even with typical (STACKS=9,128) or max (STACKS=64,512) stacks set, sometimes while still just sitting on the command prompt.

Pyche: Won't display initial resolution selection screen, starts and dumps back to command line.

VMWare:
kPlasma: Immediate crash, Runtime error 200 at OD24:0091. Corrected via TPPatch. Seems to auto scale the image from 320x200 to 640x480, fullscreen produces a non-fullscreen centered output.

Pyche: Starts, hangs up showing a black screen post initializing the 640x480x16 mode used for resolution selection.

Post some internet poking I've come to understand their support for older OSs seems rather limited. Only minimal support seems to be provided for running anything pre-WindowsNT. Can anyone recommend a DOS virtualization solution that might provide better support of older OSes/software to me, or provide any insight regarding the issues I list above?

Last edited by kolano on 2014-02-13, 03:39. Edited 4 times in total.

Eyecandy: Turn your computer into an expensive lava lamp.

Reply 2 of 10, by Davros

User metadata
Rank l33t
Rank
l33t

If you have programs that run slow in dosbox (what programs what cpu ?)
how about booting into actual msdos ?

Guardian of the Sacred Five Terabyte's of Gaming Goodness

Reply 3 of 10, by leileilol

User metadata
Rank l33t++
Rank
l33t++

That would defeat the point of virtualization.

apsosig.png
long live PCem

Reply 4 of 10, by Jorpho

User metadata
Rank l33t++
Rank
l33t++
collector wrote:

Isn't VMware Player free? https://www.vmware.com/products/player/

My thoughts exactly.

QEMU seems to be getting some attention lately. There's also Bochs, MESS, and PCem, but I guess those aren't really virtualization.

Also, when you say "Windows ME command prompt", do you mean Windows ME hacked to run in MS-DOS mode, or the Windows ME commmand prompt as executed from the Windows ME desktop? Because I wouldn't expect the Windows ME command prompt to be particularly well-behaved even on real hardware when it comes to fancy "eye candy".

Reply 5 of 10, by Zup

User metadata
Rank Oldbie
Rank
Oldbie
kolano wrote:

kPlasma: Immediate crash, Runtime error 200 at OD24:0091

Some programs made with Borland Turbo compilers crashes when using a very fast processor and throw a runtime error 200. Try tppatch to patch that program, or try to slowdown your virtual processor (moslo?).

I have traveled across the universe and through the years to find Her.
Sometimes going all the way is just a start...

I'm selling some stuff!

Reply 6 of 10, by kolano

User metadata
Rank Oldbie
Rank
Oldbie

Thanks all.

collector wrote:

Isn't VMware Player free? https://www.vmware.com/products/player/

I hadn't realized their was a free VMWare version. Or perhaps I did but thought that you could run VMs with it but not create/modify them (outside of their filesystem), or there being some other restrictions. I'll check it out.

Jorpho wrote:

Also, when you say "Windows ME command prompt", do you mean Windows ME hacked to run in MS-DOS mode, or the Windows ME commmand prompt as executed from the Windows ME desktop? Because I wouldn't expect the Windows ME command prompt to be particularly well-behaved even on real hardware when it comes to fancy "eye candy".

I was using a Windows ME command prompt boot disk. I had initially been trying with DOS 6.22, but that seemed to more quickly hit the stack overflow issue mentioned (i.e. I couldn't even launch the programs before it would occur). Eventually I'll probably need to check out FreeDOS, since I want to have something I can distribute.

Zup wrote:
kolano wrote:

kPlasma: Immediate crash, Runtime error 200 at OD24:0091

Some programs made with Borland Turbo compilers crashes when using a very fast processor and throw a runtime error 200. Try tppatch to patch that program, or try to slowdown your virtual processor (moslo?).

Wow, thanks for cluing me in to that. Kplasma was Turbo Pascal complied.

For future note to others the tppatch I got from http://www.rose-hulman.edu/~moloney/tp7bug.htm just hangs up, showing a flashing cursor but apparently never completing the patch. I attempted both in a VMWare Player DOS 6.22 VM and in DOSBox with the same results. The one I got from http://www.infostat.sk/DOSME/software/patch.htm seems to complete the patch, and provides a working executable in the VMWare Player.

Last edited by kolano on 2014-02-13, 20:57. Edited 2 times in total.

Eyecandy: Turn your computer into an expensive lava lamp.

Reply 7 of 10, by kolano

User metadata
Rank Oldbie
Rank
Oldbie

OK, post the help above I've gotten kplasma running just fine, though for it DOSBox's speed had been acceptable.

The one I'd more like to see running under virtualization, Psyche, seems to get hung up on the Allegro resolution selection screen. Let me know if anyone has any experience with such.

Eyecandy: Turn your computer into an expensive lava lamp.

Reply 8 of 10, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

Have you tried consulting with the Allegro message boards? Allegro is so widely-used that I would think someone would have already tried running a DOS Allegro program in a virtualizer at some point.

Reply 9 of 10, by Stiletto

User metadata
Rank l33t++
Rank
l33t++
kolano wrote:

For future note to others the tppatch I got from http://www.rose-hulman.edu/~moloney/tp7bug.htm just hangs up, showing a flashing cursor but apparently never completing the patch. I attempted both in a VMWare Player DOS 6.22 VM and in DOSBox with the same results. The one I got from http://www.rose-hulman.edu/~moloney/tp7bug.htm seems to complete the patch, and provides a working executable in the VMWare Player.

This is very confusing. Do you mean to have linked to two different tppatch's?

FWIW, discussion on solving Runtime Error 200 is one of this forum's first major threads.
Fix "Error 200" (Divide by zero) - by Snover and Stiletto (updated!)

We prefer ctbppat because it's a bit more user-friendly and "supports faster processors and other exe formats" (this is the ancient past, I've no idea what I meant!)

"I see a little silhouette-o of a man, Scaramouche, Scaramouche, will you
do the Fandango!" - Queen

Stiletto

Reply 10 of 10, by kolano

User metadata
Rank Oldbie
Rank
Oldbie
Stiletto wrote:
This is very confusing. Do you mean to have linked to two different tppatch's? […]
Show full quote
kolano wrote:

For future note to others the tppatch I got from http://www.rose-hulman.edu/~moloney/tp7bug.htm just hangs up, showing a flashing cursor but apparently never completing the patch. I attempted both in a VMWare Player DOS 6.22 VM and in DOSBox with the same results. The one I got from http://www.rose-hulman.edu/~moloney/tp7bug.htm seems to complete the patch, and provides a working executable in the VMWare Player.

This is very confusing. Do you mean to have linked to two different tppatch's?

FWIW, discussion on solving Runtime Error 200 is one of this forum's first major threads.
Fix "Error 200" (Divide by zero) - by Snover and Stiletto (updated!)

We prefer ctbppat because it's a bit more user-friendly and "supports faster processors and other exe formats" (this is the ancient past, I've no idea what I meant!)

Yes, I had meant to and have since corrected the post above. I thought I got to it before anyone would notice. Are there differences in the patched executable between ctbppat and tppatch (I guess the working one, though perhaps the non-working one did for some exes), or was the preference just user-friendlinesss? Or was it so long ago you're not sure?

Jorpho wrote:

Have you tried consulting with the Allegro message boards? Allegro is so widely-used that I would think someone would have already tried running a DOS Allegro program in a virtualizer at some point.

I haven't yet. I still need to register an account there to do so (though perhaps my ancient one from around 2000 is still around).

Eyecandy: Turn your computer into an expensive lava lamp.