Bâshrat the Sneaky

hehe gamehead200, no problem Since how long are you a happy Mac user? Right after seeing the commercial, I guess?

I know, it also works with txtsetup.sif editing only, but only when you're installing from CD/DVD. NOT when you're installing with winnt.exe/winnt32.exe. That's why I have to add the entries to dosnet.inf. And to be complete, they also have to be added to drvindex.inf. That's it!

@grisensko: please test as many as you can... Check the Success/problemdevices topic in the DriverPacks General Discussion Forum for the currently known list. EDIT: and you said your G550 wasn't installed? That driver is included in DP Graphics B, did you slipstream that one too?

No, this folder isn't used by nLite or anything else afaik. And why you would ever want something from %tmp%\subfolder? Because I used it as a temporary folder...

errr... I told you it was stickied Here is the link

Method 1 takes ~260 MB, so that's quite possible yes. Why not use method 2 in your case?

You're using it for your work then? And I don't know if it works... It's been reported that it does NOT work, which is the one and only reason that I added viaSraid.sys in this release... It's very possible that it's a driver modified by ASUS and will therefor not work on any other mobo... So if any ASUS A8N SLI user is reading this post, please CONTACT me. I know how we could solve this... But I can't do it without you... (if you're not yet registered here at MSFN.org, please contact me: contact [at] BTSunattended.net ) EDIT: oh about that hardware with exclamation marks: I think I misunderstood you there... I downloaded all drivers for that VIA mobo Well, I'll do it for the SiS mobo then Last question: was the sound driver on that VIA mobo correctly installed?

OK, at least you're an active user, so I know we can cooperate to get this fixed . First of all: please tell me WHICH EXACT soundcard you have. An Audigy 2 or a ZS?

Could you please send me a link to those drivers? Or mail them to me please. (the .zip files you downloaded from the official site if possible) If you send me either of both, I'll add them.

That second one is SUBLIME I wish there was a larger version of it, and I'd et it immediately as my wallpaper

Indeed offline again.. Should be online again tonight...

**** mate, don't scream, no need to do that... Then I really truly don't know... I wish I could check your disc, to find it out myself... sorry mate...

I really need you to tell me WHICH hardware shows these exclamation marks. I'm downloading all drivers for your motherboard now. EDIT: all your drivers have been downloaded. EDIT2: CRAP! Probably your motherboards RAID controller uses the hwid that I've switched to the viasraid driver, to get it working on for example the ASUS A8N. But YOUR motherboard has the SAME hwid, but is delivered with the viamraid driver! Crap crap crap.... Please do this as a test: open your txtsetup.sif and search the line PCI\VEN_1106&DEV_3149= "viasraid" to PCI\VEN_1106&DEV_3149= "viamraid" and let me know!

Probably this is because they will only use it for their own services and for a limited number of 3rd party services. The .Net passport has not become as popular as Microsoft had hoped for...

Maybe with external hdds or so... But I've never removed it that way, without any problems at all.

I somehow came accross the o so famous Ellen Feiss movie today. I though why not post it? Well here it is... http://spherule.com/media/video/switch/ellen_feiss.mov I've watched it more than 10 times today, rolling on the floor each time B) Enjoy

If you use a pendrive/USB stick/whatever name under Windows XP, you don't even have to use the 'Save hardware remove wizard', or whatever it was named like. If you don't use it, you won't get any error

@eagle00789: please check this topic for the solution. I'm working on it this very moment.

Toolman, I think I've found the solution Please add this to your winnt.sif: [Data] MsDosInitiated=No if STILL no success, try to add this: [Data] UnattendedInstall=Yes MSDosInitiated=No AutoPartition=1 I'll be trying WITHOUT these and see if I get the same error. EDIT: fixed typo's EDIT2: I've successfully reproduced this error by completely removing the [Data] section. Now I'll test which entry/entries are needed to avoid it. EDIT3: the first suggested fix did the trick: you'll have to add [Data] MsDosInitiated=No Or you can wait for DPs BASE V5.04.5 (which will be released tonight)

@mark49: 100 indicates an updated file, not SP2.cab. 100 was also used for SP1. 100 is also used for all pre-SP3 hotfixes in RyanVMs updatepack, and to they go looking for SP3?

@eagle00789: pfffff I thought we were finally getting it stable... crap crap crap You're NOT using a Multi-Boot DVD, are you? Which DriverPacks are you using? I really thought we got rid of this error. After searching I found really fast a possible solution. Therefor I ask this: did you have a winnt.sif file before you applied my DriverPacks? No matter what the answer is, please attach your winnt.sif!

Yes, I see that reference. But does that mean it's entered by me? Without a doubt this is entered by nLite or RyanVMs updatepack. I'm 200% sure of that. Please put a semicolon before it and try again. (as sort of a bad work-around)

As you said yourself, the file is created if it doesn't exist yet. It's required for the installation of the control panels. And it has NEVER WORKED for you??? Please tell me these: -do you get that error in VMware too? -your hardware specs -is it a clean UWXPCD? I mean are there any other things slipstreamed?

Doing the comparison now...

Err... it IS working... on all languages reported so far. You can read my bath files thirty times if you want, you will NEVER find in ANY file a reference to SP2.cab. My guess is that you applied RyanVMs updatepack or nLite incorrectly. And... that ... is exactly what I'm doing: only I did not collect that info from all users, I just wrote everything myself and I'm fixing all bugs I or any user finds. So far with success. Most of errors like these aren't caused by my DriverPacks, but by users that made mistakes (not always mistakes in the DPs part, but quite often in other parts). P.S.: the files you attached seemed to be OK.