[Stable Release] Windows XP PowerPacker v1.0 RC17

[Siginet]

As for the Upgrade issue. I wouldn't doubt if it has an issue because I don't test the upgrade disks very often. I don't normally create upgrade packs. i will look into it. Yes there is a newer PowerPacker in the works that allready fixes minor flaws like the ones you see in this thread... and possibly allready fixes your flaw as well.

[pcguy]

Thanks for the reply. Strangely enough, PowerPacker works just fine with my XP Home Retail & Xp Home upgrade. The menu lists them correctly.

Hmmm....

[pcguy]

Siginet,

The new Intergrator Beta 28b properly identifies my Pro Upgrade disc correctly. However, I just built a multi-dvd install disc, and PowerPacker still mis-identifies the XP Pro SP2 Upgrade as RETAIL.

Really looking forward to a updated PowerPacker.

Thanks

[wimb]

Hi Siginet,

Windows XP PowerPacker is a very powerfull program.
I used to make my MultiBoot DVD's manually according to http://flyakite.msfn.org/
but I must say your program is very handy and much faster for making a MultiBoot DVD.
Especially the way in which you make the folders with XP Boot Files ($WIN_NT$.~BT) is very smart,
because it is made without launching winnt32.exe /noreboot
Interesting ...., how is it done ?
In my DVD I usually make 3 versions of XP Professional:
SP2, SP2 + UpdatePacks and SP2 + UpdatePacks + BTS DriverPacks using RyanVM Integrator and DP Base.
But in that case making 3 times the XP Boot Files Manually is a lot more work than using Windows XP PowerPacker.

Also the integrated use of BCDW of Alex Kopylov for booting from DVD is working very well
and making new boot options for BCDW is very handy.
See for BCDW http://bootcd.narod.ru/index_e.htm and http://www.wolfgang-brinkmann.de/bcdw/index_e.html
Everything works fine, I also added options for booting with BartPE and
booting from Memtest and MS-DOS bootfloppy images.
For BartPE I noticed that the very long filenames (112 chars) for WinSxS\Manifests,
which are always a problem when making a DVD,
are well treated and reproduced in the PowerPacker ISO made with the integrated CDIMAGE.
And BartPE is running very well.

Somehow there is a lot more space on the DVD.
The 4,2 GB in files and folders now only take 3,4 GB for the size of the ISO image made with CDIMAGE,
whereas my ISO made with mkisofs.exe (ISO + Joliet + Rock Ridge) was 4,3 GB in size. A nice reduction .....

There is only one question that I have:
All files and folders get now on DVD the date 23-08-2001 10:00
Is it possible to preserve the original filedate in the ISO, by setting some option for CDIMAGE ?
Or is that on purpose in view of making the new ISO directory, which has only Capital Letters.

Cheers,

wimb

[pcguy]

I've just compiled a Multi-DVD with:

XP Home OEM SP2
XP Home Retail SP2 Upgrade
XP Pro OEM SP2
XP Pro Retail SP2
XP Pro Retail SP2 Upgrade
XP Pro Corporate OEM SP2 HP
XP Pro Corporate OEM SP2 Dell
XP Pro Corporate OEM Multi OEM (using OEMScan Addons)

Precompiled = 13,602,388 kb (13.2 gb)
Finished = 2,829,592 kb ( 2.69 gb)

Wow!

Now if I could just get my hands on a copy of XP Home Retail and more corporate discs I'd be really happy!

By the way, I do have one question: What is a Tri-Pack?

[Siginet]

Thanks for the appreciation! It means a lot! I'll look into the data/time stamps. BTW I make the Boot folders by parseing the dosnet.inf file. Every [FloppyFiles.*] section in dosnet.inf is reffering to the files needed in the boot folder. the d1 is refferenced in the [Directories] section. Which shows the path of where the file resides.

A Tri-Pack is: PowerPacker will automatically create 3 versions of the OS in the Boot menu. For instance if you are using windows XP Pro Retail it would make:
Windows XP Professional Retail - Unattended With DriverPacks
Windows XP Professional Retail - Unattended
Windows XP Professional Retail - Attended (Perfect for repair option)

[wimb]

Thanks for the appreciation! It means a lot! I'll look into the data/time stamps. BTW I make the Boot folders by parseing the dosnet.inf file. Every [FloppyFiles.*] section in dosnet.inf is reffering to the files needed in the boot folder. the d1 is refferenced in the [Directories] section. Which shows the path of where the file resides.

Thank you very much for the info on how to use dosnet.inf for making the Boot folders.
It is very interesting to use this method also in the usb_prep7.cmd Batch Program
to prepare in a similar way the USB-stick for Install of Windows XP http://www.msfn.org/board/index.php?...c=61384&st=423

By the way when I was using Windows XP PowerPacker I observed that XP SP2 and SP2 + Updates Integrated with RyanVM
get the same foldername XOPC and so overrule eachother, which is not desired.
I forced them to get different foldernames X2PC and X7PC by using the handy build in option of providing a Custom Pack Name.
But it would be nice if the PowerPacker would make by default already a distinction between Source and Source with Updates Integrated.

The option of making a Tri-Pack as you explained is also very handy, thank you for the explanation.

[wimb]

Thanks for the appreciation! It means a lot! I'll look into the data/time stamps.

Hi Siginet,

Do you have already an idea what is causing all data/time stamps in ISO's made with XP PowerPacker being 23-08-2001 10:00 ?

I followed your way of making the XP Bootfolder by parsing DOSNET.INF
and have made for this purpose a small Batch Program BT_folder2.cmd .
The same Code was then added to the usb_prep8.cmd program to make Bootable USB-stick or USB-Harddisk for Install of Windows XP.
http://www.msfn.org/board/boot-insta...84.html&st=437

Everything works very fine, thank you for your help.
It would be nice to make a single-file GUI Program from the usb_prep8.zip file, like Windows XP PowerPacker,
but I have not the experience nor the programming software to do it.

Regards,

wimb

[wimb]

Hi Siginet,

Just to keep you informed:

USB_MultiBoot_10.cmd Batch Program is presented at CD Forum, which:
- Prepares MultiBoot USB-Drive provided with Windows XP Setup LocalSource
- Supports Booting: MS-DOS BartPE WinPE 2.0 and Setup Windows XP
- Supports GRUB4DOS with DOS FLOPPY IMAGES + Linux and Supports SYSLINUX Menu
- Supports Portable WinTools which run direct from GO-Menu button

How to Install XP from USB + Program USB_MultiBoot_10.zip

NEW - Install XP from USB AFTER Booting with PE from HDD or USB
Tutorial USB_XP_Setup + Program U-XP-SET

Regards,

wimb

[ENU_user]

most definitely will need a way to boot up some things
i keep thinking all this can be done with integrator ... which is the best tool for precompiling things

it be great if some integrator routines stuff can be merged into this
so we can integrate pre-compiled boot images
"i would like to have an easy way to compile a special boot routine .."

mainly for booting up tools or images ...
bartPE
winPE
install boot for USBHD "XP setup" not finishd
USB KEY Boot
USB KEY "XP setup"
.etc

now if it can all be upgraded in a way that one can integrate a boot method that can get interesting ...

as i understand, there are many ways and many boot images everywhere on the net , i think its time to let everyone give it there best shot .. using future Power packer

if it features a simple way that someone can write down something like and addon! that is what will be needed then IMO ...

Wimb, i need to ask, can the usb key boot from a boot image or do we need to change setting in the bios for that ...
there must be a something that can do the change auto or with reboot or as needed ...

thanks