PROCESS1_INITIALISATION_FAILED

[Andreas Sichtig]

Hi there ,

tried to create a XPE-runtime for an Compaq Evo N620c
Notebook (Drive E).

My configuration :
Pentium M
Win2k SP4

Settings in Targetdesigner are as follows:

"Target Device Settings"
Boot drive > C:
Windows folder > e:\windows
Program Files Folder > e:\Program Files
Documents and Settings > e:\Documents and Settings
Boot ARC path > multi(0)disk(0)rdisk(0)partition(2)

boot.ini looks like that :

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

NTLDR created by Targetdesigner is used in the
rootdirectory .

After reboot the system starts booting XPE (Logo for about
2 seconds) and stops before FBA with a bluescreen
"PROCESS1_INITIALISATION_FAILED"

Any ideas are welcome ;-)

Thanks ,
Andreas

 

[Hans de Vetten]

Hi,

If I'm not mistaken this error is handled in the
following:
http://www.microsoft.com/windows/embedded/community/tips/x
p/default.asp

(STOP error 6b)

It has to do with not including the correct filesystem.

Hans

 

[Slobodan Brcin]

Partition 2 should be D: in most cases.

Also you can use this:
This document should describe how to force drive letter assignment in Target
Designer that will be used on target device.

Using Extra Registry Data from TD it is possible to assign drive letters for
every volume on target device.

Example:

1. On target device, from a full build of Windows XP, export the following
keys to a REG file:

HKLM\System\MountedDevices

2. In Target Designer use file->import option to load registry values from
that REG file. Those keys will appear in the center pane in the "Extra
Registry Data" node.

3. Remove any imported keys that begin with
HKLM\SYSTEM\MountedDevices\??\Volume{guid}.

For instance:

HKLM\SYSTEM\MountedDevices\??\Volume{99a4d6c3-bc54-11d6-81af-fd310b342a24}

4. Reassign drive letters in key names than begin with \DosDevices\

For instance if you wanted to place the runtime on the G: partition but make
the runtime think and behave as if it were on the C: partition you would do
this -

Change this reg key: \DosDevices\G:

To this: \DosDevices\C:



5. Folder settings in Target Designer should all go to C:\. For instance:

C:\Windows
C:\Program Files
C:\Documents and Settings

However, the Boot ARC path should point to the true location of the runtime.

Insight to boot process:

During the boot windows mount and assigns drive letters according to
following order.

First it uses letters for volumes that have reserved positions saved within
entries in HKLM\System\MountedDevices\\DosDevices

Then it tries to find new Volumes that don't have matching ID in both
Volume, and DosDevice key groups. If volume that matches this criteria is
found XP assign first available letter and creates both Volume and DosDevice
keys for it.

Insight to volume ID:

This is binary value 12 or more bytes long. It is unique for every partition
on disk, and is always the same for all installed XP based operating
systems.

First four bytes are Disk ID and are the same as value obtained using
diskpart utility.

Last eight bytes represent partition offset on disk.

For removable devices there is more complex algorithm for creating Volume
ID, but it is unique for every device.

Applications:

- Easy deployment of pre FBA image to remote HDD that has XP on drive C:
this allows us to use C: for our XPE image and stop worrying about drive
letter order that will be assigned.

- When making SDI image we need to have XPE installed on C: for ramdrive to
work.

- In test scenarios we can have more than one working XPE that differs in
some settings. For instance testing application behavior on volume D: while
we have

minlogon and winlogon builds than should be booted from volume C:.

- Running FBA on drive C: that is 64 MB or 128MB for purposes of deploying
image to CF.

Hi there ,

tried to create a XPE-runtime for an Compaq Evo N620c
Notebook (Drive E).

My configuration :
Pentium M
Win2k SP4

Settings in Targetdesigner are as follows:

"Target Device Settings"
Boot drive > C:
Windows folder > e:\windows
Program Files Folder > e:\Program Files
Documents and Settings > e:\Documents and Settings
Boot ARC path > multi(0)disk(0)rdisk(0)partition(2)

boot.ini looks like that :

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

NTLDR created by Targetdesigner is used in the
rootdirectory .

After reboot the system starts booting XPE (Logo for about
2 seconds) and stops before FBA with a bluescreen
"PROCESS1_INITIALISATION_FAILED"

Any ideas are welcome ;-)

Thanks ,
Andreas

 

[Andreas]

Hi Hans ,

thanx ! Forgot to implement NTFS into my build ;-(

Andreas

-----Original Message-----
Hi,

If I'm not mistaken this error is handled in the
following:
http://www.microsoft.com/windows/embedded/community/tips/x
p/default.asp

(STOP error 6b)

It has to do with not including the correct filesystem.

Hans

-----Original Message-----
Hi there ,

tried to create a XPE-runtime for an Compaq Evo N620c
Notebook (Drive E).

My configuration :
Pentium M
Win2k SP4

Settings in Targetdesigner are as follows:

"Target Device Settings"
Boot drive > C:
Windows folder > e:\windows
Program Files Folder > e:\Program Files
Documents and Settings > e:\Documents and Settings
Boot ARC path > multi(0)disk(0)rdisk(0)partition(2)

boot.ini looks like that :

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

NTLDR created by Targetdesigner is used in the
rootdirectory .

After reboot the system starts booting XPE (Logo for about
2 seconds) and stops before FBA with a bluescreen
"PROCESS1_INITIALISATION_FAILED"

Any ideas are welcome ;-)

Thanks ,
Andreas

.

.