Ah, that's solved in 6.08... Sent you an e-mail.

TNX, but you did sent 6.07 NOT 6.08.
May you send me please the 6.08 link?

@Helmi: TNX for the shed light on

Regards
coucou

What do you recommand about KTD, enable or disable???

That entirely depends on two things:
* Whether you have the HDD space to spare
and
* Whether you plan to change the hardware of the system often

If the latter is the case, then you should enable KTD, if not and you want to save some space, then disable KTD.

AFAIK it does not have any influence on the unattended installation at all.

It's just for afterwards maintenance, so to speak.

When did I recommend method 1 over 2? I always recommend method 2.

Oooooops, I think i red that somwhere in MSFN.
What do you recommand about KTD, enable or disable???

and finally what about the errors regarding DriverPack Modem V1.8.5and DriverPack TV 1.8.2 (see here bellow image)?

Regards
coucou

And yes, you must register at the bugtracker too... I will merge the user accounts, but don't have the time to do that yet....

But you NOT recommand using Method 2 with the NON GUI DP_BASE_6.034. Isn't it?
Because i intersted by slipstreaming DriverPack Modem V1.8.5 and DriverPack TV 1.8.2 which are not possible with the latest DP_BASE_6.061

BTW, can't connect to the bugtracker: feature request #123. It asking for alogin+pass

Regards
coucou

And your OemPnPDriversPath is TOO long then. All entries listed after the 4096th character will not be processed. (Most likely DriverPack Sound and WLAN entries). You may want to use method 2...

Finally, i solved the blue screen problem. It was the 3rd Party DriverPack_Monitor_1.7.2 at fault.
1000 appolgies to Bashrat.

As Bashrat suggested, i slipstreamed (Method 1) all DP's one by one.
I must say that all the Official Bashrat DP's (DP_CPU_6.05, DP_Chipset 6.031* (not the latest), DP_Graphics_A_6.06,  DP_Graphics_B_6.03,  DP_Graphics_A_6.03, DP_LAN_6.05.1, DP_MassStorage_6.03.1, DP_Sound_A_6.06.1,  DP_Sound_B_6.06 and DP_WLAN_6.05) works just fine.
i slipstremed also the 3rd Party DriverPack Modem V1.8.5 and DriverPack TV 1.8.2 with success

All the above DP's was sliptreamed with DP_BASE_6.034 (not the latest) because errors when they're slipstreamed with 6.06.1 (see error details here DriverPack Modem V1.8.5 released and DriverPack TV 1.8.2 released). Hope Bashrat could solve that problem.

*DP_Chipset6.05 can't be slipstremed by DP_BASE_6.034

3rd Party DP_WB_wnt5_x86-32_1.0\D\WB\C\17\readme.txt gives Cabinet Maker (MakeCab.exe) error

@RogueSpear: the actual OemPnPDriversPath is 6,192 characters

Regards
coucou

I've submitted it as a feature request to the bugtracker: feature request #123.

In the past, when I did use Method 1 from time to time, I had run into circumstances where it would be around 5,200 characters.  I never had a blue screen as a result, but I did have some devices which did not install.  When I looked into why they did not, sure enough, their directory listings were past the 4,096 mark in the OemPnPDriversPath.

P.S yup. russian community in Antwerp is big. welcome to the russian disko in antwerp on 26th august.

ok. i have G-Skill DDR500 which is working at 520 and i never had a pboblem. last night i spend on changing slots, changing memory, underclocking memory, and testing, testing, testing. so my conclusion after all is that if WINNT.SIF with all integrated drivers is in I386 folder, setup fails, if i remove PNPDRV lines, setup is ok. i don't have a clue what could it be? and why.

Well, if it DOES work when you use method 2, then you'd have convinced me half the way... so just try method 2 as DriverPacks Method and then let uw know if it worked.

P.S.: you speak Russian and you live in Antwerp???