WinUAE 1.6.1 beta series

[McDuck]

hi,

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

[TCD]

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)