> I got the following from the customer:
>
> *****
> Problem identified - sort of.... I re-ran the install
> one more time after the failed one this morning, this
> time monitoring it with SysInternals "Process
> Monitor".
>
> I happened to filter down the events to a point where
> I could see the failed file access attempts, and
> noticed the that it was trying to use a bogus
> temporary directory under
> "C:\WINNT\system32\YSTE~1\TEMP". If I create the
> "YSTE~1\TEMP" subdirectory under the Windows directory
> C:\WINNT\system32, the installation does indeed
> succeed.
>
> I'm guessing the "YSTE~1" is an 8.3 name for system32,
> but I don't know why it wouldn't just use the existing
> system32 name itself. Can someone please comment? I
> do not consider this issue resolved (just worked
> around) until we understand why this is happening.
> This may be an issue we'll hit on other systems in our
> development environment.
> *****
>
> I looked at the accompanying screenshot of the Process
> Monitor; the file on which CreateFile fails is
> C:\WINNT\system32\YSTE~1\TEMP\fb_152.lck Do you have
> any insight as to why it can be happening? Our
> software is installed on thousands of computers and
> I've never seen this problem before.
>
> Thanks,
> Yuliya

if you issue SET a the prompt - what do you see? is the temp variable set
incorrectly?
Alan