VOGONS

Common searches


First post, by kapkao

User metadata
Rank Newbie
Rank
Newbie

previous 3 versions of dosbox terminate without error.

65 opens a status window then *poof!*

D875PBZLK mainboard
p4 2.6 ghz
1 gig 400 mhz sd/ddr ram
radeon x800 xt agp 8x 256mb internalDAC
SBlaster Audigy
Winxp/sp2
Directx 90b
ATI Catalyst 7.1x

Read readme, multiple times actually

stuff

Reply 1 of 13, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Is this just from starting DOSBox? Before you start a game or anything? How do you start DOSBox?

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 6 of 13, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Get a dependency walker then, though i doubt this will solve your problem.
If it crashes that early it's most likely something with sdl. Try upgrading
your graphics card drivers, change the output= in dosbox.conf or try
replacing sdl.dll with an older/newer one.

Reply 7 of 13, by kapkao

User metadata
Rank Newbie
Rank
Newbie
wd wrote:

Get a dependency walker then,

A which? :p
(I'll look it up later)

I think exescope can find these, actually. Either way...

wd wrote:

though i doubt this will solve your problem.

Lotsa crap gets messed up, over the years.

And my crap works most of the time, so if I could get DOSBOX to work without reinstalling XP I'd prefer it.

If it crashes that early it's most likely something with sdl. Try upgrading
your graphics card drivers, change the output= in dosbox.conf or try
replacing sdl.dll with an older/newer one.

I tried 62, 63, 65, so I doubt it's old/new code.

I got 63 to work a couple years ago so I'm guessing it's what mf2hd said...

edit quote tag

edit2... welll maybe it is something with the grafix card. that's the only MAJOR difference between a working dosbox for me.

I had a geforce 6200 before going to an x800

stuff

Reply 8 of 13, by mf2hd

User metadata
Rank Newbie
Rank
Newbie

I've thought something related to sdl.dll or other dll that dbox wants (sdl_net.dll,libpng...), these ones are in dbox directory.
I had a similar problem with some dbox compiled by myself, it works fine with a sdl but with other ones it crashed at start up (status window shows an incomplete message: "CONFIG:Loading primary settings from con".

Try this (I don't have an xp english version so don't know if the names are the same):

right-click on dosbox.exe ->Proprieties -> Compatibility -> set "win95" or
"win98/Me".

On my system this setting locks the "status window" on exit, so I can see the errors . After this, the dosbox.exe must be terminated by the tasks manager (ctrl-alt-del).

Reply 9 of 13, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

could you post all your environment settings ?
(startup cmd.exe and type set)

Perharps there are more places for them, but I leave that to someone with winXP installed

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

Reply 10 of 13, by MiniMax

User metadata
Rank Moderator
Rank
Moderator
kapkao wrote:
MiniMax wrote:

Is this just from starting DOSBox? Before you start a game or anything? How do you start DOSBox?

yes, yes, and by clicking on the start menu shortcut or just the exe itself.

But not from a CMD-window?

Try starting DOSBox with

C:\> dosbox -noconsole

and watch for the files stderr.txt and stdout.txt appearing in the working directory.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 12 of 13, by kapkao

User metadata
Rank Newbie
Rank
Newbie
C:\Documents and Settings\xxxxxxxxxx>set ALLUSERSPROFILE=C:\Documents and Settings\All Users APPDATA=C:\Documents and Settings\x […]
Show full quote

C:\Documents and Settings\xxxxxxxxxx>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\xxxxxxxxxxxxx\Application Data
CLIENTNAME=Console
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=xxxxxxxxxxxxxxx
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\xxxxxxxxx
LOGONSERVER=\\xxxxxxxxxxxxxx
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Pro
gram Files\ZipGenius 5;C:\Program Files\UltraEdit;;;C:\Program Files\cvsnt;c:\Pr
ogram Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\ATI Technologie
s\ATI.ACE\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0209
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\xxxxxxxxxx\LOCALS~1\Temp
TMP=C:\DOCUME~1\xxxxxxxxxxx\LOCALS~1\Temp
USERDOMAIN=xxxxxxxx-63B2IXUE
USERNAME=xxxxxxxxxxx
USERPROFILE=C:\Documents and Settings\xxxxxxxxxxx
windir=C:\WINDOWS

Reply 13 of 13, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I don't see anything wrong here.
Do you have the motivation to run some test executables to see how far dosbox comes ?

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