Bâshrat the Sneaky

Sorry muiz, but Siginet is right here. You should post in the DriverPacks BASE topic Please be kind for eachother!

It's a BIOS setting: Boot devices > First Boot Device > USB-drive (or something similar)

NEW FIX CHECK FIRST POST!!! Should fix everything...

What can I say? Only this: HUH? Your HWID is only listed for the SiI3112r (which works for both the Silicon Image 3112 SATALink and 3112R SATARAID)! So the ONLY CONCLUSION can be this: Windows Setup only checks the first part for the HWID... Or doesn't do it right. I'l let the ASH1205 controller use the same driver as the SiI3112r: that should work for both!

@RogueSpear: exactly what I was thinking. Currently there is not a single DriverPack that I would like to keep after the installation (for many LAN and certainly WLAN might be the exception). I'll include the option to choose DPs to be kept in one of the next versions.

@X-Savior: eh... the SATARAID drivers just work fine for the SATALINK devices too That's why I excluded the SATALINK drivers, when I included them it gave problems with RAID setups!

Use RapidShare!

Eh... you should be moving on to V5.05 V5.04.14 is no longer online

Why do you want to use the txtsetup.oem method? It works just fine when using the regular method Topic moved to Device Drivers.

OK then, I guess I can trust you In that case more files can be removed But I'd be glad if someone could confirm this with OTHER drivers?

Thanks, downloading them.

Yes, of course I've been planning that In fact I've already collected some drivers I'll release them when I got a decent amount of drivers. (now it's like 10 drivers )

WOW I would almost think we've degraded to the V5.04 times, when LOTS of problems showed up... Same story here :s @midiboy: ****.. For some reason it seems that this doesn't work anymore... :s I'll explain it to you: I use nircmd.exe to set all winnt.sif values. In my experience, it was overwriting previous entries, but apparently it doesn't check properly (anymore??!) if the spaces/tabs before the entries differ. I know somebody who could write a small program that CAN do this, and I'll contact him right away! Until then, I think you'll have to check your winnt.sif yourself every time... @simpleman: at least some good news P.S.: they're added to the Success list! @BAM: please post your hwids! I checked and there were NO identical HWIDs! But I'll check again in this case... CHECKED and I can confirm that there aren't any double entries. So I'll need your HWID before I can fix this problem. @imdos: For now I see 2 possible causes+solutions: 1) Windows Setup chokes because your NIC is active. Please DISCONNECT it as I suggested earlier (didn't I?), or did you already do that? That's not clear to me. 2) CHECK your hardware specifications! That's VERY close to the minimum requirements! Did it work before? Did you use nLite to modify your UWXPCD? Please try an installation without nLite'ing, maybe that's causing it. @willerman: I don't understand why you're having this problem. This will only give problems on systems with Intel chipsets though. Maybe you can live without them for the first days. Though I have to admit that you're not the only one with this problem. Someone else reported it to. But I *truly* don't know WHAT could be causing this, I haven't been able to reproduce this error yet...

Thanks midiboy (or is it Alex?) CMD /C was missing indeed! But as I said, it was a hasty job, which is why I added the [EXPERIMENTAL] label to it! Edited it right away! EDIT: RunOnceEx.cmd or cmdlines.txt shouldn't matter... But I'll change it to prevent more problems.

@Vid0: 1.I've seen that if not all files in the SourceDisksFiles section are present, Windows will choke. THAT's why I've included them. If you can assure me it won't give any errors, I'll remove them. 2. OK LOL @ Broadcom driver signing @jeff: is already fixed for some time now

Topic closed. It has been added for some time now!

@mark49: what if it hasn't to do ANYTHING with the KB888111? I got it from RyanVM (he got it from a 'insider' hehehe ), he uses it in his pack and is there someone having problems with that? I didn't think so! Please post the HWIDs & the names of the soundcards that gave problems!

Nope nope! I'll add them

@BAM: the one with a zero (0) is from nLite, while the one with 'No' is from my DPs BASE. But I don't understand, it *SHOULD* be overwritten!!! EDIT: just noticed this: nLite uses 'MsD...' while I use 'MSD...' THAT's the problem, I'll change it to nLite's setting to improve compatibility.

That's indeed all you have to do

Personally I think this isn't a good idea. Who's going to control the drivers? Who says they've included the correct files? You have to know that alot of newbies also use my DriverPacks... A VERY nice idea! I will switch to that ASAP It seems it's very easy in use. The modded phpBB 'KnowledgeBase' I'm using now, has always been rather a temporary solution. Moving to dokuwiki would definetely be a step forward! Thanks again A CVS server? Wouldn't that be a bit over-the-top? I mean, this project doesn't contain THAT much code! :s I'd rather stay here and keep things the way they are... I think you agree with me when I say that everything is almost stable.

You'll have to use intallation switches, possibly you'll have to use AutoIt! to let it install automatically or WinInstall LE 2003 to create your own setup.

VERY nice Topic moved to DriverPacks General Discussion.

Is it also present in the I386 dir? Did you download the FIX??? Topic moved.

Please use code tags next time Change it to: [SourceDisksFiles] sisraid.sys = 1,,,,,,3_,4,1 [HardwareIdsDatabase] PCI\VEN_1039&DEV_0180 = "SISRAID" [SCSI.load] SISRAIDP = sisraid.sys,4 [SCSI] SISRAID = "WinXP SiS964 Raid Controller"