Siginet

I'm such a newbie.

Wow... I never thought to disable the sound in the bios! That is a good idea! I think I'll add realtek drivers back to my soundpack now. Thanks for that tip avis!

Seems to have worked flawlessly for me so far. Method2 RunOnceEx kTd No

Not sure what the 10.3 rule is. lol! I know you will be able to fix it better than I did... cause to be honest... I haven't really a clue as to what to do. I just know that when I made those edits my install went well.

Here is a fix for DriverPack V5075 All you need to do is: 1. Extract this i_a_nvmissing.zip file into your i386 directory (or your boot directory). 2. Then edit txtsetup.sif with the entries I placed below. In the [sourceDisksFiles] section add these entries. i_nvraid.sys = 1,,,,,,4_,4,1,,,1,4 a_nvraid.sys = 1,,,,,,4_,4,1,,,1,4 i_nvatabus.sys = 1,,,,,,4_,4,1,,,1,4 a_nvatabus.sys = 1,,,,,,4_,4,1,,,1,4 i_nvata.sys = 1,,,,,,4_,4,1,,,1,4 a_nvata.sys = 1,,,,,,4_,4,1,,,1,4 I am not sure if this is really a fix or not. But it worked for me and it allowed me to do a complete install with a multibootdvd. @Bashrat please correct me if I am wrong here. ← OOps... sorry. Forgot to mention... You need to go back into txtsetup.sif and change: i_nvabus = i_nvabus.sys,4 a_nvabus = a_nvabus.sys,4 to: i_nvatabus = i_nvatabus.sys,4 a_nvatabus = a_nvatabus.sys,4

Here is a fix for DriverPack V5075 All you need to do is: 1. Extract this i_a_nvmissing.zip file into your i386 directory (or your boot directory). 2. Then edit txtsetup.sif with the entries I placed below. In the [sourceDisksFiles] section add these entries. i_nvraid.sys = 1,,,,,,4_,4,1,,,1,4 a_nvraid.sys = 1,,,,,,4_,4,1,,,1,4 i_nvatabus.sys = 1,,,,,,4_,4,1,,,1,4 a_nvatabus.sys = 1,,,,,,4_,4,1,,,1,4 i_nvata.sys = 1,,,,,,4_,4,1,,,1,4 a_nvata.sys = 1,,,,,,4_,4,1,,,1,4 I am not sure if this is really a fix or not. But it worked for me and it allowed me to do a complete install with a multibootdvd. @Bashrat please correct me if I am wrong here.

About how much space have you saved (in your experiance) from doing this? Is it worth the hassle? If so... I may make a tool to do this.

I wasn't aware that you could install more than one file in a directory with winrar. BTW... how would it be able to do multiple switches? Also... the point of the program is to install multiple exe's which have the same switches. Alphabetically.

the output from BTS contains not valuable infos (devices using Windows OS built-in drivers) and sections headers. Could you enhance the GUI of your tool with a selection (drop down list?): PCI Devices: PCI\VEN_ USB Devices: USB\VID_ All Devices: PCI\VEN_ + USB\VID_ <{POST_SNAPBACK}> Good idea. As soon as I get some spare time I will work on changing it.

Nice This will definatly be a good DP to have.

Correct. This tool is made for exe's that have the same parameters. It's main use in my opinion would be for hotfixes... or exe's which have no parameters.(Like custom made autoit install scripts.) If you have a lot of exe's with different parameters this tool would not be of any use for you. It is just made to simplify things when it comes to installing many exe's with the same parameters. Thanks for the feedback.

Sorry I think I posted this in the wrong forum. Can a moderator please move this to Application Installs forum. Thanks.

SetDevicePath.exe can be used from the command line. I simply made a gui to make it easy for others.

Install It All This tool that I made makes it easy to install multiple exe files from within the same directory. Basically all you have to do is caLL the tool from a script file with 2 parameters. 1st Parameter is the path to the directory you want installed and the 2nd Parameter is the switches you want to use. For instance... let's say you have a directory called: HOTFIXES. Inside this directory you have downloaded a bunch of hotfixes you want to autoinstall to your system. (Make sure all of the hotfixes use the same switches ) You would put this in your script: d:\InstallItAll.exe "d:\HOTFIXES" "/q /n /z" Once this has been executed all of the hotfixes will be installed that are in that folder. You can use this tool for any type of exe file. For instance if you have a bunch of exe files you've made with autoit (which do not need switches) you would just put the path for parameter 1 and "" for parameter 2. You could even use it to integrate multiple hotfixes into your XP disk by using "/integrate /quiet" for parameter 2. Let me know how well it works for you. I may make the tool better down the road. You can download it HERE

I agree 100% with RogueSpear on this one. Make sure the entries have been placed in txtsetup.sif when integrating the RVMPack. I got the same error a long time ago when I forgot to edit the txtsetup.sif file.

I have the same problem.

Use bartPE. Boot into BartPE and click on the file winnt32.exe in the i386 folder you put on your hard drive. Or... try a dos NTFS boot disk.

Good news I wonder why it creates an error?

@Bashrat... I like how you worded that. Sounds so nice... but really says a lot! LOL! I like the italics too. I don't think I could have been so nice. I would speak my mind right now... but then I'd probably get banned for vulger language. This guy is obviously not a professional. Also he obviously doesn't know how much work comes into making this project. Professional my A$$! LOL!

Sorry forgot to answer your question... Actually this is a DriverPack question. But it sounds like you are not integrating the Mass Storage pack. If you aren't than that error is normal... and it actually isn't an error it is just reminding you it is not integrating the Mass Storage drivers.

@Telenut... do you get the same error without using the DPs and using NLite? I know that there are limitations with NLite and the DPs.

OK... here's a clue as to what I have planned for v2.0 (Which I have allready tested writeing code for.) I plan for v2.0 to not only have support for Windows XP. It will have tabs at the top of the main window. Tabs like: "Windows XP", "Windows 2003", "Windows 2000", "Bart PE" and so on and so fourth. Each specific tab will open a portion of the gui that will be specific to each tab. So version 1.0 will only be for "Windows XP" but v2.0 will be very simular... except it will support a lot more OSes. If anyone finds out a way to multiboot XP64 then I will add support for it as well... but as of now XP64 support is not possible. BTW I think I found a bug... It looks like in the boot menu when you select Windows XP Home The next section of the menu says "Windows XP Professional - Retail" etc... It's just a minor bug... but I will fix it in the next release.

BartPE is possible. I use it on my Multiboot disk. But you would have to create it manually the first time. Just follow the tutorial Here. Once you have finished createing your BPE1 folder... make sure to backup the filse elsewhere. You will need to backup the \BPE1 folder from the root of your disk, the \BPE1.DAT file on the root, and The \ROOT\BPE1 folder. Put it all somewhere in a directory called \ExtraRoot. Later if you make another boot disk you can just point to the "ExtraRoot" folder and your bart pack will get copied over as well. Oh and make sure you edit the cdshell.ini file in the \BOOT folder on the disk. You can find info on how to edit the file here. For now that is how you would do it. But later a plugin will probably be made.

I reccommend either Counterspy + Adaware SE. Or MS Antispy + Adaware SE. Or for enterprise (As stated earlier.) Counterspy Enterprise Edition. Works very well!

Or buy an old junk computer for 100$ that has 98 installed allready. lol Looks like your answer has allready been given. Good luck. BTW... is there a specific reason you choose 98 over XP?