VOGONS


dosbox freezeing on windows 8?

Topic actions

First post, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

my version of dosbox suddenly just freezes when ever i boot it up.
anyone got a clue of how to fix it?

Reply 2 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

What output?

Reply 4 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

Stil no luck..

Reply 5 of 30, by ripa

User metadata
Rank Oldbie
Rank
Oldbie

What did you try exactly?

Reply 6 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

all output functions.

Reply 8 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

the other non official builds worked fine, i used HAL's build for the image make function.
and the official version and daum.

Reply 10 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

that was not my problem at all.
its just crashing, i have re-installed it and no luck, so now i really need a old computer that uses dos and windows.

Reply 11 of 30, by truth_deleted

User metadata
Nic-93 wrote:

my version of dosbox

Use supported versions instead.

Reply 12 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

i meant the official supported version, my bad.

Reply 13 of 30, by truth_deleted

User metadata
Nic-93 wrote:

the other non official builds worked fine.... and the official version and daum.

What do official version and daum have in common?

Reply 14 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

I dont know really, all i know they dont really wanna load anymore, they are stuck on the splash screen and crashes.

Reply 15 of 30, by ripa

User metadata
Rank Oldbie
Rank
Oldbie
Nic-93 wrote:

that was not my problem at all.
its just crashing, i have re-installed it and no luck, so now i really need a old computer that uses dos and windows.

Looks like Dosbox silently ignores specific types of exceptions:

int main(int argc, char* argv[]) {
try {
...
catch (int){
; //nothing, pressed killswitch
}
catch(...){
; // Unknown error, let's just exit.
}

If you want to resolve this, install the free version of Visual Studio and build your own version of Dosbox with those two catches commented out. Then run it in the debugger, and it will point out exactly where the exception gets thrown and from there we should be able to figure out where the problem lies.

Reply 16 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

oh, wait, i have the full version of visual studio, duno why, i just have random programs laying around.
uh, were? i have no experince in these code program things.

Reply 17 of 30, by ripa

User metadata
Rank Oldbie
Rank
Oldbie

Follow these instructions (I hope they are applicable to your specific version of Visual Studio): http://www.dosbox.com/wiki/Building_DOSBox_wi … _C_2008_Express

Except at the end do not switch to Release mode. Keep it in Debug. When you've got the build working, edit src/gui/sdlmain.cpp and delete these lines:

	catch (int){
; //nothing, pressed killswitch
}
catch(...){
; // Unknown error, let's just exit.
}

Then start Dosbox in debugger (F5 key). When it crashes, it should automatically switch to the Visual Studio debugger and point out the source code line that throws the exception.

edit:
Alternatively, find out what Dosbox prints before crashing or find any relevant logs. I think Dosbox writes stdout.txt and/or stderr.txt by default somewhere. Those should contain error prints. Also, Windows event log might be helpful (I don't know where to find it on Win8).

Reply 18 of 30, by Nic-93

User metadata
Rank Oldbie
Rank
Oldbie

i have visual studio 2012.
i dont really see any error messages in the command prompt it just crashes.