Re: Access limitations(?), and moving to a simple LAN

In article <4db7cf3c9fJeremy@xxxxxxxxxxxxxxxx>,
Jeremy C B Nicoll <Jeremy@xxxxxxxxxxxxxxxx> wrote:

[Snip]

> Where do I need to put the new version of the module so that it
> gets loaded - I mean, does that have to happen early on in !Boot or
> can it be done anytime before I actually use the NIC? I presume I
> don't have to (or even want to?) replace the older module stored on
> the NIC itself?

I have mine at:
!Boot.Resources.!System.310.Modules.Network.EtherH16

You might need a one line obey file in:
!Boot.Resources.Configure.!InetSetup.AutoSense

containing:
Set InetSetup$Driver$NIC I-Cubed Ethernet NIC:eh0:EtherH:4.33:EtherH16

I called the obey file 'EtherH'. I can't remember if that's important.


> Do I need to issue an *unplug or something of EtherH followed by an
> RMLoad from the new module's location?

Yes. The version of EtherH on the network card needs to be unplugged.

[Snip]

> <confused>

> I seem to have Internet 5.04 in !System.310.Modules.Network but
> don't appear to have any more recent version of anything else.

It's there in mine too.

> I thought I had the universal boot!

It would seem so.

> What's the point of that module being in that location if the boot
> process doesn't load it over the system rom one? - or is 5.04 only
> applicable to RO 310?
> </>

5.04 is the version in UniBoot.

!Boot.!Resources.!Internet.!Run RMEnsures v. 5.02 which is the
version in the RISC OS 3.7 ROM. You'd need to unplug it or I
suppose you could modify the !Run file to RMEnsure 5.04.

You are taking copious notes, aren't you? ;-)

Evan.

PS. I wonder if all this effort is worthwhile if you're going to go
ahead with the RISC OS 4 upgrade which has later modules in the ROM.

.

Relevant Pages

  • Re: Access limitations(?), and moving to a simple LAN
    ... > I called the obey file 'EtherH'. ... You'd need to unplug it or I ... > ahead with the RISC OS 4 upgrade which has later modules in the ROM. ... As well as that the other RPC went 'bang' a few days ago and I haven't ...
    (comp.sys.acorn.networking)
  • Re: So many problems with XP
    ... here to check for replies. ... Ummm, rom de rom ... ...
    (microsoft.public.windowsxp.hardware)
  • Re: Message file contents
    ... but it also does special processing of of occurrences of ... vary from ROM to ROM, as they are auto-generated in the ROM build ... My faulty memory: I was thinking of the strings supplied by!Help, ...
    (comp.sys.acorn.programmer)
  • Re: Message file contents
    ... of these will vary from ROM to ROM, ... not release any software without interactive help - but I won't hold ...
    (comp.sys.acorn.programmer)
  • Re: Home built Z80 computers
    ... The character ROM is in the code ROM somewhere. ...
    (comp.os.cpm)
Loading