I get an error message (see bottom, for the error message) on all my win2k machines when I login in to our Novell Network. Here are the specifics: 1. Using Netware v. 5.1 2. Using Client v. 4.83.0.0 and v. 3.30.0.0 3. Error message only occurs on win2k machines, does not occur on win98/95. 4. Error message occurs when using both version of the clients listed above. It is not specific to either version. 5. No other symptops of software, network, security, or hardware problems. My network admin has searched and searched for the cause of this. She thinks is might be a force run coming from somewhere. Let me know if you can offer any suggestions or if you have seen this kind of situation before. (Feel free to email me, I am fairly new to Novell). Thanks. This is the error message: Can't run 16-bit Windows program (Title on the error message) Cannot find file \\FS1\SYS\Public\Client.SP3\WIN95\IBM_ENU\SETUP.exe (or one of it components). Check to ensure the path and filename are correct and that all required libraries are available.

Forgot to mention..... This also happens on client v. 4.81 Thanks, Matt

Is this the rest of the error message you get for the Can't run 16-bit..... "Can't run 16-bit Windows program ... The path is invalid."? As for your second error I read it that the "Setup.exe" file or "One of it's components" can not be found where something (An application, Batch file, etc.) is telling it to look at. In this case it is "\\FS1\SYS\Public\Client.SP3\WIN95\IBM_ENU\". This error message pretty much spells out exactly what the problem is. What happens when you go to the directory where the "Setup.exe" is located and try to execute it manually? Underdog V-Peace-V

I went to the directory path of the error message and there is not setup file. But Zenworks executes the same forced runs on the 98 machines, but does not give this error so the missing setup file is an avenue of concern. So I thought it might be a win2k thing, since it only happens on those machines. And Yes, both phrases in bold on the first message are the entire error message. Basically, some app or policy is failing to run on the win2k machines only. Thanks for the reply though Underdog. This forum gets hit with tons of requests, and it is always nice to get some attention. Matt

Don't give up totally. There are a lot of people on here that have tons more knowledge than I do. Just check back ocassionally, if you don't get your problem fixed. And if I run into anything I'll post back, if it's more definitive. Later! Underdog V-Peace-V

Matt... \\FS1\SYS\Public\Client.SP3\WIN95\IBM_ENU\SETUP.exe This is *not* the path for a setup of the Win2K client. What you are seeing is the attempted setup of the Win95/98 client on your Win2K workstations. You should also have a directory on your server for the 4.83 client for Win2K/XP. It is probably something like... \\FS1\SYS\Public\Client.SP3\WINNT\I386\SETUPNW.exe In the login script, there will probably be an entry that calls the ACU (automatic Client Update) routines. You may find that these are not properly set uo to refect the differences between the setup paths for 3.32 and 4.83 clients. Geoff Taylor IT Manager, Carine Senior High School Western Australia

SOLUTION 2 Can't run 16-bit Windows program. One of the library files needed to run \ is damaged. Please reinstall this application. CAUSE This problem may occur when a program attempts to access an incorrect version, outdated, missing, or damaged DLL file. RESOLUTION Expand the following files from the original Windows NT compact disc to the %SystemRoot%\System32 folder: Commdlg.dll Compobj.dll Ddeml.dll Ole2.dll Ole2disp.dll Storage.dll Ctl3dv2.dll Ole2nls.dll Stdole.tlb Typelib.dll Ver.dll Additional files may also be at issue. Check the %SystemRoot%\System folder for the correct version as well. Check for additional files elsewhere on the computer. Some files may be replaced by installing Microsoft Windows 95 or Microsoft Windows 98 versions in the System\System32 folder. NOTE: The Ver.dll file is located in the %SystemRoot%\System folder and the %SystemRoot%\System32 folder, and both versions have the same file size and date. To expand a file from the Windows NT CD-ROM, follow these steps: 1. Click Start, click Run, type cmd in the Open box, and then click OK. 2. Type the following lines, pressing ENTER after you type each line cd-rom cd i386 where cd-rom is the letter of your CD-ROM drive. 3. The files you may need are compressed in this directory and the file names will be truncated by one letter. For example, the Ntvdm.exe file is listed as the Ntvdm.ex_ file. To expand the Ntvdm.exe file to the System32 folder, type the following command: expand ntvdm.ex_ c:\winnt\system32\ntvdm.exe Repeat this step for each file in the previous list. NOTE: You should reapply the current service pack after copying the files from the product CD.