WinUAE 3.3.0 beta series

[ReadOnlyCat]

Originally Posted by Toni Wilen

32-bit is still main version. There still can be some 64-bit only issues remaining, they get slowly fixed one by one..

Are there specific areas to test where you think the 64 bit pointer bugs might lurk in particular?

-"Atari ST palette fix" added to Display panel, called "Dark palette fix". It is wrong to mention Atari ST in GUI There are few stupid Atari ST ports that use original palette (3 bits/component) = halved brightness in Amiga.

Nice, but this has to be the most depressingly necessary option ever.

[Toni Wilen]

Originally Posted by AMIGASYSTEM

OK, for further confirmation attaching a screenshot, I also noticed a default floppy, but I do not know if it's due to you.

Nothing has changed, it has always been like that.

Originally Posted by ReadOnlyCat

Are there specific areas to test where you think the 64 bit pointer bugs might lurk in particular?

Yes and no. Everywhere.

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Nothing has changed, it has always been like that.

They are my 61 years that are taking their toll !

Up to version 3.3.0 Beta 1 on Quickstart, any model Amiga had chosen the default settings of the Keyboard and Mouse

Now from version 3.3.0 Beta 2 settings will Quickstart i'm up "None"

[Toni Wilen]

Originally Posted by AMIGASYSTEM

They are my 61 years that are taking their toll !

Up to version 3.3.0 Beta 1 on Quickstart, any model Amiga had chosen the default settings of the Keyboard and Mouse

Now from version 3.3.0 Beta 2 settings will Quickstart i'm up "None"

Note that I quoted only "default floppy" part of you reply. Default floppy has always been like that.

I wasn't talking about mouse/joystick defaults.

[turrican3]

thanks Toni !!!! Happy to see microcosm in gray !!

[AMIGASYSTEM]

Originally Posted by Toni Wilen

Note that I quoted only "default floppy" part of you reply. Default floppy has always been like that.

I wasn't talking about mouse/joystick defaults.

Excuse Toni, it is guilty of a bad translation

[mark_k]

Originally Posted by Toni Wilen

- "Atari ST palette fix" added to Display panel, called "Dark palette fix". It is wrong to mention Atari ST in GUI There are few stupid Atari ST ports that use original palette (3 bits/component) = halved brightness in Amiga.

Is the current code for that less than ideal? Atari ST white will end up less bright than it could be. In gfxutil.cpp you have:

if (currprefs.gfx_threebitcolors)
	vi *= 2;

Atari ST white = $777. Shifted left by one bit that maps to Amiga colour $EEE which maps to 24-bit $EEEEEE. OK so far. However, if mapping 3-bit directly to 8 bit, you could map each component value %xyz to %xyzxyz00.

In other words Atari white $777 could/should map to 24-bit RGB $FCFCFC

[Toni Wilen]

Originally Posted by mark_k

Is the current code for that less than ideal? Atari ST white will end up less bright than it could be.

There is no absolute correct solution.

Current matches what you would see when game is fixed to work with OCS/ECS system (where you can't do linear 000 to FFF mapping without ugly color fades = 000 222 .. EEE is the best choice. Black should be black, less than full brightness white is fine), not what Atari ST would show. Both options are unfortunately correct.

[mark_k]

But you can do it so Atari ST white (Amiga $777) maps to 24-bit $FCFCFC which is better than $EEEEEE. Instead of
vi *= 2;
do
vi = (vi + vi&7)*2;

(I guess that could alternatively be implemented in a GPU shader?)

By the way... what is the "resolution" of the BPLCON0 COLOR bit? The A1000 schematics I found online aren't very clear. If COLOR is 0 during the colour burst period of the scanline (i.e. between sync pulse start of active part of the line), then there being no colour burst, will a real NTSC monitor show the whole line as monochrome, even if COLOR is set to 1 at some point later in the scanline?

[Toni Wilen]

Originally Posted by mark_k

But you can do it so Atari ST white (Amiga $777) maps to 24-bit $FCFCFC which is better than $EEEEEE. Instead of
vi *= 2;
do
vi = (vi + vi&7)*2;

I know but I only wanted to add one option. Ok, option moved to Brightness/Contrast/etc select box and both options added

(I guess that could alternatively be implemented in a GPU shader?)

Yes but it is not my problem.

By the way... what is the "resolution" of the BPLCON0 COLOR bit? The A1000 schematics I found online aren't very clear. If COLOR is 0 during the colour burst period of the scanline (i.e. between sync pulse start of active part of the line), then there being no colour burst, will a real NTSC monitor show the whole line as monochrome, even if COLOR is set to 1 at some point later in the scanline?

I assumed it is scanline based, didn't bother to test because it probably depends on monitor or other more mysterious things..

EDIT: I forgot that my A1000 has NTSC composite encoder but PAL Agnus and NTSC main crystal = can't really test this..

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3300b4.7z
http://www.winuae.net/files/b/winuae64_3300b4.7z

Beta 4:

- Default game ports config without default.uae (Mouse + keyboard layout A) was not set. (b3)
- On the fly input device change crash fix. (b3)
- Monochrome mode config file entry added.
- Atari ST dark palette fix moved to Brightness/Contrast/etc select menu and added alternate mode.
- UAE expansion resident structures are now injected to execbase ResList. Now less important expansions are initialized later. Previously all were initialized during diag init time. Now also uses normal RTF_AFTERDOS resident to start clipboard sharing instead of ugly hack.
- Simplified rawinput support, also removed rawinput checks, added when long time ago WINE didn't fully support rawinput.
- Added harddrive master write protection checkbox to Misc panel. WARNING: don't use it with hardfiles unless you know exactly what you are doing.
- UAE Boot ROM with PPC native OS message now asks to enable correct boot ROM mode.

OS4 UAE expansion updates: (Use this thread: http://eab.abime.net/showthread.php?t=81146 for this topic!)

- Clipboard sharing is now supported.
- Magic mouse is now supported.
- Virtual mouse driver is now supported.
- uaenative.library converted to new trap system but not tested.
- uaescsi.device initialization converted to new trap system, device will open now without crashing but any CD access commands will not work (and most likely will also crash strangely).

Still not supported:

- Directory filesystem on the fly insertion/removal, including CDFS CD swaps. Getting this to work will be extremely complex task. Not sure if it is worth the trouble. Unless I get lots of donations
- bsdsocket.library
- uaeahi (Probably not needed, PCI sound card emulation is better choice)

[Retro-Nerd]

Beta 4:

There something wrong with the joyport settings. The set joystick/joypad always automatically switches back to Keyboard Layout A in port 2.

[Arnie]

B4

No quickstart config settings are loaded.

CDTV set to 3.2.2 defaults boots to red screen (ala ext rom 2.3)

Can't boot hdf's on default CDTV either.

EDIT: doesn't red screen any more. (I did previously use a WB1.3 floppy to test if any drives were detected using info)

[Toni Wilen]

Originally Posted by Arnie

B4

No quickstart config settings are loaded.

CDTV set to 3.2.2 defaults boots to red screen (ala ext rom 2.3)

Can't boot hdf's on default CDTV either.

EDIT: doesn't red screen any more. (I did previously use a WB1.3 floppy to test if any drives were detected using info)

What? Some much better descriptions are needed..

[DamienD]

Originally Posted by Retro-Nerd

Beta 4:

There something wrong with the joyport settings. The set joystick/joypad always automatically switches back to Keyboard Layout A in port 2.

Yup, definitely an issue with Game Ports

Here's a good example where I can replicate everytime... Let's take "Roketz [AGA]": http://eab.abime.net/showthread.php?t=81349

In my config I have the following set; Port 1 = Keyboard B, Port 2 = Keyboard A:



I start the game, "PPMore" displays the "Readme" file, I press the <Space Bar> to start the text scrolling, press <F12> to look at the Game Ports and they've now changed to; Port 1 = Windows Mouse, Port 2 = Keyboard A:



I haven't even used the mouse / pressed any mouse buttons...

Anyway; logs attached Toni.

[Arnie]

Originally Posted by Toni Wilen

What? Some much better descriptions are needed..

All quickstart configs have A500 settings, no model specific settings are loaded.

Using a quickstart CDTV, (with the correct setting from 3.2.), no hdf HD will boot.

[Toni Wilen]

Originally Posted by Arnie

All quickstart configs have A500 settings, no model specific settings are loaded.

I understand but "works for me" = more information needed, how do you select it, using set configuration button or quickstart mode active, do you have default.uae or not and so on.

[Toni Wilen]

winuae.7z should fix game port selection.

I can't see any difference with CDTV + HDF compared to previous version = config needed.

[DamienD]

Originally Posted by Toni Wilen

winuae.7z should fix game port selection.

You mean the version from here: http://www.winuae.net/files/b/winuae.7z

...indeed it does (using the same "Roketz" test anyway)

[Retro-Nerd]

Yep, it's working again. Thanks for the fast fix, Toni.