Why Does Debug Message Come Up When Installing WinBatch over a Network?
Keywords: debug installation FileRename error
Question:
I have a server license, and I'm trying to install WB over a network from Windows 95 to a Novell server, and the debug message is coming up, "FileRename Error". My directory is read/write and I have enough disk space. I have the netware client. Any idea of what the problem might be?Answer:
We install the file with a strange name onto the server, then rename it to the name we want. Somehow you do not have permission to rename files.Here are some possible explanations:
- Is there some kind of network policy that prevents files from being renamed?
- Perhaps an overly zealous virus scanner is going beserk trying to prevent a file from turning into an exe or something.
- Sometimes you can get this message when installing over a network drive. Copy all the files to the local drive and install from there.
- The server must support long filenames. This includes Netware NETX and VLM drivers. You'll need to use the 32-bit client provided by Novell, or the Win32 client from Microsoft. NetWare servers must be configured to use the OS/2 namespace (which emulates the native OS/2 NPFS file system) in order for Windows 95 to see long filenames on them. To configure the Netware server to use the OS/2 namespace, take the following steps:
- On the Netware server, type the following commands at the prompt:
load os/2 add name space os2 to volume sys- To the file Startup.cnf, add the following line:
load os2- Shut down the Netware server. Copy the file OS2.nam from your Netware diskettes or CD-ROM to the disk and directory on the Netware server that contians the file SERVER.EXE.
- Reboot the Netware server.
Article ID: W13387Filename: Debug Message Comes up During Installation over Network.txt