Picasso96 problem

[Oldsmobile_Mike]

So you're saying that since you manually removed CGX and installed P96, your Amiga no longer reboots properly when you press Ctrl+A+A? At what point during Startup-Sequence does it freeze? Not familiar with CGX but are parts of it "reset resident"?

I'd start by confirming if it's hardware or software. If you boot off something like a game disk and press Ctrl+A+A, does it reboot properly then?  Also, are you using the latest version of P96 from here?  http://lilliput.amiga-projects.net/Picasso96.htm

[Oldsmobile_Mike]

How about removing P96 just to confirm that the problem goes away?

There is a command to make Startup-Sequence echo back each line as it's executed.  Damned if I can remember what it is.  I should write it on a post-it note on my monitor for the number of times people in this forum need it.  

Barring that, just edit your Startup-Sequence to have it print a number to the screen as each line is executed so you know where it freezes.  

[Oldsmobile_Mike]

How I do that?

I don't want to sound like a smartass, but your signature shows you've got like a half-dozen very souped-up Amiga's.  You don't know how to edit your startup sequence?

Just put "echo 1" "echo 2" "echo 3" between each line of your startup sequence.  It will print the number on the screen as it's executing.  Count whichever line it gets to.  When it stops, you've found your culprit.

There is also a much easier way to do this automatically, but %#%) if I can remember what it is.  Google?

[Oldsmobile_Mike]

TL;DR. Found it. See Thomas's comment #8 in this thread:

http://www.amiga.org/forums/showpost.php?p=779280&postcount=8

I should stick that on a post-it note and just give to everyone who has issues with startup-sequence.

[Oldsmobile_Mike]

That's all too complicated. If you are using Os 3.9, simply put set interactive on at the start of the startup-sequence. This will hold the Shell on every line, will print the command being executed, and allows you to continue with RETURN, "n" to skip or q to quit the interactive mode.

@THOR - you rock. I wish we had a way of doing "stickies" of the best troubleshooting tips that everyone seems to forget.