In message <422e5be250.dougjwebb@xxxxxxxxxxxxxx> Doug Webb <doug.j.webb@xxxxxxxxxxxxxx> wrote: > In message <589557e250.Orpheus@xxxxxxxxxxxxxxx> > Alex Cessford <alex@xxxxxxxxxxxxxxx> wrote: > [snip] >> >> I have no idea where to begin to try and locate the error. I am not >> even slightly technical. Before replying here, the only thing I could >> think to do was to look once more at PreDesktop, which I've just done. >> I can't see anything there that makes any sense to me. The only reason >> I was able to spot the original 'bad' line was because it referred to >> running the softload and I had seen in replies to my previous postings >> that I should make sure that I removed softload before flashing. > No it didn't refer to the 516 softload as you stated it was for a 514 > softload so please be specific and clear on what you have been > finding. Doug, I apologise for saying 516 when it was actually 516, but please, - have a heart. I started the flashing at around 2pm today, having been assured it would be a simple process. I didn't time it, but I guess the procedure took no more than 4 minutes, so by 2:05pm it was complete. The time now, as I type is 7:05pm - FIVE HOURS LATER and I'm still struggling and no further on. (Before you say it, yes I know that using capitals is akin to shouting - or in my case, screaming!!). I'm fed up. I'm not technical, have not the slightest interest in becoming technical, just doing my best to answer kind people's queries on here as best I can. Please don't pick on me - especially as the error I made in the message didn't and won't have any effect on what is currently happened because the line in question has been removed and resulted in no improvement whatsoever. I'm sitting here struggling with a hugely magnified screen that's been in this state since 2:05pm :-( > The flash of 516 went with out pain here as it has for many others > though appreciate that you seem to have difficulties with it as well > as the 514 softload in June 09 you had as well, so it seems that > something is perhaps specific to your machine and !Boot function etc That sounds very likely. Next question - what? How do I find out? >>> '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. >> I would presume the same - but that's all it is, a presumption - I >> wouldn't know for sure at all. > [snip] >>>>>>>> >>>>>> >>>>>>> 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 > So as Bernard has also asked what is in your Boot/Predesk directory > prior to the Configure directory? > Doug I've already posted a reply to cj with both a screenshot of this directory attached and also my Desktop file from Choices.Boot John Sandford has already kindly emailed me direct to suggest that I remove Interim and LoadUSB2 permanently and also !Uniprint temporarily to see if that helps. I've done all that and re-booted - result - no difference at all. I am still staring at a magnified screen and I still got the UniServeFS not recognised error message. If you have any other advice I'd gratefully receive it. Regards, -- Alex. --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support