WinUAE 4.4.0 beta series

[ross]

Originally Posted by Toni Wilen

Background: "default" scaling mode should be something that is mostly ok for most normal users. Which means Amiga view should be scaled to selected fullscreen/window size (even if it means scaling artifacts) and aspect ratio correction should be enabled.

winuae.7z now in "default" scaling mode sets aspect ratio correction off if window/screen is close enough to 4:3. Only if it isn't close enough, aspect ratio correction gets enabled (=black bars may appear).

I hope this is good enough. All other scaling modes are (and should be) fully configurable. Only "default" is special.

Well, now works.

But I really prefer a no scaling 1x/1x for the default 720x568 window in a "square pixel" monitor (like mine and the available majority).
This way Amiga pixel is sharp and you have an integer multiple quantity with the real ones (1->1 for an hires screen mode).
Now the default for a Quickstart setup is a bit blurry..

[Toni Wilen]

It is not really quickstart related. Quickstart only changes hardware settings.

Simply save your preferred config as "default.uae". Perhaps there should be some kind of "save as default" in configurations page to make it more obvious.

But I'll add special case: no scaling if window size is also original default.

[ross]

Thanks!

[Toni Wilen]

Hopefully final "default" filter update (winuae.7z):

- keeps 1:1 mapping if internal Amiga window size is same or almost same as window/fullscreen size. If larger/smaller: scaling gets enabled.
- Aspect ratio correction also has similar behavior: if aspect ratio is almost correct, aspect ratio correction is disabled.

Now behavior should be same as previously if window size is default (or close to enough). If larger, scale to window/screen size gets enabled and/or aspect ratio correct gets enabled.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_4400b8.7z
http://www.winuae.net/files/b/winuae64_4400b8.7z

Beta 8 (RC1):

- More "Default" filter adjustments: enable aspect ratio correction only if current aspect ratio is not close enough to 4:3. Enable scaling to current window/screen size only if current window/screen is "too" large or small. Main reason for this change is to keep old behavior (no scaling or aspect ratio correction if default window/screen size but enable scaling/aspect ratio correction if window is larger or smaller)
- Beta tag removed.

[Mclane]

Thanks Toni, the scaling is the one thing I find hard to get right so this is a great change..

[ransom1122]

Toni,

With Beta 7 & 8 I am having issues with a diagnostic Red screen error.

When there are more then one hdf's inserted, you start WinUAE, then remove HDF (DH0) then simply Reset always use to launch the next HDF in line (DH1).

But now I get the diagnostic Red screen error..

I have tried to use restart and that only works with only a standard default A1200 Config. Any other variant config from that obtains the diagnostic Red screen error.

I never had this issue before swapping and changing HDF's on the fly and resetting... Has something changed?..

[Toni Wilen]

I don't think that kind of use case has ever been officially supported and only worked accidentally.

Do you mean b6 does not and older ones? B1 changed how GUI reset button works internally and b6 fixed side-effect.

Include config and winuaelog.txt from latest beta and last working beta.

[ransom1122]

I lost the b6, can you share the link for betas b6 and below please?

Im not sure if I have done it right but here are the logs.

[Toni Wilen]

Originally Posted by ransom1122

I lost the b6, can you share the link for betas b6 and below please?

Check this thread for links.

[Toni Wilen]

I can only see one winuaelog.txt and config can't be correct because there is no harddrives.

EDIT: Also does it really depend on HD? If you only have single HD, does it also cause same problem?

[ransom1122]

It seems its only dependent on multiple HD's.

I figured out From Beta 5 and Below removing HDF's and resetting winuae Works, but from Beta 6 and above I obtain the diagnostics error.

Beta 1 to 5 = Working
Beta 6 to 8 = Not Working

Utilizing 3 same HDF's in DH1, DH1 & DH2.. Loading first HDF, Removing 1st HDF & clicking Reset in WinUAE GUI

Logs attached below using Beta 5 / Working & Beta 7 / Not Working

[Toni Wilen]

One more question: does it happen if you always boot without startup-sequence? Something like blizkick could in theory cause weird side-effects.

[ransom1122]

The hdfs have simple generic startup sequence ie..

Cd gamename
Whdload gamename.slave preload

These hdfs are loaded with a high end uae configuration set-up i have save and kept over the years to build my hdfs..

As I said the uae I use to build hdfs have never failed senile beta 6 and onwards.. so I doubt it's the uae config I'm using..

As for blizkick I have no idea what that is..

I use 3 ADFS upon boot, a wb disk, dopus disk, and Cygnus disk.

[Toni Wilen]

I can't duplicate and your config is far too complex (why all kinds of memory at the same time?) 68060, JIT. And attached config still does not match logs.

Make it as minimal as possible.

And when I ask to test without startup-sequence, you need to test it without startup-sequence without extra questions

Does same happen if you use GUI reset button?

(It is almost too late)

EDIT: fastest way to solve this probably is: attach all the hardfiles + config in single archive and upload it somewhere.

[ransom1122]

The config I use has a maximum speed boost unrealistic Amiga setup, I only use this uae setup to speed up the build process my HDF's.

On A standard Quuickstart A1200 with 2mb chip and 8mb fast ram this issue does not happen. But my question remains as to why all of a sudden after beta 6 my own config wont work when i remove a HDF, and the next HDF in line wont boot?

Reset Button & Restart Button has the same error after removing 1 HDF and trying to boot the next HDF in DH1

Some of your questions, re: Attach Configs dont match logs, ss with extra questions are still confusing me, but as you said I have attached 3 ordinary HDF's and my UAE for you to test..

Many thanks.

[AMIGASYSTEM]

I use more HardFile and with any configuration, i also use Blizkick and i don't have this problem, tried your "3 HDF's & UAE" and I didn't have any problem, have you tried to recreate a configuration from zero, tested on other PC?

[ransom1122]

I havent tried it on another pc, but it is a good idea. Will do when I get some time.

It's strange though, that same config on my pc always works/worked on any version of winuae from beta 5 and back.. yet beta 6 and up crashes... reverting to a working winuae.exe fixes the problem, so I doubt its my PC.

very strange indeed..

[Toni Wilen]

Config now matches logs but I still can't duplicate it and I can't see how the change would cause problems.

The only difference is that if hard reset: KS ROM(s) always gets reloaded at reset.

btw, do you really use Windows Vista SP2? At least version numbers in log matches. It shouldn't cause any problems but Windows 7 is oldest supported since 4.3.0

One possible reason is running out of process address space. 32-bit Windows + lots of RAM configured (usually if more than 512M) can cause problems. Try without 32-bit chip and Z3 RAM.

[ransom1122]

Yes, I have the oldest dinosaur I work with. My kids have healthier pcs then I lol. Dont worry I'm next In line to buy a beast pc.

Ok. So if it works on your pcs, then it must be my RAM situation. Ill take it from here and report back. Thanks toni