Bâshrat the Sneaky

You sort of mixed up two different methods 1. you placed all files in $OEM$\$1\Drivers\ , you edited the txtsetup.sif, you added the compressed .SY_ files to i386 folder. 2. you added the txtsetup.oem Questions/remarks: 1. You did NOT edit your winnt.sif? 2. In which folder did you place the txtsetup.oem file?

I've downloaded another 6 SoundMAX drivers from ASUS' website. I'll see what the differences in Hardware ID's are. I didn't know the SoundMAX drivers where SO shattered....

Maybe you've recently upgraded to SP2 and that causes incompatibility with these drivers? So maybe there are updated drivers around on the net? Just guessing...

That's the opposite of what I want... I'm using 'START /WAIT' statements so the next command is only executed after the one before has finished... So Pskill is of no use in this case... MOH uses IS setups? Well NFSU2 uses an installer I've never seen before, so I guess it's a custom one...

I need the switches for EA games' AutoRun.exe, to complete a fully automated NFSU2 dvd. It does the following: 1. Start Setup.exe /Autorun.exe (=> the problem!) 2. Open my key (txtfile) 3. after the two above, the patch is installed. 4. the nocd is automatically copied. The problem is that AutoRun.exe starts another AutoRun.exe (it calls itself or something???) SET START1=%F%\key.txt SET START2=Autorun.exe SET START3=%F%\NFSUG2V1-1US.EXE SET START4=%F%\install_nocd.cmd START %START1% START /WAIT %START2% START /WAIT %START3% START /WAIT %START4% Which is why the patch starts immediately... And of course the patch shows an error... Anyone who can help me out? Currently the only solution is: SET START1=%F%\key.txt SET START2=Autorun.exe SET START3=%F%\NFSUG2V1-1US.EXE SET START4=%F%\install_nocd.cmd START %START1% pause START %START2% pause START %START3% pause START %START4%

I'm trying to do the same, but I haven't tested it yet. Please post your results

Well I tried it today: 1. I added the EOF character to the things to be removed (like ultra.sys) 2. I added a EOF character at the end of the entries to be added to my txtsetup.sif Conclusions: 1. You can't place a EOF character in the middle of your batchfile, or in any commands of your batch file, or the batch will stop on the moment it 'reads' the EOF character. 2. For the above reason it's impossible to remove the EOF character. (in an automated way) and I guess that's also the reason why it wasn't imported... 3. When I use the patch.cmd it overwrites the EOF character! At ***EXACTLY*** that point it inserts the first line! OVERALL CONCLUSION: For the moment there's no known way to handle this in a decent automated way. The only cause I can think of is: differences in character encoding. To check the standard character encoding of your Windows system, do this: Open Notepad, type a few characters, go to 'Save file' and check what character encoding is set... A long long time ago ( ) I've had a problem with character encoding too, so why couldn't that be the problem here? EDIT: for me it's ANSI Prolly it's one of these: ANSI, Unicode or UTF-8

@www2000: well, that would indeed be asking way too much... If you want to have support for only some specific controlles, then download just the drivers for those controllers! This DriverPack is meant to create a UNIFORM UWCD, which means support for as many hardware as possible!

@rendrag: Please try this: Edit your presetup.cmd: remove the 'START' command in front of the path that points to WatchDriverSigningPolicy.exe. Please post the result!

Errr...? Just use the guide...

If some other people can verify this, I'll do the best I can to release a new version! Tomorrow I'll have some time, so please post asap! (Don't have time from Thursday to Sunday...) EDIT: @leos: Congratz! B)

Indeed tguy. plizarralde, would you care to add the tags? Thank you.

Well what can I say? I'm happy Only this negative comment o/t broken links... Well, it's fixed

FIXED!

@Ghostrider: yes, that was a bug o/t past. Goddammit! Forgot to change one stupid number :@ I'll update it, and sync the version numbers from now on to avoid these mistakes... @arjanv: dead link fixed, please do some research for integrating those controllers!

Yes, but for several people it works flawlessy... Which makes this bug very odd IMHO... And again: I did not invent this method, so I don't really have an idea what the problem could be...

Maybe I could solve it like this: 1. remove all EOF characters 2. add everything, including a EOF character at the end. I'll test it and post the results here. (But don't expect that post soon, I've got very little time...)

Are there any requests? For the moment I will only do driver updates and easy changes, because I'm having exams. Of course critical bugs will be fixed as well. Someone said somewhere (can't find where) why the viasraid driver isn't in DP MassStorage anymore. Well the reason for that is simple: I can't find it. I've downloaded ALL MassStorage drivers from VIA's website, but I couldn't find it... Anything else? If nothing else, I will skip V4.11 and go to V4.12 immediately around Christmas.

Do you select the harddriver you wish to install on manually? Or is it selected automatically? Please tell me what controller you are using.

Well, congratz SiMoNsAyS! I think you're becoming the "FAQ-man"!!!!

What versions are you using? Is everything up to date? As stated in this post, there's a huge bug atm. Working on it...

In version 1 I was renaming all of the DriverPacks so they would not have a version number anymore. But in version 2 I changed the presetup.cmd, so that it would be version independant. Apparently I've forgotten to update this file... Thanks for this bug report! P.S.: yes I know, I deleted your post, but that's my mistake too: I forgot to close that topic after editing it...

Indeed. For example when you look in the driver inf files of ACARD, you will notice there are no hardware ID's either... I have not yet tested what the result would be when there are no hardware ID's in the txtsetup.oem file, but most likely the driver will not work... P.S.: where did you quote that txtsetup.oem file from?

And is already in the available DriverPack LAN V4.11.1

It *WAS* a sticky, but there was a sticky for every DriverPack, so the stickies section was becoming quite messy.... That's why I made a new sticky "Bâshrat the Sneaky's DriverPacks: Overview"...