Bâshrat the Sneaky

Thanks for your patience, guys This is my first post & visit since... well, since I posted this announcement. You can read my exam results here at my blog! ^^ Before you think: "Yes! He's back! Finally... updates!", you should think again: Monday I'll be on vacation - till Friday. True vacation that's not, because djbe will join me. We'll be working hard on the C++ version of the DriverPacks BASE. A different location and the fresh air of the sea will give us more and better ideas, we hope . Well... it's good to be back ^^ EDIT: and apparently this is also the 4999th post ...

I strongly doubt that. This is an isolated case. I'll apply the patch suggested above then. I thought I already applied this BTW; I just checked and apparently I haven't applied it yet indeed. This will certainly be implemented in the next release of the DriverPacks BASE.

Huh? :s Then I really don't know what can be causing this. And I cannot reproduce the error, or at least I don't seem to suffer it.

LOL That one really did go under my radar. I'll endeavor to put together a list of machines from my work soon to get this going again. Cheers, Andy HOW could you have not noticed this? I link to it from everywhere... Where should I have included it so it does not stay unnoticed?

Could you explain what you exactly did to slipstream them?

Yes, you can edit the .inf files to improve the compatibility. But remember this voids the WHQL signing!

Use google. Post more information about this device. Use Everest Home Edition (freeware) to find more details about it.

Add both driver files to the dosnet.inf file under the [Files] and [FloppyFiles.1] sections. Like this: [Files] d1,sisraid.sys d1,property.dll [FloppyFiles.1] d1,sisraid.sys d1,property.dll Copy property.dll to the I386 directory. P.S.: don't forget to let us know if it worked.

You should check what motherboard or type of A-brand pc you have. Everest Home Edition is an excellent (freeware) program to find out what motherboard you've got.

Check the sticky, section #2 for tutorials covering different methods of PnP drivers slipstreaming. Topic closed.

You must set this in your winnt.sif: [Unattended] OemPreinstall = "Yes"

Google for 'sigverif.exe'. I believe you must have a genuine copy of Windows in order to download it.

Check the nLite forum and use a version that doesn't have this problem.

How did you slipstream it?

The most important reason is the softmod abillity (9500>9700).

I just wanted to post this announcement to prevent people from trying to contact me so I have to clean up my mailbox like a freak. My exams start this friday (9 dec) and will end on the second wednesday after it (21 dec). All of them are a piece of cake (or almost) with one minor exception (latin, who gives a **** about a dead language? ) and one major exception (math... HELL it is :angry:). Please don't shoot me if I don't reply very slow or if I don't respond at all. It's possible that I'll reply often, but that I'll skip the 'more difficult ones'. Thanks for your understanding... and cross your thumbs on monday the 19th (that's when I have math). Bâshrat the Sneaky EDIT: About the Christmas vacation: see post #17 & 19.

In fact your suggestion is exactly what I've already created. At the same time it isn't. My implementation of this idea is much more detailed: it also included all working devices. This implementation is exactly what people seemed to want/like/need according to a poll, BUT apparently there is virtually no one submitting to it. As I've seen the last month or so. I'll recap to this, since there's no use of having a huge database when nobody submits to it... Too bad... I've spent many hours on those pages...

I STILL need more information.... Check the link.... P.S.: rebuild your UWXPCD with nothing but the DriverPacks. The problem won't persist. The cause lies elsewhere.

@maxximum: please start a new UWXPCD with nothing but the DriverPacks. Maybe the problem lays elsewhere after all... @RogueSpear: indeed!

Tried 3drivers so far but none of them worked. Have MUIZ found a working driver? Nope, he hasn't.

It's the ORDER in which you did everything that's incorrect, as Fencer128 outlined! Read the FAQ. OF COURSE you can just merge the two files.

I need more information!

Then could you please post your HWIDs? Check my sig for a tool to find them.

I AM doing that: REM ### Removes attributes of some files we're going to overwrite. ### ATTRIB -A -R -S -H I386 /S /D But obviously it didn't work for some odd reason. Is it working now, muiz?