Bâshrat the Sneaky

Indeed... I enlisted in the Installation Instructions that you should remove the '.example' It's very optional, as it might take more work for some. DriverPacks BASE V5.05.2 should be online within minutes now.

then, why a missing drivers will CAUSE portcls's prolem ? I thought it shoud cause normal problem (i.e system tell you some files missing) and don't cause BSOD. ← Well... don't ask me to explain it... it just ***IS*** like that... Check the HUGE topic 'Portcls.sys' in the DriverPack Sound forum for confirmation...

Eh... you're wrong on all statements... 1. RS, FOLDER are being set in the first STEP: BTS_DPs_Slipstreamer_Vxxx.cmd 2. ROBOCOPY is being copied to %SystemRoot%\system32 by the same batch as the one mentioned above. And as you always have to run the other batch first... EDIT: I understand your point... it doesn' work if you run it 'stand-alone'... I'll make those changes...

Ah, now I understand . But unfortunately I do NOT have an answer :'(. My guess it's NOT being caused by the (updated) portcls.sys file itself, but because a driver is missing. What soundcard does he have? P.S.: as a test, you could retry without the updated portclsys.sys... and see if that changes anything.

Note that you can turn off unnecessary components, which significantly speeds up the loading of Trillian

@BTS, why got this BSOD problem even no HD audio when slipstream kb888111 ? ← Eh would you please reformulate that sentence? It doesn't make much sense to me... Did YOU have that problem? On what hardware? Or even in VMWare? Please clarify...

I know, I just fixed this in FIX #5... EDIT: but FIX #5 is still being tested

@mextrom: ok, thanks, I'll try to find the bug. @GhostRider: great! They're added to the SucessDevices list .

Could that have this effect? I would be amazed...

Eh ... did you do a search? It's explained detailedly in the official guide

Moved to DriverPack LAN. I'll add this one to the next update. Never heard before of that brand

Eh... would you explain yourself a bit please???

In FIX #5 this will be fixed. Probably it will simply be V5.05.2.

@Siginet... OK... I could do that... in fact I *DID* do that, but unfortunately that didn't work with Fedit... (you can check your current version if you want: it has a REM in front of it...) @sleepnmojo: thanks, that solved the problem @d0ublezer0: please tell me which soundcard you're using, I'll add the driver for it. (this problem only appears when a driver is missing) @Jeff: your GUIRunOnce section is named [GuiRunOnce] Note the 'Gui', while I'm using 'GUI' [GUIRunOnce] I'll ask djbe to do everything case-insensitive. (except for writing new entries of course). @S0mE0nesMiNd1: and on what controller does that problem occur? @Mextrom: please verify that BTS_DPs_M3.cmd is in $OEM$\$1\D.

You removed too much with nLite And DetachedProgram is only used in method 3

Indeed... Isn't that clearly marked??? :s

EDIT: fix obsolete, check first post.

eh... At what stage of which STEP is that? And what exact filename? EDIT: do you have spaces in your path?

I can confirm: it's NOT *yet* online...

@Siginet: for now I used your suggested "fix": let it check for a RunOnceEx.cmd file (as the vast majority uses this name) and if it doesn't exist let it write the title, with a /f. BUT... I was thinking... would it also work WITHOUT a title? Can't test right now, I'll try to do that this weekend. Unless somebody else could? @djbe: I'm ASTONISHED............................... Anyone's got a clue how to fix this? With the original script (by idle.newbie), it did not have this problem. And afaik I did not make any large changes.... @sleepnmojo: THANKS! I'm ASHAMED I forgot that! @mark49: thanks for that suggestion. I've used it, but I omitted the '/WAIT'. What would the use of that be??? @sleepnmojo: thanks again... That was definetely a big typo... @djbe: thanks for that new version. @all: I'll post a new fix within a couple of minutes that fixes all problems that you can find back in this post. However, the problem with the OemPnPDriversPath won't be solved immediately, as I don't have a single clue how it's being caused...

@Gnome: mail sent Almost all file editing will be automated, probably all. I think that's some good news for you users

Sorry, I have no clue. Sounds really odd to me... P.S.: I don't do any sysprep installations, so I'm not even familiar with the process. Though it doesn't sound to hard to me. Topic moved to DriverPacks General Discussion.

Then you've got a faulty setup... Nothing you can do about that...

You NEED the IDE driver. The RAID drivers won't even install without them! And... it's been more than a year now since the IDE driver caused problems!!! They're very reliable now.

Please disconnect the network cable and try the installation again. This might solve the problem. The other possibility is that you'll have to copy some .sys files to the I386 dir (more specificly: the ones that are about to be used...)