125 replies to this topic

[nikzzzz]

Create Iso for booting wim packed image.

Continuation of theme BootSdi.
Loading of an image from Wim Image allows reduce size of an image in 2 - 3.5, requirements to system resources decrease.

Files are required Automated Installation Kit (AIK) for Windows Vista SP1 or Windows Vista SP1 + SetupLdr.bin Win2003Sp1.
In the catalogue %tool%s 7z.exe it is necessary to the version 4.65 or later.

 WimBoot_2009_04_21.7z   294.52KB   2389 downloads

Regards,
Nikzzzz.

[Lancelot]

Hi nikzzzz

A dream will becoming true :)

But i guess i do sth wrong
7z.exe & 7z.dll v4.65 added to %tools% folder,
bPatch.exe 1.1.0.0 added to %tools% folder,
SETUPLDR.BIN i use with just taken md5checksum: 4352373BC08FFA6D8FFDB20A3BA5BC9A

i click extract , files extracted successfully from 6001.18000.080118-1840-kb3aikl_en.iso

my current modified script
http://lancelot.winb.../5F/WimBoot.rar

after the build
http://lancelot.winb...0422_042644.rar

I get

NTOSKRNL.EXE could not be loaded.... The error code 14

error

i extract NTOSKRNL.EX_ and run wimboot script again, no progress


ps:
i will upgrade bPatch.exe in wimpack and bootsdi script if you approve ?

Edit 20100730:
LiveXP + Wimboot + PXE topic by Rui Paz

[nikzzzz]

Hi nikzzzz

A dream will becoming true :)

But i guess i do sth wrong
7z.exe & 7z.dll v4.65 added to %tools% folder,
bPatch.exe 1.1.0.0 added to %tools% folder,
SETUPLDR.BIN i use with just taken md5checksum: 4352373BC08FFA6D8FFDB20A3BA5BC9A

i click extract , files extracted successfully from 6001.18000.080118-1840-kb3aikl_en.iso

my current modified script
http://lancelot.winb.../5F/WimBoot.rar

after the build
http://lancelot.winb...0422_042644.rar

I get error

i extract NTOSKRNL.EX_ and run wimboot script again, no progress


ps:
i will upgrade bPatch.exe in wimpack and bootsdi script if you approve ?

It is my fault.
The script does not work with packed cab files.
Add UnCab.cmd in %Tools %, it should solve a problem.

MD5:
b83fad8fd28e637b82cb4a6bef7d6920 *6001.18000.080118-1840-kb3aikl_en.iso
fb636c85e95f64ddd74740650c308b38 *fbwflib.dll
98ac67e24b18c21d3cf15d9fe75e1054 *WIMGAPI.DLL
b7529745928b8831c01aee147dc7223b *imagex.exe
22d9945b4aae36dd59620a918f2e65f4 *boot.sdi
77a786e15a46215b2549662e189a85c2 *fbwf.sys
94644648375f9f5f10a0b783e90d3a2a *ramdisk.sys
090a2b8f055343815556a01f725f6c35 *WIMFLTR.SYS
02c863078600ea925128244e46736ff2 *wimfsf.sys


 UnCab.7z   259bytes   969 downloads

Regards,
Nikzzzz.

[nikzzzz]

Fixed UnCab bug.

 WimBoot_2009_04_22.7z   294.77KB   1210 downloads

Regards,
Nikzzzz.

[was_jaclaz]

@nikzzzz
@Lancelot

Can any of you "simplify for the masses" by actually explain what is this?

And to which project(s) it may apply?



jaclaz

[nikzzzz]

@nikzzzz
@Lancelot

Can any of you "simplify for the masses" by actually explain what is this?

And to which project(s) it may apply?



jaclaz

The system is loaded in RAM and does not demand CD after loading.
Speed of loading in 2-3 times is more.
The size is reduced ~ 2 - 3.5
Economy of memory.
It is applicable to any project based by WinXp , SP3 recommended.

Regards,
Nikzzzz.

[Lancelot]

You are Wonderful Nikzzzz


Need to look more before adding LiveXP

Also I will upgrade bPatch.exe in wimpack and bootsdi scripts as there is no objection

@jaclaz:
booting .wim file (not .img or .iso )
I havent look carelfully to see if wimboot can be used with wimpack, if so you get the minimum spaced build

[nikzzzz]

Restrictions WimBoot:
It is impossible to mount Wim files on system disk.
In the localised assemblages (not Eng) bugs can be shown. In XpSp3 I them did not see.

Update WimBoot
Added UnUpx - double packing (wim & upx) is losses.

 WimBootV7_2009_04_22.7z   295.09KB   1055 downloads

Regards,
Nikzzzz.

[Lancelot]

@Nikzzzz

Also I will upgrade bPatch.exe in wimpack and bootsdi scripts as there is no objection

Verry sorry Nikzzzz , it was totally my mistake, it seems my bPAtch.exe was v1.000 on my %tools% folder, and there is only 2 scripts that contain bpatch bootsdi and wimboot (not wimpack) which already have updated versions of bPatch.exe


yep i remember .wims can not be on a wimmounted drive, it is sad this restriction continues here
but i cant remember, is it possible to make junctions on wimmounted drive, if so wimpack still can be useable

[was_jaclaz]

@Lancelot

You have a fairly "high" concept of the level of knowledge of "the masses".

Unfortunately I am not up to that standard.

This is NOT an answer:

booting .wim file (not .img or .iso )

it's a one-liner, saying NOTHING at all that wasn't already stated in nikzzzz's original post and vaguely offensive to my intelligence.


Just fake not knowing all you know and the "special secret codes" you are using, like "bPatch.exe", "wimpack", "bootsdi", WHAT remains of this thread?

If I get it right, nikzzzz found somehow a way to use a "Vista like" .wim image to boot a XP/2003 based PE.

Basically a driver for the Vista .wim (coming from the Vista WAIK 6001.18000.080118-1840-kb3aikl_en.iso) is added to a XP/2003 based PE and it is booted through the Server 2003 SP1 or R2 (NOT "gold", NOT SP2) SETUPLDR.BIN+NTDETECT.COM+RAMDISK.SYS.

Or not?

The RAMDISK.SYS seems like coming from the WAIK:

"Waik: boot.sdi, fbwf.sys, fbwflib.dll, imagex.exe, ramdisk.sys, wimfltr.sys, wimfsf.sys, wimgapi.dll"

Whilst SETUPLDR.BIN and NTDETECT.COM come from Server 2003 SP1:

If,ExistFile,"%TargetDir%\I386\setupldr.bin",FileDelete,"%TargetDir%\I386\setupldr.bin"
If,ExistFile,"%TargetDir%\I386\ntdetect.com",FileDelete,"%TargetDir%\I386\ntdetect.com"

wimfsf.sys and ramdisk.sys are later patched. WHY? What is the "added" or "modified" feature?
(for ramdisk.sys I guess that is to avoid the "double-ram used" problem )

The drivers are later added to Registry and TXTSETUP.SIF.

SETUPLDR.BIN is patched to change the path.

A new WINNT.SIF is generated with parameters:
/rdimageoffset=8192 (OK )
and
/rdimagelength=3161088 (WHY? is this a "fixed" size?)


No need to answer any of the above questions, I'll find the answer myself, thanks.

jaclaz

[Lancelot]

@jaclaz
please dont take my any post on boot-land offensive, with your sentence "simplify for the masses" i focus on simplify and didnt take masses into considiration as i didnt understand that . I dont have capability to answer your questions, One line just a joke , I wish you only had smiled


@nikzzzz

In the localised assemblages (not Eng) bugs can be shown. In XpSp3 I them did not see.

Test with xpsp2 source resulted with this, i guess you mean that too (havent tested with sp3 )

find.exe - Entry Point Not Found
The procedure entry point SdbGetAppCompatDataSize could not be located in the dynamic link library apphelp.dll.

continuing the build, iso successfully created

[nikzzzz]

This is NOT an answer:

You have answered the questions.

Basically a driver for the Vista .wim (coming from the Vista WAIK 6001.18000.080118-1840-kb3aikl_en.iso) is added to a XP/2003 based PE and it is booted through the Server 2003 SP1 or R2 (NOT "gold", NOT SP2) SETUPLDR.BIN+NTDETECT.COM+RAMDISK.SYS.
Or not?

Yes.

wimfsf.sys and ramdisk.sys are later patched. WHY? What is the "added" or "modified" feature?
(for ramdisk.sys I guess that is to avoid the "double-ram used" problem unsure.gif)

It is made only for compatibility with WinXp booting.

/rdimagelength=3161088 - It not essentially, without it some programs will be the foolish size of a disk x:, 3 Mb instead.

SETUPLDR.BIN is patched to change the path

Setupldr.bin W2003 at all does not understand Wim.

I apologise for bad English.

Regards,
Nikzzzz.

[nikzzzz]

@nikzzzz
Test with xpsp2 source resulted with this, i guess you mean that too (havent tested with sp3 )
continuing the build, iso successfully created

Bug - if path contain the localised symbols (not eng) in Documents and Setings, the menu is displayed incorrectly.



Regards,
Nikzzzz.

[was_jaclaz]

@lancelot
No problem, I just wanted to point out that sometimes you completely fail to explain things, giving a lot of things as acquired, something that often is not the case.

@nikzzzz

Thanks for the further explanation.

Don't worry about your English , if you try to use more words, you will make more errors , but still people will be able to understand a bit more about your work, otherwise it will probably be "confined" to the use of a very small number of "geeks".

Still a couple of questions, if you don't mind:

• is the Ramdisk coming from WAIK (patched for XP booting) still limited to 512 Mbytes as the Server 2003 SP1 was? Or the 512 Mb limit comes form SETUPLDR.BIN?
• The patches appear to be "version specific", any chance that they can be adapted to other versions? (for example the Server 2003 R2 SETUPLDR.BIN, that right now is probably "more available" than the SP1 one?)

jaclaz

[nikzzzz]

[quote name='jaclaz' date='Apr 22 2009, 04:17 PM' post='65602']
Still a couple of questions, if you don't mind:

• is the Ramdisk coming from WAIK (patched for XP booting) still limited to 512 Mbytes as the Server 2003 SP1 was? Or the 512 Mb limit comes form SETUPLDR.BIN?
• The patches appear to be "version specific", any chance that they can be adapted to other versions? (for example the Server 2003 R2 SETUPLDR.BIN, that right now is probably "more available" than the SP1 one?)

/quote]

Restriction ~480 Mb remains.

Server 2003 R2 SETUPLDR.BIN - can later.

Regards,
Nikzzzz.

[was_JFX]

Wow nikzzzz this is amazing! Thank you so much!

You really create a hybrid using Setupldr to load and use a WIM file as Ramdisk.

I allways want to have a LZX compressed Ramdisk for XP based PE's

Is it maybe also possible to patch ntldr to accept WIM's?

btw All the required files from the Waik seems to be language neutral or english, I used the german version of Waik Sp1 without problems.

[nikzzzz]

I allways want to have a LZX compressed Ramdisk for XP based PE's

Is it maybe also possible to patch ntldr to accept WIM's?

btw All the required files from the Waik seems to be language neutral or english, I used the german version of Waik Sp1 without problems.

You wish to make double packing? It will lead only to losses!

Regards,
Nikzzzz.

[was_JFX]

No, I was thinking about MobileOS (NTLDR loads an native Diskimage to RAM and start a real XP from this Ramdisk). If NTLDR has the same possibility to load a WIM like your patched SETUPLDR this project would become very interesting again.

[nikzzzz]

No, I was thinking about MobileOS (NTLDR loads an native Diskimage to RAM and start a real XP from this Ramdisk). If NTLDR has the same possibility to load a WIM like your patched SETUPLDR this project would become very interesting again.

I did not use MobileOs, but directly it will not work, its updating will be necessary.
Regards,
Nikzzzz.

[nikzzzz]

Update WimBoot.script

Add MultiCpu support (Automatic choice kernel at loading)

 WimBoot_2009_04_28.7z   295.59KB   890 downloads

Regards,
Nikzzzz.

[nikzzzz]

Update WimBoot.script

History06=2009_04_22 Nikzzzz fixed UnCab bug
History07=2009_04_22 Nikzzzz added UnUpx
History08=2009_08_28 Lancelot interface addings, +-//disable, +[Md5info_of_Files_In_Project] +[Information_WimBoot] sections, +contact info
History08=2009_08_28 Lancelot +[verify] only for 2 files to get faster verify (number-method can change in time if reported on boot-land)
History09=2009_04_28 Nikzzzz added MultiCpu support
History10=2009_05_05 Nikzzzz fbwflib.dll is cleaned
History10=2009_05_05 Nikzzzz bPatch.exe - fixed bug
History11=2009_05_05 Nikzzzz update Path_multi_cpu_setupldr.bin
History11=2009_05_06 Nikzzzz added PXELDR loader from boot for network

 WimBoot_2009_05_06.7z   297.4KB   893 downloads

Regards,
Nikzzzz.

[Lancelot]

+

// Bug - hostos x64 when UnUPX used

--> continues and results with bootable iso
+

Contact=http://www.boot-land.net/forums/index.php?showtopic=7801

maybe nice for next version (you decide) !
+only file boxes default folder changed and uploaded to Livexp server as beta

Thanks a loot for all

[olegpov]

Hi All

/Russian for nikzzz
Для себя сделал в скрипте такие изменения. Упрощает перенос системы на USB флешку или НDD при использовании внешнего загрузчика типо grub

/English
For itself has made in a script such changes. Simplifies carry of system on USB stick or USB-НDD when use of the external loader like grub

in

[Variables]

%WimBootTmp%=%ProjectTemp%\WimBoot

replace

%WimBootTmp%=%IsoDir%\WimBoot

in

Echo,"Creating Iso file"

ShellExecute,Open,#$q%Tools%\CdImage.exe#$q," -l%VolumeLabel% -g -h -oc -oi -yd -m -c -j1 -b#$q%ProjectTemp%\bootsect.bin#$q #$q%WimBootTmp%#$q #$q%isofile%#$q"

DirDelete,"%WimBootTmp%"

replace

//DirDelete,"%WimBootTmp%"

[felix]

I did the same thing privately (Ram-Loading a WinPE 1.x image into a WIM container) using Beta1 WIMs and Longhorn's bootloader.
I never released it and don't plan to release it as it raises the possibility of a legal ruckus and I don't want that.

nikzzz just found a way of legally doing it.
Mine however didn't had the 512mb limitation.

felix

[nikzzzz]

Hi All

For itself has made in a script such changes. Simplifies carry of system on USB stick or USB-НDD when use of the external loader like grub

Thanks for good idea

History12=2009_05_17 Nikzzzz added Boot from HDD or UsbFlash (Thanks Olegpov)

 WimBoot_2009_05_17.7z   297.56KB   891 downloads

Regards,
Nikzzzz.