WinUAE 2.2.0 beta series

[SailorSat]

Originally Posted by Toni Wilen

- floppy sound channel mask added, configuration file only (floppy_channel_mask), default is all channels. 1=left,2=right,4=center,8=sub,16=surleft,32=surright.

made my day

[Dunny]

Originally Posted by Toni Wilen

Gameports = "view only" mode (used to store gameports configuration, not allowed to edit because it would confuse everyone when gameports starts doing weird things). Use Configuration #1 (or #2 or #3)

Yep, got it now - thanks!

"Test" does not hang, read the GUI window title

It says that you can skip or exit with F12, but those keys do nothing - I have to hit the Windows key or alt-tab to jump out of WinUAE and then back to it. ISTR that this was reported before, I'll re-read the thread to see what I should be doing.

D.

[Toni Wilen]

Originally Posted by Dunny

It says that you can skip or exit with F12, but those keys do nothing - I have to hit the Windows key or alt-tab to jump out of WinUAE and then back to it. ISTR that this was reported before, I'll re-read the thread to see what I should be doing.

D.

winuaebootlog.txt please

EDIT: start winuae normally, click "test", exit by pressing alt-tab, exit winuae, attach winuaebootlog.txt.

[Dunny]

Originally Posted by Toni Wilen

winuaebootlog.txt please

EDIT: start winuae normally, click "test", exit by pressing alt-tab, exit winuae, attach winuaebootlog.txt.

Here you go!

I set up WinUAE's default config to have the autofire/non-autofire setup, enabled logging in the misc panel, then booted to the default screen (no disk in the drive) - running fullwindow mode.

Hit F12 to bring up GUI, navigated to "Input", chose "Keyboard" (config #1 already selected), found "right ctrl", hit "test".

Locked up - alt-tabbed to debug console window, then alt-tabbed back to WinUAE, then quit directly.

Logs attached:
winuaebootlog.txt

winuaelog.txt


D.

[Toni Wilen]

Originally Posted by Dunny

Here you go!

I set up WinUAE's default config to have the autofire/non-autofire setup, enabled logging in the misc panel, then booted to the default screen (no disk in the drive) - running fullwindow mode.

Hit F12 to bring up GUI, navigated to "Input", chose "Keyboard" (config #1 already selected), found "right ctrl", hit "test".

Locked up - alt-tabbed to debug console window, then alt-tabbed back to WinUAE, then quit directly.

Do it without starting emulation first. Still hanging?

btw, winuaebootlog.txt is truncated.

[Dunny]

Originally Posted by Toni Wilen

Do it without starting emulation first. Still hanging?

btw, winuaebootlog.txt is truncated.

Without starting emulation, all is fine - F11 and F12 work without problems. It's only when emulation is running.

I'll get another bootlog for you.

winuaebootlog.txt
winuaelog.txt

Bootlog ends with "Log (enabled): 'E:\Games\WinUAE\winuaelog.txt'" - no more is logged after that point.

EDIT: By "Hanging", I mean that the F11/F12 keys do not respond. The testing is still working - I can see the listview respond to mouse movements, if "mouse" is selected in the top combobox.


D.

[Toni Wilen]

http://www.winuae.net/files/b/winuae.zip should fix directinput test/remap hang if emulation is already running, please confirm.

[Dunny]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.zip should fix directinput test/remap hang if emulation is already running, please confirm.

Yep, works fine. Just one suggestion - if I hit "remap", and I have the keyboard listed, if I knock my mouse it jumps to the "mouse" page in the upper-right combobox. Other than that, it all works fine now. Thanks, Toni.

D.

[Toni Wilen]

Originally Posted by Dunny

Yep, works fine. Just one suggestion - if I hit "remap", and I have the keyboard listed, if I knock my mouse it jumps to the "mouse" page in the upper-right combobox. Other than that, it all works fine now. Thanks, Toni.

It is by design. Remap or Test is not restricted to currently selected device.

[Toni Wilen]

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

Beta 11: (RC2)

- DirectInput keyboard and mouse didn't work in Test/Remap mode after emulation was started
- directory filesystem GUI directory/file selection dialog remembers previous path
- floppy sound disabled channels had different volume level
- XP DX check reverted, for some reason DirectX web installer didn't install all DLLs (including d3dx9_43.dll) when it was released originally, seems to be fixed now
- uaescsi.device: do not send media change interrupt if actual media state didn't change (was possible when changing cdimage0 using uae-configuration), some cd filesystem versions crash(!) in this situation..., fix media detection when switching on the fly from SCSI mode to built-in image mounter. Note that on the fly device changes only works properly if CDFS uses trackdisk.device-style commands (not directscsi) and media change interrupts are enabled (not polling)
- cdimage0= in config file (nothing after '=') means enable built-in image support without media inserted, do not detect and use physical/virtual drives
- renamed pad/joystick POV pairs (1) and (2) to (X) and (Y)

[msayed1977]

Only in the latest betas:
Once the title screen of "Kick Off 2" comes, it appears as if it moves at a glance from the right side of the screen to the center.
I conclude that the horizontal centering is done after displaying a different display mode.
Please fix.
Thanks Toni.

[Toni Wilen]

Originally Posted by msayed1977

Only in the latest betas:
Once the title screen of "Kick Off 2" comes, it appears as if it moves at a glance from the right side of the screen to the center.
I conclude that the horizontal centering is done after displaying a different display mode.
Please fix.
Thanks Toni.

?Crystal ball error. What kind of configuration?

[Toni Wilen]

Originally Posted by Toni Wilen

(official release before Midsummer)

Release date will be delayed by few days. (this has nothing to do with above issue)

[msayed1977]

Originally Posted by Toni Wilen

?Crystal ball error. What kind of configuration?

I have attached my configurations.
Know that this bug happens so quickly. You can hardly recognize it.

[Toni Wilen]

Originally Posted by msayed1977

I have attached my configurations.
Know that this bug happens so quickly. You can hardly recognize it.

EDIT: never mind. for some reason I missed the real configuration file

Did you use quickstart? If you did, save the config manually and attach it, file you attached contains multiple configuration files.

[Toni Wilen]

Originally Posted by msayed1977

Only in the latest betas:
Once the title screen of "Kick Off 2" comes, it appears as if it moves at a glance from the right side of the screen to the center.
I conclude that the horizontal centering is done after displaying a different display mode.
Please fix.
Thanks Toni.

This isn't a bug. Previously display was always "centered", even if there was no display (display was totally off-screen, only very small part of right border was visible on left border, this also hide possible background color copper effects and/or sprites).

Now centering is only enabled when display is active = non-centered display is visible for one frame before centering activates (and previously it was hidden in left border)

[Toni Wilen]

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

Beta 12: (RC3, final on monday)

- directory filesystem action_read/action_write with length=0 special handling added (host OS routines may have returned weird errors in some situations)
- monitor "bezel" overlay image support added, direct3d and configuration file only. gfx_filter_overlay=<path>:x,y,width,height (only path is mandatory) x and y: position of overlay relative to top/left corner. -1 = center, value% = relative to window size. width and height: width of overlay image. -1 = scale to window size, 0 = use original size, > 0 = scale to this size. value% = scale to window size + %adjustment.

[alanwall]

Hi Toni, beta 12 does not finish loading for me using AmiKit ?
attached are logs/screenshot

[Toni Wilen]

Originally Posted by alanwall

Hi Toni, beta 12 does not finish loading for me using AmiKit ?
attached are logs/screenshot

Filesystem update had small bug, dos error field was not cleared when read length was zero (I thought it was automatically cleared by filesystem code, it wasn't and previous value was returned to caller resulting in setpatch failing to load rom updates)

At least one last minute bug found, thanks

http://www.winuae.net/files/b/winuae.zip fixes it.

[alanwall]

Thanks ! That fixed it