PRB: Installing Applications from an HPFS Formatted Drive

Last reviewed: February 12, 1998
Article ID: Q179384
The information in this article applies to:
  • Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0
  • Microsoft Visual Basic Professional Edition, 16-bit and 32-bit, for Windows, version 4.0
  • Microsoft Visual Studio versions 97, 97sp1, 97sp2

SYMPTOMS

When running the application setup wizard from a network drive that is formatted as HPFS, one of the following two errors will occur:

In Visual Basic 4.0:

   C:\WINDOWS\ST4UNST.EXE Cannot read source file

In Visual Basic 5.0:

   C:\WINDOWS\ST5UNST.EXE Cannot read source file

RESOLUTION

To work around this problem, you can create the setup application onto floppy disks, or move the setup files from the HPFS volume to either a FAT or NTFS formatted drive.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The following operating systems support HPFS:

   OS2
   OS2 Warp
   IBM LAN Server
   NT 3.51 Workstation/Server
   NT 4.0 Workstation/Server

REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q100108
   TITLE     : Overview of FAT, HPFS, and NTFS File Systems


Additional query words: hpsf
Keywords : TlsSetWiz VB4ALL VB4WIN vb5all vbwin kbsetup
Version : WINDOWS:4.0, 5.0, 97, 97sp1, 97sp2
Platform : WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.