Hello Kurt

I dont the answer to how to complete the install on your machine yet. But as
far as for the question of NT and NetBSD residing on harddrive is possible.
I do it all the time. I make 300+ meg fat partition and load NT on it and
start the install and then once we have to do disklabel in the Netbsd you
can pick the start cylinder number after the fat(NT) partition. In general
any arc platform can co-exist with NT and NetBSD. I am sorry, I am not able
to help you completely, as I have only NEC Image RISC Station with me. It is
bit different from RISC Server 2200. We will get there and make the machine
work.

Since Alpha is also a ARC machine, I am looking into the NetBSD Alpha port
now to see if they have n sysinstall. If there is one it will be very
similar to NEC ARC and we can (hopefully with little luck ) simply compile
it for mips and produce a sysinstall. Also I am looking into OpenBSD source
code as they have a very good install program that works well.

Shortly you'll have good news on your machine.

Prasad Nuli
-----Original Message-----
From: port-arc-owner@netbsd.org [mailto:port-arc-owner@netbsd.org]On
Behalf Of Kurt Bloom
Sent: Monday, July 31, 2000 12:41 PM
To: Prasad V Nuli
Cc: port-arc@netbsd.org
Subject: RE: NEC RiscServer 2200


Sitting at this "root device:" prompt, should I point it to my netbsd.eco
file which I have on my c:\? If so do I do this by ARC path?

Also, can I just burn a cd on a windows machine of the snapshot and access
it via cd and  do the install that way?

One more: should I blow away the NT on the c:\ before I try install
NetBSD? Or can the two reside on the same partition without problems?

I know you're busy with documenting your install Prasad-so don't let me
bog you down with all my crazy newbie questions! I can always wait and
read what you're in the process of writing.

On Mon, 31 Jul 2000, Prasad V Nuli wrote:

> I dont know the present state of the software you booted from. If the
video
> driver is working then you can do a netinstall using another netbsd
machine
> and then do the partition of the drives and unzip the tgzs and you should
be
> on your way to use the system. You might need  PCCONS for the box.
>
> On Image RISC station I am booted using  PCCONS and installed.It is
tedious
> but worked. I had to do a net install to install on that box. There are
some
> bugs in 1.5_X release candidate. Greg and me are working on fixing it and
do
> a good build for the ARC Image Platform.
>
> I am working on the SYSINSTALL for the platform now. I'll know in the next
> couple of days how it is working. I'll keep you posted.
>
> Prasad Nuli
>
> -----Original Message-----
> From: port-arc-owner@netbsd.org [mailto:port-arc-owner@netbsd.org]On
> Behalf Of Kurt Bloom
> Sent: Monday, July 31, 2000 11:49 AM
> To: port-arc@netbsd.org
> Subject: Re: NEC RiscServer 2200
>
>
>
> So I hooked up the serial box, used hyprtrm, booted the COMCONS ecoff
> kernel-and it worked. Now I'm sitting at a root device: prompt. So this
> kernel will work for me, I assume. Now I suppose I need to partition my
> drive for unix and boot to the kernel again. I think I'm missing a little
> of the theory here though. Once I have my drive partitioned properly and
> I'm sitting at this prompt, how do you get to the point of doing away with
> the serial hoohaw...and getting just a regular unix boot? Having the
> kernel boot does not imply that unix is "installed", I need to get the
> snapshot on the machine? I need to look back at something Warner, Maki or
> Prasad wrote earlier about this.
>
> Kurt
>
>
> On Fri, 28 Jul 2000, Warner Losh wrote:
>
> > In message <200007281451736.SM00298@digitalcommute.com> "Maki" writes:
> > : Then you get into the kernel stuff by reading some code and asking
> > : more questions.  Chances are, you wouldn't have to write a driver from
> > : scratch, just have to make sure the devices are initialized and
> > : detected correctly.  It's time consuming, but interesting and
> > : educational to say the least.
> >
> > Yes.  Also, if you make changes that we need to include in our future
> > kernel builds, please send us the patches...
> >
> > Warner
> >
>
>