Batch File Calling CD Command May Not Run on Shared Drive Using HPFS

View products that this article applies to.

This article was previously published under Q183493

Expand all | Collapse all

SYMPTOMS

When a Windows 95-based computer runs a batch file at a command prompt that calls the CHDIR or CD (change directory) command on a connected share on a drive using the HPFS file system, the batch file may not run any command in the file after the change directory command.

Back to the top

CAUSE

In Windows 95, a check occurs during the execution of the batch file to determine the type of file system in use. When the HPFS file system is returned (as an unsupported file system), Windows 95 attempts to read the file again using the new path defined by the change directory command. Because the new path does not contain the original batch file, the error message "Batch file missing" is generated.

Back to the top

RESOLUTION

To resolve this problem, download the following file from the Microsoft Download Center. Click the file name below to download the file:

Vredrupd.exe (http://download.microsoft.com/download/win95upg/vredir/1/w95/en-us/vredrupd.exe)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (http://support.microsoft.com/kb/119591/EN-US/ ) How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

This fix for Windows 95 and OEM Service Release 2.x should have the following file attributes (or later):

File name     Version    Date      Time     Size   
---------------------------------------------------------   
Vredir.vxd    4.00.1118  1/16/98   2:32pm  156,773 bytes

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95, Microsoft Windows 95 OEM Service Release 2 (OSR2), and Microsoft Windows98. There is currently no resolution for this issue in Windows 98.

Back to the top