Boot notes

Paul Middleton boot 4.02 Link to Rob Sprowson Boot notes RISCOS is initialized; power-on self-test the system is loaded from the ROMS then the !Boot app is run which can over-ride the ROM modules Hold down Ctrl and Shift while booting. Release Shift a bit at a time to see if any error message appears on screen. Better still use !Reporter

# - show boot*

Boot$Dir : ADFS::HardDisc4.$.!BOOT Boot$OSVersion : 500 Boot$Path : ADFS::HardDisc4.$.!BOOT. Boot$State : commands Boot$ToBeLoaded : Boot:Choices.Boot.PreDesk Boot$ToBeTasks : Boot:Choices.Boot.Tasks Boot$Unique : Local BootNet$File : Freeway BootResources$Dir : ADFS::HardDisc4.$.!BOOT.Resources BootResources$Path : Boot:RO500Hook.Res.,ADFS::HardDisc4.$.!BOOT. Resources.

# - *modules - list of modules in the order in order of load

to see if an app brings in any modules, do a *mod. command load the app and do another *mod. and compare the ends of the two lists. (Verma gives a good way to look at and for modules)

# system modules

When you use the boot sequence with a given OS it sets up System$Path to be all the directories from the current version and earlier so it's all safe, thus the higher numbered ones get ignored. Of course that does mean that when you're running the highest number it will appear that modules will "work" regardless of where you put them, doing so is at your own risk!

# - emergency when m/c wont finish boot

# - (1) John P

Rapidly and repeatedly pressing Escape key (not holding) should boot without running !Boot, if the keyboard is directly in a rear socket.

# - (2) Evan Clark.

My boot sequence goes something like this: Power, HD lights come on, CD light flashes. The loudspeaker crackles briefly. There is a short pause. The Floppy disc is accessed and its light flashes. There is a longer pause (USB is being initialised, I think). ** The loudspeaker beeps and the HD light dims. The screen display comes on and !Boot runs. ** Pressing escape (and holding to be sure) at this point has for me never failed to prevent !Boot from running.

# - (3) Druck

Well you need the keyboard to work to do anything else. Holding down shift and * on the numeric keypad should boot to a command prompt. Do a *Rename !Boot Boot to stop it going through the boot sequence on subsequent reboots. Then do a *Desktop If that still hangs, its probably an application being booted from the root directory of the disc thats causing the problem. In which case repeat the above procedure and rename it without the !

# - booting from a second drive

> I have a second HD for back up. How do I use it if the first fails? Assumptions: you have both drives fitted at the time of the problem Therefore you are booting normally from drive 4. About now, go to a command prompt and type Drive 5 opt 4,2 and exit the prompt. Your copied disc can now be used to boot. When you want to change over, if the boot disc isn't working: Hold down shift when booting, and at the * prompt type: configure drive 5. Then you reboot. If the original was working you can do this from a * prompt before you reboot. Fix up all the error messages caused by the boot drive now having a different name. Tip: after the first, very slow boot while you acknowledge all the errors, rename the original boot disc (if it is still recognised) then rename the new boot disc to be the original name of the disc you use to boot from. The next reboot should be clean. Alan Adams, from Northamptonshire alan.adams@orchard-way.freeserve.co. uk

# - dont do this in boot.predesktop :-

Filer_Run ADFS::HardDisc5.$.SCRAPZ.!Scrap |**** above command causes mayhem eg | boot failure and no keyboard among other things

# - restore ADFS icons to iconbar

You can easily bring back the ADFSFiler icons when you stop the module task or kill the module. I do this this all the time. I've written my own ADFSFiler (with the help of Director) but sometimes I need the ADFSFiler for some tasks like formatting. Anyway just open (with shift doubleclick) !Internet in Boot.Resources and go to dir Utils. Doubleclick on the absolute file NewFiler and voil� the ADFSFiler icons are back again. This works for every killed FSFiler (RAMFS, SCSIFS etc) task. If you accidentally killed the ADFSFiler module, you have to *RMReinit it first. does not work if you kill filer harddisc5 disappears

# emergency reset CMOS

There is an emergency reset from the command line: *fx 162,239,0 which corrupts the cmos checksum, then a reboot, which loads the default cmos settings. thanks to Dave Wisnia

#-poweron reset & break emergency keys
*help poweron
   => Help on keyword PowerOn
   When the machine is switched on, the following keys have an effect:
   R causes the operating system's CMOS RAM to be reset.
   DELETE causes all the machine's CMOS RAM to be reset.
   T and COPY are similar to R and DELETE, but set the opposite
   configured sync.
   0 to 9 on the keypad reset (just) the configured monitor type.
   Keypad dot sets the configured mode, sync and monitor type to Auto.
   See also *Help Reset and *Help Break.
   >> John Ballance advised press f12 and type in *fx 162,239,255
   >> followed by two presses of the Return key.
   >> Once you've returned to the desktop restart your Iyonix and you should
   >> find that the CMOS has been reset to its default parameters.

*help reset
   => Help on keyword Reset
   When Reset is pressed, the following keys have an effect:
   SHIFT causes an autoboot (unless Boot is configured).
   keypad-* causes the supervisor to be run rather than the configured
   language.
   See also *Help PowerOn.
*help break
   => Help on keyword Break
   The Break key either terminates tasks, or (with CTRL or SHIFT) acts
   like the Reset button.
   When Reset is pressed, the following keys have an effect:
   SHIFT causes an autoboot (unless Boot is configured).
   keypad-* causes the supervisor to be run rather than the configured
   language.
   See also *Help PowerOn.
   *