Picasso96 problem

[utri007]

Currently my Amiga boots workbench nicely, but I need shutdown it to reboot for several seconds. A + A + CTRL doesn't boot to Workbench anymore.

I removed CGX manually and installed Picasso96. Wonder if there is something left from CGX doing that?

[guest11527]

Currently my Amiga boots workbench nicely, but I need shutdown it to reboot for several seconds. A + A + CTRL doesn't boot to Workbench anymore.

I removed CGX manually and installed Picasso96. Wonder if there is something left from CGX doing that?

Unclear what the problem actually is. Ctrl+A+A is in no relation to graphics drivers. Thus, which Amiga do you have? A big-box Amiga with a separate keyboard, or a small stand-alone device? I'm asking because the reset logic works different. The big-box Amigas have the possibility to intercept the reset signal, which is used by programs like DiskSafe to shut down the harddrives savely before rebooting.

[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

[danbeaver]

I hate to throw in a Red Herring, but does your Setpatch load a ROM update that would interfere with getting to WorkBench.  I do lots rebuilds of Amigas that I rebuild and have found this a common problem as I install updates, Boing Bags and such.

[utri007]

I have a towerized A1200 with Zorro II extender.

Setpatch loads 3.9 BB1 update.

I don't know what point of startup-sequence it freezes.

Yes I manually removed CGX, there was no problem with CGX, it appeared with Picasso96

I have already tried both of installs from aminet and lilliput.amiga-projects.net

[danbeaver]

Well I'm glad it's not the Startup-Sequence!

[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.  

[utri007]

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.

How I do that?

[psxphill]

How I do that?

you'd insert lines like

echo 1
(command)
echo 2
(command)
echo 3
 (command)
 
 Then you'd know when it stops. The echos will cause the screen to open earlier though.

[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.

[zipper]

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.  

put on the first line of startup-sequence:
set echo on
so you can see where it stalls

...pah, too slow...

[psxphill]

put on the first line of startup-sequence:
set echo on
so you can see where it stalls

...pah, too slow...

When was "set echo on" added? I guess I missed that in all my amiga years.

[utri007]

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?

No problem, I do know how to edet startup-sequence, just haven't use echo command earlier on Amiga.

PS. Thanks, I need to edit my signature

[guest11527]

put on the first line of startup-sequence:
set echo on
so you can see where it stalls

...pah, too slow...

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.

I would probably guess that the P96 screen modes are missing, which might be the reason by the screen remains blank.   Merry Christmas!