Bâshrat the Sneaky

As promised, the update will be online today... Just some more patience.

This might be solved in DPs BASE V5.08, which should be online soon.

speechless.... Now what... You posted your HWIDs, your VT8237 controller HWID matches exactly one of the entries in the txtsetup.sif file. So what could be going wrong? It's not looking good It's obvious that Windows did choose the viasraid driver. I checked again and verified that both the viasraid & viamraid driver have a valid .cat file. So WHQL can't be the reason. The only reasons left I can think of are: 1) the REV codes mess things up. This would amaze me, since it has been working for sooo many other devices. 2) the order in which the HWIDs are placed in the txtsetup.sif file. Please retry with your current txtsetup.sif - after putting the viamraid.sys entries ABOVE the viasraid.sys entries. (only the hwids of course). That would become: PCI\VEN_1106&DEV_3149&SUBSYS_59011462&REV_80 = "viamraid" PCI\VEN_1106&DEV_3149&SUBSYS_04701462&REV_80 = "viamraid" PCI\VEN_1106&DEV_3149&SUBSYS_80ED1043&REV_80 = "viasraid" PCI\VEN_1106&DEV_3149&SUBSYS_71421462&REV_80 = "viasraid" PCI\VEN_1106&DEV_3149&SUBSYS_70201462&REV_80 = "viasraid" PCI\VEN_1106&DEV_3149&SUBSYS_1419147B&REV_80 = "viasraid" It'd be very helpful if you could try this suggestion.

Me too I think...

Sorry for the late reply. I'd like to refer you to this thread.

Hehe... Not at all a touchy topic Many months ago nuhi contacted me and a couple of months ago I contacted him. Both times the reasons for not doing it were simple: the DriverPacks weren't/aren't stable enough yet. Of course RyanVM's UpdatePacks are ALOT easier to get working without a hitch on all possible Windows XP system: that's because all hotfixes have to follow strict standards. (I'm NOT saying that it's easy to do - I'm just saying : once you've got them working, it'll work on virtually any Windows XP system.) In fact, that's also the case for device drivers - only the manufacturers don't take the rules serious enough. I'll give you some keywords: HighPoint hpt3xx, nVidia NVRAID, Promise, SoundMAX. If you enter either of these keywords in MSFN's search function, you'll get *many* results, while problem-free posts are rather an exception than a rule... So far reason #1: the DriverPacks' stability/compatibility issues. Secondly, there's also the problem with slipstreaming: RyanVM's DriverPacks can use a simple file that contains all entries for the txtsetup.sif, dosnet.inf & hive files. For the DriverPacks, nuhi and I'd need to standardize the slipstreaming of txtsetup.sif, dosnet.inf, winnt.sif entries, as well as where all files should be placed, which files should & should not be copied to the I386 dir and then there still is the KtD option AND the GUIRunOnce/RunOnceEx option to run the final finishing batch file... Just too much for now... And last but not least, I've decided to give the DriverPacks a GUI in the future, though I don't know yet how far that future will be (may be 2 months, may be ? months). Another sure thing: conversion into a C (win32 console) program - this should make the process faster, more stable and more user friendly. If hope I answered all of your questions.

Yes, of course, thank you for notifying me

Please keep us updated.

The update will not be online tonight (well "tonight" has passed here already ), but tomorrow, early. Solved in that update: the files that didn't get deleted, sometimes multiple sections in the winnt.sif file because of differences in the cases (lower vs upper) and last but not least, we don't need the 'cmdlines fix' anymore! Thanks to djbe and his Fedit 2.0! Thanks again, djbe!

This should not be happening. What things have you incorporated to your UWXPCD? Are you using DetachedProgram or SetupParams? Are you using cmdlines.txt...

The problem with nForce, or... ← The problem with the files not being deleted when enabling KtD. Though I *might* have a solution for the nForce drivers, but I'm not sure at all.

Eh... Did you happen to install Daemon Tools?

ROFL Nice one indeed ! Where did you get it from?

THE FASTEST WAY to shutdown your pc: unplug the power cable . As for the reboot: there is such a thing as a 'soft reboot': your pc won't have to POST again. Google will certainly give you something useful.

Maybe there should be options to get more animo: what if there'd be a cheaper forwarder and a more expensive pop3/webmail? And maybe an option to pay more to get a lifelong account. Just suggesting.

I'm trying to fix nVidia's NVRAID driver now. With some luck that update will be online tonight (in a couple of hours), if not, then it'll be tomorrow.

Eh.... English please?

Found the problem... at last... I also found the problem with the winnt.sif file not being created.

Yes it's safe to remove those files.

ccfly, have you contacted your friend already?

Please post your HWID. (check my sig for a tool)

Please ask again in the Windows x64 forum.

I'm working on it.

Are you sure they're connected correctly? Did you disable some controllers in the BIOS? Is your OS driver connected to the nForce 4 controller or the SiI3114r controller? Did both drivers install?