Auto_adm and Modifying Kernel Prompt

[Stephen Keane]

The error message you are getting on boot is saying that the ISL can't be loaded. The server hasn't read the AUTO file yet.

We had already got rid of this error by using the -K2 and -T-12289 flags on the lifcp command, and you had got your ISL loading.

Then you were getting an actual AUTO file format error, which is what I was attempting to fix. Why have we gone backwards?

What media are you using to boot from, tape, CD?

[Mark Cater_3]

I mixed up the different versions of AUTO/bootlif, as i was trying various options.
I now have a folder just for this forum.

The OS (11.11) has been loaded onto the ignite server and that is what i am using.

so currently at:
lifcp -K2 -T-12289 AUTO /opt/ignite/boot/boot_lif:
and gives error on boot:
Auto-execute file input string exceeds 2048 characters -- autoboot aborted
If i do:
lifrm boot:AUTO
lifcp -K2 AUTO /opt/ignite/boot/boot_lif:
# lifls -l boot_lif
volume ISL10 data size 859365 directory size 2 04/09/08 22:01:48
filename type start size implement created
===============================================================
ISL -12800 16 242 0 04/09/08 22:39:10
AUTO ASCII 264 2 0 05/04/13 14:59:28
HPUX -12928 272 1024 0 04/09/08 22:39:10

the boot error is:
Booting...
Boot IO Dependent Code (IODC) revision 3

HARD Booted.

ISL Revision A.00.44 Mar 12, 2003

[Stephen Keane]

We need to concentrate on the

Auto-execute file input string exceeds 2048 characters -- autoboot aborted

error. It suggests to me that your new AUTO file isn't terminated properly in some way that the original one was.

If you lifcp the old AUTO file to stdout and pipe the output through xd, then do the same for the new AUTO file, the only difference should be the 120->60 and 1->2 changes. Pay particular attention to the ends of the lines (they should have LF at the end) and the last character before the block of zeroes at the end.