1mb slow ram messing up Workbench 1.3's screen

[Maren]

512k (Workbench correctly positioned)


1mb (Workbench positioned lower than it should)

I'm running the latest beta with exactly the same config provided in the "WinUAE won't use chosen screen modes" thread.

It happens only with 1mb slow ram

You can't click on the menu and move it upwards.

I never expanded my stock A500 so I have no idea if this behavior is to be expected.

Regards.

[Ironclaw]

Just looks to me you have "Line Mode" set to normal. Change it to "Double".

[Maren]

Originally Posted by Ironclaw

Just looks to me you have "Line Mode" set to normal while "Force low resolution" is not ticked..... try ticking/activating the "Force low resolution".

Nope, it happens regardless of the host Display configuration.

[Ironclaw]

Originally Posted by Maren

Nope, it happens regardless of the host Display configuration.

I edited my post long ago, you must have had that quoted for a while . Read my post again

But oh well, if you are certain about "regardless of the host Display configuration"... then I don't know.

[Maren]

Originally Posted by Ironclaw

Just looks to me you have "Line Mode" set to normal. Change it to "Double".

Actually my config is 640x512 + hires + scanlines, just took the screenshot at 640x256 to properly exemplify the problem.

[Ironclaw]

Originally Posted by Maren

Actually my config is 640x512 + hires + scanlines, just took the screenshot at 640x256 to properly exemplify the problem.

Sorry, but I don't believe you. I think your problem is now solved and you just made up an excuse

Well, that's how I am....

If I'm wrong I hope someone finds a solution to your problem...

[Maren]

I too hope so , but thanks for trying to help. I must also mention exactly the same happens in windowed mode. 512k = ok, 1mb = lowered menu.

[thomas]

This is not a bug, it is a phenomenon which sometimes happens on a real A500, too. It confuses PAL and NTSC and opens the Workbench screen in 640x200 instead of 640x256.

The reason why the title bar is below the top is that you have enabled vertical centering. On a real A500 the title bar remains at the top but the mouse pointer cannot be moved into the lower fourth of the display.

Should be solved easily by a reboot (Ctrl-A-A).

[LocalH]

This also happens if you use one of the small PAL switching programs on an NTSC Amiga, even the higher models (my A3000 does exactly this under both 2.0 and 1.3). Anytime you switch NTSC/PAL like this (without using KS3.x Early Startup Control), you'll see this problem, as the system doesn't "know" you're supposed to be in PAL mode because the NTSC screen was already open.

This will not happen under OS2.x or greater when using the WB ScreenMode prefs. This will also happen in reverse if you use the complementary NTSC switchers on a PAL Amiga - you should still be able to move the mouse over the full 256 lines but you'll only see lines until vblank begins (a few more than 200 however).

[Maren]

Thanks both of you for the explanations, never heard anything about 1mb ram triggering this before

[andreas]

Originally Posted by thomas

This is not a bug, it is a phenomenon which
sometimes happens on a real A500, too.

Hmmm, this really does ring some bells!

Is this the same "feature" that if I press CTRL-D on the real thing when booting up Workbench, I'm sometimes unable to resize the AmigaDOS window to 256 and it will remain "stuck" at 200?
If so, getting back to normal behavior never worked by hitting CTRL-A-A here but required a cold reboot on my Miggy...

[Toni Wilen]

It is KS 1.x bug. (Fails to detect PAL. Reboot usually fixes it, if not, keep rebooting..)

Also, not enough information error:
- no information if it happens every time (it shouldn't)
- I don't care if it happens in non-quickstart configuration (you can select normal A500 qs and then modify memory setting)

[Maren]

Originally Posted by Toni Wilen

- no information if it happens every time (it shouldn't)

Well, it does.

Originally Posted by Toni Wilen

I don't care if it happens in non-quickstart configuration (you can select normal A500 qs and then modify memory setting)

It happens with the default A500/most common config plus the extra ram. I generally stick to the unmodified A500/most common config for the sake of compatibility, but this time a certain demo required the extra ram so I had no choice, and that's how I spotted the problem.

[Toni Wilen]

Originally Posted by Maren

Well, it does.



It happens with the default A500/most common config plus the extra ram. I generally stick to the unmodified A500/most common config for the sake of compatibility, but this time a certain demo required the extra ram so I had no choice, and that's how I spotted the problem.

Thanks. Now I am interested enough to do some tests

[Maren]

Thanks for showing interest

[Toni Wilen]

Can't duplicate. (a500 most common + with/without cycle exact + 1M slow)

[Maren]

Workbench 1.3.3 on hdf + Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV)[!].rom?

[Toni Wilen]

Normal wb 1.3 adf and 1.3 KS (I did say A500 quickstart = 1.3 KS). HDF isn't acceptable either. WB version shouldn't matter, even empty bootable disk will show the problem.

[Maren]

I just did some testing and found out that the problem isn't present when booting directly from the WB 1.3 adf, so that leaves me with either a corrupted WB 1.3 hdf installation or who knows what else.

[Toni Wilen]

Then the problem isn't PAL detection. Also you can still drag WB screen even if PAL Amiga is detected as NTSC.

Virus?