Nakatomi2010

Just a small request for the next version or so... The ability to configure WPI to install a pre-determined set of stuff without popping up would be nice... Sort of like populating the stuff on it's own... An alternative to program RunOnceEx on your own... This would allow me to do what I want with the multiboot thing I made a post about...

Let's take a different approach then... One which may be slightly more convenient... I'm running under the assumption that the WPI environment is directly related to the set of scripts within the WPI directory, meaning that theoretically I can have different instances called up by different commands within different WINNT.sif files, and that the applications they trigger are a result of said scripts, and they're installed from a unified directory in one location on the CD.. That being said, it may actual be wiser to use the above method since the programs would only need to be on the CD in one spot, and never referenced to again by the CDImage software while it indexes things... That being said, if it possible to have WPI automatically trigger a predetermined set of files without having to have it open, or would it still have to open for a split second? Again, assuming what I've said makes sense...

The driverpack, in my opinion, is more geared towards people who come accross several computers and need to have Windows isntalled without spending time finding drivers.. I, for example, created a Windows XP CD for the store I work at, and when a customer asks for a format and reload I use the CD, cuts down on time because I don't have to go driver huning, and it comes with a bunch of the updates on it already... If you're trying to create a CD for a set of systems that you KNOW the components in, just make your own pack using the OEMPNPDriversPath thingamy... It's what I use when I create a restore CD for computers...

I've thought about doing this myself... Though it's a massive undertaking... You can go to Planetamd64.com to get a good chunk of drivers though... Hard to find modem drivers are there....

I'm technically trying to use the RunOnceEx method for one seup, where essentially the RunOnceEx is used to install software, not WPI. On a second install it would call up WPI and not he predetermined software list on the RunOnceEx that the other method uses... Assuming that cleasr it up abit...

Essentially what I'm doing is creating a multiboot DVD which will allow me to install several flavors of Windows in different ways, for example, I've got one which will install Windows without asking for anything but a CD-Key, even uses the driver packs, and another one which will ask for input but uses the driver pac, and a third option which is just vanilla XP which you can use to perform a repair install if need be.. Well ideally what I'm after is a complete unattended, which I've already accomplish, a mostly unattended, which is what this post is inquiring about, and a fully attended one... What I'm trying to do mis see if it's possible to have WPI run independantly from other stuff, so for example... Unattended will install all the software and drivers automatically, without asking, hence I use the RunOnceEx method. The Mostly unattended install I want to popup and ask "What software do you want mee to install?" and use the driver packs... Thing is, is that since they both run out of the RunOnceEx method, I was wondering if ther's anyway to trigger different RunOnceEx from the same source directoy... Assuming the above makes any sense what so ever... Is it possible, or should I just use one method or the other?

I've tried double clicking it, an the RunOnceEx method, I only got sucess by running through the svcpack.inf file.... Typically spits back an error about something not being right and there not a browser for help....

Almost no fuss, only way I get that thing to work is by adding it to the svcpack section, and even then I think it's still causing issues...

So, I've got an Asus A8N-E and an Asus A8V-E and I'm making an unattended install CD for either of them, I get all the drivers loaded just fine, but when I get Windows fully installed it says Unknown Deivce in the device manager, so I take the Asus Motherboard CD, stick it in the machine and it goes away, I don't even tell it to install the driver, simply the act of having the machine run the auto run makes the unknown device go away... What's up? Where's the driver hiding at?

So I'm making an unattended CD for someone but don't know their CD key, so when it comes up to the CD portion of the unattended install it throws a "Hey, there's missing iniformation" error up, you hit ok and then type in the key.. Is there a way to have this message not pop up?

My apologies... I'm assuming you recommend installing it after Windows is installed, is there a method to add it using the RunOnceEx method, have it silently install in the background? (You may have said these things often, but I haven't seen multiple install methods listed only an nLite one, so I made the assumption from there.......)

I've added this back to a CD I've been making and when I run the install all the way through from scratch and it installs the traditional Windows XP theme, but I get all the new stuff except the startbar is the cliassic XP one, and I'm running under the assumption that the starbar should look more like the MCE start bar, which is does not... Or am I only going to get tat startbar using MCE 2005? Basing my complaints on the before and after shots in the 2nd sticky... I should be seeing a rainy version of Bliss and a MCR 2005 class start bar.. Which I think is sexy...

Does this driver pack function properly with Windows XP Media Center Edition?

Just so people know... I used the nvraid.sys, nvata.sys and nvchlt.sys (Or whatever they're called) from 6.65 and used them in place of the current drivers and it works properly... Just copy the files into the i386 directory... And for Multiboot into the boot directories for each OS...

I believe the nVidia drivers included in the driver pack are a little too old, I am basing this off of the fact that my CD uses drivers that appear to be larger in size, so it mmay be something wrong with their older drivers... Wont know for sure until tomorrow though, I accidentally messed up my DVD so I have to semi recontruct it....

G'day, fan-diddly-ann-dan-tastic work on these driver packs... Major kudos... I'm having issues with the nForce chipset mass storage drivers as well.. My goal has been to create a single DVD I can use to reinstall Windows XP on cusotmer units (Re brand them at the same too if I do a format/reload) and these driver packs are a huge bonus to making life easy... Funny thing is though, the computer I'm guinea pigging these on I've created a restore CD (We're selling a computer that has an Asus A8N-E, AMD A64 3200+, and 2 36.7GB Raptors in a stripped array) and while the CD I've made works like a charm when I use yours it'll see the drive as a single drive in text setup mode, but when it moves on to the point where it's going to actually run Windows for the first time (Just after the GUI setup) it going into a BSOD then reboots... I'll grab the error in a few.... I compared the NVRAID.sys stuff with the CD I made and everything looks the same, so I honestly don't know what it could be... I'm probably going to try a couple of things later since I have a functional instance I can recycle... Just thought I'd say I have it working, just not through your driver packs... Edit: The BSOD was totally useless... I think there may be some files that are inadvertantly missing from the OEMPMP directory for the nVidia drivers, though I wont be able to verify this until tomorrow... The fact that it works during the text setup tells me the textsetup configuration if fine, and when it craps out during the loading of Windows I think its related to the fact that the actual drivers which drive it in Windows are missing... Either way, I despise nVidia and vow never to intentionally buy any of their products again, unless its an insanelygood deal like last time (A8N-E, 3200+, and OEM copy of Windows XP x64 Edition for $250)

I know, if anything all I've done is proven that it can be done, so it's not impossible, but at the same time, as a temporary work around, and assuming you're not doing more than one 64-bit OS, then you're all good....

Does cheating count? Because if it does then I found a bastardized way to add it to the multiboot DVD... It was an EXTREMELY simple solution and appears to work so far, tthough it is very much limited in how it operates... BUT, assuming it works, scripters out there might be able to do something.... But, if cheating doesn't count..... So far its copying files to the hard drive without any problems.... Edit: Reached the GUI stage of the install.... Alright, it looks like its going to be a success on the install, so I'm giong to say what I did... Just remember, it's cheating, but it seems to have worked..... Extract the boot sector, and rename it to whatever it needs to be, in my case, x64.dat, don't bother hex editing it, remember, we're cheating.... Have nlite make the modifications you want to your CD so it'll install how you want it to, then copy everything, minus the usual setup.exe, autorun.inf, etc etc to the root of you AIO-DVD/CD your directory structure will be.... D:\AIO-DVD\AMD64\ D:\AIO-DVD\I386\ D:\AIO-DVD\XPHO\ D:\AIO-DVD\BLAH\ D:\AIO-DVD\ETC, ETC\ And there you go.... Now tell what ever program you use to script the install to use X64.dat, and it'll initiate the setup from the root.... Obviously this is useless to people who want to have unattended and attended install versions (Like me), BUT it's a start to get us to get X64 Edition ONTO the DVD.... It's currently installing my software sute on my end, so I'm going to call this a mild success and a half-assed work around.... Final Edit: It worked, the system is now running X64 edition run from an AIO-DVD, obviously it was to be expected, but its a start... A very, very small one....

Hey, I've been tinkering with multi-boot DVD for awhile now and finally get it fine tuned to what I want it to be, but I've having some trouble with the mass storage drivers... I used Bashrat's driver packs, and used his multiboot tool, but I don't know if I even completely grasp it... I ran the batch that takes all the file and puts them in a directory on C:, then I copy those files into the BT's, then I copy the txtsetup.sif file into that directory too, everything works fine in the text setup, but once I hit the section after te text setup, where it first initializes Windows it blue screens then reboots, the BSOD says something about 0x00000024, but I maintain it something witht he drivers, ause if I copy over the entire i386 directory it works fne... What am I missing here? I'm running striped RAID array accross 2 Raptors on an A8N-E motherboard

I've again been following the flyakite site and when it seys to copy over te BT's I copy it over, but when I actally try to install Windows I find I need to add the i386 directory to it in order for it to work right.... This normal? Or is this partly related to using SP1 BT files with SP2 install... Cause if that's true then I've got ALOT of CD's I'm going to need to make to make this DVD to work.... (Thank heavens for CD-RW's...

Turned out to be the processor.... I hd a spare 3000+ on hand, so I swapped em' out, then swapped em' again, worked like a charm after that...

So, I made a Multi-Boot DVD, (Mostly comprised of Windows XP) and I decided to add a few extra fetures, so I added the Linux NT Password changer utility, grabbed the .IMG file and did a /memdisk \ntpass.img in order to start the thing from my CD shell menu... Well, it didn't like it and stopped responding for a bit, so I hit reset and now I get nothing... At all... The system stopped working altogether now and I'm a bit concerned.... The hard drives start, the CD drives start, everything starts, but there's no POST Beep, and the monitor is never triggered.... What happened? Its an Athlon 64 3200+, in an A8N-E motherboard with 1GB of RAM, and a GeForce 6200TC PCI-E...... Have a totaly fragged the system? I've tried removing the CMOS battery and resetting it via the jumers... Nothing....

I'm tryingg to create 3 installs sequences, 1) Unattended with Drivers and Branding, 2) Attended with drivers, no branding, and 3) Attended, no drivers, no branding... 1 and 3 work fine, but I want 2 to be able to load, show me the EULA in text mode and offer me to perform a repair install, but it goes straight to the partition choices, all the WINNT.SIF file has fo the is the OEMPNPDriverspath= section and the ignore drivers signing policy, and what not.... Can I be more specific and tell it "Show the option to perform a repair install" or no...

I've been following the guide at http://flyakite.msfnhosting.com/ and I've reached a point of stumping... I'm trying to make a multiboot CD with Windows XP Home and Professional, I can get it to install in a breeze, but I can't get the different "versions" of each running, for example... I want one install to be a traditional one with no drivers, no branding and fully attended, a second one with all drivers, and branding but attented, and a third one which is completely unattended with drivers and branding... I can get the unattended with all drivers and branding working, and the attended with no drivers and no branding, but I'm having difficulty with the attended with drivers and branding, it does the same as completely unattended, I've got the thing set up properly, pro2 points to pro2 etc etc, I'm runing under the assumption this is a problem with the WINNT.sif file... I've also copied the contents of the i386 folder to the PRO1/HOM1/etc directory because that was the only way I could get the drivers to work right... I'm using a service pack 2 versions of everything, was just wondering how far off the guide some people had to go in order to get this thing working right..... And how to fix the WINNT.sif thing...

I did searches and they all pretty much came up blank, reall yon passing references on integrating drivers.... I would assume that adding drivers is as simple as the bashrat method, however since the setup is using the winnt.sif from the PRO1 directory rather than the setup\xp\professional directory, the driver path changes, what command line should I be using to change the path Windows looks for the files in? I'd assume that for every entry that's along the lines of "D\C\AT" would need to be changed to "$cdrom$\setup\xp\professional\$OEM$\D\C\AT, and that every driver entry within would need to be changed to accomodate this, is there an automated file which'll do this for me, or I'm pretty much going to have to do it? I'm also running under the assumption that the PRO1 folder is a rudimentry I386 directory, which in theory means that I could place the contents of the I386 directory in there, and have a duplicate within the 'setup\xp\profressional' directory and it should work finee, but then I'm also looking at a pretty major loss in storage space.... I'm essentially trying to create two installs for Professional and Home Edition on one DVD, I'm labaling em' Chocolate and Vanilla, essentially one's a branded version, while the other is a straight install, though for each one I want the driver pack integrated so I don't have to worry about drivers.... An explenation would be nice, I looked through the guide, but it doesn't explain how to integrate drivers, the unattended one does, but I'm trying to use the bashrat version so that I don't have to pull all the drivers myself, nor add the lines of code... Thanks....