copied d:\windows xp embedded images\ dir to second partition of target machine, now what?

  • Thread starter Thread starter John F. Davis
  • Start date Start date
J

John F. Davis

Hello

I have installed windows 2000 on the target machine. I have two
partitions on the drive. I installed win2k on the first partition. I
used the network to copy the contents of the d:/windows embedded
images to the second partition. Now what do I do to get it to boot
this partition so it will run FBA?

JD
 
2 things.

1. Your 2k partition (c:) will need a copy of XP's NTLDR.
2. Edit your c:\boot.ini to reflect dual booting. Here is mine:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect


--Gordon Smith (eMVP)
 
Hello

Thanks for the info.


2 things.

1. Your 2k partition (c:) will need a copy of XP's NTLDR.
Click to expand...

How do I do that? I have a NTLDR file on my C: drive already.
I have a NTLDR file on my d:\windows embedded images\dir. Do
I copy the one from my embedded images dir over my existing one?
For now I will skip it and see what happens.
2. Edit your c:\boot.ini to reflect dual booting. Here is mine:



[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect
Click to expand...

Ok. I did that. I rebooted. It gave me a choice of windows xp. I
selected it and it failed to boot. It says Windows 2000 failed to
start because the following file is missing or corrupt:
\WINDOWS\System32\DRIVERS\pci.sys

I definitely selected PCI as a component when built this image using
taget desginer. I'll try to build another image using the design
templats. Any suggestion on a good default template to use? ie.
set top box, etc.?

JD
 
inline below...
Hello

Thanks for the info.


2 things.

1. Your 2k partition (c:) will need a copy of XP's NTLDR.
Click to expand...

How do I do that? I have a NTLDR file on my C: drive already.
I have a NTLDR file on my d:\windows embedded images\dir. Do
I copy the one from my embedded images dir over my existing one?
For now I will skip it and see what happens.
2. Edit your c:\boot.ini to reflect dual booting. Here is mine:



[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP
Embedded" /fastdetect
Click to expand...

Ok. I did that. I rebooted. It gave me a choice of windows xp. I
selected it and it failed to boot. It says Windows 2000 failed to
start because the following file is missing or corrupt:
\WINDOWS\System32\DRIVERS\pci.sys

I definitely selected PCI as a component when built this image using
taget desginer. I'll try to build another image using the design
templats. Any suggestion on a good default template to use? ie.
set top box, etc.?
Click to expand...

My guess is that you haven't run Target Analyzer on your target yet. Target
Analyzer does the hard work of figuring out what components you need to
satisfy the hardware requirements of your system. If this is new to you,
let me know and I'll point you to the appropriate resources. If it isn't
new to you, I'll avoid typing a lot of redudant info here.

As far as template... it depends on what you're trying to build. Could you
describe at a high level what your box will do?
 
Hello

Thanks for the info.


2 things.

1. Your 2k partition (c:) will need a copy of XP's NTLDR.
Click to expand...

How do I do that? I have a NTLDR file on my C: drive already.
I have a NTLDR file on my d:\windows embedded images\dir. Do
I copy the one from my embedded images dir over my existing one?
For now I will skip it and see what happens.
2. Edit your c:\boot.ini to reflect dual booting. Here is mine:



[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect
Click to expand...

Ok. I did that. I rebooted. It gave me a choice of windows xp. I
selected it and it failed to boot. It says Windows 2000 failed to
start because the following file is missing or corrupt:
\WINDOWS\System32\DRIVERS\pci.sys

I definitely selected PCI as a component when built this image using
taget desginer. I'll try to build another image using the design
templats. Any suggestion on a good default template to use? ie.
set top box, etc.?
Click to expand...

I rebuilt a image using the target designer. And copied it to drive d
and rebooted. I selected windows xp at the boot prompt and it
promptly did the same thing. When I built this image, I selected
basic set top box as the starting point. I added pci, english, ntfs,
windows explorer when prompted to fix dependecy problems. I ended up
with a build with 1 warning and no errors. Is the problem because i
have not modified the existing ntldr file on my c drive? Is the
problem because I have chosen NTFS? Any suggestions?

BTW, I estimated that it would take two to three days to build and run
a image using windows embedded. This seems to be a very bad estimate.
How long would you estimate somebody would require to build and run a
default image?

JD
 
inline below...


My guess is that you haven't run Target Analyzer on your target yet. Target
Analyzer does the hard work of figuring out what components you need to
satisfy the hardware requirements of your system. If this is new to you,
let me know and I'll point you to the appropriate resources. If it isn't
new to you, I'll avoid typing a lot of redudant info here.
Click to expand...

No. I did not. I think Target Analyzer is on the development
machine. I am trying to boot an image I built on the development
machine on a target machine. Do I need to build and develop on the
same machine? Is this remote boot capability BS?
As far as template... it depends on what you're trying to build. Could you
describe at a high level what your box will do?
Click to expand...

I am trying to evaluate windows XP for a future embedded product. I
have done a lot of work with other embedded OS's, ie. vxworks, linux,
qnx, custom OS's etc. I would have to say that working with Windows
XP embedded is very difficult and costly compared to my previous
experiences.


FWIW, My target machine is a z pro intellistation. I am using it
because it happened to be available in the lab. There is nothing
special about it.
 
John said:
No. I did not. I think Target Analyzer is on the development
machine. I am trying to boot an image I built on the development
machine on a target machine. Do I need to build and develop on the
same machine? Is this remote boot capability BS?
Click to expand...

Target Analyzer is intended to be run on your target machine. It's job is
to document the hardware needs of your target platform. After running it,
copy the devices.pmq file to your dev machine to build your image. You
don't need to build/develop on the same machine. Assuming the target
machine is powerful enough you *can* develop and build on the same machine
but it not required.

The remote boot feature works well. The first step is getting a regular
image to work correctly for the platform. After that you'll need to ensure
that you add the RAM Drive component to your build then follow a set of
instructions for packaging the image correctly. You'll also need to set up
the remote boot server.


I am trying to evaluate windows XP for a future embedded product. I
have done a lot of work with other embedded OS's, ie. vxworks, linux,
qnx, custom OS's etc. I would have to say that working with Windows
XP embedded is very difficult and costly compared to my previous
experiences.
Click to expand...

Basic XP Embedded builds are fairly easy to get running once you have a good
picture of the process. I can, for example, build from scratch a basic
image that boots on a 2nd partition of my laptop in about an hour.
FWIW, My target machine is a z pro intellistation. I am using it
because it happened to be available in the lab. There is nothing
special about it.
Click to expand...

What is the intent of the final image though? Is it going to be a cash
register? Is it going to be a gaming machine? etc. The end purpose of the
deployment helps decide which template to use.
 
Target Analyzer is intended to be run on your target machine. It's job is
to document the hardware needs of your target platform. After running it,
copy the devices.pmq file to your dev machine to build your image. You
don't need to build/develop on the same machine. Assuming the target
machine is powerful enough you *can* develop and build on the same machine
but it not required.
Click to expand...

I am installing the xp embedded tools on my target machine. When it
gets through, I will transfer the TA output to my development machine
according to this url:
http://www.microsoft.com/windows/Embedded/xp/techinfo/howto/stepguide/identifying.asp

The remote boot feature works well. The first step is getting a regular
image to work correctly for the platform. After that you'll need to ensure
that you add the RAM Drive component to your build then follow a set of
instructions for packaging the image correctly. You'll also need to set up
the remote boot server.
Click to expand...

I have part of that setup already. The error when I tried it was that
the client complained that there were too many packages. I don't know
why m$ tftp would say that. I'll work on this problem once I get the
disk boot method working.
Basic XP Embedded builds are fairly easy to get running once you have a good
picture of the process. I can, for example, build from scratch a basic
image that boots on a 2nd partition of my laptop in about an hour.


What is the intent of the final image though? Is it going to be a cash
register? Is it going to be a gaming machine? etc. The end purpose of the
deployment helps decide which template to use.
Click to expand...

Sorry I can't say. I can say that it will run a window$ application.
 
You have some explanation in this link:
http://www.microsoft.com/windows/embedded/community/tips/xp/deployrun.asp

Read all link from:
http://www.microsoft.com/windows/embedded/community/tips/xp/default.asp

Read all doc files that came with XPE.

Search for many posts in this NG on this and other topics you encounter in
future. Use google groups.

BTW, I estimated that it would take two to three days to build and run
a image using windows embedded. This seems to be a very bad estimate.
How long would you estimate somebody would require to build and run a
default image?
Click to expand...

Somebody?

It took me few hours to install XPE tools with all appropriate target setup.
And few hours for first working build, it was nothing special, but I had
start button.

How fast you will adapt is purely based on different area of expertise you
have with Windows XP, Network administration, Drivers, Services, multi boot
setups, etc.

Slobodan

John F. Davis said:
Hello

Thanks for the info.


2 things.

1. Your 2k partition (c:) will need a copy of XP's NTLDR.
Click to expand...

How do I do that? I have a NTLDR file on my C: drive already.
I have a NTLDR file on my d:\windows embedded images\dir. Do
I copy the one from my embedded images dir over my existing one?
For now I will skip it and see what happens.
2. Edit your c:\boot.ini to reflect dual booting. Here is mine:



[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect
Click to expand...

Ok. I did that. I rebooted. It gave me a choice of windows xp. I
selected it and it failed to boot. It says Windows 2000 failed to
start because the following file is missing or corrupt:
\WINDOWS\System32\DRIVERS\pci.sys

I definitely selected PCI as a component when built this image using
taget desginer. I'll try to build another image using the design
templats. Any suggestion on a good default template to use? ie.
set top box, etc.?
Click to expand...

I rebuilt a image using the target designer. And copied it to drive d
and rebooted. I selected windows xp at the boot prompt and it
promptly did the same thing. When I built this image, I selected
basic set top box as the starting point. I added pci, english, ntfs,
windows explorer when prompted to fix dependecy problems. I ended up
with a build with 1 warning and no errors. Is the problem because i
have not modified the existing ntldr file on my c drive? Is the
problem because I have chosen NTFS? Any suggestions?

BTW, I estimated that it would take two to three days to build and run
a image using windows embedded. This seems to be a very bad estimate.
How long would you estimate somebody would require to build and run a
default image?

JD
JD
Click to expand...
Click to expand...
 
John said:
I am installing the xp embedded tools on my target machine. When it
gets through, I will transfer the TA output to my development machine
according to this url:
http://www.microsoft.com/windows/Embedded/xp/techinfo/howto/stepguide/identifying.asp

I have part of that setup already. The error when I tried it was that
the client complained that there were too many packages. I don't know
why m$ tftp would say that. I'll work on this problem once I get the
disk boot method working.


Sorry I can't say. I can say that it will run a window$ application.
Click to expand...

That is something you're going to have to answer. The process of creating
an XP Embedded image can be thought of creating an operating system that
provides the union of:
1. The OS software needed to operate the target hardware.
2. The OS software needed to satisfy the dependancies of the application
software.
 
Back
Top