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

From: Joe (Joe_at_discussions.microsoft.com)
Date: 07/23/04 

Date: Fri, 23 Jul 2004 12:16:02 -0700

I guess this is the best place to put my reply. I thought of starting a new thread.... I was hoping I could share with everybody a solution, or explain what I did wrong, but I still haven't gotten it working.

I did partition/format the disk in the development PC using NTFS. I then copied the XPembedded files from the image directory onto the drive while it was still in the development PC. I then moved the drive to the target PC and tried to boot it. I believe everything is done correctly, it just hangs up while booting up. I'm thinking now that it doesn't have anything to do with the XPembedded files at all.

When the PC is starting up, it hangs at some point and I get the following text on the display, "Verifying DMI Pool Data...". After a search of the web, I believe this is caused by some hardware problem, but i can't figure out what it might be. I removed the HDD and CD-Rom and booted with a DOS diskette with no problem. I connected the HDD and CD-ROM and booted with the Windows98 Install CD with no problem. I then installed Windows98 on the drive while it was in the target PC and "it" works fine.

Then I put the HD back into the development PC, formatted it with NTFS and copied the XPembedded back onto it. Put it into the target PC and it hangs again.

Oh well.

Thanks,
Joe

"Slobodan Brcin (eMVP)" wrote:

> Hi Joe,
>
> If you partition/format disk from Windows XP/2000 you will have bootable disk and partitions for both FAT and NTFS filesystems.
> Also you must mark first partition as active to make bootable MBR.
>
> C:\ is volume letter, and it is assigned not to disk but to recognizable partition during the boot time or you can preassign volume
> letter you want from Target Designer.
> command.com is obsolete and not used by XPe.
>
> XPe will see different volume letter order that XP on your development machine. Algorithm is rather complex for this thread to
> explain how volume letters are assigned.
>
> Read this for more info and you might find it useful some day:
> http://msdn.microsoft.com/embedded/community/community/tips/xp/rtpartin/default.aspx
>
> Best regards,
> Slobodan
>
> "Joe" <Joe@discussions.microsoft.com> wrote in message news:DAE1A8A6-1003-4165-B3DE-2B1EE0AB035E@microsoft.com...
> > KM & JC,
> >
> > Thanks for your attempts to help me out.
> >
> > KM: I have done just what you have described, but it didn't boot up. Perhaps I will spend some time with the target PC, maybe it
> just isn't even seeing the drive. Does just formatting it give it a "boot sector"
> >
> > JC: From you other post you explain that I need only command.com, boot.ini and NTLDR. I don't see a command.com (this is where I
> thought that maybe formatting the drive as a second drive "D:\" in the development PC doesn't set it as a "system" disk, so it won't
> boot as the first drive "C:\" when it is put into the target PC). Otherwise I believe that you mention the "ARC" path just as KM
> did, and I set up the project just as KM described.
> >
> > Thanks,
> > Joe
> >
> >
> > "KM" wrote:
> >
> > > Joe,
> > >
> > > Thanks for the clarifications. It helps understading your issues.
> > >
> > > In your PC configuration (when you prepeare the target drive as a second
> > > disk in development PC), you will need to:
> > > - Partition and format the driver. If you want to use NTFS, you don't
> > > need to do anything else to make the disk bootable as NTFS boot sector
> > > already knows how to find ntldr on the disk.
> > > - Build an image with directory settings set to C:\.... Arcpath is
> > > probably default: "multi(0)disk(0)rdisk(0)partition(1)", asusming you got
> > > your disk on Primary Master channel in your target PC.
> > > - [x]Copy the build to the target drive (D:\ on your dev machine).
> > > - Plug the drive in the target PC and enjoy "FBA show".
> > >
> > > KM
> > >
> > > > KM,
> > > >
> > > > I was afraid I might have caused a bit of confusion. I will describe the
> > > two pc's I'm using and what I want to do.
> > > >
> > > > PC #1: Developement PC running WindowsXP Pro
> > > > C:\ This is the main drive of this PC and where WindowsXP Pro and Embedded
> > > Studio is installed.
> > > > D:\ This is the "2nd" drive I added to complete the Tutorial. 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
> > > > The C:\ drive here is the D:\ drive from PC #1.
> > > >
> > > > I created a WindowsXP Embedded system for PC #2 on PC #1 (remember that PC
> > > #1 is the "development PC) and copied it to the D:\ drive, I then removed
> > > the D:\ drive from PC #1 and put into PC #2 and it won't boot.
> > > >
> > > > I believe the problem is that in PC #1 the "Boot" information is actually
> > > on it's C:\ drive and to boot from it's D:\ drive it reads that first. Then
> > > when I put the D:\ drive into PC #2, it is now the C:\ drive, but there is
> > > not actually any "Boot" information on it.
> > > >
> > > > I do't know if there is a way to format the drive while is D:\ in PC #1 as
> > > NTFS with "system" files like you used to beable to with the DOS format
> > > utility.
> > > >
> > > > I was hoping that all I would need to do is to change the Target Device
> > > Settings in my project to reflect that the D:\ Drive will now be the C:\
> > > drive int he Target PC.
> > > >
> > > > Hope that clears it up.
> > > >
> > > > Joe
> > > >
> > > > "KM" wrote:
> > > >
> > > > > 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

  • Need help in order to make my Win XPe recognize my CD-Rom drive and any USB devices I plug.
    ... and I manage to make it boot Win XPe from ... My PCM-9579 is plugged with a USB/Firewire controller card. ... any USB devices (even a simple USB key. ... storage component in Target Designer for that), ...
    (microsoft.public.windowsxp.embedded)
  • Re: New to XPe
    ... Slobodan Brcin wrote: ... > Also I have no idea how licensing goes for XPe that runs Visual Studio. ... To expand what I was trying to say, when debugging the control system, ...
    (microsoft.public.windowsxp.embedded)
  • Re: Create additional users XPe
    ... i.e. admin, power user ... there a way in XPe to have this done during run time, ... I assume you meant in Target Designer. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Cannot connect to database
    ... SQL server instance must be running in order for the XPe tools to work. ... First thng TD (Target Designer) does is ... Hopefully you didn't install MSDE. ...
    (microsoft.public.windowsxp.embedded)
  • Re: about install
    ... XPE image output from Target Designer is ready to be copied to an HD that ... To avoid moving disk you can format and copy on to the target device booting ... For a introductive guide to XPE setup look here, ... I can not install them into VMware to exame. ...
    (microsoft.public.windowsxp.embedded)
Loading