Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

Make a New PostPrevious ThreadView All ThreadsNext Thread*Show in Threaded Mode


SubjectWeird DOSbox problem new Reply to this message
Posted byRoushiMSX
Posted on12/19/07 11:34 PM



Ok, I ran into a DOSbox problem that I've never experienced today. Hopefully one of you peeps can help out. When I fire up DOSbox, it runs stuttery/shitty/slow. I can't figure out why.

Previously, everything worked fine. Timesynched was enabled, cycles were either auto or hand tweaked to whatever I wanted, core was either dynamic/auto/normal depending on what I was trying to run, etc. In short, it didn't matter what I tried to play before, everything was fine.

Today, all of that shit changed. At first, I thought it was just my dosbox.conf getting fucked up, so I nuked it and built a fresh one. Even on a fresh dosbox.conf with the cycles set to a paltry 3k, it'll run like doodie. I'm not even talking about ingame, here. This is well before then when you're still staring at the CLI.

- I checked Task Manager to see if anything else was robbing cycles, but I've still got ~96% free.

- I updated my DirectX Runtimes for shits n grins (using Direct3d output, but surface/overlay/opengl all have the same problem)

- I tried downgrading to the last stable/official release instead of using a more recent CVS build. Tried rolling back a few versions (to 0.70). Same problem.

- I disabled any antivirus software. Never caused a problem before, but fuck, figured killing it would be worth a try anyway. Killed Trillian too, since it will rarely do something silly like this. Started disabling every background process I could.

It did briefly work fine for a little bit for no apparent reason. Played a little bit of Blood and worked my way through a couple of Duke Nukum levels, but then performance went right back to shit and once again it would run fine, pause, run fine, pause, etc.

Has anyone else had this same problem and know of how to fix it? Kinda bumming me out over here :(




SubjectTry with this new Reply to this message
Posted bynewsdee
Posted on12/20/07 02:26 AM



Task manager doesn't give you the full story. There could be some system or other hidden processes eating away CPU time.

Check Process Explorer here:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
, it may spot something else going on.

You can double-click on a process to get a bunch of details... it also shows you what files are being opened by a process (handy in some situations).




[download a life]


SubjectHardware Interrupts? Reply to this message
Posted byRoushiMSX
Posted on12/20/07 08:56 AM



Ok, so running that I see Hardware Interrupts bumping up past everything and sucking down 15-45% of CPU time....sometimes. When it's happening, DOSbox runs like doodie. When it doesn't happen, DOSbox runs smooth as a baby's ass (in and out of game).

More often than not, the hardware interrupts are running as soon as I fire up DOSbox (like, there's only been a small handful of times when they weren't).

If I manually set the cycles to max, timesynched to on, and core to auto in the GUI after firing up DOSbox then it runs ok, though at that point it's sucking up over half of my CPU....no telling if it'll still be "ok" when I try to play a more demanding game than Duke Nukum or Raptor... I'd do more performance testing, but at this point I'm honestly happy that I can just play Duke Nukum reliably for the time being.

Thinking that it just might still be driver related, I went ahead and reinstalling my graphics and sound card drivers with the latest versions. Figured it was worth a shot but it didn't change anything. I'm teh stumped.




SubjectJoypad Driver ? new Reply to this message
Posted byTi-BOne
Posted on12/20/07 09:44 AM



I donīt know what you use, and most controllers today are USB, which should guarantee a smooth performance.
However, a bugged driver can cause that.

I had a usb printer at work, that, when plugged in, it would ear about 80% of cpu ,without being used.

I would try to disconnect every single non-necessary thing.
Like, controllers, cameras, pen drives, printers anything that might be started when DOSBOX starts.

My bet would be a faulty controller driver.

I guess itīs worth the shot.


Also, what soundcard do you use?
Try swtiching between ASIO and WDM drivers.
For my SB, it has to be ASIO, otherwise, performance is shit. (but since i use my pc to record, soundcard performance is big to me).



> Ok, so running that I see Hardware Interrupts bumping up past everything and
> sucking down 15-45% of CPU time....sometimes. When it's happening, DOSbox runs
> like doodie. When it doesn't happen, DOSbox runs smooth as a baby's ass (in and
> out of game).
>
> More often than not, the hardware interrupts are running as soon as I fire up
> DOSbox (like, there's only been a small handful of times when they weren't).
>
> If I manually set the cycles to max, timesynched to on, and core to auto in the
> GUI after firing up DOSbox then it runs ok, though at that point it's sucking up
> over half of my CPU....no telling if it'll still be "ok" when I try to play a
> more demanding game than Duke Nukum or Raptor... I'd do more performance
> testing, but at this point I'm honestly happy that I can just play Duke Nukum
> reliably for the time being.
>
> Thinking that it just might still be driver related, I went ahead and
> reinstalling my graphics and sound card drivers with the latest versions.
> Figured it was worth a shot but it didn't change anything. I'm teh stumped.
>



Previous ThreadView All ThreadsNext Thread*Show in Threaded Mode