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=\ …

ok,nvm

Get a dependency walker then, A which? :p (I'll look it up later) I think exescope can find these, actually. Either way... 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 …

kapkao wrote: mf2hd wrote: maybe dll corrupted or wrong(?) WHich one/type? actually, knowing the dependencies of Dosbox would simply rock! 😢

mf2hd wrote: maybe dll corrupted or wrong(?) WHich one/type?

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.

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