Bâshrat the Sneaky

Please post the exact hardware if possible! EDIT: I already collected the info of the Dell GX280. But what about that Maxdata PC its specs?

Magnificent I will definetely include this! I hadn't even thought of this Thanks! Bâshrat the Sneaky has added a bookmark

It's an undocumented switch. Thats why... Thanks to the 'insiders' we know it. What it exactly does isn't documented anywhere... Just use it

I noticed. This means I'll include the VIA AGP drivers from now on. But they will only be needed for those new hwIDs. Won't be a big update... Rather ridiculous...

Remove those Conexant drivers. Probably you can do that with nLite.

That's the question... I don't know anymore... Just try...

Sorry, I tend to use the official drivers only.

Please tell me which EXACT hardware worked. I can look it up too, but if everyone could just post his hardware, I wouldn't lose time by looking it up... If you give me a download link to your driver, I'll add it. EDIT: I looked it up after all... You're using a MSI K8N Diamond. I've downloaded the driver for that audio codec.

The problem is that I make changes every time. That means I'm not sure if it will get working again or not. Every time I *think* I got the problem solved, because I made a theoretical error previously, or because one or more users report it to work this or that way. But then another problem appears... There've been reports that the NVRAID controller works just fine. However I got one negative report about it. Please note that there IS a success/failure list in the DriverPack General Discussion forum!!!!

I don't know for sure, but I noticed all so called 'busextenders' are using a 3. But in fact it shouldn't matter at all... However I prefer to keep it the way it originally is/was. I will fix it

Well, in fact you can run OemPnPDriversPath.cmd standalone, and you can change the path to your liking

Please check your i386 dir for those files... All I can say for now. If you don't use DP MassStorage, you won't get any of these errors

@muiz: affirmative @robnjay: I knew it @mark49: and how could that be useful? I'm not installing any hotfixes, so...??? @anonim1979: thanks, I'll fix it.

Amazing But can it be used DURING setup? I don't think so. As far as I understand, this is for in-Windows use. OK, you can install devices from there, but I don't know if the drivers will get installed correctly using this method? Anyway, superb work! I will definetely try out this one as soon as I can!

No, that's in the changelog (isn't it), I removed drvindex.inf patching because I doubt it has any effect... It just says which files are in the driver.cab file. But we use [ForceCopyDriverCabFiles], so it's useless to patch the drvindex.inf file... Did you get any errors?

Yes, of course!

ATI hwids are already included, but this is indeed a BUNCH more!

I'm afraid this isn't a complete solution: Too bad!

Oh, well you simply used the Omega drivers... nothing special about that. I'll keep on using the OFFICIAL drivers only. By the way... the difference in performance between the Catalysts ans the Omegas has become neglible!

Please post English only from now on. And ****... could you please attach your txtsetup.sif file then? We're getting there... I think it's a corrupted entry or something...

@robnjay: please compare that txtsetup.sif file with the unpatched one. @laura: I know... @mark49: isn't that exactly what I'm doing in V5.04.9??? @RogueSpear: nope, Windows isn't _completely_ loaded at that time. Impossible, afaik.

Thanks for that link. However, I knew about the 4096 characters limit. But I did *NOT* know about the 1024 characters limit when using winnt.exe... Thanks!

There's a space in your custome themefile. Change it to: [Shell] CustomDefaultThemeFile="%WinDir%\Resources\Themes\Royal Inspirat.msstyles" and it should work just fine.

Huh? I'll check if the filenames match!

@gilesw: you simply included the Omega .inf files and it worked??? Please clarify your post!