Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Image"

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: KM (konstmor_at_nospam_yahoo.com)
Date: 07/22/04


Date: Thu, 22 Jul 2004 12:26:57 -0700

Joe,

>From your message I couldn't quite get whether you are able to plug the
drive in to a machine (with XP Pro, or XPe installed) as a second drive? If
you can, why not format it from there since you want NTFS on it.

Also, you don't need that 2nd drive to be bootable if you already have a
bootable disk in your target PC. Just set up boot.ini on the system drive
(1st bootable drive) to load OS from that 2nd drive.

I feel like we are going to get confused with the disk numbers you are
reffering to (1st, 2nd, etc.).

KM

> Hello all,
>
> I have "sucessfully" built an XP embedded system using the "Tutorial:
Building and Deploying a Run-Time Image", and it wasn't easy I'll tell ya.
The main problem is getting a development system to match the prescribed
system in the tutorial. I can't add a second hard drive on my main PC, but I
was "provided" a back-up system (a pentium II with a hard drive just barely
large enough to contain the system and studio files and a second hard drive)
for development!
>
> Following the tutorial I made an embedded system based on the hardware for
my development PC and everything went fine.
>
> Now I want to make an embedded system based on hardware different from the
development system. I obtained a *.pmq file for the "target" hardware (yet
another long story since the target PC won't boot the WinXP PE because of a
video card incompatability I think, so I used an old DOS 6.22 disk to boot
and run the TA.EXE file). I started a new project and built an image in the
same manner as the tutorial only using the target hardware *.pmq file and
copied it to the 2nd hard drive. I was hoping I would be able to remove the
2nd hard drive from the developement PC and put it in the target PC (to be
the 1st disk, I did set the settings in the project to recognise the HD as
C:\), but it didn't work. I presume because the 2nd hard drive isn't
bootable?
>
> So the question is, how would I make the 2nd hard drive bootable, if you
think that is the problem? I didn't see anyway to do it using the disk
management on the development PC. I can't use the WinXP PE (remember, the
target PC won't boot with it). I even tried just using the WindowsXP
installation disk to see if there are utilities in it I can use to make the
, but it won't boot either!
>
> I could try and use the old DOS 6.22 disk again, but I wanted to be able
to use NTFS.
>
> Thanks again,
> Joe



Relevant Pages

  • Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima
    ... try running TAP.exe under Windows 98 to ... missing a critical boot device, ... > I did partition/format the disk in the development PC using NTFS. ... drive while it was in the target PC and "it" works fine. ...
    (microsoft.public.windowsxp.embedded)
  • Re: boot sector f*ed
    ... The fbsd minimal installation that I had set up for recovery of the ... previous crash does not boot... ... touched the disk since last using it to look at the corrupted disk ... This sounds more and more like hardware troubles. ...
    (freebsd-questions)
  • Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima
    ... I was afraid I might have caused a bit of confusion. ... When I leave this drive in this PC I can do the dual boot thing as described in the Tutorial with no problems. ... PC #2: The "Target" PC ... > bootable disk in your target PC. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima
    ... runtime image problem but rahter a disk geometry/MBR problem. ... Did you mark the partition as active? ... > missing a critical boot device, ... > drive while it was in the target PC and "it" works fine. ...
    (microsoft.public.windowsxp.embedded)
  • Re: boot problem....ntldr could not open drive...
    ... - however upon reinstalling Windows XP ... goes below 7 (checklist no longer substantially matches original hardware) ... surely you need to use the correct XP recovery disk? ... which I was able to boot off. ...
    (microsoft.public.windowsxp.hardware)