21 January 2016, 09:04 | #1 |
Posts: n/a
|
WinUAE freezing my OS for 40 secs
Every time I:
1) Start WinUAE emulation 2) Move focus away from WinUAE by clicking the middle mouse button 3) Hit the OK button after changing settings 4) Exit out of WinUAE My entire Win7 desktop hangs/freezes for exactly 40 seconds. The screen freezes, no input is possible until the 40 seconds have elapsed. I was curious to see if this was a visual thing so I started a youtube video running in the background before starting WinUAE. The second I started WinUAE emulation everything froze up as before but the youtube clip's audio kept playing fine. I did notice a curious side effect once the 40 senconds had elapsed: I noticed that the youtube clip's video was playing at an extremely sped up rate while the audio had remained unchanged - like the video was trying to catch up to after being frozen for 40 seconds. This is very strange tbh I was following WinUAE's progress from the very first versions that barely ran on pentium 4s, astounded that someone was brave enough to take on the herculean task of emulating the amiga. Religiously updated my WinUAE revisions right up until 2.610 Never had any issue like this before. Quite a bizarre problem. |
21 January 2016, 09:38 | #2 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
|
Sounds like a driver bug. (It is always driver, OS or hardware bug if non-admin application causes global problems)
Tests: - switch off sound - change D3D <> DirectDraw mode - fullscreen <> windowed Run with -log command line parameter, what is the last few log lines in log window during the hang? Or did the window close? |
21 January 2016, 10:02 | #3 | |
Posts: n/a
|
Quote:
ok, I actually figured it out after using the log parameter. I have a Mayflash DolphinBar adapter. It has this unusual firmware that hangs the system for 40s while it installs drivers that are stored in the firmware itself. I'm not an expert but what I do know is that when I plug in the adapter for the very first time it does this 40s hang. Seems that WinUAE scans for it every time it starts or resumes emulation. Any way to exclude the DolphinBar from the scanning/enumeration list...? Would be a bummer to have to unplug a usb device that has nothing to do with amiga emulation in order to run WinUAE. |
|
21 January 2016, 10:13 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
|
WinUAE only queries input devices at boot and when they change, it is odd if it only happens at shutdown..
Load your usual config, boot it normally, quit emulation, attach both winuaebootlog.xt and winuaelog.txt. |
21 January 2016, 10:25 | #5 | |
Posts: n/a
|
Quote:
(Attached both log files.) |
|
23 January 2016, 13:25 | #6 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,502
|
It probably has something to do with rawinput. Winuae releases rawinput when not active which probably causes this side-effect. Originally it was done to work around some buggy drivers (when Windows XP was new..), it probably is not needed anymore.
Does it stop happening if you use -norawhid command line parameter |
23 January 2016, 21:38 | #7 |
Posts: n/a
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Winuae strange freezing. | villadelfia | support.WinUAE | 7 | 15 July 2014 08:06 |
ATX PSU stops after secs spinning | Retrofan | support.Hardware | 38 | 02 March 2013 19:39 |
WINUAE 1.4.4 freezing | DDNI | support.WinUAE | 3 | 24 September 2007 17:40 |
syndicate freezing | pbareges | support.Games | 5 | 07 March 2007 17:41 |
Freezing UP | Damage | support.WinUAE | 2 | 14 January 2003 14:01 |
|
|