startup-sequence can't get past IPrefs

Working fine up to now, when
all of a sudden, booting my Sam440 flex, OS4.1 Upd3 hangs up with the boot image displayed.

If I do a early boot menu boot-without-the-startup file, it goes into the bootup shell fine, and if I then type an "execute startup-sequence" from that shell, it all seems to work, and I end up with my system just as it should be and everything working fine! USB, Network, ScreenMode, etc.

Inserting "ECHO >> file" statements into startup-sequence indicates that it gets to the IPrefs command but no further.

Anyone seen this symptom? It seems similar to other reports, but I have not seen one that works so well doing the startup-sequence after the boot to shell.

Seems like it must be a timing thing, but I'm not sure what to do next.
Any suggestions?

Thanks,

Tom

Thanks. It was not the UBOOT date though.

Ended up renaming all the *.prefs files in SYS:Env-Archive/sys/
to *.prefsX. Boot was ok with all these prefs files removed.

Began renaming them back one by one, with a re-boot to test each one.

Apparently, there was some problem with gui.prefs, since only its restoration made the problem recur.

Funny that the Prefs program accepted that file with no problem, and I did not see anything in the displayed choices that seemed odd.

A completely new gui.prefs from scratch seems to boot fine now. Most of the settings are the same, but I have not checked every one yet.

Tom

Good.

If you still have the faulty gui.prefs file, send it to me. I'll see if we can fix the bug in iprefs.
Send it to elwoodb free fr.

Quote:

Next time just add "set echo on" to the top of the startup-sequence and everything it does is echoed to the boot cli window (the boot pic is closed/hidden automatically with this option).

Quote:

Ah. I didn't know that.

In fact, putting this in causes the problem to disappear!

Further investigation shows that adding even just one
"ECHO XXX" statement will do the same.

May be something to do with a delayed window open for the bootup CLI?
Somehow, that gui.prefs has something that gets into a deadlock if the window has not opened.

Tom