Search options (Page 2 of 6)

You're welcome.  I'm glad I could help out.

Another way is to use an application named UltraISO, which you could use the free trial or purchase the program.  You can use the following method to make a USB Flash Drive into a Windows 7 Installation Disc.  I have used this method, so I know it works.

Note:  The credit for this method goes to xoben from the EZBSystems forum.

1. Start UltraISO (V9.3 or newer version)

2. Choose ‘File’->’Open’ from main menu and open ISO file of Windows 7, for example “d:\ISO\WIN7_DVD.iso”; You may also open the original DVD by 'File'->'Open CD/DVD' from main menu if you don't have a bootable ISO.

3. Choose ‘Bootable’->’Write disk image’ from main menu

4.Insert the USB drive you intend to boot from

5. Choose proper “Write Method”,USB-HDD+ is recommended

6. Hit “Write” to get a bootable USB drive

To prevent SysPrep from installing new/extra drivers when the universal image first boots, you need to change a line in your sysprep.inf file.  The line, which is under the [Unattended] section, you want to change is:  UpdateInstalledDrivers=Yes
You want to change this line to:  UpdateInstalledDrivers=No

I have used mysysprep before and have come across it not working correctly on certain machines during first boot when it does the SysPrep process.

For having the HAL change automatically, I would recommend using Offline SysPrep.

FAT16X is supposed to be able to format up to 4 GB drives.  It is FAT16 that could only format up to 2 GB drives.

It won't get caughty up with legal wrangling as it isn't going to be integrated into Windows 7, which having IE integrated in Windows XP was the issue before.  The article WinSuperSite says:

By not including it with Windows 7, this would avoid legal issues in the EU for Microsoft.

@JakeLD:  Here is the IBM page where you could download the IBM driver for ServeRAID 6m.  I thought that I would lend a quick hand by giving the link.  The date for the 2000/XP driver is 08-30-2004.

ServeRAID 6m

The "DriverSigningPolicy=Ignore" only applies to the SysPrep mini-setup, not for while preparing and sysprepping the machine.  Try out the following method for the preparing and sysprepping stages:
1.  Go to Start-->Run...
2.  Type in the following in the Run dialog box:  gpedit.msc
3.  Press Enter or click OK.
4.  In the "Group Policy" window that comes up, in the left pane, go to "Computer Configuration"-->"Windows Settings"-->"Security Settings"-->"Local Policies"-->"Security Options".
5.  In the right pane, go into the properties for "Devices: Unsigned driver installation behavior".
6.  In "Local Security Setting" tab, choose "Silently succeed".
7.  Click the Apply button.
8.  Click the OK button.
9.  Exit "Group Policy".

After doing that, try integrating the Mass Storage drivers again, but you may need to reboot before doing this so that the Group Policy takes effect.  If you get the same result as before, you will also have to disable "Windows File Protection" in addition to the method I described in this post.  "Windows File Protection" works with the "DriverSigningPolicy" and "Windows File Protection" is what causes the message you are getting.

To get the drivers to install during SysPrep:
1.  Extract all of the DriverPacks that you plan on using to the root of the C: drive. Now, it should be C:\D and all of the subdirectories of the different DriverPack categories.  If you DON'T plan on running the DriverPacks Finisher, delete all of the DriverPack INI files at the root of the C: drive.
2.  Copy the utility that comes with the DriverPacks BASE named DevPath.exe and place in in the SysPrep folder.  Run the utility from the command prompt.  You want to use the following command:  DevPath.exe C:\D.
3.  Copy the utility that comes with the DriverPacks BASE named makePNF.exe.  Run the utility from the command prompt.  You want to use the following command:  makePNF.exe C:\D
4.  In your sysprep.inf, add the following lines to the "[Unattended]" section: 
     UpdateInstalledDrivers=Yes
     DriverSigningPolicy=Ignore
     NonDriverSigningPolicy=Ignore
5.  If you want all of the DriverPacks to be cleaned up/deleted, you will need to have DriverPack Finisher run on first logon.  If not, skip this step.
     a.  Copy DPsFnshr.ini to the root of the C: drive, extract DPsFnshr.7Z to the root of the C: drive, and copy ROE.exe to the SysPrep directory.
     b.  Edit the line in the DPsFnshr.ini with "KTD =" so that is reads:  KTD = "false"
          Note:  This makes sure that the DriverPacks Finisher deletes all of the drivers and the files it used.
     c.  Save the changes to DPsFnshr.ini and exit the editor.
     d.  Run the utility ROE.exe from the command prompt.  The command you want to use is:  ROE.exe 937
          Note:  This will make sure that DriverPacks Finisher runs on the next logon, which should be your first logon after the SysPrep setup completes.
     e.  If you want the ATI software to install when there is an ATI video card installed, either create a dummy file named ATICCP.ins at the root of the C: drive if you want to have the ATI Catalyst Control Panel installed or create a dummy file named ATICCC.ins at the root of the C: drive if you want to have the ATI Catalyst Control Panel.  If you have an nVidia card installed and want the nVidia software installed, get your hands on the nvidia.ins file and put it at the root of the C: drive.  Also, with an nVidia video card, you may or may not want to include the PhysX DriverPack.
6.  Run your sysprep.exe from the command prompt using the following command:  sysprep.exe -bmsd
     Note:  This will build the Mass Storage section of your sysprep.inf
7.  If you want to include the MassStorage DriverPack into the Mass Storage section of your sysprep.inf, I recommend using FindHWIDs, found here, using the SysPrep option, as it will export the MassStorage format that you need for your sysprep.inf file.  If you don't plan on including the MassStorage DriverPack, skip this step. 
8.  Run your sysprep.exe from the command prompt using the following command:  sysprep.exe -quiet -forceshutdown -reseal -mini

Team:  If I missed anything, please let me know or edit this post.

I do coding in AutoIt as well. I'm not as good as Jeff is, though.  Any way, your AutoIt code looks correct.

Great job, jinkazama.  Could you make one that says "driverpacks.net team"?  If you could, I would appreciate it.  Thanks in advance.

@Overflow:  I've actually made a first logon window for a friend of mine using AutoIt.  It has a picture in the window along with information and the title bar says "Performing Installation and Configurations".  Most likely you wouldn't want the title bar, which it could be removed.  If you would like, I could send you my AutoIt script for this.  The only downfall, if you want to consider it one, is that the picture that you put in the window has to be located either on a hard drive in a pre-defined location by you or on the source in a predefined location also pre-defined by you, so that when the Finisher runs it will be able to display the picture.  If you would like me to send you my AutoIt script for this, just let me know and I'll send it to you.