Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima
From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 07/22/04
- Next message: KM: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Previous message: JC: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- In reply to: JC: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Next in thread: KM: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Reply: KM: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Jul 2004 00:18:28 +0200
Hi JC,
> NTFS boot sector usually knows where to find what it needs to boot.
Just to add one note to this.
NTFS boot sector is created from Windows XP/2000 and it know that it should find and load piece of ntldr. that should continue boot
operation.
Same goes for FAT boot sector created from Windows XP/2000 code in boot sector will also try to find and load piece of ntldr.
FAT boot sector created from old DOS will not look for ntldr but instead it will load one of hidden system files (I can't remember
which one).
bootprep.exe is used for replacing boot code so it load ntldr.
Best regards,
Slobodan
"JC" <JCBSQ@nospam_yahoo.com> wrote in message news:eYABsgDcEHA.2388@TK2MSFTNGP11.phx.gbl...
> Well, Joe... it's been a long long day... :-) XP does not use command.com.
> NTFS boot sector usually knows where to find what it needs to boot. I felt
> like a moron after mentioning command.com :-)
>
> The boot.ini file, will allow the correct path to the windows directory,
> however in your SLX file in TD, you have to set Your HDD as the BOOT and the
> SYSTEM partiton. (Drive C)... as you set up the original image in the other
> PC, you most likely called the system Drive C, and the Boot Drive D. You
> need to set the System Drive to C, and the Boot Drive to C, if there is only
> going to be 1 Physical Hard Drive in the System... then rebuild the image,
> copy it back to the HDD and Boot, FBA and Play! :-)
>
> HTH.
> JC
>
> --
> JC- BSquare Corp.
> If you wish to reply directly to me, remove the <nospam_ > from the address.
> "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
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
- Next message: KM: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Previous message: JC: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- In reply to: JC: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Next in thread: KM: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Reply: KM: "Re: Moving beyond "Tutorial: Building and Deploying a Run-Time Ima"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
