On 9 Jan 2013, Frank de Bruijn <[email protected]> wrote:
> In article <6e7d520b53.old_coaster@old_coaster.yahoo.co.uk>,
>    Tony Moore <[email protected]> wrote:

> > Incidentally, there seems to be a bug affecting unplug, on
> > RPCEmu/620
>
> >    *unplug appletalk
> >    *
> >    *unplug
> >    No modules are unplugged
> >    *
>
> > Verma confirms that the module _is_ unplugged, so *unplug , without
> > parameters, doesn't return the correct information.
>
> Could that be because AppleTalk is too high up in the list (it's 170
> here)?

171 here.

> There's a finite number of bits available in the CMOS to flag a ROM
> module as unplugged. Unplugging definitely works correctly with lower
> numbered modules (e.g. RemotePrinterSupport).

That would explain why *unplug appletalk doesn't survive a re-boot. I
had tried *unplug appletalk, in predesk, but that, it seems, is not
soon enough to avoid a clash, when networking starts. However, X Unplug
AppleTalk, in the !Internet.!Run file (from your other email) does work.

Many thanks.

Networking also OK, here.

Tony




_______________________________________________
Rpcemu mailing list
[email protected]
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Reply via email to