moesasji

I use method 2 with GuiRunOnce and I choose to keep the drivers..... I'll try this process of elimination when I have the time for it; alas probably not before this weekend. Thanks for the analysis and suggestion though... On the install my problems occurred, I was booting from a DVD but not a MulitBoot DVD (still trying to make a MultiBoot DVD with your PowerPacker utility

I am using Windows XP Professional (Corporate Edition), SP2 English I just followed your directions and did not find a BootFolder.exe in my Temp folder (the TEMP folder is C:\TEMP) Thanks for your persistance !

I think you're on to something, because I do not have all of the files you mention above. In my G:\\PPOutput\XPPC folder, there's only the file winnt.sif and the G:\PPOutput\ROPC folder is completely empty. The *.DAT files you request from the G:\PPOutput folder are attached to this message..... I'll post some images of what happens during boot: After pressing the [P] key, I get the following screen Then, after pressing the [C] key, I get the following screen And finally, after either pressing the [D] or [R] key, I get the following error: Here's the directory structure: The install folder contains programs I wish to install after XP and was copied to the powerpack using the option in your program. Hope this can help you trace the things that went wrong ?

Zipped cdshell.ini is attached to this message..... Although I'm happy to see that my problem helped to solve another bug, it did not solve my problem. The folder I saved the packs in is called G:\PPOutput No spaces in that name therefore, nor in any of the other folders PowerPacker accessed in compiling the powerpack (I have some experience with the driverpacks, so I avoid spaced in UA-folders anyhow). Maybe there are some other things to explote; just tell me what information I can supply you with, and I will inform you. Your respons (the depth and the quality of it) on my first question was great and, although it did not help me, is greatly appreciated. Keep up the good work; I really think you are developing a much needed utility and once I get it to work, I'm looking forward to creating MultiBoot DVD's with it.

After laying low for a while on the subject of unattended CD's, I'd thought I'd pick it up where I left of. So I downloaded the latest driverpacks, read up on the forum and started to build a new unattended CD. Since I have experience on the previous releases, I was glad to see that at least in VMWare verything went well. Confidently, I burned the ISO to a DVD and booted from it on my laptop. At first, everything went well there too: but, during the copy process of the extra files (so even before XP was booted for the first time from HD) the laptop spontaniously rebooted..... Thinking maybe the DVD had an error on it, I burned a second copy of the image and tried again.... same result however. Because I started doubting myself and the quality of the ISO I had made, i than again ran it in VMWare.... no problems at all and the copy process (which halted my laptop) ran perfectly. Since the reboot of the laptop occurs immediately (without a waring of errormessage), I can not determine where the problem lays. I do know, that when I try to boot from the half-copied DVD, the XP-install-procedure begins with an error message that it can't find driverwatsigningpolicy.exe (or something like that). The install-procedure doesn't finish but reboots after a few minutes. I'm not a technical guy and I've not found reports like mine in this forum yet. Maybe there's someone out there who has a clue to what might cause this problem ? Just for diagnosis purposes, I will mention that the laptop in question is a Asus M6N, with 1 GB Ram, an ATI mobility 9600/9700 card and a Pentium M 1,6 Ghz processor. Any help / tips will be greatly appreciated !

Just made an iso with the PowerPack 1.05 and tried to install it in VMWare 1.05. On both packs created (one regluar, attended and one with driverpacks, unattended) I got an error-message: "CDBOOT: couldn''t find ntldr". I thought I prepared the image as desribed in the helpfile, but obviously, something went wrong.... any ideas ? Furthermore: when booting from the image I first get a graphical screen with PowerPack 1.0 beta. When I press Enter at that stage, I get a dos-screen asking me to push the Enter-key.... if i don't push this enter-key within a few seconds, the screen goes black and nothing happens any more (even not when pushing the ENTER key after the screen has gone black). It looks like if the bootmenu would want to boot something standard if the ENTER-key is not pressed, but I don't know what it is looking for.... Any help would be appreciated. I'd like this PowerPack-setup to work for me.... TIA, Moesasji

Great idea, this powerpack utility ! Just started experimenting with it, since I've been looking for a way to create a multiboot CD/DVD that gives me the option for both an attended as well as an unattended install. I'm completely new to creating multiboot DVD's, so I figure I'll probably have to learn the hard way. The help-file in the PowerPack program is very helpful though. Regarding the PowerPacker util, I do have some questions already: - How to find out if i'm using an OEM edition, Upgrade edition, Retail edition of Corporate edition of Windows ? - When Powerpacker starts packing the files into the powerpacks, it appearantly tries to hack some files. On 2 files (one being txtsetup.sif) I get an error message (but still can continue): is this the way it should be (I get this error on an attended install of XP-SP2 Corporate edition). Furthemore, I've been toying around with the driverpacks for a few months now, but never seriously used it for any real computers (just virtual computers). I'm trying to make the perfect (at least, for me) CD/DVD using the combination of the following programs: Nlite (for trimming down and applying patches / tweaks) RyanVM (for updating the XP-SP2) XPIze (for better looks) Bashrat Driverpacks (for the broadest possible driver-support) WPI (for automating the unattend installation of programs after Windows-install) PowerPack (for creating multiboot DVD's). Can anyone confirm the follwoing is in the right order: 1. Start Nlite, use it to integrate fixes, patches and apply tweaks (including RyanVM and XPize) 2. Run Powerpack, use it to integrate Bashrat Driverpacks, copy WPI-installfolder to Root op PowerPack-folder and create multiboot-folder Anyhow, thanks for developing and supporting PowerPacker. It looks very promising and is a welcome addition to the other great tools available on MSFN.

Bâshrat, Working flawlessly with the 5.03.1 basepack !! I've just tested a VMWare setup and didn't get any error with all of your driverpacks installed, as well as RyanVM and Nlite. Great work !! Have you got your paypal-account up yet ?

Hello Bâshrat, Thanks for the 5.03 updates. I immediately downloaded the new basepack, sound- and masstorage drivepacks and started integrating. The other drivepacks I use are graphics (a & B), Lan and WLan (all the most recent from the 5.02 series). After making an ISO with Nlite and installing it in VMWare, I got the following error message: In the appropriat line of txtsetup.sif, I find the following information: arcm_0= Areca (ARC1110) SATA PCI-X RAID Host Adapter" Any idea what is causing this ? I have to mention that I did not only integrate your driverpacks, but also used Nlite and RyanVM. I however first used Nlite (also to integrate RyanVM), then applied your driverpacks and finally made an ISO with Nlite.

Hello Bâshrat, Thanks for the 5.03 updates. I immediately downloaded the new basepack, sound- and masstorage drivepacks and started integrating. The other drivepacks I use are graphics (a & B), Lan and WLan (all the most recent from the 5.02 series). After making an ISO with Nlite and installing it in VMWare, I got the following error message: In the appropriat line of txtsetup.sif, I find the following information: 1564U3-1= "PM1564U3 Ultra3 Single Channel" Any idea what is causing this ? I have to mention that I did not only integrate your driverpacks, but also used Nlite and RyanVM. I however first used Nlite (also to integrate RyanVM), then applied your driverpacks and finally made an ISO with Nlite.

Bâshrat, In the past I've had critical errors in VMWare, but I guess they originated in me not using the right order of installation between Nlite, RyanVM and your DP's. However, I did install on my laptop just now and there were no errors in that 'live-environment' either... 1. Base=5.02.10, Masstorage=5.0.2.2, all other DP's most recent version 2. Asus M6B000Ne (don't know the model of the motherboard) 3. No RAID 4. ?? 5. YES: installation on the laptop including all DP's was succesful !! Thanks (again) Bâshrat ! Hope you'll have your Paypal-account soon so I can donate to support your further development !

1. Base=5.02.10, Masstorage=5.0.2.2, all other DP's most recent version 2. VMWare 4.52 3. No RAID 4. ?? 5. YES: installation on VMWare including all DP's was succesful !! Thanks Bâshrat ! Some background-info Just thought I'd let you know; just tested a UAXP install with all of Bâshrat's driverpacks, RyanVM cab-update. Installed it all with Nlite (first applied the appropriate Nlite options, including integrating RyanVM's cab-package, paused Nlite (kept it at the window for making an iso without activating the making of the iso) and then ran the Bashrât-install (all driverpackages including the MassStorage; all in their most recent version). Then edited txtsetup.sif according to Bâshrat's instructions, saved the modified txtsetup.sif and returned to Nlite where I ordered the ISO to be made. Just installed it on VMWare and there were no errors whatsoever . I'm going tot ty it now on my laptop and if that's succesful too, I'll try it (in the weekend) on one of my pc's with a Raid-controller. Unfortunately I don't have any pc's that use the Nforce-chipset, so I can't help out in testing that ones.

Keep on going Bâshrat ! I'll be donating too if you start using PayPal. It's rapidly becoming a (trusted) standard for internet banking and with the revenues you get from it, you'll easily be able to pay for the subscription-charge for your creditcard. Keep up the good work, eventually you will reach perfection

Running the 5.02.10 basepack, I seem to have a few problems: - My update.cmd doesn't seem to work: when I run the cmd, it quickly opens a dosbox and shuts again (all within a fraction of a second). I do not get any output from the cmd-file, so therefore I do not get any information on whether my files are up to date; - when running the run_me.cmd (method 2), I get a error-message that txtsetup.oem can not be found. I do not use the mass-storage DP since Bâshrat advises against it. All other DP's I do use. Because of the error messages, I think my install in VMWare will not work, but i'll find that out tomorrow. I do have to mention that before applying the 5.02.10 method 2, I did a Nlie (0.99.8b2) to incoroporate some tweaks and the RyanVM cab-package... I know mixing this with DP makes it difficult to track where the errormessages relate to, so I'll try a fresh install with just Bâshrat's DP's tomorrow. I'm not a very experienced user on UAXP, but maybe else with some more experience and skills in writing tutorial, could start a topic on the right combination (and order of installation) of these four great programs: - NLite - RyanVM cab-hotfixes - Bâshrat Driverpacks - WPI I'll report back tomorrow (or saturday) on how my VMWare-installation responded. *EDIT* Tried to install the image, but didn't get far: got an error message that winnt.sif in line 95 was missing something. I'l try again tomorrow, only with Bâshrat Driverpacks (mass-storage ecxcluded)

I'm almost afraid to say it, but I've tested method 2 twice today in VMWare, and both times, everything worked out perfectly. My second install even had RyanVM and WPI incorporated and some NLite tweaks. I made the ISO with Nlite. I've used all the latest driverpacks and basepack and did not get any errors... I'll test the ISO on my laptop tomorrow, hopefully it'll work on that one too. Bâshrat, keep up the good work... you're getting nearer to perfection !

Hi Bâshrat, Just tried the 5.02.27 (and all updated driverpacks) with method 2 and everything seemed to go well. However, when I tried to install the iso in VMWare, at the first reboot after t-0, the familiar windows screen shows up, after a second followed by a BSOD. It keeps coming back and it soesn't matter whether I try safe bootmode or not. I'll try to find out more on this error, but maybe you have some ideas on it ? Moe

Bâshrat, First of all, my sincere apologies if my messages may have looked disrespectful. I very much respect you for the effort you are making and the support you are giving. I will test my UAXPDVD in the future more carefully..... I did test an integration tonight with just the driverpacks (so without RyanVM teherefore), but alas, I still get the errormessage in windows setup that th txtsetup.oem is missing. I've used the 5.02.6 basepack with the updated run_me.cmd (you've posted in this forum). My method of installation was method 2. I haven't seen this error reported with the 5.02.6 release, so I'm wondering whether there have been succesfull driverpacks installation out there, using the 5.02.6 basepack ? Again, keep up the good work. My respect for it goes out to you ! Moe

Just tried a fresh install using the 5.02.6 basepack, the most recent driverpacks and the updated run_me.cmd. Using method 2... In VMware, I get a setup error that txtsetup.oem is missing and the setup halts. Am I doing something wrong or is there still a bug ? BTW, I also integrated RyanVM's CAB (1.05) in this install, could this have something to do with it ?

I'll answer my own question; the mass-storage driver-pack isn't ready yet. Just downloaded the 5.02.6 driverpack and the mass-storage driverpack and installed all of the driverpacks using method 2. There's still no aecd6280.sys in my I386 folder, so I didn't bother trying to install this UAXPCD.... it'll most probably stop on me during setup, because windows setup won't be able to find some device drivers that are part of the modified txtsetup.inf. This time I installed the driverpacks without installing RyanVM's cab's, so now I know for sure this problem is Driverpack-related. Pitty, because to me the mass-storage drivers are essential (since I use the UAXPCD created to install on a couple of pc's that have RAID-controllers)

Bâshrat, Do you mean it's safe to install all driverpacks now, using the 5.02.6 basepack ? Also the mass-storage driverpack ? I've tried installing yesterday with the 5.02.5 base and leaving out the mass-storage driverpack, but the DVD I burned for it gave me a windows-setup error because it reported aec6280.sys missing (as I mentioned earlier, I don't know if this problem had something to do with the driverpacks, possibly it has something to do with the combination of integrating your driverpacks and RyanVM's cabfiles). Please confirm that according to your knowledge, it's safe to use the 5.02.6 basepack in conjunction with all (also the mass-storage) driverpacks... I generally use method 2 for integration. Furthermore, as I also use WPI on my UAXPCD, I'm looking for a confirmation from you that it is safe to transfer the control panel command from GuiRunOnce in winnt.sif, to the RunOnceEx.cmd..... WPI is started from my RunOnceEx.cmd and I've read somewhere that it is not wise to use both methods (GuiRunOnce and RunOnceEx.cmd) simultaneously.... Again, my thanks and appreciation for your efforts and a job well done !

I'm not sure whether it's a bug or I did something wrong, but after integrating your driverpack, RyanVM's CAB (1.05) and making an iso, I get the windows setup error that 'aec6280.sys' is not found and setup stops. I've looked into my I386 folder, and indeed, there's no aec6280.sys (or any aec*.sys for that matter). I used the latest driverpack (.5) and all of your driverpacks, except for the mass-storage driverpack (as you report there are still problems with that one). Any idea ? If it has something to do with the RyanVM-package (in applied the changes in the txtsetup.tif and dosnet.tif according to RyanVM's instructions and than ran your driverpack-batchfiles), can you tell me which is the right order: RyanVM-Bâshrat or Bâshrat-RyanVM Keep up the good work ! Moe

Hi, Thanks for sharing your work with us. As a newbie to unattended installs, I've been reading up on the different methods and possibilities. I'm not a programmer though, nor a very technical computer user. Although I understand you probably want to spend your time on programming, I'd still like to ask you if you could help me out with some more detailed instructions on how to use your program. Maybe an example or a (excuse the use of dutch language, since I don't know the english word for it:) stappenplan can also enlighten the less-experienced user ? If you would be so kind to post an example, maybe you can come up with an example that uses the driverpacks by Bashrat: they seem to include all possible drivers and if you can explain where to copy them and then how to use you program, I would be very grateful. Anyhow, again my thanks for sharing your work and thoughts. It's sharing of work and thoughts that will keep the world turning !

I have the same question / problem. I haven't tried a (virtual) install either, but by analyzing the .cmd files I too suspect something will go wrong. I use the Driverpacks available: (WLan, Lan, Sound and Massstorage) and the first three of them are of the 5.1 version, while the Masstorage is version 4.1. The 5.1 version all unpack to the DP directory, the 4.1 version still unpacks to the Drivers directory. According to its author, the setdeviceptah.exe accepst only one parameter and therefore only one directory. It does scan all subfolders, but it cannot scan both c:\dp as well as c:\drivers. So therefore, I have the same question as you do: is it correct that the driverpacks extract to 2 directories instead of 1 (either DP or DRIVERS) ? Moe

Hello to you all, First of all ofcourse, a very happy new year to all. May it be a year of progress, hapiness and good health ! Secondly, and more down to earth , a question maybe some of you can answer. I've tried making an unattended CD from the Retestrak Unattended DVD (XP-SP2) and have put my own favorite programs in the RunOnceEx.cmd. I've made an image of this with both Nlite 0.99.5b4 as well as with XPcreate. On every install I try out in VMWare, the setup hangs/loops at T-19, when installing start menu items. It is right at the end of the progress bar of the start menu items, when the install hangs (it seems to go in a loop, constantly trying to read from the image). Can anyone tell me what happens in the install at T-19 ? Where should I start looking for solutions to this problem ? Any help will be greatly appreciated, since I don't have a clue what went wrong or where I should start looking. The lofgiles from VMWare don't help me very much, since I have no experience with them and don't really understand if they contain usable information. I've already asked around at the NLite-forum, alas with no luck yet (NliteForum on T-19 problem) Greetings, Moe