Prometheus - Best Practices?

[Hedeon]

Thought you said you hadn't installed the mmu libs, but doesn't 3.2.1 come with those?

[spudje]

Grrr, apparently it has indeed. I'll do a clean install and add the 68060 library manually instead via the 3.2 installer.

[spudje]

OK, so I did some testing. Started from scratch with an AOS 3.2.1 setup. No MMU, only Phase5 060 library for my CSMKII from A1k.

Issues remain, no matter what I try:
- latest icomp P96 or latest free Aminet P96. (No difference, except the latest iComp has artifacts in Dopus on positions where pop-up/dialog boxes appeared and dissapeared)
- with and without the tooltype DMAsize
- with and without openpci.library
- with and without PPC installed
- with and without OpenPCI network card installed installed
- with and without PPC initiated
- with and without Zorro 2 USB card
- with and without setting P96 ENVARC according to Sonnet "Good Config"

Issues remain:
GearPPC full screen = OK
Gear68k & GearPPC windowed result in recoverable error
Gear68k only works from time to time (I think when starting from a relatively low res P96 screen)

I ran an AGA 060 demo, The Martini Effect, awesome demo, went totally fine. So I guess my 060 card is fine. I ran a successful memory test on the 060 memory.

So if it's hardware it can only be the voodoo. I have 2 more, iIRC, so I can swap.

If it's not hardware, then I'm doing something wrong with configuring
- prometheus
- Warp3D
- Voodoo card in P96, do I have to set/delete other tooltypes?

[grelbfarlk]

Originally Posted by spudje

OK, so I did some testing. Started from scratch with an AOS 3.2.1 setup. No MMU, only Phase5 060 library for my CSMKII from A1k.

Issues remain:
GearPPC full screen = OK
Gear68k & GearPPC windowed result in recoverable error
Gear68k only works from time to time (I think when starting from a relatively low res P96 screen)

I ran an AGA 060 demo, The Martini Effect, awesome demo, went totally fine. So I guess my 060 card is fine. I ran a successful memory test on the 060 memory.

Some other things to test:
Amigenerator WOS (I assume this works on Prometheus)

ScummVM Hedeon's WOS version(this will test P96 and AHI and a lot of RAM)

[spudje]

Thanks, I will put that on the list. But I'm currently not even getting Warp3D stable with 060. PPC is only next step.

In the mean time tried with 2 more Voodoo3 cards and in different PCI slots. All same results. So it seems software most likely, or something wrong with my AA3000+?

Could the fact I'm using the external SCSI port for HDD be an issue?
DSP stuff is currently not installed.

Just a check, how have you guys called your monitor driver (in DEVS:monitors)? I have it called voodoo. Maybe I should call this prometheus?

And are any other ENVARCs needed, e.g. setenv PowerPC/gfxaddr although this shouldn't matter for 060 W3D I assume.

[trixster]

Do you have a zz9000 in this machine at the moment?

[spudje]

No, I removed all cards except the voodoo for latest trouble shooting sessions. And I have not used a ZZ9000 in this setup.

Is any of you on AOS 3.2.1? Or should I try with AOS 3.1 or 3.9?

Am I referring correctly to the P96 lib in the voodoo monitor tooltype? Or should I use the voodoo lib, or add .card or .chip???

Suggestion for another 060 lib than the phase5 I now use? The Thor libs require mmu/lib as well as it seems. Without mmu lib in libs I get a recoverable alert on boot.

Other weird behaviour when runing the SD card in WinUAE. When copying a certain amount (typically more than 4) files in dopus I get a guru at the end of copying and after a reboot the files are not in the destination folder. So maybe my SD is corrupt?

[spudje]

Some more progress.

SCSi is not the issue. I have same behaviour when using FastATA.

I think it's either some memory thing or screenmode thing. I used the prometheus screenmodes that came out of the box with Hedeon's libs. Iirc I only checked and updated a few in the Picasso mode tool.

In 640x480 16bit (none PC) and 800x600 16bit (none PC) I got gears68k windowed and small working. The full screen mode still results in a black screen (no signal). Higher resolutions result in the recoverable alerts.

So should I go over all the desired resolutions in the Picasso Mode tools?

Next option is to install MMU properly I guess.

[Hedeon]

There were screenmodes out of the box? Weird. They are saved in Picasso96Settings in DEVS: (or you can point it to another file if needed through the monitor .info file).

I can't remember putting a settings file in that archive.

Anyway, I made multiple setting files myself (combinations of Prm and Med and V3, V4, Radeon and Permedia2). Always made them from scratch after an installation.

Doesn't your monitor give a warning if the settings are out of range? Didn't you test the screenmodes while in Picasso96Mode?

[spudje]

mmm, maybe the screenmodes were from the Cybervision3D monitor which I used as starting point? Or with P96 3.2.4?

Yes I tested some of them and a subset I had to adjust a bit. But I'll create them from scratch (hate that work, hehe).

[Wrangler]

@spudje your set up is similar to mine except I am using OS3.9 and P96 2.1b - although I don't think that should make a difference. My first instinct is that you have a dodgy Voodoo card. Did you try swapping that out?

Otherwise, can you do "version full" on prometheus.card in your picasso96 folder and a "list" of it to see if there is a version difference.

It's a long time since I set my system up but my recollection is that the various P96 screenmodes worked straight away and I didn't need to adjust them. What happens when you try a test of 1024x768 in Picasso96Mode - does that work? Can you paste a screenshot of that screenmode selected in Picasso96Mode so we can see the settings.

[spudje]

Thanks Wrangler. I'll do the check of versions later and go look for some 3.1 roms. I don't think it's the voodoo, I have exact same symptoms with 3 different cards.

[spudje]

Could the tick jumper (J350) be causing this? I'm not sure how it's set and I'm using an ATX PSU.

[spudje]

OK, so I think I at least fixed the 060 Warp3D issues (haven't tried PPC yet).
I used the P96 monitor file of the CV64/3D as starting point. I made a copy and created the voodoo monitor out of it. The original CV64/3D monitor file was also still in DEVS: monitors. When I moved that CV64/3D monitor file to storage and only kept the voodoo monitor file there (next to the native monitor files), the gears68k demos all worked at multiple resolutions I threw at it.

I also tried setting the jumper to tick, but that actually didn't work, the machine got into a bootloop.

[Wrangler]

Ah, you need the tick jumper set because the original PSU provided a tick signal but a modern ATX PSU won't. And, yes, don't have a monitor driver for a card you don't have in DEVS:!

But does Warp3D work on the PPC now?

[spudje]

Yes I now also tested Warp3D with GearsPPC and it worked. Tried Wipeout successfully again for a few minutes too. Not yet checked how long it lasts before crashing again (which I fear it will still do, but that's most likely caused by something else, e.g. heat). I'm still struggling with Quake2, but haven't spent too much time on it yet. Need to try Cowcat version, so far only used Hyperion's.

As said setting tick results in bootloop. Maybe some conflict with other jumpers/CS MK2?? Although I haven't found any (other than Warp3D) issue so far with having tick not set.

[dr.doc]

Hi,
Thanks to all of you who have spent time untangling this crazy ball of yarn!

I've finished assembly of my '030-based ReAmiga 3000 and Hese's new Firebird DB. The hardware tests to boot with 3.1 ROMs, but I want to make sure I'm on the right path before I go further.

1) I had planned to run OS v3.9, P96 v2.1b and Roadshow, but I have paid copies of OS v3.2 and P96 v3. Is there any reason, regarding the Prometheus/Firestorm operation, to choose one or the other?

2) @Hedeon - Are the Prometheus updates in your "Sonnet 7200" posts 68k and OS v3.x compatible?

3) Is the old OpenPCI page the most current source for drivers?

4) @Wrangler Is the ArakAttack key still available? May I have it, please?

Again, thanks to everyone who's made this easy for us amateurs!

Doc

[Hedeon]

Regarding point 2 and 3:

2) You tell me :-) They should be. Only bug I am aware of at the moment is that Ratte's monitor switch does not seem to work with it (at least the built-in one of the AA3000+). Are you also using a V3?
3) Depends on what drivers.

[spudje]

Huh? What isn't working with the Ratte switch in the AA3000+. I haven't tested extensively with native<->RTG switching scenarios, but what I have seen so far, mostly it works. I have maybe encountered a black screen once or twice, which now that I'm reading this, may be caused by this?

[Hedeon]

Trixster reporter that my new Prometheus library or voodoo driver didn't switch the screen. Black screen.