moesasji

Hi SigiNet, Just thought to drop in again.... Remember me ? I haven't been on this forum much lately, but about a year ago (or has it been longer) I was one of the first to test and support PowerPacker. I see you've been busy with other projects too: the attention needed for RyanVM-integrator and other utils probably kept you from taking PowerPacker to the ambitions you explained to me then: to have PowerPacker be a multiboot-creation utility for not only XP, but also all other MS-OS'es. I'm planning on reading up on all of the UA-MSFN-forums myself, since there seems to be a lot going on. I however do hope that you will continue to support and further develop PowerPacker, since it allready has great merit and still has great potential of being one of the main utils for creating the truly ultimate unattended install DVD (maybe in conjunction with other great programs as RyanVM (als integrator), BTS Driverpacks and Roguespears AutoImage). Anyhow, my appreciation and thanks for the joy you bring us and best regards. Keep up the good work! Moesasji (moesasjilive@gmail.com)

SigiNet, Personally, I liked the checkboxes on the GUI better than hiding them in a menu. But I guess with all your plans for PowerPacker, a menu is ultimately unavoidable... As far as the bootscreens is concerned; it is a beautiful image, but (again) personally, I do not think it is appropriate for such a great business-tool as PowerPacker is. It's a bit boy'ish, a bit too much toylike now.... A more stylish, business-like bootscreen would be more apropriate in my opinion (and alas I don't have any graphical skills, otherwise I would have taken up your challenge for developing a bootscreen for PowerPacker, as posted by you in one of the topics) I love the tricpack-feature and the rename-feature that were introduced in RC5 ! Again, keep it up !!!! Moesasji

GREAT NEWS Congratulations. Appearantly, more and more people are realising the benefits of a MultiBoot CD/DVD and now that you have made it a possible task for even the not-so-technically-skilled, people obviously start implementing their different needs for reinstalls with your product. Maybe MicroSoft should be looking in to this obvious need people have, and make a tool like PowerPacker a standard program in their development kits or in the next Vista-release.... Keep it up; read your ideas on how to implement Plugins and am looking forward to an 100% unattended MultiBoot-creation tool !!

Just installed the tri-pack in VMWARE for the first time, and everything went great. The tripack-option works like a charm and it is indeed much faster to build than the previous way. Great option therefore !! I ran into a problem however when I also integrated my release without masstorage drivers. I was able to name it differently (XHPT) with the new rename option in PowerPacker, and it integrated in the total package just fine. When I tried to install it in VMWare though, on this install Windows reported hpt3xx.sys missing and aborted the setup. This has probably nothing to do with PowerPacker and I'll look into the way I integrated the Highpoint drivers in the image with Nlite first. Seems you again have made a great application even better; I'm very curious what more you can do

Sorry to have to report a possible bug so soon, but I wanted to try out the new TriPack-option. So I chose the input and output director, chose XP Professional Corporate edition etc... Did not fill out whether I wanted to make an unatteneded or DP-pacakage, since I figured PowerPacker would fill this in.... When I chose to make the pack(s), I got the following errormessage: "Invalid DriverPack Files!: Please check your driverpack settings. Make sure the directory you select contains the RUN_ME.cmd file, usually found inside the UWXP_ROOT dir" I however filled out the path to my UWXP_CD dir correctly and checked for the presence of RUN_ME.cmd.... is is there.... Any ideas ? I'll test it in a few other ways now... ---EDIT--- Tried the same (tri-pack checked), but also with the DP-button selected now; PowerPacker does not report the above mentioned error any more and has just started to automatically build the packs...

Siginet, Congrats on the new forum and even more on the new PowerPackerXP release. I'm going to try it real soon and post my feedback on this forum. Keep up the good work, but (as I noticed you spend a lot of time for coding PowerPackerXP and the RyanVM Integrator) also do not forget to get some sleep

Siginet, The problem is that I need two packs with dp ON and from the same XP-source. In one pack I use all the driverpacks except the masstorage, in the other I use all driverpacks including masstorage. So if OnOff=P in powpack.ini bot times, then it is correct, but both times the directory created in the output directory is XPPC. This is not a bug of PowerPacker, but by design. It is logically also, because not many people will need to make two almost identical packs. I need to, because the masstorage driverpack is not working on one of my pc's, but on the other one it is working. Maybe you can integrate a check in PowerPacker 1.0RC6 to check whether the output-directory already exists. If it does, Powerpacker could create a ne directory based on the standard name + 1 (say: XPPC1). This way, I would be able to integrate the desired images into one MultiBoot DVD. As for the development of PowerPacker concerns; I think you're doing great work. Keep it up, I'm already looking forward to the undoubtedly superb 1.0 Release !

Powerpacker 1.0rc4 is (again) a great program. I do have a question concerning it however.... One of my pc's uses a Highpoint 370 Raid controller (integrated on the mobo) and so far I have not been able to use the driverpacks massstorage succesfully on it. For my ultimate MultiBoot DVD I am looking for a way tha powerpack packs these two packs: The basis of this pack is XPSP2, Nlited with RyanVM and the official (and confirmed working) Highpoint 370 integrated through Nlite. As far as the Bashrat Driverpacks are concerned, I compiled a UWXPCD_ROOT dir WITHOUT the masstorage driverpack. The settings in powerpacker I use are: Input = g:\uaxp\uaxpenglitedhpt Output = G:\PPOutput Unattended Install Winnt.sif directory = g:\uaxp\uaxpadd $OEMdirectory = g:\uaxp\uapxextras\$OEM$ Driverpacks = integrated (except masstorage driverpack) Windows XP Version = Windows XP Professional Windows XP Edition = Corporate Extra Pack Files = NO Extra Root files = YES And the second pack looks like this: The basis of this pack is XPSP2, Nlited with RyanVM. In this pack I do not integrate the official Highpoint Driverpack, and do use the Bashrat's driverpacks INCLUDING the masstorage driverpack (I've compiled an UWXPCD_ROOT directory incorporating the massstorage driverpack). The settings in powerpacker I use are: Input = g:\uaxp\uaxpenglitedhpt Output = G:\PPOutput Unattended Install Winnt.sif directory = g:\uaxp\uaxpadd $OEMdirectory = g:\uaxp\uapxextras\$OEM$ Driverpacks = ALL integrated (including massstorage driverpack) Windows XP Version = Windows XP Professional Windows XP Edition = Corporate Extra Pack Files = NO Extra Root files = YES It seems that PowerPacker, since both versions have the options to use the driverpacks, make an unattended CD (DVD) and are based on WinXP Pro Corp, tries to install both the packs in the same directory on the output-folder.... Both packs get copied into the XPPC folder and therefore I have only one image to boot from, instead of the desired two.... Since the two only differ as to the uses base and the usage of masstorage Bashrat Driverpacks (but I explained above why these differences are important to me), Powerpacker treats them as the same packs and copy the second one over the first one in making the packs. Any ideas on how to avoid this and get a working setup ?

Powerpacker 1.0rc4 is (again) a great program. I do have a question concerning it however.... One of my pc's uses a Highpoint 370 Raid controller (integrated on the mobo) and so far I have not been able to use the driverpacks massstorage succesfully on it. For my ultimate MultiBoot DVD I am looking for a way tha powerpack packs these two packs: The basis of this pack is XPSP2, Nlited with RyanVM and the official (and confirmed working) Highpoint 370 integrated through Nlite. As far as the Bashrat Driverpacks are concerned, I compiled a UWXPCD_ROOT dir WITHOUT the masstorage driverpack. The settings in powerpacker I use are: Input = g:\uaxp\uaxpenglitedhpt Output = G:\PPOutput Unattended Install Winnt.sif directory = g:\uaxp\uaxpadd $OEMdirectory = g:\uaxp\uapxextras\$OEM$ Driverpacks = integrated (except masstorage driverpack) Windows XP Version = Windows XP Professional Windows XP Edition = Corporate Extra Pack Files = NO Extra Root files = YES And the second pack looks like this: The basis of this pack is XPSP2, Nlited with RyanVM. In this pack I do not integrate the official Highpoint Driverpack, and do use the Bashrat's driverpacks INCLUDING the masstorage driverpack (I've compiled an UWXPCD_ROOT directory incorporating the massstorage driverpack). The settings in powerpacker I use are: Input = g:\uaxp\uaxpenglitedhpt Output = G:\PPOutput Unattended Install Winnt.sif directory = g:\uaxp\uaxpadd $OEMdirectory = g:\uaxp\uapxextras\$OEM$ Driverpacks = ALL integrated (including massstorage driverpack) Windows XP Version = Windows XP Professional Windows XP Edition = Corporate Extra Pack Files = NO Extra Root files = YES It seems that PowerPacker, since both versions have the options to use the driverpacks, make an unattended CD (DVD) and are based on WinXP Pro Corp, tries to install both the packs in the same directory on the output-folder.... Both packs get copied into the XPPC folder and therefore I have only one image to boot from, instead of the desired two.... Since the two only differ as to the uses base and the usage of masstorage Bashrat Driverpacks (but I explained above why these differences are important to me), Powerpacker treats them as the same packs and copy the second one over the first one in making the packs. Any ideas on how to avoid this and get a working setup ?

Is there nobody reading this with suggestions for a solution ? Any help will be greatly appreciated, I'm just trying to make an unattended XP DVD that will work with both of my computers... (one using the Highpoint 370 Raid controller)

Hello, Just tried my UAXP on my old computer, an Abit-SA6R motherboard with an integrated Highpoint Raid 370 controller. Setus eems to go fine, but after the first reboot, the computer stops with a BSOD and the error message: STOP: 0x0000007B (0xF894D528, 0xC0000034, 0x00000000, 0x00000000) Looking for a solution, I found the following thread: HPT 370/372 installation troubles It sums up the troubles I have and I don't think the ultimate Highpoint driver has been integrated into the massstorage drivers yet. I've used the 5.07.7 Base pack and the 5.073 Massstorage driverpack. Strange thing is that the BSOD problem also occured when I made a second attempt with an install without the masstorage driverpack; on this second attempt I did use oll ather drivepacks, but left the masstorage driverpack out. Same BSOD though (maybe the fact that I use RyanVM update package in my UAXP has something to do with it ?) When I tried a third attempt with a fresh, clean install on a clean XPSP2, I have to press F6 during install. I got my HPT drivers from HighPoint Drivers and downloaded the 2.351 drivers for the RocketRaid100 controller. Put them on a disk and after pressing F6 during install, the drivers (and windows) get installed correctly. I've included the link to the driver that worked for me on a clean install: Highpoint 370 driver. Hopefully Bashrat can integrate these drivers into his masstorage pack in a way that an unattended install will be possible ? Using the HWID-program from Bashrat, I got the following results on my PCI-devices: =========== PCI devices =========== PCI\D347PRT\0000 : D347PRT SCSI Controller PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7&REV_74\4&157D4F1A&0&20F0: 3Com EtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX) PCI\VEN_10DE&DEV_0110&SUBSYS_40151043&REV_A1\4&20FB8C34&0&0008: NVIDIA GeForce2 MX/MX 400 (Microsoft Corporation) PCI\VEN_1102&DEV_0004&SUBSYS_00531102&REV_03\4&157D4F1A&0&10F0: Creative Audigy Audio Processor (WDM) PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_00\4&157D4F1A&0&12F0: OHCI Compliant IEEE 1394 Host Controller PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_03\4&157D4F1A&0&11F0: PCI Input Device PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_03\4&157D4F1A&0&30F0: HighPoint HPT3xx ATA RAID Controller PCI\VEN_8086&DEV_1130&SUBSYS_00000000&REV_02\3&13C0B0C5&0&00: Intel(R) 82815 Processor to I/O Controller - 1130 PCI\VEN_8086&DEV_1131&SUBSYS_00000000&REV_02\3&13C0B0C5&0&08: Intel(R) 82815 Processor to AGP Controller - 1131 PCI\VEN_8086&DEV_2440&SUBSYS_00000000&REV_01\3&13C0B0C5&0&F8: Intel(R) 82801BA LPC Interface Controller - 2440 PCI\VEN_8086&DEV_2442&SUBSYS_0405147B&REV_01\3&13C0B0C5&0&FA: Intel(R) 82801BA/BAM USB Universal Host Controller - 2442 PCI\VEN_8086&DEV_2443&SUBSYS_0405147B&REV_01\3&13C0B0C5&0&FB: Intel(R) 82801BA/BAM SMBus Controller - 2443 PCI\VEN_8086&DEV_2444&SUBSYS_0405147B&REV_01\3&13C0B0C5&0&FC: Intel(R) 82801BA/BAM USB Universal Host Controller - 2444 PCI\VEN_8086&DEV_244B&SUBSYS_0405147B&REV_01\3&13C0B0C5&0&F9: Intel(R) 82801BA Ultra ATA Storage Controller - 244B PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_01\3&13C0B0C5&0&F0: Intel(R) 82801 PCI Bridge - 244E Since I have been using the driverpacks for quite some time now and also have been following this forum, I'm confident that this problem can and will be solved. Bashrat usually doesn't give up until his driverpacks truly are universal usable... If integration of the attached drivers is not possible however, maybe someone can explain to me how I can integrate this driver myself (and replace the buggy driver in the original massstorage driverpack) ? TIA !!

Just tested with 5.07.7 using GuiRunOnce and KtD yes.... I have the same problem; a lot of files that are normally removed remain after completing the installation of driverpacks. Can you confirm that it is safe to remove these extra files ?

I use the driverpacks for my UA install. One of the driverpacks I use is the WLAN driverpack, but after installation on my laptop (which embeds a Intel 2200BG), I can't connect wireless to my router. The driver makes the connection, but does not get authenticated (it does not acquire a network address). When I install the full driverpackage (downloaded from intel), it does work. Maybe it has something to do with the WPA I have setup on my router ? Does anyone experience the same problem ? Any ideas on a solution ? TIA ----- SOLVED this problem has been solved with the update of DriverPack WLAN (V5.07), which included a newer driver version (Intel 2200BG, 2915ABG driver from 10/29/2004,9.0.1.9 [9.0.1.9] to 04/29/2005,9.0.2.25 [9.0.2.0]). Bâshrat the Sneaky -----

Bashrat, Again a great service to the community by you. Not only a good tutorial on how to make your own driverpacks, but also the UAWiki is a great idea. As a non-technical and interested follower of MSFN, I do have some questions on the tutorial though: - You write one should build the driverpacks in a D-folder. Then you write one has to 7-zip the DP-folder; what folder is meant to be 7-zipped; the base folder (X:\D or the subfolder(s): X:\D\sub) ? - The .inf-analysis method (keeping the files that are named under SourceDisksFiles) is helping on 95% of the drivers; are there other methods to be mentioned that kan aid in the remaing 5% ? I, for example, have problems driverpacking the ATI-driver for my laptop using the inf analysis method. Again, TIA...... Moe

While you are receptive for compliments, I will try a new suggestion too :-) Could you implement an option in PowerPack to run a batch-file of choice between building the packs and compilin them into an ISO. That way I would be able to automatically apply changes that need to be made (such as adjusting the winnt.sif after Bashrat's method was applied and copying some extra info (specific to one of the packs on the DVD) into the package. Ofcourse I could run such a batch file myself between packing and building an ISO, but I would like to be able to build the multiboot DVD completely withing PowerPacker; through the PowerPacker GUI I would also be easily reminded I have to make some adjustments (using my batch-file) before building an ISO from the packages ? I hope you understand what I mean ?

I second this compliment to Siginet and applaud his plans to continue development and broaden it to a tool that is able to implement a lot of the great MSFN-tricks and techniques. And as a tip to enuffsaid; I doubt that you will run into problems trying out the PowerPacker 1.0 RC1-program, but if you do, you can rely on great support by Siginet. I have found out for myself that with his support and enthusiasme, any problems occurring with his tool will be solved quickly. I hope a lot more MSFN-posters and MSFN-readers will give PowerPacker a try and report their results and suggestions in this forum.

Can't connect to at least the chipset, cpu and Lan-driverpacks now. Internet Explorer reports it can't download from sever.dnshostname1.net. Or have I done something stupid ?

Siginet, I have to agree with your assumption that 1.o RC1 is the most complete version as of yet. I have tested it by making a multiboot DVD with an attended and unattended setup (the last one with all DriverPacks included), and it worked flawlessly. Much obliged for all the work you put into it ! Now that we have it working, maybe we can start requests on making it more configurable ? I, for example, would like it if the multiboot graphical screen can be a screen of my own choice. I would also like it if I get presented one screen (directly aftre the graphical screen) on which setup to boot (instead of the tree-like structure you have implemented now). Furthermore, I would like it if you can incorporate a message straight after the graphical screen, that if you don't press Enter within x seconds, the PC will boot from the HD instead of the DVD/CD (or even better, can you make booting to the HD optional ?) Ofcourse, if you continue development, I will be glad to assist you with testing. As you have found out, my technical skills and knowledge of this subject is limited, but I can and will test everything you put out Thanks again and good luck on further development, Moesasji

I second the posts by Siginet regarding the combination of Bashrat's driverpacks with PowerPacker. On my pc, Powerpacker builds the packages and multiboot just fine, but when running the DP'ed setup, at the setup-level it returns an error message that it can't find the vgaoem.fon file (errocode 14). I don't get this when I use the driverpacks to make a single-boot install and I know for a fact that Siginet has analysed his package as well as Bashrat's for it. Maybe these tow great software-makers can contact each other to see if the power of two can solve this ?

I just tried the dp-base 5.07, using the powerpacker-program by SigiNet. On the unattended install with driverpacks, in setup it returns the following error: "File \XPPC\vgaoem.fon could not be loaded. The error code is 14" Any idead on how this is caused and what I can do to solve it ? I use all of the most recent driverpacks by Bashrat.

GOOD NEWS (hopefully travels fast). Siginet and me have solved my problem of not being able to use PowerPacker 1.06. Whatever I tried, I kept getting erors on patching the ntldr.bin and txtsetup.sif. After some experimenting and thinking, we resolved the problem by uninstalling XPIze from my sytem. XPize tweaked the commandline (cmd.com) and it seems therein lies the problem.... there appear to be compatibilityproblems between XPize and .NET. My thanks and respect to Siginet for his support and determination; it did the trick and I am looking forward to building my first Multiboot DVD now using PowerPacker 1.06

Hi Siginet, I'm afraid I have to report that further testing did not yet solve the ntldr.bin and txtsetup.sif-patching problems on my end. I tried disabling the virus scanner (AVG) and all ad-aware programs, but that didn't help. Then I tried a safe boot, but also in that environment the errors popped up. I then continued to do an install under a virtual environmet, using VMWare, but als in this virtual environmet, the error pops up. Finally I replaced my soure input disc for another XP source input disc, but this did no good either.... I am running out of options to test: do you have any suggestions ? BTW, in all tests I use the original PowerPacker 1.06beta (bootfolder.exe edition) Moesasji

Siginet, When I try to download the winnt32 version, I get a "cannot find server" error message. I sent you a PM with the suggestion to use MSN to transfer this file.

I'm sorry, but it doesn't solve it. I still get the errormessages on hacking the files setupldr.bin and txtsetup.sif...... The patchprogram reports it can't find these files and when I search my HD for them (during the pack-process, so at the moment the patch-program haults for the error message), I do find them in G:\PPOutput\ROOT\ROPC\I386. The Folder G:\PPOutput\ROPC is completely empty though (still) There's nothing with those filenames on my C: drive, neither in my TEMP directory (C:\TEMP) nor in the usual TEMP directories (C:\Document and Setting\...) All the others files that have to be patched do not return an error message, so I guess those get found and patched fine. Is there maybe something special about the files setupldr.bin and txtsetup.sif ? Where should your program find them when it tries to patch them ? I did find out BOOTFOLDER.EXE is placed in my Temp folder (C:\TEMP) during the PowerPacker process. Just to be complete, I will post a screendump of the GUI of PowerPacker as I used it... I'll ofcourse continue to give you any information you want in tracking this error and am still looking forward to creating my first MuliBoot DVD with PowerPacker (1.07 ?) Maybe you can inform me on what processes PowerPacker starts / does, so I can try to analyze by way of trial and error where the problem may lie ?

I know it's not the normal TEMP directory (that's why I specifically mentioned it in my post). I tweaked XP to use just one folder for TEMP-files (adjusted the temp-variables), since I had constant difficulty finding the TEMP-folders when I needed them. Thanks for the continuing development on your program. I will try out the new release as soon as humanly possible