Bâshrat the Sneaky

Though M3 is STILL EXPERIMENTAL, it's ok indeed.

You've got an InstallShield setup there (I can see that by the fact you have 2 data.cab files). Use the command line utility i6comp to extract them. Google will provide you with al the information you need

@Toolman: huh? Are you using the latest version, PLUS THE FIX? @shortie: You mean the M1 folder in the root of your UWXPCD, after running RUN_ME.cmd? Please attach that 'complex' winnt.sif. Note that this is probably being caused by a (small) error in Fedit.exe... @robnjay: NOTHING has changed to the method. I've only added the ABILITY to do everything WITHOUT COPYING MANUALLY. You don't /have/ to do that... At least if that was your problem/issue/question?

DOH I didn't read that line where you said you noticed the identical HWIDs ! In that case... is it maybe a known error that sysprep DOES NOT CHECK THE CC CODE??? If it isn't, it is by now... I don't know how you could possibly fix that... Obviously it doesn't check it PROPERLY. BUT, if this is a straight copy from your sysprep.inf file... then I do know a possible solution. List the Adaptec driver AFTER these two Intel drivers! That way it will first have to detect the CC codes! And if it DOESN'T find them, it will skip them and use the Intel driver! Please give it a try! P.S.: please use CODE tags next time!

1. Are you sure of that? When I checked it WAS there... 2. WHERE did you find that driver??? 3. ok...

This one: PCI\VEN_10EC&DEV_8139&SUBSYS_032010BD That is: -WITH VEN ID -WITH DEV ID -WITH SUBSYS ID -WITHOUT REV / CC

Well, in that cse, could you please verify the .exe files ARE in %DPDIR%? (commonly %DPDIR% is the variable for %SystemDrive%\D)

Indeed. You stated 'VIA Vinyl AC'97', and there is a VIA driver what that exact same name, so I suggest you'd use that one.

What is your OS? And your hardware? Which specific driver didn't work?

You only should post HWID's in the following cases: -DriverPack MassStorage -double HWID's -problems with a specific device: possible identical HWID's. In this case, it's better that you post a link to the (official) driver, so that I can compare it with (in this case) the Realtek driver.

WTF.... Intel releases an update ONE day after I updated the pack. And Marvell puts AGAIN an update online!!! Will be updated

@erik_demon & midiboy: thanks, I'll fix those. @mark49 & RogueSpear: in the pas I've tried similar things and I always had to use CMD /C. But quite frankly, I only changed this because it didn't work for mark49. Why I didn't add it immediately? Because I thought RogueSpear's hybrid method would be tested in detail, so that all the commands he posted should work. Apparently I should have kept thinking that... Probably your problem lies somewhere else, mark49? @Siginet: Note that at the end of that line you quoted there is NO /f, i.e. it does NOT force to write that entry to the registry: if it already exists, it WON'T be overwritten. Which one is listed first in your cmdlines.txt: my BTS_DP_ROE.cmd or your RunOnceEx.cmd?

FIX #2 for DPs BASE V5.05.1 -*should* fix everything (problems in winnt.sif & cmdlines.txt, ASH1205 error when using winnt.exe/winnt32.exe) (includes new version of Fedit) -fixes the problems with Fedit.exe -fixes the problem with the cleanup batch file not being executed -fixes the problem with the erroneus REG ADD command in BTS_DPs_ROE.cmd download How to apply the fix: 1) Download; 2) Open your DriverPacks BASE dir, open the FILES dir; 3) Move the downloaded file into that dir, click 'Yes' when asked to overwrite.

No problem

I meant of MY DRIVERPACKS you genious

You posted this before, though I don't know where. I AM working on it, I just don't have the time to do it immediately. Please have some patience

Did you use the latest version of everything? Your latest prob was an old problem...

Your first post: yes, please give me his HWID. Your second post: I strongly disagree, and I'll explain you why. 1) As you say for yourself, most users are very n00bish and so they don't know how to add their own HWIDs. Additionally, they don't always know which driver they should be referring to. That's why I'd rather keep doing it myself. 2) These HWID's are most definetely NOT user-specific, rather hardware-specific. Don't forget that not EACH device has a unique HWID! Only a device with the same productname/revision/etc. (you get my point), have a unique HWID. The problem is that sometimes the vendors didn't include specific enough HWIDs. That's why I have to add them... So it it's in everyone's advantage to all have the newly added HWIDs. I hope I explained it clear enough

Quite obvious that you're new here and new to all this. As for the nLite download link: here (try MajorGeeks for example) As for the information about app installs: here. Please post on-topic next time. And more importantly use the SEARCH function of both this board and of google. Thanks.

@zomig: could you please also post your HWID? That makes it easier to track the problem. @iLLuZZiOn: of course I'll check yours as well. Thanks for posting the HWIDs, at least someone who's getting to know the process I'm at school ATM so I can't check immediately.

@simpleman: I checked and I understand the problem. I will change that system: I will remove the ability to set DPDIR in the BTS_DPs_finish.cmd file, and only leave it in RUN_ME.cmd. That way you'll only have to edit RUN_ME.cmd, and BTS_DPs_finish.cmd will automatically inherit your setting. BTW... you're using M3? EDIT: /me was in a period of stupidity. It was WRONG indeed. I wanted to change the default folder of the cleanup batch file to %systemdrive%, I made all the necessary changes, afterwards I decided not to and forgot the changes I made in the finish batch file... Fixed in the next fix! @all: this Fedit related problem can't be solved by me. That's up to djbe, but I'm sure he'll do it ASAP. The problem with double entries in cmdlines.txt should be fixed by the next update as well, because I *DO* have the code for that in RUN_ME.cmd: Fedit -clean -f $OEM$\cmdlines.txt BTS_DPs_ROE.cmd > NUL @midiboy: thanks for that, that's indeed a typo @Siginet: yes, I'm afraid you'll have to enter a number... I'll try to change that in the next release as well.

EDIT: new fix online, that renders this fix obsolete.

Dammn.... Those are nearly all Fedit.exe problems :'( :'( :'( I've informed djbe!

Interesting, didn't think that it would work at that stage But unfortunately unusable for my DriverPacks - they would not yet be extracted at that stage... unless you use method 2 or method 1. May I ask on how many drivers (the number of .inf files) you're applying this? And how many megabytes?

It seems there's still a strange bug in Fedit that prevents it from updating the winnt.sif file... Djbe is working on it. @mark49: DetachedProgram = "CMD /C BTS_DPs_M3.cmd" @all: all 'bugs' have been fixed, except for the bug 'that does not update the winnt.sif file if none was present'. By this I mean that the current download does not have the earlier posted problems. EDITed: post obsolete: new fix.