WinUAE 3.3.0 beta series

[Toni Wilen]

I optimized one RTG function a bit and then forgot about it (not in changelog either)..

http://www.winuae.net/files/b/winuae.7z should fix it.

[Diz_57]

I was just about to post a crash log... DOpus5 as WB replacement crashed WinUAE with an access violation when i had a background picture set... but that new beta fixed it just seconds before i was gonna post! lol

[jotd]

And the french keyboard is now automatic for me in HRTMon thanks!!

[emufan]

I think I also have an issue related to RTG scaling.
the result of the following are not very good readable texts under icons or in the shell - on that rtg screen:

I made two screenshots - one from within winuae ( print key )
and the second just some seconds later windows screenshot (alt + print key)

the left one from within winuae looks good, protection lines all look the same.
the right one - windows-screenshot - you can see the lines are different size.
also the numbers and letters are different rendered.

what i see, when i use workbench on rtg is what the windows screenshot looks like.
while the internal screenshot of winuae looks very good.

scale the image in a pixel paint program to see it better

just wanted to report, is it worth to make some more tests?

the more improtant thing :
Wb size is 800x600 and windowed it larger: 1216x 958
but whatever values i try larger than the workbench's 800x600 it does not looks crisps, allways blurry.

forgive my ignorance - if this is normal - then ignore.
just scaled the window to me needs.

windowed size is 1216x989

[Dunny]

Have you seen what happens when you move the window up and down, emufan? You'll need full-window dragging enabled of course.

[emufan]

Originally Posted by Dunny

Have you seen what happens when you move the window up and down, emufan? You'll need full-window dragging enabled of course.

not sure, if i understood, but i made a little video. it is the region from my images above.
Workbench 800x600 and the Windowed size starts with 800x600 as well.
when you see lines moving up or down, I do move the workbench shell window.
after a short black image i was scaling the winuae window, and make it a bit larger
several times.
at the end i scale the winuae window again to 800x600.

here is the link to the video at sendvid - is a cool and fast videohoster, no need to make an account.

#1) if these are known scaling/aspectratio problems, then tell me and all is ok

[Toni Wilen]

Originally Posted by emufan

Wb size is 800x600 and windowed it larger: 1216x 958 but whatever values i try larger than the workbench's 800x600 it does not looks crisps, allways blurry.

It is normal. Any non-integer scaling value equals blurriness or sharp image with missing/doubled pixels. (Depending on filter settings)

(Guaranteed nothing to do with 3.3 betas!)

[AlexC]

Originally Posted by Toni Wilen

I optimized one RTG function a bit and then forgot about it (not in changelog either)..

http://www.winuae.net/files/b/winuae.7z should fix it.

Yes it did :-)

[mark_k]

There seems to have been some regression in shared directory support on Kickstart 1.2.

The attached config is A500/Kick1.2/512K+512K with a shared directory configured, which is read-only and not bootable.

For testing I booted from a WB 1.2 disk, pressed Ctrl-D to interrupt the startup-sequence, then typed these CLI commands:
> CD SHARE:Work/TST.L_test (that dir exists and there are a couple of files in it)
> Dir

3.2.2: seems to work OK
3300b2: seems to work OK

3300b3: on typing Dir, get a Software failure requester. Log output:
Illegal instruction: 00c0 at 00000004 -> 00FC07E0

3300b4 and later: does not begin to boot from floppy, get flashing power LED then alert #00000004.00C01570
Log output:
filesystem: diagentry 00c04628 configdev 00000000
Illegal instruction: 00c0 at 00C04682 -> 00FC07E0

[Toni Wilen]

Originally Posted by mark_k

There seems to have been some regression in shared directory support on Kickstart 1.2.

Fixed. New resident list injection (b4) overwrote pre-KS1.3 hack data and code.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3300b17.7z
http://www.winuae.net/files/b/winuae64_3300b17.7z

Beta 17: (Perhaps last or second to last beta)

- Pre-KS1.3 boot hack code and data was overwritten by new resident structure update in b4.
- PlanarToDirect RTG optimization fixed. (b16 included forgotten borken version).

[emufan]

Originally Posted by Toni Wilen

It is normal. Any non-integer scaling value equals blurriness or sharp image with missing/doubled pixels. (Depending on filter settings)

(Guaranteed nothing to do with 3.3 betas!)

ok, I understand - I thought I found something special :]

[Mclane]

Originally Posted by emufan

ok, I understand - I thought I found something special :]

You presumed to know better than the great Wilen!

He shall cast you into the soul less dungeons

Happens to us all, you think you have found something and then Toni brings you back to earth with a bump..

[AlexC]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae_3300b17.7z
http://www.winuae.net/files/b/winuae64_3300b16.7z

Beta 17: (Perhaps last or second to last beta)

- Pre-KS1.3 boot hack code and data was overwritten by new resident structure update in b4.
- PlanarToDirect RTG optimization fixed. (b16 included forgotten borken version).

The second link probably was meant to be:

http://www.winuae.net/files/b/winuae64_3300b17.7z

[DamienD]

Hello Toni,

Another post that I wasn't sure where to place; I think it's beta related... it's also a little hard to describe...

Anyway; as a test with one of my configs I have selected 800% floppy drive emulation speed. The disks I'm testing extract files from an .LZX archive.

With WinUAE v3.2.2 all works perfectly but if I use the latest beta when extracting the .LZX it will fail at the last file I guess. If I then set to 400% floppy drive emulation speed in the latest beta it works again.

Nothing in terms of the floppy drive emulation speed / process has changed in the betas has it?

[DamienD]

Heya Toni,

Don't worry about looking into the above...

When I tested on another Windows 7 computer the issue is as above.

I'm now home and have tested on my own Windows 7 laptop with the latest beta 17 and all is good

Anyway; I think the issue is really with .LZX extraction and not WinUAE. It doesn't always like 800% floppy drive emulation...

Of course in the real world you wouldn't set this and even if you did I know that it can sometimes cause issues.

[emufan]

Originally Posted by Mclane

You presumed to know better than the great Wilen!

He shall cast you into the soul less dungeons

Happens to us all, you think you have found something and then Toni brings you back to earth with a bump..

hehe, I keep trying, one way or the other

[James]

With betas 12-17 WinUAE crashes on reset with my main config (No crash with a simpler config). Betas 2-11 crash on boot with this config. It boots and resets OK with beta 1.

winuaelogs.zip

[Toni Wilen]

Originally Posted by DamienD

Anyway; I think the issue is really with .LZX extraction and not WinUAE. It doesn't always like 800% floppy drive emulation...

You need to find repeatable test case. (LZX decruncher is reverse-engineered one so it can have unknown corner cases)

Originally Posted by emufan

hehe, I keep trying, one way or the other

But don't try too hard

Originally Posted by James

With betas 12-17 WinUAE crashes on reset with my main config (No crash with a simpler config). Betas 2-11 crash on boot with this config. It boots and resets OK with beta 1.

Looks like timing sensitive (not that rare) Amiga-side bug (some utility/patch/etc). It has the usual signs, first accesses of non-existing memory and finally CPU jumps to non-existing memory that JIT don't always like and b2 changes are too minimal.

Usual test: Try without JIT. Try with more compatible ticked. Try without Z3 fast, only mainboard fast. Attach your config.

[James]

Originally Posted by Toni Wilen

Usual test: Try without JIT.

WinUAE did not crash, but I got an 80000003 guru followed by an 80000006, and then an 80000003 again. Screen then went black and did not boot.

Originally Posted by Toni Wilen

Try with more compatible ticked. Try without Z3 fast, only mainboard fast.

Makes no difference.

Config.zip