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

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

BB CMOS change

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

Contents

  BB CMOS change Patric <patric@invalid.de> - 2012-01-04 16:13 +0100
    Re: BB CMOS change Grahame Parish <maillist.parish@millers-way.net> - 2012-01-04 15:41 +0000
      Re: BB CMOS change Howard Dawson <hsdawson@ormail.co.uk> - 2012-01-06 20:05 +0000
        Re: BB CMOS change Dave Higton <davehigton@dsl.pipex.com> - 2012-01-06 21:37 +0000
          Re: BB CMOS change Richard Ashbery <basura@invalid.addr.uk> - 2012-01-09 15:29 +0000
            Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-09 16:35 +0000
              Re: BB CMOS change patric <patric@invalid.com> - 2012-01-10 01:39 +0100
                Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-10 22:52 +0000
              Re: BB CMOS change Richard Ashbery <basura@invalid.addr.uk> - 2012-01-11 16:46 +0000
                Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-11 22:41 +0000
                  Re: BB CMOS change Howard Dawson <hsdawson@ormail.co.uk> - 2012-01-12 18:56 +0000
                    Re: BB CMOS change Richard Ashbery <basura@invalid.addr.uk> - 2012-01-14 13:35 +0000
                      Re: BB CMOS change Doug Webb <doug.j.webb@btinternet.com> - 2012-01-14 15:24 +0000
                        Re: BB CMOS change Richard Ashbery <basura@invalid.addr.uk> - 2012-01-14 17:10 +0000
                        Re: BB CMOS change Richard Ashbery <basura@invalid.addr.uk> - 2012-01-15 10:56 +0000
                      Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-14 18:02 +0000
            Re: BB CMOS change Dave Higton <davehigton@dsl.pipex.com> - 2012-01-16 21:00 +0000
              Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-16 22:39 +0000
                Re: BB CMOS change davehigton <davehigton14@googlemail.com> - 2012-01-17 00:19 -0800
                  Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-17 11:28 +0000
                    Re: BB CMOS change Patric <patric@invalid.de> - 2012-01-17 15:42 +0100
                      Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-17 15:05 +0000
        Re: BB CMOS change Rick Murray <heyrickmail-usenet@yahoo.co.uk> - 2012-01-08 16:42 +0100
          Re: BB CMOS change Howard Dawson <hsdawson@ormail.co.uk> - 2012-01-09 19:34 +0000
            Re: BB CMOS change Richard Ashbery <basura@invalid.addr.uk> - 2012-01-10 20:15 +0000
        Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-08 22:40 +0000
          Re: BB CMOS change Fred Bambrough <fred@[127.0.0.1]> - 2012-01-08 22:46 +0000

Page 2 of 2 — ← Prev page 1 [2]

#3353

On Tue, 17 Jan 2012 12:28:38 +0100,  wrote:

>> On Jan 16, 10:39 pm, Fred Bambrough <fred@[127.0.0.1]> wrote:
>> > In message <8d9ea15252.davehig...@dsl.pipex.com>
>> >      DaveHigton<davehig...@dsl.pipex.com> wrote:
>> >
[snip]

>> But you don't need EEPROMs.  You get the functionality for free
>> in software and the SD(HC) card.
>
> I thought that was changed with the latest ROM. I know you can store the
> settings on the SD but I thought changes on the fly was now gone in
> preparation for real EEPROM on the BB xM.
>

AIU the general idea is to separate CMOS settings from the SD card and  
making
the latter available to the user. I could be wrong though!

https://www.riscosopen.org/forum/forums/4/topics/876#posts-10231


patric

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

#3354

In message <op.v78gg3f0eksv19@aristide.fritz.box>
     Patric <patric@invalid.de> wrote:

> On Tue, 17 Jan 2012 12:28:38 +0100,  wrote:
> 
> >> On Jan 16, 10:39 pm, Fred Bambrough <fred@[127.0.0.1]> wrote:
> >> > In message <8d9ea15252.davehig...@dsl.pipex.com>
> >> >      DaveHigton<davehig...@dsl.pipex.com> wrote:
> >> >
> [snip]
> 
> >> But you don't need EEPROMs.  You get the functionality for free
> >> in software and the SD(HC) card.
> >
> > I thought that was changed with the latest ROM. I know you can store the
> > settings on the SD but I thought changes on the fly was now gone in
> > preparation for real EEPROM on the BB xM.
> >
> 
> AIU the general idea is to separate CMOS settings from the SD card and  
> making
> the latter available to the user. I could be wrong though!
> 
> https://www.riscosopen.org/forum/forums/4/topics/876#posts-10231

Yes. So you either have to have a real EEPROM or create a fixed CMOS file
with SDCreate, is how I read it.

I'm glad to have had Jeffrey's explanation though. I was wondering where the
EEPROM would plug in given that the underside of the board is restricted
with the Specialcomp case - and where to get it.

-- 
Fred

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

#3252

On 06/01/2012 21:05, Howard Dawson wrote:

> I don't think it looks after things like mouse, k/b, sound, screen blanker,
> etc. though (please correct me if wrong as it doesn't seem to for me).

Er, that what CMOS RAM does... You're running a recent build of RISC OS?


Best wishes,

Rick.

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

#3268

In article <4f09b97b$0$2538$ba4acef3@reader.news.orange.fr>, Rick Murray
<heyrickmail-usenet@yahoo.co.uk> wrote:
> You're running a recent build of RISC OS?
> 
>
OK thank you Dave and Rick, have now got rid of my kludge. All works
swimmingly now.

I have indeed been running most recent builds but seem to have fallen foul
to some kind of finger trouble ICW misleading/out of date help files.

Not sure what the finger trouble actually was, but the Readme/txt and
!SDCreate.!Help files in the latest ROM update (22 Dec 2011) both still
either state or imply that Risc OS cannot yet write CMOS settings back to
the SD card.


Cheers
Howard.


-- 
-------------
Howard Dawson
 
hsdawson@ormail.co.uk

http://hd-audio.orpheusweb.co.uk/
---------------------------------

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

#3274

In article <na.3efee7524e.a80520hsdawson@ormail.co.uk>, Howard Dawson
<hsdawson@ormail.co.uk> wrote:

> OK thank you Dave and Rick, have now got rid of my kludge. All
> works swimmingly now.

> I have indeed been running most recent builds but seem to have
> fallen foul to some kind of finger trouble ICW misleading/out of
> date help files.

> Not sure what the finger trouble actually was, but the Readme/txt
> and !SDCreate.!Help files in the latest ROM update (22 Dec 2011)
> both still either state or imply that Risc OS cannot yet write CMOS
> settings back to the SD card.

Feel envious - This is the first time I've come unstuck with getting
development software to work correctly on the Beagleboard - but I
suppose I was bound to run out of luck :-((

The main problem after setting network configuration (enabling TCP/IP)
and saving it CMOS is that it doesn't save it.  When power is
re-cycled to the BB the network is no longer enabled. Actually I don't
think it saves any configuration parameter.

Tried with the ROM update (22 Dec 2011) and Rob Seaton's 5.19 ROM.

Grhhh

-- 
Richard Ashbery

Wakefield 2012 - Saturday 28th April
http://www.wakefieldshow.org.uk

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

#3263

In message <na.a97638524d.a80520hsdawson@ormail.co.uk>
     Howard Dawson <hsdawson@ormail.co.uk> wrote:

> In article <je1ruq$fcg$1@speranza.aioe.org>, Grahame Parish
> <maillist.parish@millers-way.net> wrote:
> > The CMOS file on the SD card is the equivalent to CMOS RAM in an older 
> > machine.  It stores settings that you need at start-up, filesystem, boot

> > drive, etc.
> >
> Hi,
> 
> I don't think it looks after things like mouse, k/b, sound, screen
blanker,
> etc. though (please correct me if wrong as it doesn't seem to for me).
> 
> When I first got my BB, I wrote a little workaround (until a full fix is
> available) to get this stuff to be remembered and reinstated at boot-up.
> It seems to work OK with all issues of Beagle ROM to present time.
> 
> You might want to try it.
> 
> http://hd-audio.orpheusweb.co.uk/downloads/bb_cmos.zip
> 
> Settings are stored inside the small application when shutting down and
are
> reinstated at boot-up.

If you are using BB_CMOS and also need to use the keyboard scroll lock fix
(adding FX 202 4 251 & FX 118 to !Boot.Utils.BootRun) then you'll need to
create an obey file with those commands that executes after BB_CMOS.

BB_CMOS seems to re-init the scroll lock setting.

-- 
Fred

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

#3264

In message <mpro.lxi4be00001h20257@ypical.nospam.invalid>
     Fred Bambrough <fred@[127.0.0.1]> wrote:

> In message <na.a97638524d.a80520hsdawson@ormail.co.uk>
>      Howard Dawson <hsdawson@ormail.co.uk> wrote:
> 
> > In article <je1ruq$fcg$1@speranza.aioe.org>, Grahame Parish
> > <maillist.parish@millers-way.net> wrote:
> > > The CMOS file on the SD card is the equivalent to CMOS RAM in an older

> > > machine.  It stores settings that you need at start-up, filesystem,
boot
> 
> > > drive, etc.
> > >
> > Hi,
> > 
> > I don't think it looks after things like mouse, k/b, sound, screen
> blanker,
> > etc. though (please correct me if wrong as it doesn't seem to for me).
> > 
> > When I first got my BB, I wrote a little workaround (until a full fix is
> > available) to get this stuff to be remembered and reinstated at boot-up.
> > It seems to work OK with all issues of Beagle ROM to present time.
> > 
> > You might want to try it.
> > 
> > http://hd-audio.orpheusweb.co.uk/downloads/bb_cmos.zip
> > 
> > Settings are stored inside the small application when shutting down and
> are
> > reinstated at boot-up.
> 
> If you are using BB_CMOS and also need to use the keyboard scroll lock fix
> (adding FX 202 4 251 & FX 118 to !Boot.Utils.BootRun) then you'll need to
> create an obey file with those commands that executes after BB_CMOS.
> 
> BB_CMOS seems to re-init the scroll lock setting.

That should have read Num lock rather than scroll lock - doh!

-- 
Fred

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

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

csiph-web