Certifications
Categories
RSS
Last web search to here
google xsx mouse cursors
antennae search .com
xsx alpha blended cursors
no add legacy on device manager
xsx alpha blended cursors
xsx alpha blended cursors
xsx alpha blended cursors
xsx alpha blended cursors
http://blog.tiensivu.com/aaron/archives/1823-Windows-7-fix-for-crashing-Windows-Installer-errors-cannot-install-or-uninstall-MSI-packages.html
kb982867
antennae search .com
xsx alpha blended cursors
no add legacy on device manager
xsx alpha blended cursors
xsx alpha blended cursors
xsx alpha blended cursors
xsx alpha blended cursors
http://blog.tiensivu.com/aaron/archives/1823-Windows-7-fix-for-crashing-Windows-Installer-errors-cannot-install-or-uninstall-MSI-packages.html
kb982867
Tuesday, February 20. 2007
2 confirmed BDD RTM bugs (mostly for people doing desktop deployments)
*Bug #1:*
Windows 2003 and Windows XP do not like the new Virtual Disk Service cylinder-alignment algorithm in WinPE 2.0 / Vista. You will know you are running into this issue when the machines you have just imaged bluescreen on boot. MS is working on getting updated fixes out for Windows 2003 and Windows XP.
In the meantime, there are 3 workarounds, before creating disk partitions in WinPE 2.0 or Vista:
1. Disable the automatic disk translation in the BIOS of the affected machines
or
2. Force use of the pre-WinPE 2.0 cylinder-alignment policy (no alignment) by setting the following DWORD registry keys to 0:
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\LessThan4GB
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\Between4_8GB
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\Between8_32GB
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\GreaterThan32GB
or
3. Use BDD/WIM to deploy Vista machines and get rid of the XP images.
*Bug #2 (thanks to Steve6375):*
Deleting 2 images within a WIM without an /append operation in between will corrupt the WIM image overall.
Update on bug #1: KB 931760 contains an updated kernel for Windows XP to avoid this issue!
Windows 2003 and Windows XP do not like the new Virtual Disk Service cylinder-alignment algorithm in WinPE 2.0 / Vista. You will know you are running into this issue when the machines you have just imaged bluescreen on boot. MS is working on getting updated fixes out for Windows 2003 and Windows XP.
In the meantime, there are 3 workarounds, before creating disk partitions in WinPE 2.0 or Vista:
1. Disable the automatic disk translation in the BIOS of the affected machines
or
2. Force use of the pre-WinPE 2.0 cylinder-alignment policy (no alignment) by setting the following DWORD registry keys to 0:
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\LessThan4GB
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\Between4_8GB
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\Between8_32GB
HKLM\System\CurrentControlSet\Serivces\VDS\Alignment\GreaterThan32GB
or
3. Use BDD/WIM to deploy Vista machines and get rid of the XP images.
*Bug #2 (thanks to Steve6375):*
Deleting 2 images within a WIM without an /append operation in between will corrupt the WIM image overall.
Update on bug #1: KB 931760 contains an updated kernel for Windows XP to avoid this issue!
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
re. #1
Simplest solution is to use ALIGN=16065 in all DISKPART create partition commands. This may leave gaps of up to 32Mb between partitions but works.
Bug #1 also applies when installing Vista or WinPE too.
Simplest solution is to use ALIGN=16065 in all DISKPART create partition commands. This may leave gaps of up to 32Mb between partitions but works.
Bug #1 also applies when installing Vista or WinPE too.
Steve,
Re: your comment about using the ALIGN=16065 as a solution for the thread "2 confirmed BDD RTM bugs (mostly for people doing desktop deployments)", could you comment further on where you are using this ALIGN.
We use Symantec Drive Image (v5.0) to deploy our XP image and now, on Vista-installed machines, we are seeing the Error 105(Partition wrong boudary start) and I was wondering if this would pertain to us. I cannot find anywhere that we use the ALIGN parameter. All replies appreciated.
Scott
Re: your comment about using the ALIGN=16065 as a solution for the thread "2 confirmed BDD RTM bugs (mostly for people doing desktop deployments)", could you comment further on where you are using this ALIGN.
We use Symantec Drive Image (v5.0) to deploy our XP image and now, on Vista-installed machines, we are seeing the Error 105(Partition wrong boudary start) and I was wondering if this would pertain to us. I cannot find anywhere that we use the ALIGN parameter. All replies appreciated.
Scott
You use this in WinPE v2 or Vista DISKPART command
e.g.
DISKPART
CLEAN
SEL DISK 0
CRE PAR PRI SIZE=10000 ALIGN=16065
format FS=NTFS quick
exit
would wipe the disk and make a 10GB partition.
Vista and WinPE, when they create a partition, do not start a partition at whole cylinders which was the normal convention.
Normally the first partition starts at the 2nd track, but Vista utilities leave/need more space as ETFS requires a larger area for boot code. So a partition created by WinPE/Vista starts at about 1024 sectors in instead of 63 sectors (1 track). As most dos/XP tools think that partitions should start on either the 2nd track (sector 63) or a cylinder boundary then these tools get upset. Indeed XP will not install from a CD if the partition was created by Vista.
The solution is to not use Vista/WinPE to create your XP partitions or to use the ALIGN=16065 command and Diskpart.
Note that this only works on systems that use 255 tracks per cylinder and 63 sectors per track for LBA translation (255x256=16065). Some PCs and notebooks use 240x63 - so for these you use ALIGN=15120 instead.
HTH
Steve
e.g.
DISKPART
CLEAN
SEL DISK 0
CRE PAR PRI SIZE=10000 ALIGN=16065
format FS=NTFS quick
exit
would wipe the disk and make a 10GB partition.
Vista and WinPE, when they create a partition, do not start a partition at whole cylinders which was the normal convention.
Normally the first partition starts at the 2nd track, but Vista utilities leave/need more space as ETFS requires a larger area for boot code. So a partition created by WinPE/Vista starts at about 1024 sectors in instead of 63 sectors (1 track). As most dos/XP tools think that partitions should start on either the 2nd track (sector 63) or a cylinder boundary then these tools get upset. Indeed XP will not install from a CD if the partition was created by Vista.
The solution is to not use Vista/WinPE to create your XP partitions or to use the ALIGN=16065 command and Diskpart.
Note that this only works on systems that use 255 tracks per cylinder and 63 sectors per track for LBA translation (255x256=16065). Some PCs and notebooks use 240x63 - so for these you use ALIGN=15120 instead.
HTH
Steve
Also note that if you use Microsoft Deployment (the newer BDD 2007, aka BDD 2008), one of the default task sequences is to provide a workaround for what is now called the 'uberbug'. It is disabled by default, and crippled by default, unless you patch Microsoft Deployment with my .ZIP file from my site or manually fix it with the instructions from http://blogs.technet.com/msdeployment.
Most people are still using BDD 2007, but I have been diving head first into Microsoft Deployment lately.
Most people are still using BDD 2007, but I have been diving head first into Microsoft Deployment lately.
Search this blog
Links
My e-mail address
Exchange:
Hotfix Tracker (All products)
OCS:
OCS 2007 R2 Documentation Collection
Office:
Office Cumulative Updates Site
Windows:
Other:
FriendFeed
IM me on Live Messenger
Translate this page
Calendar
|
April '18 | |||||
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||
