https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/930995&feed=atom&action=history
Microsoft KB Archive/930995 - Revision history
2024-03-29T05:24:21Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/930995&diff=227037&oldid=prev
3155ffGd: importing KB archive
2020-07-18T17:35:58Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB930995"></span>Some applications fail to sequence to specific drive letters =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 930995<br />
<br />
Article Last Modified on 5/14/2007<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft SoftGrid for Terminal Services<br />
* Microsoft SoftGrid for Windows Desktops<br />
<br />
<br />
-----<br />
<br />
<div class="symptoms_section"><br />
<br />
== SYMPTOMS ==<br />
<br />
Some programs that are sequenced by using the Microsoft SoftGrid Sequencer do not sequence to specific drive letters. Both Microsoft programs and third-party programs can be affected by this problem.<br />
<br />
</div><br />
<div class="cause_section"><br />
<br />
== CAUSE ==<br />
<br />
This problem may occur because the sequencing process of parsing and replacing specific drive letter information by using the %SFT_MNT% variable in case-sensitive registry keys can cause unexpected behavior.<br />
<br />
</div><br />
<div class="workaround_section"><br />
<br />
== WORKAROUND ==<br />
<br />
To work around this problem, use one of the following methods.<br />
=== Method 1 ===<br />
<br />
Configure the application to sequence to a drive letter other then the drive letter that is causing the problem.<br />
=== Method 2 ===<br />
<br />
Configure the application to sequence to the drive letter that is causing this problem. However, move the Package Root Directory one directory level deeper than the current level for the directory.<br /><br />
<br /><br />
For example, this problem occurs when the Package Root Directory has the following path on drive O:<br />
<div class="indent"><br />
<br />
O:\msoffice.v1<br />
<br />
<br />
</div><br />
Instead, move the Package Root Directory to the following path:<br />
<div class="indent"><br />
<br />
&quot;O:\SoftGrid\msoffice.v1<br />
<br />
<br />
</div><br />
After you move the directory, you would still select &quot;msoffice.v1&quot; as the Package Root Directory.<br />
<div class="indent"><br />
<br />
'''Note''' This modification requires that files that use a hard-coded path of O:\SoftGrid\msoffice.v1 are manually modified to use the path of O:\msoffice.v1 before you save the sequence. These files include such extension as .cfg, .config, and .ini.<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div class="status_section"><br />
<br />
== STATUS ==<br />
<br />
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.<br />
<br />
</div><br />
Keywords: kbtshoot kbexpertiseinter KB930995<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd