Re: Release Build running on hard disk
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Mon, 8 Aug 2005 12:49:56 -0400
Also, note that the ability to access the release directory across the kitl
connection is a separate component. If you have kitl support included, and
you also include CE target control support (also known as relfsd,
SYSGEN_SHELL etc) then the release directory should be mounted and
accessible.
--
Dean Ramsier - eMVP
"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
wrote in message news:Ot6niPDnFHA.860@xxxxxxxxxxxxxxxxxxxxxxx
> Well, any way you can access the hard disk (boot from floppy with network
> support on the floppy and copy from a network, move the hard disk to
another
> machine which has the nk.bin on one of its other hard disks and copy it,
> etc., etc.).
>
> Paul T.
>
> "Waratah" <Waratah@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:3306BB95-0B10-4003-9BDC-B9D0EB8E5CF0@xxxxxxxxxxxxxxxx
> > I'm trying to run a CE image of a hard disk using BIOS bootloader, and
> > copying the image as outlined in the PB documentation.
> >
> > But when the image runs from the disk no networking is available.
> >
> > I assume this is due to the KITL enabled setting. I disable this, but
when
> > I
> > download the image using PB/LoadCEPC etc. there is no release directory
to
> > copy nk.bin.
> >
> > How to I get this image to the hard disk?
> >
>
>
.
- Follow-Ups:
- Re: Release Build running on hard disk
- From: Waratah
- Re: Release Build running on hard disk
- References:
- Release Build running on hard disk
- From: Waratah
- Re: Release Build running on hard disk
- From: Paul G. Tobey [eMVP]
- Release Build running on hard disk
- Prev by Date: Re: Solved! (was: Re: Anyone from MS, especially GWES group (was: Re: Pinning dialog on top of other dialogs))
- Next by Date: Re: How to change interrupt priority
- Previous by thread: Re: Release Build running on hard disk
- Next by thread: Re: Release Build running on hard disk
- Index(es):
Relevant Pages
|