What tool/mechanism do most people use for getting the built images over to
their target? I've been using Remote Recover but Winternals charges $1500
for the Administrator Pak and won't sell RR separately and won't do any
volume discount or floating license. Paying that much for a bunch of
developers when we only need a very tiny part of the Pak is ridiculous but I
don't see any other good alternatives. Booting XP from the CD just to be
able to share out the target to copy for is quite a long boot. All that's
needed is a DOS boot that supports long file names and can share out to be
seen by XP. Are there any alternatives? Thanks!

Larry,

Personaly I use XPP that share one volume on target machine. (1GB network) Then I build my image directly to network share from TD.

Regards,
Slobodan


"Larry Waibel" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> What tool/mechanism do most people use for getting the built images over to
> their target? I've been using Remote Recover but Winternals charges $1500
> for the Administrator Pak and won't sell RR separately and won't do any
> volume discount or floating license. Paying that much for a bunch of
> developers when we only need a very tiny part of the Pak is ridiculous but I
> don't see any other good alternatives. Booting XP from the CD just to be
> able to share out the target to copy for is quite a long boot. All that's
> needed is a DOS boot that supports long file names and can share out to be
> seen by XP. Are there any alternatives? Thanks!
>

Does "booting XP from the CD" mean booting WinPE? True it is slow but it's
hardly my biggest problem. I've done that and I've used BartPE because WinPE
doesn't support my GigE interfaces. As far as DOS/long names/share is
concerned, I haven't done all 3 but I have used a DOS-like/long name scenario
supported by the LFN open source package. In this case I made a bootable
Win98 startup Zip disk, added LFN, and had room to add the image and then
boot on the target. It is a slow and awkward procedure but I think it
illustrates the point that you simply need to improvise something that works
for you.

"Larry Waibel" wrote:

> What tool/mechanism do most people use for getting the built images over to
> their target? I've been using Remote Recover but Winternals charges $1500
> for the Administrator Pak and won't sell RR separately and won't do any
> volume discount or floating license. Paying that much for a bunch of
> developers when we only need a very tiny part of the Pak is ridiculous but I
> don't see any other good alternatives. Booting XP from the CD just to be
> able to share out the target to copy for is quite a long boot. All that's
> needed is a DOS boot that supports long file names and can share out to be
> seen by XP. Are there any alternatives? Thanks!
>
>

I don't have a Zip disk drive, just a floppy. I need a floppy that will boot,
support long file names, and be able to share the target disk out to an XP Pro
machine on the network.

In article <03D61CD9-3D75-47FB-8FF3-(E-Mail Removed)>, Hal korstead
wrote:
> From: hal korstead <(E-Mail Removed)>
> Subject: RE: Development tool
> Date: Tue, 28 Jun 2005 05:41:01 -0700
> Newsgroups: microsoft.public.windowsxp.embedded
>
> Does "booting XP from the CD" mean booting WinPE? True it is slow but it's
> hardly my biggest problem. I've done that and I've used BartPE because WinPE
> doesn't support my GigE interfaces. As far as DOS/long names/share is
> concerned, I haven't done all 3 but I have used a DOS-like/long name scenario
> supported by the LFN open source package. In this case I made a bootable
> Win98 startup Zip disk, added LFN, and had room to add the image and then
> boot on the target. It is a slow and awkward procedure but I think it
> illustrates the point that you simply need to improvise something that works
> for you.
>
> "Larry Waibel" wrote:
>
> > What tool/mechanism do most people use for getting the built images over to
> > their target? I've been using Remote Recover but Winternals charges $1500
> > for the Administrator Pak and won't sell RR separately and won't do any
> > volume discount or floating license. Paying that much for a bunch of
> > developers when we only need a very tiny part of the Pak is ridiculous but I
> > don't see any other good alternatives. Booting XP from the CD just to be
> > able to share out the target to copy for is quite a long boot. All that's
> > needed is a DOS boot that supports long file names and can share out to be
> > seen by XP. Are there any alternatives? Thanks!
> >
> >
>

Not sure I understand. My target just has a 256MB M-Systems disk that's not removable. How
do I get the output from TD from my development system to the target M-Systems disk when
there's nothing on it? Are you saying you boot XP Pro from a CD on the target and then
share out the target disk?

In article <OoOe#(E-Mail Removed)>, Slobodan Brcin (eMVP) wrote:
> From: "Slobodan Brcin \(eMVP\)" <(E-Mail Removed)>
> Subject: Re: Development tool
> Date: Tue, 28 Jun 2005 12:12:54 +0200
> Newsgroups: microsoft.public.windowsxp.embedded
>
> Larry,
>
> Personaly I use XPP that share one volume on target machine. (1GB network) Then I build my
image directly to network share from TD.
>
> Regards,
> Slobodan
>
> "Larry Waibel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> > What tool/mechanism do most people use for getting the built images over to
> > their target? I've been using Remote Recover but Winternals charges $1500
> > for the Administrator Pak and won't sell RR separately and won't do any
> > volume discount or floating license. Paying that much for a bunch of
> > developers when we only need a very tiny part of the Pak is ridiculous but I
> > don't see any other good alternatives. Booting XP from the CD just to be
> > able to share out the target to copy for is quite a long boot. All that's
> > needed is a DOS boot that supports long file names and can share out to be
> > seen by XP. Are there any alternatives? Thanks!
> >
>

Larry,

I said what I use for most of my developments and testing purposes.
If you have M-Systems uDOC device then you can plug it to dev machine, place files on it and them plug it back to target machine.

Or you can make small deployment XPe that will run from network and then move your image to target computer.
Or you can boot it from second disk. There are many options available depending on your computer configuration.

Regards,
Slobodan







"Larry Waibel" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Not sure I understand. My target just has a 256MB M-Systems disk that's not removable. How
> do I get the output from TD from my development system to the target M-Systems disk when
> there's nothing on it? Are you saying you boot XP Pro from a CD on the target and then
> share out the target disk?
>
> In article <OoOe#(E-Mail Removed)>, Slobodan Brcin (eMVP) wrote:
> > From: "Slobodan Brcin \(eMVP\)" <(E-Mail Removed)>
> > Subject: Re: Development tool
> > Date: Tue, 28 Jun 2005 12:12:54 +0200
> > Newsgroups: microsoft.public.windowsxp.embedded
> >
> > Larry,
> >
> > Personaly I use XPP that share one volume on target machine. (1GB network) Then I build my
> image directly to network share from TD.
> >
> > Regards,
> > Slobodan
> >
> > "Larry Waibel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > > What tool/mechanism do most people use for getting the built images over to
> > > their target? I've been using Remote Recover but Winternals charges $1500
> > > for the Administrator Pak and won't sell RR separately and won't do any
> > > volume discount or floating license. Paying that much for a bunch of
> > > developers when we only need a very tiny part of the Pak is ridiculous but I
> > > don't see any other good alternatives. Booting XP from the CD just to be
> > > able to share out the target to copy for is quite a long boot. All that's
> > > needed is a DOS boot that supports long file names and can share out to be
> > > seen by XP. Are there any alternatives? Thanks!
> > >
> >
>
>

I zip the entire TD output tree into a self extracting archive and
extract it over the wire via winpe. Once I am happy with this, the self
extracting archive is written to the WinPe CD and called from there. It
removes any need for expensive third party cloning programmes. Let me
know if this methodology is of interest and I will provide you with
more details.

Take a look at http://www.drdos.net/faq/
The basics of long file names and networking are supported but will you be
able to share to XP Pro and fit it all on a floppy(s)? I have my doubts but
let us know if you succeed.

"Larry Waibel" wrote:

> I don't have a Zip disk drive, just a floppy. I need a floppy that will boot,
> support long file names, and be able to share the target disk out to an XP Pro
> machine on the network.

I'm not familiar with 'winpe' so not sure what you're describing but I am
interested in some more details; thanks!

In article <(E-Mail Removed)>,
(E-Mail Removed) wrote:
> From: "(E-Mail Removed)" <(E-Mail Removed)>
> Newsgroups: microsoft.public.windowsxp.embedded
> Subject: Re: Development tool
> Date: 28 Jun 2005 07:55:49 -0700
>
> I zip the entire TD output tree into a self extracting archive and
> extract it over the wire via winpe. Once I am happy with this, the self
> extracting archive is written to the WinPe CD and called from there. It
> removes any need for expensive third party cloning programmes. Let me
> know if this methodology is of interest and I will provide you with
> more details.
>