WinUAE +uaefgx + Picasso96 = black screen

[mikettl]

Hey guys,

after quick browsing the forum I didn't find specific hints so I like to ask with an own thread. If I oversaw information in the forum, I apologize and encourage you to point me to, many thanks in advance.

System configuration before installing Picasso96:

WinUAE 3.0

CPU and FPU
68040, FPU internal, Emulation Speed: fastest possible, JIT (Constant jump, FPU support, No flags, Indirect)

Chipset AGA, Chipset Extra A4000, Sprites and Sprites vs. Playfield
Adv. Chipset Compatible Settings
ROM KS ROM v3.1 (A4000)(Cloanto) rev 40.68 (512k)

RAM
Chip 8 MB, Z3 Fast 256 MB, 32-bit Chip 256 MB, Motherboard Fast 64 MB, Processor Slot Fast 128 MB, Z3 mapping mode Automatic

Expansion
UAE Zorro III, VRA size 128 MB, Scale if smaller than display size setting,
Refresh rate Chipset, Buffer mode Triple Buffering, Aspect ratio Automatic

Display Generic PnP Monitor (1920*1080), Fullscreen 1280x720/32, Windowed 800*600, Native Windowed, RTG Fullscreen, Default refresh rate, Triple buffering, Line Mode Double, VGA mode resolution autoswitch, Resolution Hires

System installation
Standard AmigaOS 3.9, Boing Bags 1-4, Hard drive DH0 (System in file structure

All works fine so far.

After the standard installation of Picasso, following this link:
http://guide.abime.net/wb3.1/chap5.htm

when I reboot (step 39) I only get a black screen, the emulated Amiga won't successfully boot. When I deactivate C:LoadMonDrvs in startup-sequence the Amiga starts as expected.

Please what did I wrong?

[BigFan]

did you install 3.9 directly or after 3.1 ?

Is there another section in your startup-sequence like:

if exists devs:monitors
..
...
endif

?

this can be commented out, instead use loadmondrv then

[Toni Wilen]

Need config file and winuaelog.txt. (tick logging checkbox in misc panel to enable creation of winuaelog.txt, check paths panel for correct path).

One possible reason: too much RAM configured + 32-bit Windows. (Your config is too weird anyway, one type of fast RAM is enough..)

[mikettl]

Originally Posted by BigFan

did you install 3.9 directly or after 3.1 ?

Is there another section in your startup-sequence like:

if exists devs:monitors
..
...
endif

?

this can be commented out, instead use loadmondrv then

Hey BigFan,

many thanks :-)

yes, this section exists in the startup-sequence. I commented it out and the emulation booted again. So as next I'll check more in detail if Picasso96 works. I thought the standard installation is ok, but it seems I need to modify a bit.

Great, I appreciate your hint.

Best regards
Mike

PS
Forgot, AmigaOS 3.9 was directly installed on a blank HD (directory)

[mikettl]

Originally Posted by Toni Wilen

Need config file and winuaelog.txt. (tick logging checkbox in misc panel to enable creation of winuaelog.txt, check paths panel for correct path).

One possible reason: too much RAM configured + 32-bit Windows. (Your config is too weird anyway, one type of fast RAM is enough..)

Hey Toni,

thanks a lot :-).

Yes, the config is strange. It's just a playground config to check out what is possible with WinUAE. So I'll reconfigure the RAM.

The host system is Windows 7 64 bit 12 GB RAM, the Amiga partitions are placed on an USB HD 500 GB.

So please let me try to reconfigure the system, probably I exaggerated it. As soon as I'm ready I'll give you guys an update.

Many thanks and best regards
Mike

[mikettl]

So, run a couple of tests:


First of all the configuration only uses Z3 Fast RAM, and the VRAM was set to 16 MB (also tested 2 MB but this made no difference in the behavior). Then:

Test 1

followed BigFan's recommendation, commenting something out, but NOT using loadmondrvs. Therefore I doubleclicked on uaegfx in folder devs/monitors, then the screen became black for a couple of seconds, and I got a Guru Meditation. Afterwards the system restarted it went back to the standard.

Test 2

followed BigFan's recommendation, commenting something out, now using loadmondrvs in the startup-sequence. After starting the system the screen became black and nothing else happened, neither automatic restart nor Guru meditation.

The related log files and the configuration are attached.

Many thanks guys for your help and effort, I appreciate.

Best regards
Mike

[Toni Wilen]

1) Does it work if you disable all Z3 fast and only enable Processor Slot Fast?
2) Does it work if you use latest 3.1 beta?

(Using blizkick? Technically it is not compatible with Z3 fast only configurations, even on real hardware)

[BigFan]

i gave your playground settings a test run. works fine with wb 3.9 and p96 with uaegrfx.

there must be something missing or wrong with your p96 installation, i assume.

edit : tested on winuae 3.0.0 (2014.12.17)

[mikettl]

Originally Posted by BigFan

i gave your playground settings a test run. works fine with wb 3.9 and p96 with uaegrfx.

there must be something missing or wrong with your p96 installation, i assume.

thx BigFan,

This is strange because I just used the latest Picasso96 installation (downloaded from the link in the 1st post). So I think I need to do it again. Does it maybe make sense to use an older Picasso version?

However many thanks for your try, so it must be something on my side.

I also followed Toni's advice with version 3.1 beta but this doesn't work as well. It's obvious after your discovery.

Many thx guys, I'll spend some time to figure out.

Best regards
Mike

[Toni Wilen]

55-553 [1954 211-071]: 13: 50981000 1920x1080 UAE:1920x1080
2015-05-30 14:10:00
00-984 [2226 225-070]: Illegal instruction: 4ffe at 402A6008 -> 4FFEAF0E
00-986 [2226 224-092]: Illegal instruction: 4ffe at 402A6008 -> 4FFEAF0E
01-150 [2234 224-163]: CPU reset PC=4ffeb22c (Zorro III Fast RAM)..

Something goes wrong at this point. Try without any unofficial patches first. (Which includes BB3+)

[BigFan]

ah, i must second that. forgot to write that i've installed bb3 and 4 without crappy hacked libraries and rom-patches.
system is more close to bb2
no loadmodule entry in startup-seq, no rompatches loaded, no rom-modules excluded.

if you didn't already, start a new installation with BB1+2 , install p96. if it runs then, make a backup of your sys. i recommend using hardfiles rather than directories.

if you still dare, install BB3 + 4 carefully, (test each before continuing). but be warned: you might face more problems than you wished to solve.

[Magic]

I sure appreciate this information ^^^ I am back in to my classics again after some time away. Trying to build a current OS 3.X has been driving me nuts! Everything seems fine until I use either BB3+ or later, now I know

Is there a 3.9 installation guide with suggested upgrades and cautions about what to avoid, or is it trial and error? I am setting up several systems including an A4000D Mediator PCI system.

[BigFan]

hey , this is AMIIGGAAA -> trial and error ;D

but if you start with a good stable basis, it's less stressing to toy around with whacky tools

i made backups of all stages of installation. saved me a lot of time when rebuilding os

[mikettl]

Hey,

it works successfully now. Just following BigFan's advice NOT to install BoingBag3&4 :-). Picasso96 from AmigaOS3.9 CD is stable.

Amiga OS 3.9 on my flat screen 1920 x 1080 looks pretty good!

Thanks guys for your effort, I really appreciate.

No it's time for a backup and to continue with some other configuration enhancements:
- juggling with memory and performance
- UI improvements, especially backdrop to get rid of the rectangle
around icons, maybe GlowIcon or comparable...
- 68060 config
- PPC config (Amiga OS 4.1 FE is on the way...)
- and maybe WHDLoad (probably on another UAE configuration)

Best regards
Mike

[Magic]

Congrats that's Great!

[mikettl]

Thx Magic, I miss a like button :-)