[iyonix-support] Re: Flashed it now, but ...

  • From: cj <chris@xxxxxxxxxxxxxxxxxxxx>
  • To: iyonix-support@xxxxxxxxxxxxx
  • Date: Sun, 31 Jan 2010 23:11:40 +0000 (GMT)

Alex

Looking at your predesk directory there are certianly a number of
things that you must have put there yourself at some time. The boot
process is obviously being interupted while running one of these
files, preventing the rest of the Predesk contents being executed.

Comparing your listing with mine there are some things that should be
there.

!+Resource
!Country
ARPLayer
Configure
DALimit
Discsetup
Miscsetup
Setupnet
Sndsetup
Winsetup
SoftSCSI

The rest could be considered 'non-essential' although you have a lot
of printer related stuff, so don't run !Printers if you take the rest
out. Unplug toolbox should be as early as possible in the boot
sequence (I think the recommended place is in !Boot.Utils) because it
must do its unplugging before any other software has used a toolbox
module.

A helpful way to proceed would be to install and setup Reporter. When
setup correctly, this will list the commands run during booting and
should give pointers to where the boot sequence is failing.

While it is not helpful to you, there are a large number of us that
simply reflashed to 5.16, rebooted, and carried on as before. Thus
there must be something in your boot sequence (most likely predesk)
that is causing the problem. The 5.16 ROM image is not the direct
problem. It may be you have a misbehaved bit of software that has
been caught out by some of the stricter checking that the OS now does
on certain code.

      Chris...

-- 


---
To alter your preferences or leave the group, 
visit //www.freelists.org/list/iyonix-support
Other info via //www.freelists.org/webpage/iyonix-support

Other related posts:

  1. Home
  2. iyonix-support
  3. Archive
  4. 01-2010