Jump to content

Recommended Posts

Posted (edited)

If I remember correctly Pyron's post about WatchDriverSigningPolicy.exe, it is called from presetup.cmd which is in your i386 folder (drivepack base should place it there). Sounds like presetup.cmd is calling \OEM\BIN\WatchDriverSigningPolicy.exe which is not in \OEM\BIN\ inside your CD/DVD/Network share. Check that, and also check the relevant MSFN forum since your questions are probably more suited for the drivers discussion section of MSFN ...

CF

[Edit] You can find out what Intel chipsets are supported by BTS's drivepacks if you refer to the changelog of the appropriate pack.

Edited by cancerface

Posted

i'll try to do it by hand. but I have a question already. when i setup my structure in the drivers folder. 000_intel_inf 001_intel_LAN

i have 2 several different types of video cards and nics do I just keep 001_REALTEK_LAN

with the 001 folders?

Posted
i'll try to do it by hand. but I have a question already. when i setup my structure in the drivers folder. 000_intel_inf 001_intel_LAN

i have 2 several different types of video cards and nics do I just keep 001_REALTEK_LAN

with the 001 folders?

The folders can be named anything you like. For example, on my disk I have the following:

$OEM$\$1\Drivers

Easy enough so far.

From there I break it down by my different hardware.

The drivers for my ATI cards are here:

$OEM$\$1\Drivers\ATI\x700

I use the same NIC in all my machines:

$OEM$\$1\Drivers\Broadcom

Next is my Dell laptop:

$OEM$\$1\Drivers\Dell\D600\Audio

$OEM$\$1\Drivers\Dell\D600\Video

$OEM$\$1\Drivers\Dell\D600\Wireless

Now my desktop:

$OEM$\$1\Drivers\Abit\VT7\SATA

$OEM$\$1\Drivers\Abit\VT7\Audio

Then my kid's computer:

$OEM$\$1\Drivers\Asus\P4S800\Audio

$OEM$\$1\Drivers\Asus\P4S800\Video

So on and so on until I have all my drivers on the disk. My WinNT.sif just lists them all out. I boot any of my machines from this disk and I can fully install all the hardware without problems.

The names of the folders don't matter, as you see you can call them anything you want just as long as it makes sense to you. I break mine down based on the hardware, you can do anything you want, even lump them all together into a single folder if you want. Windows won't care, all it wants to know is where to find the drivers. The folder structure and names are only there to make sense to us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...