VOGONS

Common searches


First post, by OJ

User metadata
Rank Newbie
Rank
Newbie

My QB4.5 compiled program seems to lose it's place in the program and locks up in another place in the rpogram. Running the basic program in the QB4.5 environment, the program freezes, shows the windows busy symbol, the curser changes to a bigger arrow and a message appears at the bottom of the screen saying "binding". After a little while the window closes and the win7 64 bit desktop appears with a window saying DOSBOX DOS Emulator has stopped working. I have tried to increase memory and played around with screen resolution with no success.

Config file is attached.

Any help is appreciated.

Attachments

  • Filename
    dosbox-0.73MB5.conf
    File size
    15.21 KiB
    Downloads
    311 downloads
    File license
    Fair use/fair dealing exception

Reply 1 of 10, by Vince.Bloodworks

User metadata
Rank Newbie
Rank
Newbie

Heyho ^^
Ehm I think it isn't about configurations like screensize and memory... but maybe I'm wrong 😊

What is that for a program you discribe ? I'm writing some QBasic/VBDOS programs in Dosbox very often and sometimes I get the same problem(Dosbox gets windowed, black screen and after a while it crashes). And everytime thats the case, I only have to rewrite some code because of errors I made....

Best Regards
Vincent

Reply 2 of 10, by OJ

User metadata
Rank Newbie
Rank
Newbie

Yes, I'm thinking it may not be memory as well, but was looking for some other suggestions. This is a chained multi-module program with fairly large arrays. I have a lot of time invested in it and hate to give it up.

QB 4.5 isn't spotting any errors and when I compile there also are no errors noted. So what kind of errors did you find that caused these problems?
Regards to all

Reply 8 of 10, by DaveKBV

User metadata
Rank Newbie
Rank
Newbie

Hi.
I have MS QB45 compiler working in DosBOX 0.72 OK. Compiles and runs just fine, even graphics modes (the simple 640x480 ones I use anyway.)
Only problem... I/O
From the sound of things, looking elsewhere on the list, some of that might work soon, serial coms (COM1: etc) would be most useful indeed.
Binary access to LPT1: would be nice. On NT based systems (no idea about 'nix) there are several hardware access tools. InpOut32.DLL I've used with Delphi7 (on XP and 2k) and works very well indeed. If something like that can be used by DosBOX, (via the hardware emulator no doubt) I suspect a lot of things might work, that currently dont.
I'll go and look in the wish list... NetBIOS is another need, for old office apps to work (Smartware etc)
Regards All.
D'KBV

Computers only do what you tell them, however that's not always what you want them to do.

Reply 9 of 10, by DaveKBV

User metadata
Rank Newbie
Rank
Newbie

PS:
I've yet to try "Installing" National Instruments GPIB drivers in DosBOX. 😀 I suspect that is a going a bit too far!
D

Computers only do what you tell them, however that's not always what you want them to do.

Reply 10 of 10, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

This topic is about the Megabuild and not ancient official versions...

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper