WinUAE 3.0.0 beta series (was 2.8.2/2.9.0)

[Locutus]

Originally Posted by Toni Wilen

Screenshot please
Crashes as in kernel level crash or user program crash? Anything interesting in logs?

No screenshots yet as the boot process does not get to the point where it will load CGX and Monitor drivers, also curiously it crashes randomly at various points.

But the interesting part is that Quark does boot and loads ABox which then starts the normal Amiga style bootup.

It gets all the way till executing MOSSYS:S/Startup-sequence, but crashes there.

http://locutus.puscii.nl/mosboot_2 <- boots till startup-sequence script.

WinUAE Bootlog error at that point:

@fff1b2b8 (793772032 ops) pdec: 0002453c lr: 00000000
[PPC/DEC] Bad opcode: 7c095415 (31:522) PC=111b6cc4
singlestep set from ..\..\ppc\pearpc\cpu\cpu_generic\ppc_dec.cpp:96, info: unknown instruction

Also: these are the times that its so frustrating that you don't have a sourcetree to cross reference with :-)

[Retrofan]

Originally Posted by Toni Wilen

"Couldn't open CPU board rom 'cyberstormppc.rom'"

Sorry I was using the ones in the zone, but I didn't rename any. Now I've renamed the cyberstormppc_44.69 as cyberstormppc.rom and reescaned for what I read in the OS4.1 instructions: "Note that there is a known issue with the installation Disc not being able to detect a Cybervision PPC or Blizzardvision PPC graphic card if the Cyberstorm PPC or Blizzard PPC version is the very last private release (version 44.71) that included support for OpenPCI."

After some rainbow screen I get a red screen now.

[Toni Wilen]

Originally Posted by Locutus

I've added the MOS boot up output which crashes on a illegal page access.

http://locutus.puscii.nl/mosboot_1

Also: these are the times that its so frustrating that you don't have a sourcetree to cross reference with :-)

RBF interrupt as in serial receive buffer full. Strange..

I agree, it was easy to find problems with netbsd just by checking the source..

Originally Posted by Retrofan

Sorry I was using the ones in the zone, but I didn't rename any. Now I've renamed the cyberstormppc_44.69 as cyberstormppc.rom and reescaned for what I read on the OS4.1 instructions ("Note that there is a known issue with the installation Disc not being able to detect a Cybervision PPC or Blizzardvision PPC graphic card if the Cyberstorm PPC or Blizzard PPC version is the very last private release (version 44.71) that included support for OpenPCI."

After some rainbow screen I get a red screen now.

You have old version, redownload winuae.zip.

[Retrofan]

Originally Posted by Toni Wilen

You have old version, redownload winuae.zip.

Isn't it 2.9.0, beta 9 from here? http://www.winuae.net/files/b/winuae.zip

[Locutus]

mosboot_1 was a stupid user error btw, it boots further with the correct boot arguments, i edited my post.

[21stcentury]

Originally Posted by Retrofan

Isn't it 2.9.0, beta 9 from here? http://www.winuae.net/files/b/winuae.zip

Exactly the same problem for me : red screen with the last version.

Just notes the blizzardppc44.71 doesen't work, it's impossible to entering in BIOS. 44.69 is better.

[Toni Wilen]

Originally Posted by Retrofan

Isn't it 2.9.0, beta 9 from here? http://www.winuae.net/files/b/winuae.zip

Yes but first untick all Hard drive options-checkboxes, untick bsdsocket and disable Z3 fast. Also technically your system is impossible, CSPPC + A1200 Could cause IDE related problems depending on used detection method, perhaps others too. (A1200 IDE is different than A4000)

If winuae.zip still does the same, download winuae2.zip (same url path). It has lots more debugging enabled. Stop emulation immediately (enter gui and exit with quit button) when red screen appears to prevent filling the log with useless information.

[Retrofan]

This is with WinUAE2.zip. I get first a blue screen and then different bands of horizontal colors on screen.

Edit: Ups I've got to untick what you said.
Edit: Where do I get the memory? if I disable Z3 fast I get could not allocate kernel memory message

[21stcentury]

Originally Posted by Retrofan

This is with WinUAE2.zip. I get first a blue screen and then different bands of horizontal colors on screen.

Edit: Ups I've got to untick what you said.

Kickstart 3.0 ? OS4.0 / 4.1 needs kickstart 3.1

and for me it's diffrents colors and black screen.

[Toni Wilen]

Originally Posted by Retrofan

This is with WinUAE2.zip. I get first a blue screen and then different bands of horizontal colors on screen.

Edit: Ups I've got to untick what you said.

Do not set chip ram to larger than 2M (and you still have z3 fast). Make sure hardware is exactly right!

Config is wrong (has "software emulated" expansions) as long as "UAE Boot ROM" appears in log.

[Retrofan]

...

Originally Posted by Retrofan

Edit: Where do I get the memory? if I disable Z3 fast I get could not allocate kernel memory message

[Toni Wilen]

Originally Posted by Retrofan

Edit: Where do I get the memory? if I disable Z3 fast I get could not allocate kernel memory message

Set accelerator board ram to max. PPC CPU can't even boot without it. Accelerator on-board RAM is rarely (if ever) Z3 RAM!

[Retrofan]

Blue and red screens.

[Toni Wilen]

Originally Posted by Retrofan

Blue and red screens.

Config is still not perfect. Harddrive panel Options are still ticked, disable also clipboard sharing in misc panel. "UAE Boot ROM" _must_ not appear in log file.

EDIT: PPC CPU is not even started yet. It would be easy to debug.

[Retrofan]

Originally Posted by Toni Wilen

Config is still not perfect. Harddrive panel Options are still ticked, disable also clipboard sharing in misc panel. "UAE Boot ROM" _must_ not appear in log file.

EDIT: PPC CPU is not even started yet. It would be easy to debug.

UAE Boot ROM will disappear now unclicking HD panel options and clipboard sharing or elsewhere?

Edit: It seems that elsewhere, I've got it still on the log, but don't know how to disable it.

[Toni Wilen]

Originally Posted by Retrofan

UAE Boot ROM will disappear now unclicking HD panel options and clipboard sharing or elsewhere?

Edit: It seems that elsewhere, I've got it still on the log, but don't know how to disable it.

UAE Boot ROM is needed if any following option is enabled:
- "UAE" HD controller (HDF or directory)
- automount removable drives
- bsdsocket.library
- uaeserial.device
- uaescsi.device
- uaenet.device
- tablet emulation
- uaegfx RTG
- >2M chip RAM
- 32bit chip RAM

[zevs]

How about MorphOS? Has anyone tried to boot MorphOS?

[Retrofan]

Puf. Then I can only use a real Cf (example) Hd and not an Hdf?

[Toni Wilen]

Originally Posted by Retrofan

Puf. Then I can only use a real Cf (example) Hd and not an Hdf?

Only UAE controller can't be used (it is not hardware). Any other HD controller (IDE or SCSI) is full hardware emulation. HDF vs real HD makes no difference.

Directory harddrives are also completely unsupported in non-m68k AOS operating systems.

[Zilog]

Originally Posted by Toni Wilen

UAE Boot ROM is needed if any following option is enabled:
- "UAE" HD controller (HDF or directory)
- automount removable drives
- bsdsocket.library
- uaeserial.device
- uaescsi.device
- uaenet.device
- tablet emulation
- uaegfx RTG
- >2M chip RAM
- 32bit chip RAM

Ok Tony,
it possibile puy into Menu Miscellaneus a check for activate or not Uae boot Rom; if disable all option link with uae rom are disable.