WinUAE 1.3 crashing

[Tony Landais]

My configuration for Amigasys3 is crashing WinUAE. It actually freezes the PC and needs rebooting.
I noticed aswell WinUAE can't save the resolution 1920 * 1200 and always come back to 1280 *1024 then even if I am configurated for a fullscreen resolution I have the message :
"the selected screenmode can t be displayed in a window, because the desktop is too small..."
My resolution is 1920 *1200 and it used to work in WinUAE 1.2

[Toni Wilen]

I think the question is: Does it work in 1280x1024? (Do you have enough RTG memory enabled? and can Workbench/P96 even support resolutions over 1280*1024?)

btw, there is other possible reason for crashing: make sure you don't have >1M bogo RAM in AGA configuration (Having bogo RAM in AGA mode is totally bogus configuration in my opinion, no wonder I didn't notice it..) because now it crashes due to address conflict in JIT-mode (Gayle address space conflict).

Bogoram size will be limited to max 1M in next version if AGA is enabled.

[Tony Landais]

I just checked and I don t use bogo ram and I don t try to open a workbench in 1920, but just a fullscreen resolution to keep a good 16/9 ratio. My Amigasys is viewed in a window of 1024*768
well I suspect a bug because it crashes only if I start straight with my amigasys configuration. But if I start a simple A500 emulation then return to the panel and start my amigasys config it works.

[thomas]

Check the uaescsi settings on the Misc page. Choose SPTI instead of ASPI and test if it still crashes.

Also check ROM settings after loading a config. If it shows the path instead of the name (i.e. "C:\blabla\kick310.rom" instead of "KS 3.1 Cloanto..."), then choose the ROM's name from the list and test if it still crashes.

[Tony Landais]

It s Nero Aspi that created the crash!
Thank you for the suggestions.
Crash is solved but I still have my resolution problem to fix

[quote=Toni Wilen]I think the question is: Does it work in 1280x1024? (Do you have enough RTG memory enabled? and can Workbench/P96 even support resolutions over 1280*1024?)

quote]

Sorry Toni. I think the question is, what's the mainproblem of V 1.3.
All my Configs doesn't run under V 1.3 (see another thread).
After reinstallation of V 1.2 they run successfully.

So, V 1.3 doesn't have only a screensize-problem.

Kind regards,
Ulli

[Toni Wilen]

Originally Posted by ulli.amitown

Sorry Toni. I think the question is, what's the mainproblem of V 1.3.
All my Configs doesn't run under V 1.3 (see another thread).
After reinstallation of V 1.2 they run successfully.

This is different thing. OP's problem was ASPI and display (if width > 1280).

Another known problem: Some Kickstarts (A4000, maybe others) will freeze if AGA is not enabled.

[Mad-Matt]

1650x1080 isnt a problem for workbench/p96, working fine in the later winuae versions. I suspect the problem is that the 1920x res is being set in the winua display prefs ? which shouldnt need to be any higher then 800x600 for both window and fullscreen.

One issue thats annoyed me in every winuae version is that icons flicker or break up abit while dragging (mostly noticable with newicon/coloricon.). It kinda looks like vsync issue maybe is there anyway to lock vsync for p96 in winuae ? as apposed to the winuae vsync option for non p96 screens.

[andreas]

Originally Posted by Toni Wilen

Bogoram size will be limited to max 1M in next version if AGA is enabled.

What about disabling bogo RAM if AGA is enabled?
People can as well use real fast RAM, that's what it's for, and even closer to the real thing IMO.

[Toni Wilen]

Originally Posted by andreas

What about disabling bogo RAM if AGA is enabled?
People can as well use real fast RAM, that's what it's for, and even closer to the real thing IMO.

No, I don't want to restrict "stupid" configurations, only configurations that are impossible due to address space conflicts, because experimenting with them can be fun

[Ironclaw]

Not worth a new thread, but...

Stop everything and prioratize this... ehh.. prioretize...... fix this first... the other bugs can wait !
built.....

[Tarzin]

Originally Posted by thomas

Check the uaescsi settings on the Misc page. Choose SPTI instead of ASPI and test if it still crashes.

Hi!

First Post, first problem
I've uninstalled WinUAE 1.3
All is working except if uaescsi.device is checked. If checked, nothing boots and I can't kill winuae's task with windows task manager.
SPTI is selected (available options are SPTI / SPTI+SCSI SCAN / AdaptecASPI / NeroASPI / FrogASPI)

If unchecked, all is unnning well except that I can't access to my CDROM.

If I come back to WinUAE 1.2, no problem, all is right with uaescsi.device enable.

Any idea ??

Thanks a lot.