WinUAE 3.3.0 beta series

[Toni Wilen]

Originally Posted by James

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.

Points even more to Amiga side problem. Remove all unnecessary expansions etc.. (including harddrives except boot drive). What kind of AOS installation you have? "Standard" or some heavily patched?

Does same happen if you boot without startup-sequence, run setpatch (or whatever you use to load patches), then boot without startup-sequence again? Does it still crash?

[vagrant]

Originally Posted by Toni Wilen

Beta 16:

- Replaced obsolete Logitech LCD API usage with current version. No other changes, still plain black and white only.

Hi Toni, since this update the lcd output on my G19s is no longer working. I download the latest Logitech software but it made no difference, is there something else I need to update?

[James]

Originally Posted by Toni Wilen

Points even more to Amiga side problem. Remove all unnecessary expansions etc.. (including harddrives except boot drive). What kind of AOS installation you have? "Standard" or some heavily patched?

Heavily patched.
I get no crashes if I switch to an AGA screen and disable RTG emulation (crashes with ZorroII and Zorro III). Tried AmiKIT... no crash.

Originally Posted by Toni Wilen

Does same happen if you boot without startup-sequence, run setpatch (or whatever you use to load patches), then boot without startup-sequence again? Does it still crash?

Got UAEGFX program failed 80000003 after running setpatch (tried to get back to boot screen but think I missed it .

[Toni Wilen]

Originally Posted by ED-209

Hi Toni, since this update the lcd output on my G19s is no longer working. I download the latest Logitech software but it made no difference, is there something else I need to update?

Should be fixed now (with slightly different output). New API does not anymore do b&w -> color conversion automatically and I didn't bother to test it..

Originally Posted by James

Heavily patched.
I get no crashes if I switch to an AGA screen and disable RTG emulation (crashes with ZorroII and Zorro III). Tried AmiKIT... no crash.

Got UAEGFX program failed 80000003 after running setpatch (tried to get back to boot screen but think I missed it .

b2 has absolute no changes that could affect emulation and only b12 change I can see that could have some effect in situation where program accesses invalid memory. Which can break bad code even worse..

uaegfx is just a "loader", something is already broken if it crashes.

Some (or even more) of your patches are broken or don't like to work together. It is normal, not the first or last time it has happened..

[Toni Wilen]

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.

Thanks for the PM hint. It was emulator bug that overwrote part of boot rom data space if conditions were right (enough UAE expansions etc..).

Did you really mean beta 2? Beta 3 does have one change that could have triggered this.

One more beta to do..

[DamienD]

Originally Posted by Toni Wilen

One more beta to do..

Getting there Toni; good to get these small bugs identified / fixed before the major, 6 month long release

...this new 3.3.0 version will be the best / feature rich version so far. I can't wait!!!

Again, we all really appreciate the continued hard work you put into WinUAE. You're a very knowledgeable / skilled / dedicated man and obviously have a passion for all things Amiga (even if sometimes it gives you headaches)

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3300b18.7z
http://www.winuae.net/files/b/winuae64_3300b18.7z

Beta 18: (another possible last beta)

- "ROM needs 68020+" dialog repeated forever.
- Fall back to old GDI screenshot method if GetRenderTarget() fails.
- Logitech color LCDs work again, old API did the conversion automatically.
- Fixed UAE boot ROM trap code corruption if "too many" UAE expansions were enabled. (b3)

[DamienD]

Cheers Toni; will continue testing with this latest beta

[James]

Originally Posted by Toni Wilen

Did you really mean beta 2? Beta 3 does have one change that could have triggered this.

I thought it was beta 2, but I could have been mistaken, or maybe there was some other problem with beta 2 that has already been fixed? Could test it again if you think it is important...

Originally Posted by Toni Wilen

- Fixed UAE boot ROM trap code corruption if "too many" UAE expansions were enabled. (b3)

Working great now, thanks!

[rbm]

Shapeshifter does not work, crashes to a blank screen with no error message. I have just tested all the versions back and the last one that worked is the beta 10

Attached the config file, beta10 and beta18 logs.

[Toni Wilen]

Originally Posted by rbm

Shapeshifter does not work, crashes to a blank screen with no error message. I have just tested all the versions back and the last one that worked is the beta 10

Attached the config file, beta10 and beta18 logs.

You have really complex config.. Remove everything unncessary first (I don't think you need cyberstorm or A2386SX or even PCI bridgeboards to duplicate this)

- Does it happen without JIT?
- Does it happen with 68020 or 68040? (Only b11 change is bug fix that allowed dummy 68030 MMU instruction in 68060 mode)
- Do you have proper 68060.library installed? (c:cpu says "68060 68882")

[Toni Wilen]

Originally Posted by rbm

Shapeshifter does not work, crashes to a blank screen with no error message. I have just tested all the versions back and the last one that worked is the beta 10

Does http://www.winuae.net/files/b/winuae.7z work? (68060 special case for unimplemented instructions was fixed too well..)

Ignore previous post if this fixes it.

[rbm]

Originally Posted by Toni Wilen

Does http://www.winuae.net/files/b/winuae.7z work? (68060 special case for unimplemented instructions was fixed too well..)

Ignore previous post if this fixes it.

Now it works again. Thank you very much !

[Toni Wilen]

Thanks. I think it is time for final 3.3.0 later today.

[DamienD]

Originally Posted by Toni Wilen

Thanks. I think it is time for final 3.3.0 later today.

Awesome

[vagrant]

Originally Posted by Toni Wilen

Should be fixed now (with slightly different output). New API does not anymore do b&w -> color conversion automatically and I didn't bother to test it..

Thanks is working now! Though the new API seems to stretch the lcd display vertically x2 for some reason.
Is it possible to implement green/red color to drive r/w & power led, similar to that of the native on-screen display?

[Toni Wilen]

Originally Posted by ED-209

Thanks is working now! Though the new API seems to stretch the lcd display vertically x2 for some reason.

I did that

It is 2x horizontal, 3x vertical.

Is it possible to implement green/red color to drive r/w & power led, similar to that of the native on-screen display?

Yeah, someday. Including Logitch Arx support.