lamaii

Found the problem My boot.wim file is Win7 SP1 My install.win is also Win7 SP1, however my sources DVD was Win7 (no service pack) So once I had replace all files in the sources folder (exlcuding boot & install wim) with Service pack 1 versions the error about adding the driver went away.

I've tested this again by deleting the winpeshl.ini in the boot.wim file, which causes the startnet.cmd file not to be run, and still get the same message box. My next step is to use an unmodified boot.wim file and check if I get the same message, as it's only since making changes to the boot.wim that I have seen this problem. Just tried using an unmodified boot.wim file and there is no change, need to figure out what is being called that is external to the boot.wim file which could be causing the fault. Another test I'm now going to try is to use a clean source with my modified boot.wim file. So I just tested a clean source and my modified boot.wim file and it's working fine. So it must be a problem with my current OS source disk or my modified install.wim file. I've had a seach around and see if there is a limit to the wim file and it appears not. my install.wim is currently at 12GB.

I don't get a error message box just the driver prompt window. ----------------------------------------------------------------------------------------------------------------- Load Driver A Required CD/DVD device driver is missing............................................................ Browse OK Cancel ------------------------------------------------------------------------------------------------------------------ I've attchached the setupact log, the setuperr.log file was empty. If I use "Shift - F10" then I can see all the partitions using diskpart and access the drives as they were formated using disk part. The mad thing is if I copy the boot.wim file to my WDS server and boot off the network then it see's the drives fine, when the setup.exe run's Here is my winpeshl.ini file [LAUNCHAPPS] x:\windows\system32\startnet.cmd %SYSTEMDRIVE%\sources\setup.exe

Fully understand what your saying now, will try and stick to that format. Cheers for your help. Lee

Changed the description of the thread as I was able to fix the last problem. What I am seeing now, is something I just don't understand. When I boot the system using a USB pen drive or DVD drive, all my scripts work but once finished I get an error message about windows cannot find a hard disk and requires drivers, however if I open up and command prompt I can see the drive with diskpart, and my script create the partitions so I know the drive is fine and working. However if I take the same boot.wim file and copy it to my test WDS server and boot form there it see the drive fine, and windows can install What the hell am I doing wrong!

Yep , BTW an issue for which we have NO idea WHAT was the cause, let alone the solution finally found by the OP.... jaclaz It was cause by changing the "HKLM\SYTEM\Setup\Cmdline" system registry and removing winpeshl.exe and replacing it with startnet.cmd. Very stupid mistake on my part.

I tested all three and none of them worked. As stated in my post I was causing the error by my lack of fully understanding of the wim environment.

Things you learn everyday, I'm just starting to make changes to the boot.wim and with XP being simple I figured Win7 would be the same (Skipped Vista thank...) but I think a little more reading is reqired. Google is a fine search tool but there is a lot of incurrent information, even microsoft have a fair amount of bad information, it's why I joined a forum like this. It cuts out the BS.

Found out I should be running the setup.exe in the sources folder, all is now working well

Thanks for the reply. After more mucking around, I've realised I've made a complete hash of things and have started from scratch. My error was to edit the registry, rather than creating a Winpeshl.ini file So I've not created a Winpeshl.ini file and diskpart is working fine however I'm now stuck on the formatting of the Winpeshl.ini. I just want it to run startnet.cmd and once processed start the windows installer. The file only has the following entry [LaunchApps] %SYSTEMROOT%\SYSTEM32\startnet.cmd After the startnet.cmd file runs it reboot the machine! what do I need to get it to continue the installation?

Sorry should have said, I have already run the following command "select disk 0" and run the "clean" command They run without error.

So, with thanks to the people in my last thread I've finally got the start of the system build Automated. However I'm having trouble with diskpart. I've using an Adaptec 5405 raid controller and tried a Raid 1 & Raid 5 setup. Using the adaptec command line tools I'm able to detect how many disk are connect to the raid controller and create the appropriate array. Once this is created the system reboot and then detects the array and run's a disk part script. This is the point where I'm getting problems, no matter if I use a diskpart script or type in the command line I'm getting the following error. DISKPART> create partition primary size=100 Virtual Disk Service error: The operation timed out. DiskPart has referenced an object which is not up-to-date. Refresh the object by using the RESCAN command. If the problem persists exit DiskPart, then restart DiskPart or restart the computer. DISKPART> I've manually tried to start the VDS service and it starts fine with no errors I've then tried to rerun diskpart but I get the same error Create the disk during windows install works fine

So after a week of head scratching I finaly looked into the registry and found the Winpeshl.exe, so changed that to startnet.cmd. Now able to dump all pre-installing commands I need then re-run the Winpeshl.exe at the end of the file. Thanks for your help.

Yer, I've got an old PE disk that uses startnet.cmd then runs an XP OS setup. On a standard boot.wim you have the 2 images PE & Windows setup, I take it that if I make changes to the startnet.cmd on the "Windows setup" wim then that will be processed prior to windows setup starting?

Had a play with MDT and I cannot get it to do what I need. I've got a fully Automated Win7 installation and that is all working fine. Currently all deployments are done off DVD's, I do have plans to move to WDS but the company I work for is FDA audited and making changes to how we build systems takes time due to the testing and documentation required. I've got a boot.wim file which I have injected all the required drivers & applications. The boot.wim file is a standard MS Windows 7 boot.wim from an install disk. All I need it to do is run a .cmd file before setup starts, but for the life of me I just cannot figure it out.