WinUAE 1.6.1 beta series

[Toni Wilen]

REALLY READ THIS BEFORE POSTING!: http://eab.abime.net/showthread.php?t=26715

Quick(ish) 1.6.1 beta series. Will be mainly 1.6.0 bug fix release.

http://www.winuae.net/files/b/winuae_1610b1.zip

Beta 1

- development PC updated to Intel Core i7 based. (Asus P6T DeluxeV2, i7 920 2.66GHz CPU @ 3.7GHz, 3x2G 1866MHz RAM)
- ASPI crash fixed (calling convention mismatch.. I didn't test and only assumed previous fix would be the only problem left..)
- filesys default codepage changed to default ansi page (1252 breaks many non-european characters)
- added more directory harddrive error codes to Windows->Amiga code translation table (unit not ready, bad unit)
- directory harddrive Windows illegal character handling was broken
- do not capture mouse at startup if window is hidden/minimized
- archive dragging to HD-led really mounts it as a harddrive, even if it contains only disk images
- 1760k HD and 10 sector DD PC formatted had switched internal DD/HD flag (=above image types didn't work)
- FAT12 formatted images supported as a harddrive (uaeunp feature)
- turbo/warp mode in fullscreen mode wasn't as fast as possible

[Retro-Nerd]

Any chances that you add a GUI tickbox for the beta warning message? I KNOW that i use a beta version, this is very annoying.

[Toni Wilen]

Originally Posted by Retro-Nerd

Any chances that you add a GUI tickbox for the beta warning message? I KNOW that i use a beta version, this is very annoying.

No. There is a way but you have to find it yourself. (Anyone posting it here: -> deleted and code changed)

[Kyon]

Toni i tried it and it fixes my aspi problem but game freeze continious maybe thats another bug . i really dont know

[hexaae]

Toni, can you fix the inconsistent behaviour of the checkmark to enable/disable mouse emulation?



When used in conjunction with "Configuration #n" keyboard/mouse remap behaves incorrectly. When you launch WUAE with the checkmark disabled mouse works from Workbench, if you enable it will stop working. Now if you just call WUAE-GUI with F12 on the Input page and press OK (you didn't touch the checkmark!) mouse emulation gets re-enabled (???) and things like these...

[NoX1911]

Beta1 heavily eats up cpu cycles here and freezes when starting up (nothing shows up). There are some free cycles every 5 sec or so, so you can move the mouse somehow from time to time. I could barely manage to start the taskmanager to kill winuae.

I wanted to test if vsync is working again. V1.4.6 is the last one with working vsync.

AMD K7
Radeon9700
XPSP3

[Toni Wilen]

Originally Posted by NoX1911

Beta1 heavily eats up cpu cycles here and freezes when starting up (nothing shows up). There are some free cycles every 5 sec or so, so you can move the mouse somehow from time to time. I could barely manage to start the taskmanager to kill winuae.

There is ALWAYS something. (hint: log. set lower priority etc..)

[Toni Wilen]

Originally Posted by Kyon

Toni i tried it and it fixes my aspi problem but game freeze continious maybe thats another bug . i really dont know

I already said that in other thread. It is not a bug.

Originally Posted by hexaae

Toni, can you fix the inconsistent behaviour of the checkmark to enable/disable mouse emulation?

If you can explain how this is 1.6.1 specific? ("wrong thread")

[hexaae]

Ok, will continue on the other thread...

[NoX1911]

Originally Posted by NoX1911

Beta1 heavily eats up cpu cycles

The log is incomplete. It stops out of a sudden during a line.

I took a quick look with olly. Its not freezing in winuae itself. It somewhat messes with oal. When removing OpenAL32.dll in windows/system32 folder winuae starts up properly. 1.6.0 is not affected.

[Toni Wilen]

Originally Posted by NoX1911

The log is incomplete. It stops out of a sudden during a line.

I took a quick look with olly. Its not freezing in winuae itself. It somewhat messes with oal. When removing OpenAL32.dll in windows/system32 folder winuae starts up properly. 1.6.0 is not affected.

Try -logflush command line parameter, it should fix truncated log (it is not default because it makes startup slower)

EDIT: there are no changes in sound code between 1.6.0 and 1.6.1

[NoX1911]

Yep, that helps. It goes at least some lines further until 'Enumerating OpenAL devices..' now and hangs there.

But its not a winuae bug. I've discovered other apps that suffer from that freezes as well now (adobe audition). The problem is not OAL related. The root seems to be on even lower level.

Strange that it triggers on 1.6.1 only. Whatever... never mind.

[Toni Wilen]

Originally Posted by NoX1911

Yep, that helps. It goes at least some lines further until 'Enumerating OpenAL devices..' now and hangs there.

But its not a winuae bug. I've discovered other apps that suffer from that freezes as well now (adobe audition). The problem is not OAL related. The root seems to be on even lower level.

Strange that it triggers on 1.6.1 only. Whatever... never mind.

Which sound card and which openal version? (full version string from openal32.dll)

[NoX1911]

Soundblaster Live! (CT4670 - VEN_1102&DEV_0002)
Creative driver 6.0.1.1304 - 22.02.2008 WHQL
OpenAL32.dll 6.14.0357.22

Don't follow this bug. My sound subsystem may be corrupt indeed. The SB Live! driver is inf patched (officially for 5.1 only), i've deregistered asio.dll, installed a tuner card lately and the 'Adobe Default Windows Sound' driver is not the friendliest one around as well. There are some points i have to check out first to make sure. Until then its maybe wiser to ignore this bug until proven by at least one another user.

Edit: I reinitialized the sounddriver. The bug is gone. I shouldn't jump the gun when it comes to soundproblems next time.

[exoticaga]

Originally Posted by Toni Wilen

No. There is a way but you have to find it yourself. (Anyone posting it here: -> deleted and code changed)

Anyone posting it here: -> deleted and code changed

On this thread only ? or all of eab forum ?

[Toni Wilen]

Originally Posted by exoticaga

Anyone posting it here: -> deleted and code changed

On this thread only ? or all of eab forum ?

Lets say it this way: if I see it in public _anywhere_, it won't work in following beta

[rsn8887]

Thank you for the new beta!

Turbo/warp mode seems to work correct now in all screenmodes APART from 100 Hz Pal Fullscreen + Vsync. In that mode, it is now different than 1.6.0 release (where it was just slow) but still wacked: The display including on screen LEDs now completely stop updating once warp mode is turned on, e.g. it looks like WinUAE is just hanging, the display is frozen, mouse pointer doesn't move etc. However it is not hanging, when you turn warp mode off again you realize that WinUAE was running in warp mode just fine, it just did so without updating the display at all while it was in warp mode.

[exoticaga]

Originally Posted by Retro-Nerd

Any chances that you add a GUI tickbox for the beta warning message? I KNOW that i use a beta version, this is very annoying.

It's now clear and precise.

If you know it and have been asked to share it. Do so, but don't let Toni see it.

(there's email, pm and other ways to share this info)

[McDuck]

hello,

i cant get this beta to work. 1.6 worked fine. it starts and wenn i select my configurations with a double click. it crashes.
i renamed my winuae.ini and tryed again. just clicked my rom path and choose quickstart and choose a 500 or a 1200. without changing anything else. and pushed start and nothing happens it just crashes with out a warning. winuaelog.txt is empty

[Toni Wilen]

Originally Posted by McDuck

hello,

i cant get this beta to work. 1.6 worked fine. it starts and wenn i select my configurations with a double click. it crashes.
i renamed my winuae.ini and tryed again. just clicked my rom path and choose quickstart and choose a 500 or a 1200. without changing anything else. and pushed start and nothing happens it just crashes with out a warning. winuaelog.txt is empty

Attach the crash dump file and start winuae with -logflush command line parameter to get non-truncated log.

[McDuck]

hi,

hmm Attach the crash dump file < where can i find it ?????????

[TheCyberDruid]

Originally Posted by McDuck

hi,

hmm Attach the crash dump file < where can i find it ?????????

In the folder where the WinUAE exe is with a '.dmp' extension.

[McDuck]

nope sry nothing there. but maybe crashes was the wrong word before. winuae just quits, maybe that describes it better.

[Toni Wilen]

Originally Posted by McDuck

nope sry nothing there. but maybe crashes was the wrong word before. winuae just quits, maybe that describes it better.

Even in windowed mode? No errors, nothing at all?

Try using -log -logflush command line parameters ("winuae.exe -log -logflush"). Log should be more complete this way.

[McDuck]

jup nothing its like hitting the quit button. but it quits a little slower and down on the right in the taskbar stays the winuae symbole and wenn i go down with the mouse it disappears. i opend the task-manager and looked at the prozesse if it is still working in the background but it isnt it just stops. as soon as i hit the start button.

[Toni Wilen]

Originally Posted by McDuck

jup nothing its like hitting the quit button. but it quits a little slower and down on the right in the taskbar stays the winuae symbole and wenn i go down with the mouse it disappears. i opend the task-manager and looked at the prozesse if it is still working in the background but it isnt it just stops. as soon as i hit the start button.

does http://www.winuae.net/files/b/winuae.zip still crash? and if it does, attach -logflush log again please.

[McDuck]

i started winaue looked at the quickstart option a 1200 was selected. look at the rom path with was okay and pushed start. it didnt stop running it came you need a floppy disk. in df0...............which is wiered becouse i have that rom. i push okay it went back to the gui. i rescanned the roms everything okay. all roms there. i push start in comes again i need a floppy disk in df0 to use the system rom replacement. i changed to a 500 pushed start and it just quits like before ?? no crash nothing just quits. started winuae again selected a 1200 pushed start and it just stops.
i just dont understand why this beta dosent work all other betas i downloaded so far worked.

[Marcuz]

try this workaround: in the ROM panel click on the icon next to the drop down menu for the roms, and when the requester appears, choose manually the kickstart you want to use.
you need to save the configuration if you want to use it again.

[Toni Wilen]

Originally Posted by McDuck

i started winaue looked at the quickstart option a 1200 was selected. look at the rom path with was okay and pushed start. it didnt stop running it came you need a floppy disk. in df0...............which is wiered becouse i have that rom. i push okay it went back to the gui. i rescanned the roms everything okay. all roms there. i push start in comes again i need a floppy disk in df0 to use the system rom replacement. i changed to a 500 pushed start and it just quits like before ?? no crash nothing just quits. started winuae again selected a 1200 pushed start and it just stops.
i just dont understand why this beta dosent work all other betas i downloaded so far worked.

I don't understand it either because it works fine here and there has not been any rom-related changes..

Perhaps it is some specific rom that causes this issue.. Try clearing your rom directory and only leave normal ks 1.3 rom and testing again.

[Toni Wilen]

http://www.winuae.net/files/b/winuae.zip updated. Another -logflush log please.

[Marcuz]

winuae still quits when pressing start button (paths are correct, "start in quickstart mode" on, quickstart mode, choose whatever rom from the drop down menu, press start ---> quits)

[Toni Wilen]

Problem found (supposedly "unrelated" uaeunp file handling update). Only (?) happens when loading zipped cloanto roms.

[Toni Wilen]

http://www.winuae.net/files/b/winuae.zip should fix the problem (brown paper bag quality bug), please confirm.

[McDuck]

jup works. thanks tony your are the best there is and there ever will be

[Toni Wilen]

http://www.winuae.net/files/b/winuae_1610b2.zip

Beta 2:

- fs "double vsync" mode (100Hz+) was still slow in warp mode (note D3D mode will stay "slow" because afaik it is not possible to switch D3D vsync on/off on the fly)
- added warp mode to configuration file (warp=true/false, config file read-only)
- and another read-only configuration entry, "headless" that switches invisible emulation mode (window gets hidden). future feature..
- log window scrollback buffer increased to 900 lines
- command prompt "console wrapper" support (run winuae in command prompt: output goes to command prompt window, does not open separate log window) More information later, not important just yet..
- saving configuration after modifying input-panel autofire setting caused modified input event to be saved incorrectly (old bug)
- display scaling does not anymore change D3D filter scanline scaling
- unicode conversion broke magic mouse
- uaeunp file handling update broke some archive operations (b1)
- loading config from command line with GUI enabled didn't override quickstart (if enabled)
- added "toggle" option to input panel. First button/key press = emulated button is pressed and kept down. Second button/key press = emulated button is released

[andreas]

Originally Posted by Toni Wilen

- added "toggle" option to input panel. First button/key press = emulated button is pressed and kept down. Second button/key press = emulated button is released

Thanks for this !
This is a great option - you're really about to make a MESS out of WinUAE!
Ohh...did I say something wrong?

Not really, because MESS stands for Multi Emulation Super System in which this feature was implemented long ago (iirc activated by Scroll Lock key)

[rsn8887]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae_1610b2.zip
- fs "double vsync" mode (100Hz+) was still slow in warp mode (note D3D mode will stay "slow" because afaik it is not possible to switch D3D vsync on/off on the fly)

Warp mode seems to work fine now also in 100Hz. Awesome! Sometimes, the fps on-screen LED shows "C00" or something like that here. It is not a number for sure. Maybe it means "bigger than 999" or maybe it is a bug?

[hexaae]

WUAE b2 crashes trying to connect with AmiGift2.0: http://amigift.sourceforge.net/
To reproduce the bug boot from 3.1+ WB and run AmiGift 2.0. Click on the "Connect" button: after a failure error WUAE crashes. I use WUAE's bsdsocket emulation and IBrowse, YAM, AmiNetRadio etc. do work flawlessly.

[Toni Wilen]

Originally Posted by hexaae

WUAE b2 crashes trying to connect with AmiGift2.0: http://amigift.sourceforge.net/
To reproduce the bug boot from 3.1+ WB and run AmiGift 2.0. Click on the "Connect" button: after a failure error WUAE crashes. I use WUAE's bsdsocket emulation and IBrowse, YAM, AmiNetRadio etc. do work flawlessly.

Thanks. Ancient (yet another) bug in win32 bsdsocket...

[Toni Wilen]

http://www.winuae.net/files/b/winuae_1610b3.zip

Beta 3: (almost final 1.6.1)

- added exception handler that writes log message if openal or portaudio device enumeration crashes
- fixed d3d pot/square texture restriction check, only for really old display cards (which may be too slow for d3d filter..)
- bsdsocket cleanup crash fix (ancient win32-specific bug)
- gzip decompression problem (yet another unicode conversion bug), also broke built-in hrtmon (which is gzipped internally)
- reset fpu rounding state to original temporarily when doing filter calculations (single pixel jittering in some filtering modes if Amiga-side code uses FPU and modifies rounding mode)