Diskless Workstation Setup Err: Not Enough Space on Drive C

Last reviewed: June 17, 1996
Article ID: Q108655

The information in this article applies to:

Microsoft Works for Windows version 3.0

SYMPTOMS

When you install Works for Windows 3.0 on a floppy-drive-only workstation, and choose a Program Group for Works, Setup checks for the necessary disk space and then displays the following error message:

   Not enough space on Drive C:

The dialog box indicates that the space required/needed on drive C is 4K. Setup uses this disk space, which in Works version 3.0 must be available on a drive designated as drive C, to modify the AUTOEXEC.BAT and CONFIG.SYS files. Because diskless workstations by definition do not have a C drive, you will need to create one by mapping to a network server as drive C, using the workaround below, or upgrade to Works for Windows version 3.0a or 3.0b (full disk set required).

STATUS

Microsoft has confirmed this to be a problem in Works version 3.0 for Windows. This problem was corrected in Works version 3.0a for Windows.

WORKAROUND

NOTE: After you have completed the following steps, you can connect to the server where the Works shared files (files installed by SETUP /A) were installed, and run SETUP.EXE from there. The Works user's directory itself can be installed to any available share.

From the workstation, log on to a server.
From an MS-DOS prompt on the workstation, map (connect) to a network server as drive C. If you are on a Novell network, use the following command:
```
      map root c:=<server volume>:<subdirectory>
```
For example, to map to the USER\TEMP subdirectory on the default login server, type
```
      map root c:=sys:user\temp
```
where temp is an actual subdirectory on the server in the user directory.
Copy the CONFIG.SYS and AUTOEXEC.BAT files from the startup floppy disk to logical drive C (in the directory mapped in step 2).
If you skip this step, Setup will run, but will display the error message:
```
      Could not rename the file 'C:\AUTOEXEC.BAT' to
      'C:\AUTOEXEC.BAK'.
```
You could choose the Ignore button at this point, and the installation would finish, but an AUTOEXEC.BAT file with only one line (the Share command) would be created.
Make sure that Share (SHARE.EXE) is available on the startup disk, and that the boot disk is in the floppy disk drive.
Run the Works workstation Setup program. Note that Works itself does not need to be installed on the same share (drive C).
Copy AUTOEXEC.BAT and CONFIG.SYS back to the startup disk and make sure that the Share statement is similar to the following before restarting your system:
```
      A:\SHARE.EXE /L:500 /F:5100
```
NOTE: Share must be positioned in the AUTOEXEC.BAT file somewhere above a command that starts Windows or any menu program.

MORE INFORMATION

After Setup displays the "Not enough space" message, four options are available: Change Options, Install Now, Exit Setup, and Help. The Change Options command isn't pertinent because the only option listed, Custom Options, refers to the temporary file and is required. If you select Install Now, Setup will appear to continue successfully, but eventually the following error message will be displayed:

   Could not open the file named C:\AUTOEXEC.TMP.

At this point Setup is incomplete, with no program icons installed, so the best thing to do is reinstall using the map root workaround above, or its equivalent.

Note that the Works administrator's installation can be done without access to drive C.

For more information about the map root or other Novell commands, see your Novell documentation.

KBCategory: kbbuglist kbfixlist
KBSubcategory: wworkskb
Additional reference words: Netware LanMan Share Installation not enough
space nouvelle
w_works

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: June 17, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.