8 replies to this topic

[triplexxx]

Hi!

I have created a Win PE (based on Windows XP SP1) ISO and booted it successfully from a UFD into RAM using bootmgr.
To do this copy the ISO-File, bootmgr, ntdetect.com, ntldr (renamed setupldr.bin from Win PE) and winnt.sif in the root of the UFD and create a BCD with a legacy entry.

The winnt.sif looks like this:

[SetupData]
BootDevice="ramdisk(0)"
BootPath="\I386\System32\"
OsLoadOptions="/fastdetect /minint /rdexportascd /rdpath=test.iso"
Architecture="I386"

Because the size of that ISO-File is more than double than the size of a WIM-File, I tried booting into RAM using WIM-Technology (made WIM from ISO) using bootmgr (legacy entry) again.

When I boot from the UFD, booting stops with the following error: INF file txtsetup.sif is corrupt or missing, status 2.

The winnt.sif looks like this:

[SetupData]
BootDevice="ramdisk(0)"
BootPath="\I386\System32\"
OsLoadOptions="/fastdetect /minint /usenewloader /rdpath=\sources\boot.wim"
Architecture="I386"

Has anyone an idea where the problem is?

Thank you!
triplexxx

[Rui Paz]

Hi,

Seems you are not using Winbuilder?
Winbuilder + LiveXP project with WimBoot will create WINNT.SIF like this:

[SetupData]

BootDevice="ramdisk(0)"

BootPath="\i386\System32\"

OsLoadOptions="/fastdetect /minint /rdimageoffset=8192 /rdimagelength=3161088 /rdpath=images\LiveXP.wim"



[wimain]

systrim=1

Try it but if i correctly understand the "WimBoot way" it need some patched files to work...

Edited by Rui Paz, 25 October 2010 - 10:36 PM.

[Wonko the Sane]

Are you using \I386 or \minint paths?

Are you using a "standard" SETUPLDR.BIN?

Compare:
http://www.911cd.net...showtopic=17504


Wonko

[triplexxx]

Are you using \I386 or \minint paths?

Are you using a "standard" SETUPLDR.BIN?

Compare:
http://www.911cd.net...showtopic=17504


Wonko

I tried it with \i386 and \minint

I tried it with "standard" SETUPLDR.BIN and the patched one from Nikzzzz. Found here: http://sanbarrow.com...opic.php?t=1694

I found this in web:
http://www.msfn.org/...sta-bootloader/
http://www.911cd.net...php/t23040.html
http://sanbarrow.com...opic.php?t=1695

But I didn't get it to work.

[Wonko the Sane]

A .wim is a "partition-like" (and NOT a CD-like) device.

A CD-like device works with \I386, a partition-like uses \minint.

Try using the SAME SETUPLDR.BIN you used successfully for the .iso and modify it as per given thread (and keep the \I386 structure) OR use the SAME SETUPLDR.BIN you used successfully for the .iso and change the structure to \minint.

The references you posted have NO or very little relations with what you are attempting, they are a mix of things that shouldn't be really mixed.

The post by SEAKZ (as stated on the thread) is NOT understandable (to me at least) and is anyway related to a "full" Windows XP (and NOT a PE) .

The Nikzz modified files are for DIRECT booting a "full" XP (and NOT a PE) from .wim.

Just FORGET ANY attempt you made and create a working PE booting from .wim (LiveXP has such an option).
Boot it "normally" (i.e. WITHOUT using BOOTMGR or adding to it an entry to grub4dos grldr.mbr to BOOTMGR and from grub4dos boot the Live XP):
http://diddy.boot-la...ws.htm#windows3

Once you get that working, start your experiments again.


Wonko

[triplexxx]

I found another topic here ("can we use WIM for XP/2003 based projects?") dealing with my challenge:
http://www.boot-land...?...c=3549&st=0

I have been seraching now for a while for a solution and tried a lot. I think I get the error from post 1 (" INF file txtsetup.sif is corrupt or missing, status 2.") because setupldr is NOT able to load a WIM-Image into RAM. Setupldr can only load ISO-Images into RAM ...

Any other suggestions?

[Rui Paz]

Why not download LiveXP project and try to study what the Wimboot script do?

[cdob]

setupldr is NOT able to load a WIM-Image into RAM. Setupldr can only load ISO-Images into RAM ...

Setupldr.bin can load any file to RAM. But can mount some file systems only.
A default setupldr.bin can't mount a WIM-Image.

A edited setupldr.bin may mount a WIM-Image.
Booting such a image is another question.

Read Rui Paz's recommendation.

[triplexxx]

@Rui Paz: Thank you for you hint!

I did study WinBuilder and especially the Wimboot.script and adopted my PE 1.x (patched drivers, etc.). I can start my PE 1.x with WIM now but after loading I get the following BSOD-error:

PROCESS1_INITIALIZATIO_FAILED

Technical information: *** STOP: 0x0000006B (0xC000003A,0x00000002,0x00000000,0x00000000).

Any ideas?