Impossible to boot

[Guest]

Hi

I've a big problem, although I've made many images none functions. I've tested a lot of proceededs
I used ta.exe, tap.exe, sdi loader... I tried to boot on the second partition, on another disk
The pc has boot one time, and I don't understand why. Why it don't worked the other times
I've seen many errors, black screen, blue screen, file corrupted
Does it exist a standard image which works on all system

Thank
I will appreciate all comments

 

[Cato Svellingen]

Tell us how you made the images .

How do you deploy the images ?

Is your drive bootable from XP ?

Is your HDD active ?

Cato

 

[Guest]

1/ I use tap.exe, import .pmq into TD and complete the image. I created a partition and copy the image files, modify the boot.ini of the first partition
The result don't work

2/With the same image, I created a logic disk with sdi loader, format the disk, basic type, active mode. Copy the image files on the disk and remove it. I burn this sdi on a cd-rom. I use sdi2hd to extract the image on a disk. The result don't work

This is just 2 examples of what I did, I've made lot of image

I've installed Win 2000 Server, Xpe Sp1.

 

[Slobodan Brcin \(eMVP\)]

Yes image that work on all systems can be made, but you don't have problem
with OS as I can see it.

BLUE Screen, etc it related to OS, but black screen (not having anything it
related to you, your BIOS, your disk).

You should not use SDI file for this purpose.
1. You should create partition.
2. You MUST set it as active.
3. You must format it and place valid boot block in partition. (XP will do
this by default), in DOS you will have to use bootprep.
4. Make sure that ntldr can be loaded.

After that we can talk about XPe and universal solution.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1/ I use tap.exe, import .pmq into TD and complete the image. I created a

partition and copy the image files, modify the boot.ini of the first
partition.

The result don't work.

2/With the same image, I created a logic disk with sdi loader, format the

disk, basic type, active mode. Copy the image files on the disk and remove
it. I burn this sdi on a cd-rom. I use sdi2hd to extract the image on a
disk. The result don't work.

 

[Gordon Smith \(eMVP\)]

Thank you very much,

I've just tried to copy my image on a disk and use bootprep ; it's
work.
Can I use bootprep if I want to boot on the second partition of my
disk without damaged my first os. I read somewhere that bootprep is
useless on a ntfs disk. Is it true ?

XP needs a NT style boot sector to boot using NTLDR. NTFS already contains
a NT style boot sector. FAT does not. FAT's boot sector assumes that it
will boot DOS. The purpose of bootprep is to replace a FAT volume's boot
sector with a NT style boot sector.

You can run bootprep on the 2nd partition without affecting the first
partition.

 

[Slobodan Brcin \(eMVP\)]

Hi Gordon,

Just to add to this.
Both FAT and NTFS partitions created from Windows XP are bootable.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Gordon Smith \(eMVP\)]

True, I was only addressing how he was formatting. Most people avoid
bootprep issues by booting into either XP or WinPE and formatting from
there.

--Gordon Smith (eMVP)

 

[Guest]

I have the same problem. Here are the steps I followed both on the "getting started" from Microsofts Web page and form the book "XPE Advanced

I have one hard drive that has
C: Primary XP Professional (Development dual booted with G:
[operating systems
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetec
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Target Embedded" /fastdetec
E: Extended partition for storing files (File storage
G: Primary,Not active partition 512MB (XPE target test drive

I have edited the boot.ini file on C: for dual boot

I use Target designer to only add the "Winlogon Sample Marco" componen
I edit the settings of the build in target designer for the following
Boot drive = G
Windows Folder = G:\window
Program Folder = G:\Program File
Documents and settings folder = Gocuments and Setting
Boot ARC path = multi(0)disk(0)rdisk(0)partition(3
Boot Partition size (MB) = 51

I build the imag
I copy all files to the G: driv
I reboot and select "Target Embedded
I get the XPE splash screen with the bar moving across the scree
I get the FBA blue scree
I get the message installing components with a mouse visabl
It reboots and I select "Target Embedded" again
I get in the endless cycle of FBA all the time ( I have selected "Target Embedded" as many as 10 times to get it to boot but I believe it's in a infinite loop
I have looked at the books warnings and microsofts getting started and I can't get it to boot. I need something to boot before I move on to feel confident but I have been working on this for two days

Thanks for your hel
Steve

 

[Gordon Smith \(eMVP\)]

One thing to keep in mind is that the drive letter assignments from XP Pro
aren't necessarily going to be the same as when booting your computer fresh.
You might want to try different drive letters (F:?) in your run-time
settings in Target Designer.

--Gordon Smith (eMVP)

I have the same problem. Here are the steps I followed both on the
"getting started" from Microsofts Web page and form the book "XPE
Advanced"

I have one hard drive that has:
C: Primary XP Professional (Development dual booted with G
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows
XP Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Target Embedded"
/fastdetect
E: Extended partition for storing files (File storage)
G: Primary,Not active partition 512MB (XPE target test drive)

I have edited the boot.ini file on C: for dual boot.

I use Target designer to only add the "Winlogon Sample Marco"
component
I edit the settings of the build in target designer for the following:
Boot drive = G:
Windows Folder = G:\windows
Program Folder = G:\Program Files
Documents and settings folder = Gocuments and Settings
Boot ARC path = multi(0)disk(0)rdisk(0)partition(3)
Boot Partition size (MB) = 512

I build the image
I copy all files to the G: drive
I reboot and select "Target Embedded"
I get the XPE splash screen with the bar moving across the screen
I get the FBA blue screen
I get the message installing components with a mouse visable
It reboots and I select "Target Embedded" again
I get in the endless cycle of FBA all the time ( I have selected
"Target Embedded" as many as 10 times to get it to boot but I believe
it's in a infinite loop)
I have looked at the books warnings and microsofts getting started
and I can't get it to boot. I need something to boot before I move on
to feel confident but I have been working on this for two days.

Thanks for your help
Steve

 

[Slobodan Brcin \(eMVP\)]

Gordon you are correct.

Here is the problem:
http://msdn.microsoft.com/embedded/community/tips/xp/reboots/default.aspx
Here is the solution:
http://msdn.microsoft.com/embedded/community/tips/xp/rtpartin/default.aspx

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

One thing to keep in mind is that the drive letter assignments from XP Pro
aren't necessarily going to be the same as when booting your computer fresh.
You might want to try different drive letters (F:?) in your run-time
settings in Target Designer.

--Gordon Smith (eMVP)

I have the same problem. Here are the steps I followed both on the
"getting started" from Microsofts Web page and form the book "XPE
Advanced"

I have one hard drive that has:
C: Primary XP Professional (Development dual booted with G
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows
XP Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Target Embedded"
/fastdetect
E: Extended partition for storing files (File storage)
G: Primary,Not active partition 512MB (XPE target test drive)

I have edited the boot.ini file on C: for dual boot.

I use Target designer to only add the "Winlogon Sample Marco"
component
I edit the settings of the build in target designer for the following:
Boot drive = G:
Windows Folder = G:\windows
Program Folder = G:\Program Files
Documents and settings folder = Gocuments and Settings
Boot ARC path = multi(0)disk(0)rdisk(0)partition(3)
Boot Partition size (MB) = 512

I build the image
I copy all files to the G: drive
I reboot and select "Target Embedded"
I get the XPE splash screen with the bar moving across the screen
I get the FBA blue screen
I get the message installing components with a mouse visable
It reboots and I select "Target Embedded" again
I get in the endless cycle of FBA all the time ( I have selected
"Target Embedded" as many as 10 times to get it to boot but I believe
it's in a infinite loop)
I have looked at the books warnings and microsofts getting started
and I can't get it to boot. I need something to boot before I move on
to feel confident but I have been working on this for two days.

Thanks for your help
Steve

 

[Guest]

Sorry forgot to add. If it wasn't using the correct drive letter. In this case G: my assuption is that it wouldn't boot at all like when I change the partition informatio

from

multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Target Embedded" /fastdetec

to

multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="Target Embedded" /fastdetec

The above change will tell me there is no system to boot

I guess than I am confusing the two points. The actual boot partion assignment and the assignment of the target designer

 

[Gordon Smith \(eMVP\)]

One Last question.

The first setting in TD under settings for the Boot Drive:

In the "getting started" From Microsoft when they dual booted they
set this as C: but all other paths to D:

In the XPE advanced book it states all the drive settings should be
d: including boot drive.

The help topic under TD states the boot drive as the Target drive
which to me would be D: and not C:

I am confused on this issue. Which one is correct?

Thanks so far you have been a great help. I am trying your solutions
right now and will inform how they go.

I always set them all to the letter it will use at runtime (d: in this
case).

 

[Slobodan Brcin \(eMVP\)]

Steve,

Default drive letters:

C: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
D: multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
E: multi(0)disk(0)rdisk(0)partition(3)\WINDOWS

You should read article I have provided you link on.
Also you should reassign drive letters from TD so you don't have to think
how BIOS will assign letters.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sorry forgot to add. If it wasn't using the correct drive letter. In this

case G: my assuption is that it wouldn't boot at all like when I change the
partition information

from

multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Target Embedded" /fastdetect

to

multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="Target Embedded" /fastdetect

The above change will tell me there is no system to boot.

I guess than I am confusing the two points. The actual boot partion

assignment and the assignment of the target designer.

 

[KM]

Slobodan,

Is it true? I have always thought the assigning algorithm is a little bit more complicated than the one you mentioned below.
E.g., if you have another drive(s) with primary partitions on it (them), the OS (NT/2K/XP) will assign C:/D:/E:/... letters to those
partitions first. And then, once the letters have been assigned to the first primary partitions on all drives in the system, letters
are assigned to the recognized logical disks in the extended partitions using the same algorithm, starting with the first drive in
the system.

Anyway.. here is what I mean: http://support.microsoft.com/default.aspx?scid=kb;en-us;93373

 

[Slobodan Brcin \(eMVP\)]

Hi Konstantin,

Steve said: "
I have the same problem. Here are the steps I followed both on the "getting
started" from Microsofts Web page and form the book "XPE Advanced"
I have one hard drive that has:.....
"

Although he mentioned some very unusual partition order (It was impossible
to tell drive letter that would be assigned from these info)
I guessed that since it is only one HDD and OS is located on partition 2 and
XPe on partition 3 there must be unmentioned partition 1.
So partition 4 would be extended partition.

In this case what I have said would be true.

Regards,
Slobodan

BTW:
You are right that algorithm is complicated so I always recommend and
reassign volume letters from TD.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Slobodan,

Is it true? I have always thought the assigning algorithm is a little bit

more complicated than the one you mentioned below.

E.g., if you have another drive(s) with primary partitions on it (them),

the OS (NT/2K/XP) will assign C:/D:/E:/... letters to those

partitions first. And then, once the letters have been assigned to the

first primary partitions on all drives in the system, letters

are assigned to the recognized logical disks in the extended partitions

using the same algorithm, starting with the first drive in

 

[KM]

Slobodan,

I actually agreed with what you said about the order. It just sounded more general than for the issue being discussed.
Now I definitely see your point.

Thanks for the explanation!