On Tue, 18 Nov 1997, Thomas Hoenl wrote:

> The boot-messages from the kernel display: em0 with UTP active
>   Sorry, mine is connected, using the BNC connector. Dispite that,
>   the network is working.

Hmm, does it get this correct under RiscOS ? UTP is recognised by a status
bit in an diagnostic status register on the card and the UPT flag just
indicates that the UTP bit in this register is set. It may be the case
that this bit needs to be read only at certain times e.g. during a chip
reset etc. 

> Ther are two minor bugs in the config script for the network
>   a '==' where a '=' should be (metmask-section)
>   a lonely 'esac'

OK I will check these out.

>   The question for the active interface is a little bit irritating
>   The script issues a default [10baseT/UTP]. So answered 10base2/BNC
>   I don't know if it is correct or if it matters. 

Erm it does not actually matter. Just about all the ethernet driver
including the em driver autoselect the media interface and there is no
driver involvement in select it.

> The 'show me the kernel messages' to get my harddisc information
> (during install) displayed only rubbish.

What sort of rubbish ? It does display a load of ^@ characters in reverse
video to start with. There is norammly then a more prompt and you need to
go on to the next page before any real text is seen. This is due to a
collection of 0x00 characters in the unused part of the message buffer.

> How do I make the rc.conf go (apart from editing it). 'rcm' did not
> remove the 'configured=NO'?

At the moment you can't. rcm really need a bit more of an overhaul to
bring it fully uptodate with all the changes that have occurred in rc,
rc.local and rc.conf between 1.2 and 1.3

> How about supplying a suitable .xinitrc and a .fvwmrc?

Could do, anyone got any nice ones that would be suitable ?

Cheers,
				Mark