[quote=“dvlsg, post: 5167, member: 1186”]Got it working as a Multi-Partition Single disk. It’s interesting that a Single Partition upload works for a VM with two partitions, but only a Multi Partition upload works for a VM with one partition.[/quote]

well it is not realy one partition as windows 7 has boot partition of 100Mb and it is counted as partition so you have a 2 partition image.
i usually get rid of the boot partition when building windows 7 images from scratch to make it easy when using cloning systems like fog.

i dont know about vmware player as i have vmware workstation but i use gparted ISO to boot from then shrink the disk. i used it once with a windows 7 image to reduse the size from 79 Gig to 38.

i have 8.0.1 and as i said it works after updating the kernel.

Hi mate
sorry for not responding fast as there are no mail notification here. i was going through the latest and found this. any way i would gladly upload my bzImage some where if you cant get it working and put a link on the forum.

Hi
I downloaded the latest kernel 3.2. used this link to build a custom kernel
[url]http://www.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]
enbled SCSI low-level drivers from the left side and VMware PCSCSI drivers support from the right side.
built the new kernel and it worked like charm
just to note that this command does not work anymore “[FONT=Courier New]make bzImage”. just writing make will fix the bzImage in case you need to update the wiki[/FONT]

Well mate i just updated to the latest kernel and still cant clone a vmware workstation. i have the driver for the vmware harddisk but is there a way to inject it into the kernel. i followed the walkthrough on how to enable the network drivers but it is just enable and disable.

as i said before. i am using 2 xml files “audit.xml and unattend.xml” and both are in “C:\windows \system32\sysprep” and i am using 2 patch files audit.bat where i have this command “C:\Windows\System32\sysprep\sysprep.exe /audit /quit /unattend:C:\Windows\System32\sysprep\audit.xml” after running the audit.bat the sysprep will import all the drivers into the system and then boot windows, at that point it will show you the GUI of sysprep just close it. i run the other phase of sysprep oobe.bat “C:\Windows\System32\sysprep\sysprep.exe /generalize /quit /unattend:C:\Windows\System32\sysprep\unattend.xml”
and here everything is getting done for deployment. why would you put your drivers into WinPE ??? you should put them into the Audit phase “look at my audit.xml” in the previous post. anyway it depends on your deployment method. this process is working for me and may be there are other ways out there but i couldnt find any better than this. i attached a copy of my audit.xml just try it and see if it works for you. as i said before just change the path to the drivers and the architecture.

[url=“/_imported_xf_attachments/0/30_audit.zip?:”]audit.zip[/url]

you need definitely to seperate the xml files. it didn’t work for me when i chose one xml file. as running the audit mode with unattend.xml will run some of the settings that should be run on the generalize mode and i lost one of the administrator logins " i have 3 logins after the generalize". i dont know why but it worked for me when i separated the files.

Hi
i am using windows 7 with multiple hardware support. i run 2 phases, the first phase is the sysprep with audit mode and audit.xml where i point the drivers in the audit.xml. after running sysprep with audit mode, i just generalize the imgae with the unattend.xml and generalize command. i put all the drivers in a folder in the root of driver but you can point it to what ever place you want. both the audit.xml and unattend.xml are placed in the c:\windows\system32\syaprep and i advice putting a script to delete the unattend.xml file on first boot.

the audit.xml file contains only this part
<?xml version=“1.0” encoding=“utf-8”?>
<unattend xmlns=“urn:schemas-microsoft-com:unattend”>
<settings pass=“auditSystem”>
<component name=“Microsoft-Windows-PnpCustomizationsNonWinPE” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“[url]http://schemas.microsoft.com/WMIConfig/2002/State[/url]” xmlns:xsi=“[url]http://www.w3.org/2001/XMLSchema-instance[/url]”>
<DriverPaths>
<PathAndCredentials wcm:action=“add” wcm:keyValue=“6873ff00”>
<Path>C:\drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
<cpi:offlineImage cpi:source=“catalog:windows 7 enterprise.clg” xmlns:cpi=“urn:schemas-microsoft-com:cpi” />
</unattend>
the only part that you may want to change is the “C:\drivers” and dont forget the processor architecture. you can put all your drivers there. i usually sort them after model type and hardware type.

Hi mate
am working on updating the kernel and trying to put the driver of vmware SCSI in it. i will inform you if i succeed. i just want to get some time so i can finish it.