Guide: WinUAE PPC OS 4.0 Classic Install Guide (Beta 12+)

[fitzsteve]

@Leo42

Do you have any UAE drives or folders? If so remove them, only emulated scsi.device is supported

[FOL]

Originally Posted by Leo42

Is AmigaOS 4.0 classic supposed to work as well ?

Followed the tutorial but Amiga enters infinite reboot loop: after rainbow, screens turns to pink, and the power led flashes 4 or 5 times, then I got rainbow again, screens turns to pink, and so on...

Only hint is "JIT direct not supported with blizzard boards message".

Problem is that when I uncheck the option, save config file, if I exit WinUAE, and load the configuration, the option is ticked again: it doesn't seem to be saved unticked.

Start with a fresh config. I used to get this alot when twekaing configs between versions.

[Minuous]

I have OS4.0 installed and running now, thanks for the guide. I suggest that the guide should point out the need to disable screen blanking etc. in Preferences. Otherwise emulator will crash after 20 minutes, preventing eg. unattended install of SDK.

I also have an issue here on OS4 (beta 22 of WinUAE) where the screen doesn't update properly; the pointer leaves some pixels of itself behind, and only the rows that the pointer traverses have correct graphics. Does anyone else get this bug?

[B14ck W01f]

Try going into Miscellaneous and choose Direct3D under the Graphics API drop-down list, on the right.

[Minuous]

It was already set up to use Direct3D. Using DirectDraw instead doesn't seem to make any difference.

[FOL]

Originally Posted by Minuous

It was already set up to use Direct3D. Using DirectDraw instead doesn't seem to make any difference.

Any chance of screenshot?
Use screen grab in OS4.1 or Printscreen.

[Minuous]

Here's a screenshot showing some symptoms of the problem:

1. Mouse pointer only leaves trails if it is moved quickly on the vertical axis. Horizontal movement, or slow vertical movement, doesn't cause it.
2. Just before doing this screenshot, I have pressed Amiga-A (Select all icons), thus both files are actually selected, however you have to move the pointer over Koules.guide before the glow will show. The true pointer is the one near the Koules icon, all the rest are just remnant copies.

WinUAE screenshot function always makes perfect images. This image was grabbed using Screenshot Pilot (Windows app), and I have then reduced it to 256 colours to save bandwidth.

Messing around with WinUAE under wine on OS X. I had little luck getting FS-UAE to do the right thing. With Wine/WinUAE I am able to see the OS 4.1 Classic boot screen before it goes black. I can see the FPS indicator moving, but nothing seems to happen after this. There is no CD or floppy access. How long, roughly, did folks end up waiting in this phase?

I tried setting the CD-Rom as both IDE as well as SCSI (A4091) and both get me to the same place but neither seems to do much after the PPC takes over. Any suggestions? I'm using WinUAE 29b23 and CyberstormPPC_44.71.rom. I'm also using Picasso_Iv_Flash.rom which is the latest version supported by the folks who made the PIV.

Is the BinoX Guide Files.adf corrupt? I get disk errors on 4.0 and 3.1 cant seem to open it.

[Minuous]

So, does anyone else experience the bug I have described?

Should I lodge a formal bug report with the WinUAE developer?

[Toni Wilen]

Originally Posted by Minuous

So, does anyone else experience the bug I have described?

Should I lodge a formal bug report with the WinUAE developer?

Never heard about that. Note that it has to be duplicated under OS3.x. Any problems under OS4.x that can't be duplicated easily will be ignored (and some will be even if they can be duplicate easily!)

Also as usual (to everyone who has problems): No logs = no (useful) help.

EDIT: Screenshot being correct means something goes wrong when display gets moved to host side. Does the mouse cursor also appear normally in screenshot? (not invisible?)

[FOL]

Originally Posted by Minuous

So, does anyone else experience the bug I have described?

Should I lodge a formal bug report with the WinUAE developer?

I only even got that issue, if direct3d wasnt select in misc menu.

[Minuous]

OK, I have solved the issue now. It was happening regardless of whether Direct3D or DirectDraw was used, but FOL's post did give me a hint that it might be DirectX-related.

It turns out that DirectX needed a 50Mb upgrade or downgrade from http://www.microsoft.com/en-us/downl...s.aspx?id=8109. That's very odd, because this Win7 SP3 machine was bought new in 2012, whereas the dates for the files on that page are 2010 and 2011. (Also odd that it is listed as being 95Mb but is really only 50Mb.)

Now it works fine whether Direct3D or DirectDraw is selected.

Does the mouse cursor also appear normally in screenshot? (not invisible?)

Yes. But anyway it doesn't matter as it is fixed now. Many thanks to BlackWolf, FOL and Toni for their help.

[Ian]

Followed the guide to the letter, yet it doesn't work for me.

I waited well over an hour at the black screen after the coloured flashes.

In windowed mode I can see that the PPC never actually starts. (Using Cyberstorm)

I managed to get it working on a 3.9 install but it froze and then crashed the emulated amiga each reboot.

Also using Blitz using the a1200 quickstart settings results in a not enough memory for kernal message.

[Minuous]

I've just upgraded to V3.0.0, also upgraded the qemu-plugin to match. Now RTG has stopped working, only AGA is available. I haven't changed the UAE configuration nor the AmigaOS configuration.

[Toni Wilen]

Originally Posted by Minuous

I've just upgraded to V3.0.0, also upgraded the qemu-plugin to match. Now RTG has stopped working, only AGA is available. I haven't changed the UAE configuration nor the AmigaOS configuration.

Memory panel, Z3 mapping -> Real. Or disable m68k JIT. Or get 64-bit Windows.

Originally Posted by Ian

Followed the guide to the letter, yet it doesn't work for me.

Guide is not really fully valid anymore. Config and logs needed as usual. (NEVER say "does not work" if you want useful replies)

[Minuous]

Originally Posted by Toni Wilen

Memory panel, Z3 mapping -> Real

That fixed it; thank you!

[mritter0]

Mine a more complete guide:

http://eab.abime.net/showthread.php?t=75264

[B14ck W01f]

Originally Posted by mritter0

Mine a more complete guide:

http://eab.abime.net/showthread.php?t=75264

But where are the screenshots?

[Ian]

Originally Posted by Toni Wilen

Guide is not really fully valid anymore. Config and logs needed as usual. (NEVER say "does not work" if you want useful replies)

I was hoping the OP would be able to update the process if it no longer works.

Now I know you are on the case, I shall provide the information

Here are some log files created from the update from OS 3.x option and from boot floppy.

Halt 5 happens from OS, nothing appears to happen once the kickstart is loaded from boot floppy.

OS4.0 ends with a HALT3