I've been trying run MorphOS 1.4.5 on every beta version science b10, but no success.
Is currently possible run MOS on WinUAE or is it still require improvements on PPC/board emulation?

Winuae crashes with BPPC 040 Rom and 68040 selection.

Narutard

Logs and Configfile ???

Sry

@huepper
>Known ROM 'KS ROM v3.1 (A4000)' loaded

Isn't this the issue? ks for A4000 when you emulate a 1200?

I loaded my A4000 PPC config that has the hard drive containing AmigaOS 4.1 mounted. Upon startup, I get the message "Error loading qemu-uae plugin", yet that same file is sitting in my WinUAE/plugins folder.

Check the first page. It was updated a while ago.

Thanks!

Impact A4000-HC+8 (aka Impact A2000-HC+8 Series II) is supposedly OS4 compatible, perhaps it can also work in A1200 config with BlizzardPPC (256M RAM without slow IDE)? It is not real world config but it should work as long as there is no extra checks in driver.

It is not yet emulated, existing WD33C93 SCSI emulation currently depends too much on Commodore's DMAC.

Should be much faster than IDE because it is DMA SCSI controller. (But it won't be as fast as CSPPC SCSI to emulate)

i'm using OS4.0, but i see some strange situation: mplayer don't work. Black screen. DVplayer idem. Mp3 don't load and no audio.
is there some to setting or i lost some important files?

Hi, someone tested AmigaOS 4.1 Final Edition Classic on the lastest WinUAE ?

If so or when so, can you please share your experience ?

Considering the availability and the new price (nearly 30€), i might buy AOS4 if it works.
My wish is that the duo WinUAE + AOS4 solution is enough for simple app development, software porting using gcc.

Does the WinUAE/SaveStates functionality works under PPC emu ?

No. PPC CPU, most SCSI devices and RTG hardware emulation does not have statefile support.

Ok no problem (idea was that it would have speed up boot time as i saw that os4 boot is slow).

I would also like to try, did anyone get MorphOS 1.4.5 working yet?

WinUAE 3.1 doesn't freeze on my system, but crashes (no dump, just a Windows message about WinUAE no longer working) after AOS4.1 idles for some hours. I have installed Extras, SDK, vbcc/ppc-target and spent much time actively without much problems before (WinUAE 3.0).

I noticed ejecting a CD-image (device ide:1) is not always recognized inside OS4.1.

Ive had this too, but its very random.

I've just ejected an iso-image. cd0: is still accessible but empty, and shows about 80MiBs allocated. Is this an OS4.1 bug?

Also, I find it rather inconvenient that ejecting an image leads to the assignment of a physical drive to cd0:. Can this behaviour be changed? Not that it would work (see above), the drive spins up and that's it.

Edit: Forget it - silly me overlooking the obvious *rolleyes*. And now ejecting works ok.

I have tried on latest FS-UAE (A4000/OS4 config) - works, is stable, performance is decent - but I have Core i7 4790K and I am running a 64-bit emulator (I suppose 32-bit might be slower).

@Romanujan, How is it possible that you run AmigaOS 4.1 FE Classic on a 64-bit emulator as FS-UAE? FS-UAE are based on sources from WinUAE and the Experimental 64-bit WinUAE PPC CPU emulation is not yet supported in WinUAE 64-bit.

The QEMU-UAE PPC plugin works fine with 64-bit on operating systems other than Windows.