Startup not running !Boot

In the absence of a forum for “strange behaviour” I have posted this as a bug, but it is possibly just a misunderstanding.

My Iyonix was turned off and left in a cold room.
When it was switched on three weeks later it booted into mode 28 and did not run !Boot on the harddrive.

Acting on advice from Sprow I tried *opt 4,2 and reboot, but with the same result.
Looking at the output from *status showed that it was set to boot:-
*STATUS
Configuration status:

Baud 7
Boot
Cache On
No Caps
Num
Data 4
…
Mode Auto
MonitorType 1
….
TV 0,1
WimpMode Auto
FileSystem ADFS
ADFSbuffers 255
ADFSDirCache 255K
Drive 4
….
SoundDefault 1 7 4
SCSIFSDirCache 255K
SCSIFSDrive 0
BootNet Off

==========

It is now working but there are two oddities.

1)
the opt command appears to have no effect on the configuration status
ie after keying opt 4,0 – *status still showed – “boot” not the expected “No Boot”

2)
after a *configure NoBoot, the *status showed – No Boot – not surprising

However the Iyonix now boots correctly – ie it runs !Boot on drive 4: and
*status is still showing No Boot

John,

*Configure Boot sets the boot action so that on poweron, reset or Ctrl-Break it runs a boot file

*Configure NoBoot sets it so that a Shift-PowerOn , shift-reset or shift-breaks runs the boot file

Opt 4,2 *Runs the boot file and Opt4,3 *Execs it

If you were not getting to the correct screen this rather points to a corrupt boot file as by going NoBoot you will not run a boot file on a normal power on or reset.

I’d clear the contents of !Boot.Choices by renaming it and then going back to a normal *Configure Boot to check things out as this is as good a clean disc image install and you can then set things up form there.

the opt command appears to have no effect on the configuration status ie after keying opt 4,0 – *status still showed – “boot” not the expected “No Boot”

Correct.

The Boot/NoBoot status is set by *Configure Boot/NoBoot, as you say. This controls whether the system will try to boot from the configured drive, and is a system wide setting.

On the other hand, *Opt 4 applies to individual discs on the machine, and when you issue it, the currently selected drive is updated. It controls what the drive will do if the system tries to boot from it: one option is “do nothing”, but that doesn’t stop the system having a go.

*Opt 4 applies to individual discs on the machine, and when you issue it, the currently selected drive is updated. It controls what the drive will do if the system tries to boot from it:

So the *opt 4 sets a flag – Is there any way to check its status?

So the *opt 4 sets a flag – Is there any way to check its status?

A simple ‘*.’ command on the current drive will show what it is set to.

A simple ‘*.’ command on the current drive will show what it is set to.

Thanks – the fog is slowly clearing.

*Configure Boot sets the boot action so that on poweron, reset or Ctrl-Break it runs a boot file

*Configure NoBoot sets it so that a Shift-PowerOn , shift-reset or shift-breaks runs the boot file

The penny has just dropped!

The Iyonix boots with the “No Boot” option configured.
This suggests that the keyboard is dodgy the system detects a keyboard “shift” when it powers on or executes a “reset”.

So, I changed the wireless keyboard for a wired keyboard and now the behaviour is reversed.
Ie. No Boot means No Boot.
So there is something wrong with my Advent wireless keyboard not the boot process.
After a *configure boot all is well and the Iyonix boots correctly when reset.