1 Reply by OCMan

(9 replies, posted in Software)

You'are right, I think I have to disable the KTD option for end user, but it's very useful (KTD) when you want to set up a Test machine wich will like everything you gave it something to eat :-)


By the way, I have seen the reply of roguespear where he gave me a link to his script ( sorry I really wouldn't to steal the idea, I haven't even search before... shame on me!)

His script seems very advanced compared to my poor one, I need to read more about his work, but at this time, my simple sricpt is enough for my use, I just wanted to share with you my work ,

So if you need a simple scirpt take this one, if will ask you or not for DP then for KTD, i think I shall put a timeout on each, it could be good to have some help about that... a timeout choice in CMD, how make we that???

If we can set up a time choice, maybe overflow will like it though!!! smile:):) ( because a timeout doesn't break automation, so the "pause"  fonction is invalid for us...)

See you soon.

Go to forum: Software

2 Topic by OCMan

(9 replies, posted in Software)

Hello, I'm using driverpacks for quite some times now and it comes to me an idea just lite a flash : a script for installing driverpacks during the setup!!!

With that script, the bug of fakesetup is resolved as well when repairing is selected!
The script is launched by a modified presetup.cmd, it will ask you if you want to use driverpacks or not, after decompression, it will ask you if you want to use KTD or not.
That's simply but vey useful I think.

Here is the detail for installation :


Scripts For Installing Drivers Packs Directly During Setup for Method 2!
v1.0


Method :
Just integrate driverpacks you want with method 2 and KTD disabled (VERY IMPORTANT!!!) to your XPCD.
You should now have a OEM directory at the root of your driverpacked method2 XPCD.

Now there is only 4 simply steps :
    - copy the attached KTD directory in the OEM directory ( so now the tree looks like \OEM\KTD )
    - copy the three CMD Files in the i386 folder of the XPCD overwriting the existing presetup.cmd
        (the 3 files are DPsFNSHR.cmd , DRVPack.cmd , PRESETUP.CMD )
    - Editing txtsetup.sif  : search for "presetup.cmd" in the txt, add theses two lines :
            DPsFNSHR.cmd= 1,,,,,,,2,0,0
            DRVPack.CMD= 1,,,,,,,2,0,0
    - Editing txtsetup.sif  : replace DPSFNSHER.exe by DPSFNSHR.cmd
   
   
That's all folks!!!!!!

I know this is simply a tweaky bullshit ( my english is bad so maybe that mean nothing )
But may be usefull for all-in-one creations like I do.

NEXT TO COME :  Scripts wich will ask you if you want 3rd party dp or not, because it's loosing time when decompresing them for nothing.

See The attached file containing theses instruction.

here is the link to download the file :

http://dl.free.fr/mqYHPFeZp/OCManDrvPackScript1.zip


Give it a try and let me know!
(There is two version included in the zip : ENG for ENGLISH and FR for French script -- that's why my english is so bad lol)

See you soon.

Go to forum: Software