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

  • From: John Ballance <jwb@xxxxxxxxxx>
  • To: iyonix-support@xxxxxxxxxxxxx
  • Date: Sun, 31 Jan 2010 16:37:09 +0000

Title: (no subject)
effectively the same answer holds .. ANY error in the boot sequence will prevent the sequence completing fully

So.. find the cause of this error and resolve it.

'UniServeFS' .. not personally familiar with this, but presume its part of !Uniprint or similar.. In any case, it is the disc load that is complaining.. this is NOT a rom based item.


JB

--

John Ballance C.Eng MIET - jwb@xxxxxxxxxx - 07976 295923


John says: Free Utilities? -> http://www.ucallusave.co.uk



For a registration fee (which can be refunded) of £199.75 I specialise 

in helping people set up their own business in their spare time. 

Imagine having your own utilities business - that’s gas, electricity, 

telephones and the internet. These are major expenses for every 

home and business in the country. There is no stock to buy and 

the money is handled for you. All you do is guarantee to save 

people money and help them fill in a simple one page form, or they 

can use the internet. After that, every time they pay their bills, you 

get about 5%. If you can spare a couple of hours a week, I will 

guarantee your success.

        Interested?       Call me now: 0800 298 0768




Alex Cessford wrote:
In message <4B65A5D7.104@xxxxxxxxxx>
          John Ballance <jwb@xxxxxxxxxx> wrote:

  
Hi
you've spotted it..
command returning error as softload not there .. hence boot sequence stops
hence remove that offending line
JB
John Ballance C.Eng MIET - jwb@xxxxxxxxxx - 07976 295923
    
Hi John, thanks for helping me.
Unfortunately, this cure has not worked!
After reading your reply, I suddenly noticed that this offending line 
should *not* (as far as my limited knowledge goes), have made any 
difference - because it was REM-ed out with a |
I deleted it anyway, re-saved it, checked that the re-save had 
resulted in the file now being minus that line, then re-booted.
Result - no change. Display still huge, Display Manager cannot be 
altered.

By the way, the re-boot process reminded me of the other hiccup that I 
forgot to mention the first time:
After the Iyonix RO5 splash banner, I get  ERROR: Filename 
'UniServeFS' not recognised. and a Cancel button only offered. I duly 
cancel and after a short, but quite significant pause, it proceeds to 
the desktop.
Now what, please?



  
Alex Cessford wrote:
    
In message <499c4be250.Bernard@xxxxxxxxxxxxxxxx>
          Bernard Veasey <bernard@xxxxxxxxxxxxxx> wrote:


      
In message <b8e94ae250.Orpheus@xxxxxxxxxxxxxxx>
          Alex Cessford <alex@xxxxxxxxxxxxxxx> wrote:

        
      
Ok, now flashed to 5.16.

          
      
All seems fine but small hiccup.

          
      
I have very carefully recorded all messages, etc, in case I need to
re-tell them. Hopefully I won't.

          
      
So, short version:
Task Manager Info now says 5.16
I am using a Digimate 19" flatscreen. The display is huge.
Checked Display Manager, results as follows:
    Colours:    256     (menu all greyed-out)
    Resolution: 640x480 (drop-down menu button doesn't respond)
    Frame Rate  Unknown (drop-down menu button doesn't respond)

          
      
I would say something in your !Boot.Choices.Boot.PreDesk
has gone wrong before it reaches: !Boot.Choices.Boot.PreDesk.Configure
Open the PreDesk folder and tell us what is there before 'Configure'.

        
      
Bernard

        
Bernard, I am so very grateful for your near-instant response. Thank
you so much.
Ok, I've attached PreDesk. However, whilst being strictly
non-technical, I think I might have spotted the problem. The last line
reads:
| Put other things which need setting up here.
|RMEnsure UtilityModule 5.14 Run
!Boot.Choices.Boot.PreDesk.Softload.go514
|End

So am I right that this instruction to run Softload.go514 should be
deleted? I *did* ensure that I removed Softload itself from !Boot
before I re-flashed.



      


  
__________ Information from ESET Smart Security, version of virus
signature database 4822 (20100131) __________
    
  
The message was checked by ESET Smart Security.
    
  
http://www.eset.com
    

  

Other related posts: