Single Step Boot

Hi,

is there a way to single step the boot sequence to find an error, I tried the boot logging but that just told me the same as the error on the screen which is a ‘No such variable’ it comes up after the banner but that is all I can determine so far. Its an old RO4.39 machine that has not been used for a few years but time is set and if I click the error window it continues and seems to work just fine.

Thanks

You do not say which ‘boot logging’ you used, but is probably my Reporter, or Rick’s Harinezumi. If it is Reporter, and you are logging all commands issued, then the cause of the problem is likely to be in the commands just before the error – probably the one immediately before. Note that command may run a program, and it could be in that program that the missing variable is used. You probably need to dig a little deeper.

Is there a clue in the fact (afaics) that there’s no “No such variable” string in the RO sources? That would place the problem somewhere else, wouldn’t it?

You do not say which ‘boot logging’ you used

OS4.39 has boot logging built in.

Posting a log here showing a single start up might assist in pinning down where the error is coming from. OS4.39 has three Choices, Hardware Disabled, Default and Users.Single. Simply double clicking on the contents of the Choices directories might reveal the culprit.

@David: OK – I had forgotten 4.39 had some boot logging – Reporter had it some 3 years before 4.39!

Hi All,

thanks for the help, it turned out to be a copy of !SerialDev that had been put in the Apps directory that was causing the error, I moved it to its own directory (…$.Serial) and the machine boots fine now. I have no idea what the issue is with SerialDev as I have never used it.

Thanks