Bâshrat the Sneaky

Oh, shame on me ... not I simply removed ALL IAA, both RAID and non-RAID till further notice. I'm really thinking of adding the txtsetup.oem method, as this driver certainly works this way! (Intel gives these instructions, so...) Bâshrat the Sneaky

RAID won't work on a single disk, so no fear! Bâshrat the Sneaky

I think I'll add this method in the next release of DriverPack MassStorage. It seems several big companies give the advice to use this method. The point is: I should be able to send you lots of new entries! Bâshrat the Sneaky

I'd like to know this, because I'm really thinking of adding, or maybe even switching to the txtsetup.oem method for DriverPack MassStorage. Why? Because I've got the feeling that it might be alot of work to add all drivers, but that they will ALL work flawless! We'll see about this last one... Bâshrat the Sneaky

could you please post what have you changed? Here you go: PCI\VEN_1095&DEV_3114&SUBSYS_61141095&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_288510F1&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_90181695&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_F642270F&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_100415BD&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_12501462&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_13101462&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_15601462&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_16101462&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_B0031458&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1B711019&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_61141071&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_003515D4&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1025147B&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1001147B&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_130A147B&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1C0A147B&CC_0104 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_81361043&CC_0104 = "si3114r" EDIT: before these changes there were no "&CC_0104" strings at the end. Bâshrat the Sneaky

You just have to extract the driver, put all the files and folders in $OEM$\$1\Drivers\nvidia, and point to there in your winnt.sif file! You can find detailed info in the official guide! Bâshrat the Sneaky

I can only say this: WOW! SUPERB work you've done there! Still I have a couple of questions: -If I well understood your (quite huge ) post, RASOR doesn't look into the txtsetup.oem files for the necessary winnt.sif entries, but they're stored inside the program itself? -Could you please add nVRAID support ASAP? As I can't get it to work for everyone with my DriverPack (but it does work for some... :s ) Keep on the good work! Bâshrat the Sneaky

Yes, it uses the Intel Application Accelerator, which I let out of this DriverPack, because it was always running in DMA mode. I found the reason: it has two other .sys files that have to be in use, but they don't have a standard PCI\* entry, so it will be something for one of the next releases. iSmart told me that they are already included in Windows XP, so that shouldn't be much of a problem! Bâshrat the Sneaky

OK, great news! And now I know what to say every time they ask me this question Bâshrat the Sneaky

Are you guys SURE you ran the patch.cmd batch file (successfully)? Bâshrat the Sneaky

Where do you live, BetaSith? I think Belgium? Bâshrat the Sneaky

Or import them with cmdlines.txt at T-12, so ALL users that will be made will inherit those regtweaks! Bâshrat the Sneaky

Well, you must do *something* wrong, as it works for everyone else. Hopefully tomorrow, if not within a few days, I will release a new, greatly simplified version. Method 1 will exist of only 5 steps, method 2 of 3 steps! If you still can't get it to work then, I'll contact you by IM. Bâshrat the Sneaky

You've already posted the exact same thing in another topic, please don't make double posts! Bâshrat the Sneaky

It's a multiboot DVD problem You might want to add the dosnet.inf entries, don't know if that helps, they will be included again in the new version. And maybe it helps to use M2 in your case... Bâshrat the Sneaky

Well, your problem is painfully simple, that you will get mad at windows setup Please remove the ";" at the end of OemPnPDriversPath: ...Drivers\blahblah;Drivers\blahblahagain" That should do the trick Bâshrat the Sneaky

OK Please post the result in this topic! Bâshrat the Sneaky

Well it IS like that, a cat file points to the fact that it's signed... So I don't understand why Windows says it isn't signed... I'll redownload the Marvell driver and add it again... Bâshrat the Sneaky

@a06lp: change the settings of Windows Update to 'Catalog' view (or something alike), then you can select the updates you want and choose a folder to which you want to download @nemesis5: RyanVM's Update Pack is designed to work with win xp English... So I'm afraid it won't work for the German windows versions... Bâshrat the Sneaky

www.soundblaster.com Bâshrat the Sneaky

Firefox, without a doubt! Bâshrat the Sneaky

B) LOL

You can find the info you need for the installshield method in this topic: http://www.msfn.org/board/index.php?showtopic=27750 Bâshrat the Sneaky

It's because the driver is cached/back-upped in the Driver.cab file in the i386 folder. Windows detects the hardware, tries to use the driver and notices it isn't the correct size, so it gets it from the Driver.cab file. I don't know exactly how to disable SFC during setup, but I'm sure people in the Unattended Windows subforum will help you out! Bâshrat the Sneaky

Hmmm... this is strange... For example I've seen a D-Link WLAN USB adapter working just fine, while plugged in during Windows setup. Bâshrat the Sneaky