jbm
MemberContent Type
Profiles
Forums
Events
Everything posted by jbm
-
Drivers? If I'm injecting my drivers into install.wim is there any reason I have have the drivers folder on the DVD? During cleanup.cmd it always asks if you want to delete the drivers folder after reboot. But I'm wondering why it needs to be on the DVD at all, unless your using the setdriverspath in Autounattend.xml It also says deleting it will save space on the DVD but I dodn't see how.
-
@maxXPsoft regarding the error fernando 1 and other have reported. I uninstalled 6.1.0 and installed 6.1.1 with no problems. Then I uninstalled 6.1.1 and went thru the registry and removed any mention of se7en I also searched the c: drive and removed files or directries that had se7en in the name. Installed 6.1.1 and had the error. The screen at to bottom says wait and in my se7en directory there is a directory call appswithch.dat All I have to do to get the error is uninstall se7en then delete c:\se7en directory. Then reinstall
-
@Fernando 1 Thanks for these, I've been searching, trying to find a way to do this. I get this error on the 64bit drivers 2009-11-29 11:20:40, Error DISM DISM Driver Manager: PID=3884 Failed to install the driver package 'C:\zMountDir\Drivers\graphic\C7_91527.inf'. - CDmiDriverStore::Import(hr:0x80070002) 2009-11-29 11:20:40, Error DISM DISM Driver Manager: PID=3884 Failed to install the driver package 'C:\zMountDir\Drivers\graphic\C7_91527.inf'. - CDriverPackage::InternalInstall(hr:0x80070002) 2009-11-29 11:20:40, Error DISM DISM Driver Manager: PID=3884 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002) 2009-11-29 11:20:40, Info DISM DISM Driver Manager: PID=3884 Driver package C:\zMountDir\Drivers\graphic\C7_91527.inf failed to install. (hr:0x80070002). - CDriverManager::AddDriverPackagesFromCollection 2009-11-29 11:20:47, Error DISM DISM Driver Manager: PID=3884 Failed to install the driver package 'C:\zMountDir\Drivers\graphic\CH_91527.inf'. - CDmiDriverStore::Import(hr:0x80070002) 2009-11-29 11:20:47, Error DISM DISM Driver Manager: PID=3884 Failed to install the driver package 'C:\zMountDir\Drivers\graphic\CH_91527.inf'. - CDriverPackage::InternalInstall(hr:0x80070002) 2009-11-29 11:20:47, Error DISM DISM Driver Manager: PID=3884 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002) 2009-11-29 11:20:47, Info DISM DISM Driver Manager: PID=3884 Driver package C:\zMountDir\Drivers\graphic\CH_91527.inf failed to install. (hr:0x80070002). - CDriverManager::AddDriverPackagesFromCollection
-
Was able to delete both the upgrade and support folders and still complete the install. I feel kinda stupid tho, I should jave looked in the upgrade folder. I assumed it had something to do with upgrading to windows 7.
-
If I don't plan on ever doing an upgrade with my unattended DVD is it safe to delete the upgrade folder?
-
I would do both. This just seemed too good to be true to me. Bet if you went to Microsoft to buy another key they would charge a lot more that $16 dollars which is what the keys were selling on ebay whaen I lookled. Besides a key does no good with out the proper disk.
-
When processing my autounattend.xml file part of it always gets deleted and I have to edit it with notepad to add it back in. <DiskConfiguration> <WillShowUI>OnError</WillShowUI> <Disk wcm:action="add"> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>100</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Extend>true</Extend>[color="#FF0000"] <<This allways gets deleted[/color] </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>System</Label> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Label>Windows</Label> <Letter>C</Letter> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> </DiskConfiguration>
-
:Creating ISO After pack image a message box about logs being created pops up. The create ISO box is not clickable. I looked thru the logs but couln't see any errors. So I made an ISO with UltraISO and it instlled in Vmware with no problems. Had othe problems but they were fixed when I deleted the ini file and restarted se7en_UA Edit: one problem I was having is the drivers weren't injected at pack image.
-
In the right click wim your have to enter the number of the image you want to mount. for me I enter 4 for ultimate. Now when you right click on install.wim you'll have menus to mount or unmount etc the image that you've choosen. You won't beable check a box unless you've completed the previous one ie you have to copy dvd before addons is usable then add drivers etc.
-
Should never change folder I see you are at pack so go to uaDVD\sources, right click a .wim file and choose the zMountdir cleanup and try again if you have the Right click options. When it initially mounts after copy you should watch those windows and it prob tell you unable to cleanup zMountdir. Occasionally it does that. definitely need to leave everything alone, don't jack with the folders or have them open or nothing. Do that separately if you want after it copies and finishes. If it tell you unable to cleanup zMountdir, right then you should Cleanup the Mountdir. The command windows after DVD copy have always reported no errors. Right clicked on install.wim did a clean zMpuntdir and cleanup was successful. Tried packing image again with same error. So without doing a cleanup I rightclicked and did a mount image with R/W was able to look at the files in C:\zMountdir. Did an unmount then a cleanup tried packing again still failed.
-
That is exactly why I prefer to partition manually, each of my machines is different, and is too easy to wipe the wrong drive. Before I've always partitioned manually. Just had a bug to try something new. I keep backups of my backups for just this reason
-
Your code creates one primary partition (C:) and one extened partition with one logical drive (D:) Mine creates two primary partitions. (C: D:). Both will work as far as installing windows. The only reason I can see to create an extended partition is if you want to have a drive partitioned into more the four drives.
-
I found the problem Was trying to install to disk 1 when I changed it to disk 0 it worked. On my physical computer disk 0 is a eSata drive and disk 1 and 2 are internal drives. Guess I'll have to stick with manually choosing the partition
-
I had tested this on vmware with two disk drives and it was working fine. Then I decided to delete all the partitions. After that I got the following error So...
-
I modified this from what I use <DiskConfiguration> <WillShowUI>OnError</WillShowUI> <Disk wcm:action="add"> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>20000</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Extend>true</Extend> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>Windows</Label> <Order>1</Order> <Letter>C</Letter> <PartitionID>1</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Label>Data</Label> <Order>2</Order> <Letter>D</Letter> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> </DiskConfiguration> It creates a 20GB partion and a second that covers the rest of the drive. Both are Primary partitions.