You're saying it boots now, whereas before you said it was at the purple 'insert disk' type screen. Do you think then that putting the 'p' on the ACATune line to delay the startup is actually causing your black screen after it boots? If it is indeed booting from the hard drive now, try changing the ACATune line to just the basic option and cold boot:
C:ACATune >ram:acaoutput.txt
Or better still, before you do that just put a ';' at the beginning of the ACATune line so that it comments the line out (which means it will read the line as a comment and will not execute the ACATune command line). Your Startup-Sequence will then act as if the ACATune line isn't even there, so that we can see if you can boot correctly again without the ACATune line.
;C:ACATune -cache on - burst on....ETC
So, if booting from your Workbench floppy; to edit the CF Hard Drive Startup-Sequence you'd type 'ed dh0:s/startup-sequence' into a shell, or use the Execute Command in the Workbench menu.
Ok. I accessed the startup sequence via the shell, having booted from floppy. I removed the "P". I then turned the power brick off and then back on. It now goes straight to the insert floppy disc screen. There was no hardrive activity at all.
One curious thing, and Ive double checked, If put the W.B 3.1 floppy in the drive and then power on at the brick, It boots into the cf hardrive desktop.
Here the W.B 3.1 floppy icon is selectable. If I attempt to load anything via the cf desktop it says programs/tools not found etc. Here i can access the cfcard startup sequence via the w.b 3.1 floppy.
However, if I turn on the amiga at the brick and then insert the W.B 3.1 floppy, it boots staright into the W.B 3.1 floppy desktop. Here there is no visible sign of the cf desktop. Strange.
And here i cannot access the cfcard startup sequence via the w.b 3.1 floppy.
And yes indeed, adding the ";" to the startup sequence has fixed the cf card. Its working fine again. Damn good thinking chap!
But we are back to the same problem...I have to manually add the other mem via the maprom * command.
Perhaps the acatune startup command would have to be placed somewhere else in the startup sequence. Perhaps classic workbench is
loading something else first? Or there is some kind of confliction?