IcemanND

what happens if you do nothing iwth the hal, at least when putting on another uniprocessor hal system or on a MP hal system? Nothing should have to be done in either case. If it goes back to the ACPI hal then you would have to change it.

Spaces in the path should make no difference whatsoever. I regularly backup the drivers to a folder on my desktop with multiple spaces in the path. And every driver that gets backed up has spaces in the name of the device which is how the folder is named. @clavicle - If you rename the INF for your Audigy to audigy.inf do the drivers work? @spazmire - I'm not sure what is happening with the problems you are seeing. the GUID that comes up as being unable to create folder is not a guid in the CSV file you sent me so I'm not sure where it even got it from in the first place. Once you click scan system all the information is either pulled from the CSV file or the related INF once that is located. And any folders are created before the INF is even searched for. I'll keep looking to see what I can find though.

what is the name of yout CMD file?

Bound to find some bugs when you give it to the public to use on evedry piece of hardware out there. I only have access to a couple dozen different machine models. @ clavicle - I think I found the problem you discovered. As soon as I find Spazmires I'll post an update, probably tomorrow morning. @ spazmire - Two things can you email me the system_scan.csv file from your temp folder. and also I need the complete display name in the device manager for your network card. And I'll see if I can track down what happened there.

Are the files in the picture all of the files found? No CAT file?

if using xp encryption you may be hosed unless you had your keys backed up somewhere and/or you set and know the recovery password

I updated the coded to fix the font problem and added some additional error checking for folder creation. Oh, and a select all button.

@madboy - what is the name of the driver it was attempting to back up? And did it contain any special characters, that would not be allowed in a file or directory name? And What directory are you backing up to? I thought I had removed all of the special characters and replaced them with underscores but where it says it is failing is on creating the folder to back up to. @ P51D - Thanks type will be fixed in the next version. I'll see if I can fix the font size issue. How it does it: First it uses WMI to query Win32_PnPEntity to collect information on installed hardware. Then using this it creates a directory named after the hardware description. If the folder already exists it deletes it and its contents first the recreates it. Then searches for the INF file based on the information returned by the WMI call. THen I parse the INF file to find what files are installed when using the INF and search for each first in the default install location and then on the entire boot drive for the file if not found in the appropriate windows subfolder. then copy that file to the previously created folder When the CAT file is found it is renamed to match what is listed in the INF, and I rename the INF to the same name also rather than have OEMXX.inf in all of the folders. then repeat for the next selected driver.

sounds like it is not installing the HAL correctly on the multiprocessor machines. You poor soul still having to deal with P3's. FYI: The GX400 and GX300 can be changed to ACPI Uniprocessor via bios upgrade and bios setting change. Possibly the 8000 also since it is basically a gx400 with a different bios.

How are you changing the HAL between ACPI and ACPI Uniprocessor and for that matter to ACPI Multiprocessor? The ATA controller should only be and issue if you have to press F6 to install it when doing a standard installation, and if you didn't build the mass storage section in sysprep.

@clavicle - let me know I no longer have a machine with a Creative card so I can't test it.

@Jeremy - here you go http://www.msfn.org/board/index.php?showtopic=83960

Dissatisfied with both freeware and commercial driver backup applications I wrote my own for personal and work use. The biggest difference is that instead of relying on what is stored within Windows in regards to driver files it locates the install INF and then gathers the files from the files listed in it. This has only been tested in 32 bit Windows XP. It may work in other version of Windows but I have no way to test. If you do and it works post here and I will update this post accordingly. Requirements: v2.1.x mscomctl.ocx (sorry not licesnsed for distribution, believe it gets installed with Office so you may already have it) v.79 Must be run with administrative permissions .NET 1.1 Recommend 1024x768 resolution How to use: If you want the Microsoft drivers uncheck 'Non-Microsoft drivers only' Click 'Scan System' Highlight listed drivers you wish to backup Enter path to backup drivers to Click 'Backup Now' Each driver will be backed up to its own folder inside of the folder you select named by what is shown on the screen. Update Log: v2.1.83 - complete rewrite, don't remember what other changes were made. does not elevate permissions in Vista and 7, need to run as administrator v.79b - 10/12 - 98 - fixed resoltion issues - added additional logging v.78b - 10/6 - 34 - fixed inf filname missing when no cat file found - change 'browse' to start ad desktop - modified data store v.77b - 10/5 - 30 - Changed fonts to be static sizes. - added select all button - added additional error checking for folder creation driverbackup79.exe DriverBackup2183.exe

you could run it then or even at t-13 from cmdlines.txt

the HAL can be an issue but it depends upon how old of machines you are dealing with. Almost every P4 desktop I have seen is either a ACPI uniprocessor or ACPI mulitprocessor HAL. The GX400 can be either ACPI or ACPI Uniprocessor depending upon bios rev and the apic setting in the bios. The laptops get a little trickier, they are one of the three acpi hals and the wrong hal on a laptop is a much bigger problem in my experience than the wrong hal on a desktop. I've found alot of drivers that won't even install if the wrong hal is on a laptop, haven't found that for desktops.

you can either add them to all of the proper folders, or my prefered method is to create a folder structure of drivers and point to it using either the devicepath key in the registry or when I did not have many drivers I put the paths in the sysprep.inf. On Dell systems check the bios for a setting either called ACPI, APIC, or AOPIC and turn it on. Depending upon model the HAL which is installed during windows setup from either Standard to ACPI or ACPI to ACPI Uniprocessor.

the short answer is to search but the answer you want I believe is: in Word Tools -> Options -> View Tab uncheck Picture placeholders

I said that.

two things are probably causing your problems as mentioned by the previous posters the HAL causes problems. You may find a setting in the bios on the systems that refers to APIC or ACPI that if you enable it and reinstall the os you will find it changes the machine from a standard ACPI HAL to an ACPI Uniprocessor HAL. If you can get all of the machines to be Uni or Multiprocessor HALs you can add UpdateUPHal or updateHAL to the sysprep.inf to change the HAL, though in my experience if you build it on a ACPI Uniprocessor HAL system and deploy it to an ACPI Multiprocessor HAL it automatically upgrade the HAL when it detects the additional processor/core. If you build on a Multiprocessor HAL you'll need to change the sysprep.inf to reinstall the HAL. Then you only have one real problem left... The MassStorage Controllers if you get a 0x0000007B BSOD it's because the Massstorage driver is missing for the traget system. Sysprep provides a way to solve this. add the following to the end of your sysprep.inf file and sysprep will build the list and add drivers to the image. You don't need to add anything else unless you have machine you need to press F6 to add text mode MSD to install windows. [sysprep] BuildMassStorageSection=Yes [sysprepMassStorage] The last thing to deal with you already do in collecting all of the drivers. You can then either add the paths to the INF or directly to the registry. Doing this I have an image which I deploy to gateway e-4000, e-4100, e-4200, e-4300, profile 4, 4.5, 5, 5.5, m460, Lenovo t43, r52, x41, z60t, z61t, Dell Gx300, gx400, gx240, gx260, D810, d610, d620

Download the nesest Intel chipset drivers and ditch the drivers from Dell. As a matter of fact if you can do this for any of the drivers I would recommend it. It requires a little more testing but it is well worth the effort. Also before you capture your image go to the windows\inf folder and delete all of the oem*.* files.

Check the INF files for each of the audio drivers. You will likely find that whichever is the newest has all of the devices in it for the other systems and works for the other also. Likeliy the gx280 would be the newest. Take out the others and just use the newest for all of them. You will find as your driver list grows you will run into this more and more if you divide them up by machine instead of by device class.

You can use diskpart to reassign driver letters. depending upon when you start writing things to those drives you ccan do it during any of the ponts during an install where you can run your own installers and scripts.

make sure there is not an INF file in the windows\inf folder that already references the dirvers you are having a problem with. I have had this cause this sort of problem in my images in the past.

when you partition the disks Windows assigns the drive letters by the type of partition. Since you setup the drive letters in PE they are not store in XP so they are reassigned. You can either reassign them suring the install or create your partitions differently. Windows assigns drive letters in order to primary partitions first, the returns to the first disk and assigns to extended partitions. If you create all of your partitions as primary partitions your porblem should be solved, or create the partition on the second drive as an extended partition instead of a primary partition.

Delete a printer: For a printer which the drivers exist in the installed ntprint.inf (part of the windows install) Install a printer that the driver is NOT in ntprint.inf Save the contents of the appropriate quote above to say add_printer.vbs then double click or add as a startup script or however you want to do it. If needed you can add the delte script and the add scripts into one just don't duplicate the lines that begin with SET that are the same.