Bâshrat the Sneaky

Did you try this already?

InstallShield setups need the Windows Shell to be loaded! So you can't install them during setup, only when you're logged on to Windows. At least, that's how I understood you... Correct me if I'm wrong!

Did all you guys update all files? The /F switches were added 2 versions of Method_2_files ago!

I will entirely convert my DriverPack MassStorage to the txtsetup.oem method. (at least, probably) But even in that case the txtsetup.oem files will be merged into one huge txtsetup.oem! (I guess that won't be a problem?) But if you want these txtsetup.oems immediately, I'm afraid, you'll have to download the drivers manually and get them out of there. I don't have all of them on my harddisk myself! Because, as you prolly already know, RyanVM handed over this DriverPack to me, he started this one!

Hmm.... you're the first one to say this. But I have to admit, there are only a few people who have the external stuff as well... Someone has to be first..; I'm afraid this would be much too advanced, it would bring me too far to solve this. There can be sooo many causes for this. However, you could start with the following: use regsnap (or something similar) to make a snapshot of your registry when you're using the unattended drivers of my DP. After that, re-install Windows, and ONLY manually install the required drivers. Now take a snapshot of your registry again and compare them. Remove the irrelevant differences (like recent documents), and maybe (if you're lucky), you'll have the solution!

then why "...\base\boot\setup\..."???

So you're using a multiboot DVD.... I don't have any experience with that yet, so I'm afraid I don't know how to help you... You can try the method DevHead suggested!

Noticed those

Next time use CODE tags! Please specify WHEN it hangs. Also please remove this backslash and try again: OemPnPDriversPath="Drivers\002_graphics\" to OemPnPDriversPath="Drivers\002_graphics"

Did you already try this method? Gave this link to someone else and it did work for him!

Won't forget this one

Now this is a story! They should be ashamed... Didn't know it was THAT bad, thought it was 'only' a conflict... One and a half week to go untill I can start working on the DriverPacks again... To be honest, I can't wait to start on it

I was still using the nV system utility V1.01 LOL Thanks prathapml! EDIT: but it doesn't work... :s Error 1316.A at the end of the installation... Downloaded it already twice, let's go for a third time... EDIT2: Nope didn't help... Am I the only one having this problem? :s

@njay: it's $OEM$ @mpyr: never heard of this one before!!! Maybe the dir is copy protected? Try to verify that...

@DJ_Datte: Please download the nVidia PATA drivers from www.nvidia.com and compare them. I don't have time to look everything up atm! Sorry... @iSmart: I suppose you want me to add those? I'll do that in the next update.

If you really need to get it too work quick, no time for testing, then use a floppy... If you want to slipstream it, it will cost some time to verify everything. Please don't use capital letters in topicnames (forum rules!) and note that everyone here wants quick help!

Oh, I've read over that one, so you're upgrading from an older version of Windows (9x, Me, 2k) to XP? Well that has to cause problems.... Never tried that... Why would you want to do that? Just erase the partitions and recreate them... If you want to keep some files, just back them up to a CD-RW!

Thanks

Then you should try to find out what installer is being used for it, to determine which switches you can use to install those programs unattendedly. If you don't know how to find out which installer is being used, please look at the guide!

Seen this one before You did not, or not properly, run the RUN_ME_METHOD2_V*.cmd file. That's why your driver files haven't been compressed to the i386 folder, which is the reason of this error. I'd entirely redo Method 2, just to be sure.

Thanks

Of course it annoys me too! This is about the last real 'bug' in this DriverPack. But as I've said several times now, I don't have much time atm... I'm doing the best I can...

I guess you do know about the guide, Kyor? What's so special about these drivers?

Hmm... Unless you like to find the error, I'd recommend to use Method 1 untill this is fixed... I really have no clue. And at the moment no time...

This has indeed nothing to do with an unattended installation, but it does fit in with the Device Drivers I think... Did you overclock your setup? Because if the memory becomes instable due to too high overclocking, it's quite normal that such errors show up...