Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.acorn.misc > #13633 > unrolled thread

failure to complete Boot - any help please

Started bycdecordova <chrisdecordova@gmail.com>
First post2016-01-17 07:54 -0800
Last post2016-01-28 00:34 +0100
Articles 20 on this page of 25 — 9 participants

Back to article view | Back to comp.sys.acorn.misc


Contents

  failure to complete Boot - any help please cdecordova <chrisdecordova@gmail.com> - 2016-01-17 07:54 -0800
    Re: failure to complete Boot - any help please freak6767@freakmail.de - 2016-01-17 23:16 +0100
      Re: failure to complete Boot - any help please Stuart <Spambin@argonet.co.uk> - 2016-01-17 23:55 +0000
        Re: failure to complete Boot - any help please freak6767@freakmail.de - 2016-01-19 01:17 +0100
          Re: failure to complete Boot - any help please Stuart <Spambin@argonet.co.uk> - 2016-01-19 02:11 +0000
            Re: failure to complete Boot - any help please freak6767@freakmail.de - 2016-01-20 00:01 +0100
              Re: failure to complete Boot - any help please Stuart <Spambin@argonet.co.uk> - 2016-01-19 23:30 +0000
              Re: failure to complete Boot - any help please cdecordova <chrisdecordova@gmail.com> - 2016-01-20 02:22 -0800
          Re: failure to complete Boot - any help please "Chris Evans (CJE/4D)" <chris@cjemicros.co.uk> - 2016-01-20 09:57 +0000
          Re: failure to complete Boot - any help please dec <chrisdecordova@gmail.com> - 2016-01-27 06:07 -0800
            Re: failure to complete Boot - any help please Russell Hafter News <see.sig@russellhafter.me.invalid> - 2016-01-27 14:33 +0000
              Re: failure to complete Boot - any help please dec <chrisdecordova@gmail.com> - 2016-01-27 08:45 -0800
      Re: failure to complete Boot - any help please cdecordova <chrisdecordova@gmail.com> - 2016-01-20 02:25 -0800
      Re: failure to complete Boot - any help please dec <chrisdecordova@gmail.com> - 2016-01-27 06:05 -0800
    Re: failure to complete Boot - any help please Stuart <Spambin@argonet.co.uk> - 2016-01-17 23:46 +0000
    Re: failure to complete Boot - any help please Andrew Wickham <ajw99uk@yahoo.co.uk> - 2016-01-20 07:04 -0800
      Re: failure to complete Boot - any help please dec <chrisdecordova@gmail.com> - 2016-01-27 06:11 -0800
        Re: failure to complete Boot - any help please dec <chrisdecordova@gmail.com> - 2016-01-27 06:14 -0800
          Re: failure to complete Boot - any help please News <chrisjohnson@spamcop.net> - 2016-01-27 15:20 +0000
            Re: failure to complete Boot - any help please dec <chrisdecordova@gmail.com> - 2016-01-27 08:46 -0800
          Re: failure to complete Boot - any help please Andrew Wickham <ajw99uk@yahoo.co.uk> - 2016-01-29 07:30 -0800
            Re: failure to complete Boot - any help please Andrew Wickham <ajw99uk@yahoo.co.uk> - 2016-01-29 07:36 -0800
              Re: failure to complete Boot - any help please Alan Griffin <ajg@argonet.co.uk> - 2016-01-29 17:14 +0000
              Re: failure to complete Boot - any help please Stuart <Spambin@argonet.co.uk> - 2016-01-29 18:00 +0000
        Re: failure to complete Boot - any help please freak6767@freakmail.de - 2016-01-28 00:34 +0100

Page 1 of 2  [1] 2  Next page →


#13633 — failure to complete Boot - any help please

Fromcdecordova <chrisdecordova@gmail.com>
Date2016-01-17 07:54 -0800
Subjectfailure to complete Boot - any help please
Message-ID<df3cb67d-7e36-4169-b319-5544cfe7f499@googlegroups.com>
It's an A5000 running RO3.7

I either get it flashing through the colours and sticking on red - with multiple horizontal black lines

or occasionally as far as 

risc os 4988 (or simimlar)
supervisor
*

I have tried R+ break,

CTRL + anything does not work.

Any ideas please?

[toc] | [next] | [standalone]


#13636

Fromfreak6767@freakmail.de
Date2016-01-17 23:16 +0100
Message-ID<e9b5904355.JF@freak67>
In reply to#13633
In Nachricht <df3cb67d-7e36-4169-b319-5544cfe7f499@googlegroups.com>
          cdecordova <chrisdecordova@gmail.com> haben Sie geschrieben:

> It's an A5000 running RO3.7

> I either get it flashing through the colours and sticking on red -
> with multiple horizontal black lines

> or occasionally as far as

> risc os 4988 (or simimlar)
> supervisor
> *

> I have tried R+ break,

> CTRL + anything does not work.

> Any ideas please?

Hallo,

has the A5000 perhaps been stored a longer time before you recently 
powered it up again?
In this case it could be, that the CMOS-battery is defect/empty and 
your CMOS-settings are unrestorable or meaningless for the computer.
Sometimes, if the battery is changed or charged (I don't know if the 
A5000 has an rechargable or real battery builtin) and if the 
rechargeable battery isn't defect (Poweron the Computer and regardless 
of it's behaviour let it on for some minutes) you could poweron and 
press the delete-button the same time, to reset the whole CMOS.

Another reason could be, that after your Poweron-Reset +Break all
CMOS-settings are deleted/resetted and now any podules (e.g. IDE, SCSI 
etc.) must be found again. This procedure sometimes take a while, so 
after Poweron you could try waiting some minutes or so, with a bit of 
luck it will boot to the desktop.
Otherwise, if you get a *-Prompt, try typing "desktop" to boot to 
desktop.

Hope this helps a bit.

Greetings, Jürgen

[toc] | [prev] | [next] | [standalone]


#13638

FromStuart <Spambin@argonet.co.uk>
Date2016-01-17 23:55 +0000
Message-ID<554399d23aSpambin@argonet.co.uk>
In reply to#13636
In article <e9b5904355.JF@freak67>,
   <freak6767@freakmail.de> wrote:
> Hallo,

> has the A5000 perhaps been stored a longer time before you recently 
> powered it up again?
> In this case it could be, that the CMOS-battery is defect/empty and 
> your CMOS-settings are unrestorable or meaningless for the computer.
> Sometimes, if the battery is changed or charged (I don't know if the 
> A5000 has an rechargable or real battery builtin)

Rechargeable like all older RISC OS kit. If it fails the RTC will
frequently fail to re-start even after the battery has been replaced.

The answer is here:

http://www.cjemicros.co.uk/micros/products/rtc.shtml

> and if the rechargeable battery isn't defect (Poweron the Computer and
> regardless of it's behaviour let it on for some minutes) you could
> poweron and press the delete-button the same time, to reset the whole
> CMOS.

-- 
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/

[toc] | [prev] | [next] | [standalone]


#13642

Fromfreak6767@freakmail.de
Date2016-01-19 01:17 +0100
Message-ID<899c1f4455.JF@freak67>
In reply to#13638
In Nachricht <554399d23aSpambin@argonet.co.uk>
          Stuart <Spambin@argonet.co.uk> haben Sie geschrieben:

> Rechargeable like all older RISC OS kit.
Not sure ;-) ... my A410/1 has non-chargeable batteries.

> If it fails the RTC will
> frequently fail to re-start even after the battery has been replaced.
A longer time ago I had similiar problems as the TO and (as you wrote) 
the RTC failed. So I have changed the battery, waited some days, 
without doing anything on the comp, and afterwards the A410 booted up 
correctly. The only oddity was, that the RTC didn't run the time 
further, it always showed the same time, that I set before. Waiting 
again some days, it later worked as expected, without doing anything 
to it. I think that was luck :-) .

> The answer is here:

> http://www.cjemicros.co.uk/micros/products/rtc.shtml
Ahh, very nice to know :-) , does anybody know if this hardware is 
working in an A410? Just asking out of interest, as told, my RTC is 
working again (but one never knows what will happen in future...).

Greetings, Jürgen

[toc] | [prev] | [next] | [standalone]


#13643

FromStuart <Spambin@argonet.co.uk>
Date2016-01-19 02:11 +0000
Message-ID<55442a10f0Spambin@argonet.co.uk>
In reply to#13642
In article <899c1f4455.JF@freak67>,
   <freak6767@freakmail.de> wrote:
> > Rechargeable like all older RISC OS kit.
> Not sure ;-) ... my A410/1 has non-chargeable batteries.

OK, fair enough, but as the owner of an A5000 in which I have replaced the
battery I know the A5000 is a rechargeable. I also changed one for a
fellow member of the MUG    http://www.mug.riscos.org/   group on Saturday.

We also resurrected two A3000s using the product mentioned from CJE.

-- 
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/

[toc] | [prev] | [next] | [standalone]


#13644

Fromfreak6767@freakmail.de
Date2016-01-20 00:01 +0100
Message-ID<c3829c4455.JF@freak67>
In reply to#13643
In Nachricht <55442a10f0Spambin@argonet.co.uk>
          Stuart <Spambin@argonet.co.uk> haben Sie geschrieben:

> In article <899c1f4455.JF@freak67>,
>    <freak6767@freakmail.de> wrote:
>>> Rechargeable like all older RISC OS kit.
>> Not sure ;-) ... my A410/1 has non-chargeable batteries.

> OK, fair enough, but as the owner of an A5000 in which I have replaced the
> battery I know the A5000 is a rechargeable. I also changed one for a
> fellow member of the MUG    http://www.mug.riscos.org/   group on Saturday.

> We also resurrected two A3000s using the product mentioned from CJE.

Good to know it works.


After reading the original post once more, there was one thing 
catching eye:
> It's an A5000 running RO3.7
True or a typo? AFAIK 3.7 is RiscPC only, the A5000 should have 3.1x 
or similiar. Or a RiscPC in an A5000-case (if possible)?

> or occasionally as far as

> risc os 4988 (or simimlar)
Mmmhhh... something is a little bit unsorted here ;-) or could it be,
that the ROMs are broken? Are these the original A5000-ROMs?

> supervisor
> *

Greetings, Jürgen

[toc] | [prev] | [next] | [standalone]


#13645

FromStuart <Spambin@argonet.co.uk>
Date2016-01-19 23:30 +0000
Message-ID<55449f333cSpambin@argonet.co.uk>
In reply to#13644
In article <c3829c4455.JF@freak67>,
   <freak6767@freakmail.de> wrote:
> Good to know it works.


> After reading the original post once more, there was one thing 
> catching eye:
> > It's an A5000 running RO3.7
> True or a typo? AFAIK 3.7 is RiscPC only, the A5000 should have 3.1x 
> or similiar.

I noticed that too but decided to "let it pass"

> Or a RiscPC in an A5000-case (if possible)?

> > or occasionally as far as

> > risc os 4988 (or simimlar)
> Mmmhhh... something is a little bit unsorted here ;-) or could it be,
> that the ROMs are broken? Are these the original A5000-ROMs?

(or similar!) I decided it was declaring 4M of RAM - 4096 (k)

-- 
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/

[toc] | [prev] | [next] | [standalone]


#13646

Fromcdecordova <chrisdecordova@gmail.com>
Date2016-01-20 02:22 -0800
Message-ID<e9084c68-abda-4e65-ae5c-f5431f4f5aae@googlegroups.com>
In reply to#13644
On Tuesday, January 19, 2016 at 11:00:46 PM UTC, frea...@freakmail.de wrote:

> After reading the original post once more, there was one thing 
> catching eye:
> > It's an A5000 running RO3.7
> True or a typo? AFAIK 3.7 is RiscPC only, the A5000 should have 3.1x 
> or similiar.

That is very likely to be my memory, since I could not boot it up.
Does it make any difference?

I shall have a look at the battery ideas - I wondered about this.

[toc] | [prev] | [next] | [standalone]


#13650

From"Chris Evans (CJE/4D)" <chris@cjemicros.co.uk>
Date2016-01-20 09:57 +0000
Message-ID<ant200942345pErr@client.cjemicros.co.uk>
In reply to#13642
In article <899c1f4455.JF@freak67>, <URL:mailto:freak6767@freakmail.de> wrote:
> In Nachricht <554399d23aSpambin@argonet.co.uk>
>           Stuart <Spambin@argonet.co.uk> haben Sie geschrieben:
> 
> > Rechargeable like all older RISC OS kit.
> Not sure ;-) ... my A410/1 has non-chargeable batteries.
> 
> > If it fails the RTC will
> > frequently fail to re-start even after the battery has been replaced.
> A longer time ago I had similiar problems as the TO and (as you wrote) 
> the RTC failed. So I have changed the battery, waited some days, 
> without doing anything on the comp, and afterwards the A410 booted up 
> correctly. The only oddity was, that the RTC didn't run the time 
> further, it always showed the same time, that I set before. Waiting 
> again some days, it later worked as expected, without doing anything 
> to it. I think that was luck :-) .
> 
> > The answer is here:
> 
> > http://www.cjemicros.co.uk/micros/products/rtc.shtml
> Ahh, very nice to know :-) , does anybody know if this hardware is 
> working in an A410? Just asking out of interest, as told, my RTC is 
> working again (but one never knows what will happen in future...).

I'm 99% sure it will work. Most RTC problems are caused by a leaking battery
and as the Batteries used on the Archimedes weren't PCB mounted, I don't
think we've come across an RTC fault on one.

I will double check when I get a chance. Though I can't think how we could
test on an Archimedes with a working RTC. Just removing the battery isn't
enough as you'd have two RTC chips on the same I2C bus.


Chris Evans

-- 

**** IGEPv5: The fastest RISC OS computer so far! ****
--------- http://www.cjemicros.co.uk/igepv5 ----------
CJE Micro's  / 4D                'RISC OS Specialists' 
Telephone: 01903 523222              Fax: 01903 213901
chris@cjemicros.co.uk      http://www.cjemicros.co.uk/ 
78 Brighton Road, Worthing, West Sussex,      BN11 2EN 

Don't let the urgent things in life, crowd out the important things!

[toc] | [prev] | [next] | [standalone]


#13697

Fromdec <chrisdecordova@gmail.com>
Date2016-01-27 06:07 -0800
Message-ID<daa87b14-4633-4dcb-831f-2fb1db424557@googlegroups.com>
In reply to#13642
On Tuesday, January 19, 2016 at 12:22:39 AM UTC, frea...@freakmail.de wrote:
> In Nachricht <554399d23aSpambin@argonet.co.uk>
>           Stuart <Spambin@argonet.co.uk> haben Sie geschrieben:
> 
> > Rechargeable like all older RISC OS kit.
> Not sure ;-) ... my A410/1 has non-chargeable batteries.
> 
> > If it fails the RTC will
> > frequently fail to re-start even after the battery has been replaced.
> A longer time ago I had similiar problems as the TO and (as you wrote) 
> the RTC failed. So I have changed the battery, waited some days, 
> without doing anything on the comp, and afterwards the A410 booted up 
> correctly. The only oddity was, that the RTC didn't run the time 
> further, it always showed the same time, that I set before. Waiting 
> again some days, it later worked as expected, without doing anything 
> to it. I think that was luck :-) .
> 
> > The answer is here:
> 
> > http://www.cjemicros.co.uk/micros/products/rtc.shtml
> Ahh, very nice to know :-) , does anybody know if this hardware is 
> working in an A410? Just asking out of interest, as told, my RTC is 
> working again (but one never knows what will happen in future...).
> 
> Greetings, Jürgen

What is RTC please?

[toc] | [prev] | [next] | [standalone]


#13700

FromRussell Hafter News <see.sig@russellhafter.me.invalid>
Date2016-01-27 14:33 +0000
Message-ID<55488cb227see.sig@russellhafter.me.invalid>
In reply to#13697
In article
<daa87b14-4633-4dcb-831f-2fb1db424557@googlegroups.com>,
   dec <chrisdecordova@gmail.com> wrote:

> On Tuesday, January 19, 2016 at 12:22:39 AM UTC,
> frea...@freakmail.de wrote:

> > In Nachricht <554399d23aSpambin@argonet.co.uk> Stuart
> >           <Spambin@argonet.co.uk> haben Sie geschrieben:

> > > Rechargeable like all older RISC OS kit.

> > Not sure ;-) ... my A410/1 has non-chargeable batteries.

> > > If it fails the RTC will frequently fail to re-start
> > > even after the battery has been replaced.
> > A longer time ago I had similiar problems as the TO and
> > (as you wrote) the RTC failed. So I have changed the
> > battery, waited some days, without doing anything on
> > the comp, and afterwards the A410 booted up correctly.
> > The only oddity was, that the RTC didn't run the time
> > further, it always showed the same time, that I set
> > before. Waiting again some days, it later worked as
> > expected, without doing anything to it. I think that
> > was luck :-) .

> > > The answer is here:

> > > http://www.cjemicros.co.uk/micros/products/rtc.shtml
> > Ahh, very nice to know :-) , does anybody know if this
> > hardware is working in an A410? Just asking out of
> > interest, as told, my RTC is working again (but one
> > never knows what will happen in future...).
> > 
> > Greetings, Jürgen

> What is RTC please?

Real Time Clock

-- 
Russell
Russell Hafter
E-mail to russell at russellhafter dot me dot uk
Need a hotel? <http://www.hrs.com/?client=en__blue&customerId=416873103>

[toc] | [prev] | [next] | [standalone]


#13702

Fromdec <chrisdecordova@gmail.com>
Date2016-01-27 08:45 -0800
Message-ID<d99a2ba8-7160-43ad-9bc3-67c310c87ad9@googlegroups.com>
In reply to#13700
On Wednesday, January 27, 2016 at 2:33:37 PM UTC, Russell Hafter News wrote:
> In article
> <daa87b14-4633-4dcb-831f-2fb1db424557@googlegroups.com>,
>    dec <chrisdecordova@gmail.com> wrote:
> 
> > On Tuesday, January 19, 2016 at 12:22:39 AM UTC,
> > frea...@freakmail.de wrote:
> 
> > > In Nachricht <554399d23aSpambin@argonet.co.uk> Stuart
> > >           <Spambin@argonet.co.uk> haben Sie geschrieben:
> 
> > > > Rechargeable like all older RISC OS kit.
> 
> > > Not sure ;-) ... my A410/1 has non-chargeable batteries.
> 
> > > > If it fails the RTC will frequently fail to re-start
> > > > even after the battery has been replaced.
> > > A longer time ago I had similiar problems as the TO and
> > > (as you wrote) the RTC failed. So I have changed the
> > > battery, waited some days, without doing anything on
> > > the comp, and afterwards the A410 booted up correctly.
> > > The only oddity was, that the RTC didn't run the time
> > > further, it always showed the same time, that I set
> > > before. Waiting again some days, it later worked as
> > > expected, without doing anything to it. I think that
> > > was luck :-) .
> 
> > > > The answer is here:
> 
> > > > http://www.cjemicros.co.uk/micros/products/rtc.shtml
> > > Ahh, very nice to know :-) , does anybody know if this
> > > hardware is working in an A410? Just asking out of
> > > interest, as told, my RTC is working again (but one
> > > never knows what will happen in future...).
> > > 
> > > Greetings, Jürgen
> 
> > What is RTC please?
> 
> Real Time Clock
> 
> -- 
> Russell
> Russell Hafter
> E-mail to russell at russellhafter dot me dot uk
> Need a hotel? <http://www.hrs.com/?client=en__blue&customerId=416873103>

OK ta. Better re-read everything then, to see if it makes any more sense....

[toc] | [prev] | [next] | [standalone]


#13647

Fromcdecordova <chrisdecordova@gmail.com>
Date2016-01-20 02:25 -0800
Message-ID<cd4a1d3e-6df7-44af-a138-31d4878ef0af@googlegroups.com>
In reply to#13636
On Sunday, January 17, 2016 at 11:23:03 PM UTC, frea...@freakmail.de wrote:
> In Nachricht <df3cb67d-7e36-4169-b319-5544cfe7f499@googlegroups.com>
>           cdecordova <chrisdecordova@gmail.com> haben Sie geschrieben:
> 
> > It's an A5000 running RO3.7
> 
> > I either get it flashing through the colours and sticking on red -
> > with multiple horizontal black lines
> 
> > or occasionally as far as
> 
> > risc os 4988 (or simimlar)
> > supervisor
> > *
> 
> > I have tried R+ break,
> 
> > CTRL + anything does not work.
> 
> > Any ideas please?
> 
> Hallo,
> 
> has the A5000 perhaps been stored a longer time before you recently 
> powered it up again?
> In this case it could be, that the CMOS-battery is defect/empty and 
> your CMOS-settings are unrestorable or meaningless for the computer.
> Sometimes, if the battery is changed or charged (I don't know if the 
> A5000 has an rechargable or real battery builtin) and if the 
> rechargeable battery isn't defect (Poweron the Computer and regardless 
> of it's behaviour let it on for some minutes) you could poweron and 
> press the delete-button the same time, to reset the whole CMOS.
> 
> Another reason could be, that after your Poweron-Reset +Break all
> CMOS-settings are deleted/resetted and now any podules (e.g. IDE, SCSI 
> etc.) must be found again. This procedure sometimes take a while, so 
> after Poweron you could try waiting some minutes or so, with a bit of 
> luck it will boot to the desktop.
> Otherwise, if you get a *-Prompt, try typing "desktop" to boot to 
> desktop.
> 
> Hope this helps a bit.
> 
> Greetings, Jürgen

Thanks - I shall try these before looking at the battery

[toc] | [prev] | [next] | [standalone]


#13696

Fromdec <chrisdecordova@gmail.com>
Date2016-01-27 06:05 -0800
Message-ID<40159b38-f084-4f6f-8f0c-83b6a02d7184@googlegroups.com>
In reply to#13636
On Sunday, January 17, 2016 at 11:23:03 PM UTC, frea...@freakmail.de wrote:
> In Nachricht <df3cb67d-7e36-4169-b319-5544cfe7f499@googlegroups.com>
>           cdecordova <chrisdecordova@gmail.com> haben Sie geschrieben:
> 
> > It's an A5000 running RO3.7
> 
> > I either get it flashing through the colours and sticking on red -
> > with multiple horizontal black lines
> 
> > or occasionally as far as
> 
> > risc os 4988 (or simimlar)
> > supervisor
> > *
> 
> > I have tried R+ break,
> 
> > CTRL + anything does not work.
> 
> > Any ideas please?
> 
> Hallo,
> 
> has the A5000 perhaps been stored a longer time before you recently 
> powered it up again?
> In this case it could be, that the CMOS-battery is defect/empty and 
> your CMOS-settings are unrestorable or meaningless for the computer.
> Sometimes, if the battery is changed or charged (I don't know if the 
> A5000 has an rechargable or real battery builtin) and if the 
> rechargeable battery isn't defect (Poweron the Computer and regardless 
> of it's behaviour let it on for some minutes) you could poweron and 
> press the delete-button the same time, to reset the whole CMOS.
> 
> Another reason could be, that after your Poweron-Reset +Break all
> CMOS-settings are deleted/resetted and now any podules (e.g. IDE, SCSI 
> etc.) must be found again. This procedure sometimes take a while, so 
> after Poweron you could try waiting some minutes or so, with a bit of 
> luck it will boot to the desktop.
> Otherwise, if you get a *-Prompt, try typing "desktop" to boot to 
> desktop.
> 
> Hope this helps a bit.
> 
> Greetings, Jürgen

*desktop gave not found

[toc] | [prev] | [next] | [standalone]


#13637

FromStuart <Spambin@argonet.co.uk>
Date2016-01-17 23:46 +0000
Message-ID<554398f987Spambin@argonet.co.uk>
In reply to#13633
In article <df3cb67d-7e36-4169-b319-5544cfe7f499@googlegroups.com>,
   cdecordova <chrisdecordova@gmail.com> wrote:
> It's an A5000 running RO3.7

> I either get it flashing through the colours and sticking on red - with
> multiple horizontal black lines

> or occasionally as far as 

> risc os 4988 (or simimlar)
> supervisor
> *

> I have tried R+ break,

> CTRL + anything does not work.


http://www.retro-kit.co.uk/user/custom/Acorn/32bit/documentation/RISCOS-POST-AppNote225.pdf

> Any ideas please?

-- 
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/

[toc] | [prev] | [next] | [standalone]


#13651

FromAndrew Wickham <ajw99uk@yahoo.co.uk>
Date2016-01-20 07:04 -0800
Message-ID<75eba0a2-e1f1-4a46-9c35-e0b36d74bee8@googlegroups.com>
In reply to#13633
On Sunday, 17 January 2016 15:54:27 UTC, dec  wrote:
> It's an A5000 running RO3.7
> 
> I either get it flashing through the colours and sticking on red - with multiple horizontal black lines
> 
> or occasionally as far as 
> 
> risc os 4988 (or simimlar)
> supervisor
> *
If you get this far, check whether you see "ADFS" as well, then what happens if you use the command
rommodules
which should return a list of modules in ROM - if lots are unplugged, you could try "rmreinit [modulename]" to revive them, or "desktop"
> 
> I have tried R+ break,
> 
> CTRL + anything does not work.
> 
> Any ideas please?
Hold down DELETE from before pressing the power button until you get either a desktop or the * command prompt.  That should reset CMOS to defaults and enable a normal start-up unless something hardware-wise is broken.

Good luck!

[toc] | [prev] | [next] | [standalone]


#13698

Fromdec <chrisdecordova@gmail.com>
Date2016-01-27 06:11 -0800
Message-ID<d53dadcf-9c30-4868-846f-47d4eb2a509f@googlegroups.com>
In reply to#13651
On Wednesday, January 20, 2016 at 3:04:29 PM UTC, Andrew Wickham wrote:
> On Sunday, 17 January 2016 15:54:27 UTC, dec  wrote:
> > It's an A5000 running RO3.7
> > 
> > I either get it flashing through the colours and sticking on red - with multiple horizontal black lines
> > 
> > or occasionally as far as 
> > 
> > risc os 4988 (or simimlar)
> > supervisor
> > *
> If you get this far, check whether you see "ADFS" as well, 

I do not see "ADFS" although if that has anything to do with the floppy drive, that is flickering a lot.

then what happens if you use the command
> rommodules
> which should return a list of modules in ROM - if lots are unplugged, you could try "rmreinit [modulename]" to revive them, or "desktop"
> > 
> > I have tried R+ break,
> > 
> > CTRL + anything does not work.
> > 
> > Any ideas please?
> Hold down DELETE from before pressing the power button until you get either a desktop or the * command prompt.  That should reset CMOS to defaults and enable a normal start-up unless something hardware-wise is broken.
> 
> Good luck!

[toc] | [prev] | [next] | [standalone]


#13699

Fromdec <chrisdecordova@gmail.com>
Date2016-01-27 06:14 -0800
Message-ID<68125358-7e26-49b0-9fae-083bf4528546@googlegroups.com>
In reply to#13698
I typed *RomModules and got

UtilityModule  Running
then
Podule 
FileSwitch
ResourceFS
Messages
MessageTrans
TerritoryManager
UK 
all active

then loads Unplugged.

Does that help to know what to do?

[toc] | [prev] | [next] | [standalone]


#13701

FromNews <chrisjohnson@spamcop.net>
Date2016-01-27 15:20 +0000
Message-ID<5548910284chrisjohnson@spamcop.net>
In reply to#13699
In article <68125358-7e26-49b0-9fae-083bf4528546@googlegroups.com>,
   dec <chrisdecordova@gmail.com> wrote:
> I typed *RomModules and got

> UtilityModule  Running
> then
> Podule 
> FileSwitch
> ResourceFS
> Messages
> MessageTrans
> TerritoryManager
> UK 
> all active

> then loads Unplugged.

I guess therein lies your problem. RISC OS is rather hogtied if most
of the OS is unplugged (efectively not there). Work through all the
unplugged modules and do a *rmreinit for each one. Command would be
e.g.
   RMReInit Desktop

> Does that help to know what to do?

-- 
Chris Johnson

[toc] | [prev] | [next] | [standalone]


#13703

Fromdec <chrisdecordova@gmail.com>
Date2016-01-27 08:46 -0800
Message-ID<8c9f60fb-e2de-4e73-94e9-fb68d06f1932@googlegroups.com>
In reply to#13701
On Wednesday, January 27, 2016 at 4:09:04 PM UTC, News wrote:
> In article <68125358-7e26-49b0-9fae-083bf4528546@googlegroups.com>,
>    dec <chrisdecordova@gmail.com> wrote:
> > I typed *RomModules and got
> 
> > UtilityModule  Running
> > then
> > Podule 
> > FileSwitch
> > ResourceFS
> > Messages
> > MessageTrans
> > TerritoryManager
> > UK 
> > all active
> 
> > then loads Unplugged.
> 
> I guess therein lies your problem. RISC OS is rather hogtied if most
> of the OS is unplugged (efectively not there). Work through all the
> unplugged modules and do a *rmreinit for each one. Command would be
> e.g.
>    RMReInit Desktop
> 
> > Does that help to know what to do?
> 
> -- 
> Chris Johnson

Thanks. I'll try that tomorrow!

[toc] | [prev] | [next] | [standalone]


Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.sys.acorn.misc


csiph-web