Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• !! Complete List Of WIL Errors !!
• !!Windows System Errors!!
• 1003 FileMove failed
• 1009 FileCopy FROM File Open Failed
• 1015 FileRename Failed
• 1016 FileDelete File Not Found
• 1022 waituntil passed time not in proper format
• 1028 Log Disk DirRemove Error
• 1029 DirMake Dir not created
• 1034 Clipboard Owned by Another Application
• 1036 Clipboard error
• 1077 File Open Failed
• 111 Encrypt Encode Verification Error
• 1129 OLE Initiate Failed Error
• 1207 snapshot out of memory
• 1300 DLL file not loadable
• 1330 When Compiling
• 1395 AddExtender Not a valid Extender
• 1422 DirAttrSet Directory not Found or Access Denied
• 145 Map Attempted - Cannot access net resource
• 1470 DiskInfo Function Failed
• 1478 BinaryHash BinarySort
• 1526 RegLoad-UnloadHive Access Denied
• 1588 Unable to Allocate or Lock Memory
• 1590 FileDelete Failed
• 1900 error level list
• 1905 winexec 5 Attempt to Dynlink to a Task
• 1915 winexec 15 error
• 1932 WinExec Errors
• 2001G Could not locate
• 3052 Unitialized Variable or Undefined Function
• 3067 Error when Installing
• 3074 Expression continues past expected end
• 3088 FileRead Error - Attempt to Read Past EOF
• 3096 Out of memory for strings
• 3101 Substituted Line Too Long (greater than 256 chars)
• 3132 OLE Error
• 3338 FP Math Illegal Floating Point Numbers
• 3357 Endif Match Not Found
• 3397 List Itemization - Could not allocate global buffer
• 3437 Extender Load Failed. Make sure 16 32 bit matches
• 499 Unrecognized Network Error
• 9000 Level Errors
• Application Error with WinBatch and Wise
• Batch DLL Initialization Error
• Call Error when Launching WB from another App
• Cannot Access File Error
• Cannot locate entrypoint SetHandleContext in kernel32
• Could not Allocate (or lock) Work Buffer
• DLL Initialization Err - INETMIB1 DLL
• DrWatson Error WBDDB32I!WinEnumXXXIcon
• Error 1004 FileMove FROM file open failed
• Error 1299 DLL Dll file not found
• Error 3353 Structure Too Complex Recursive UDF
• Error 3353 Structure Too Complex
• Error 998 on Banyan Vines Network Drive
• Errors 9012 and 9015
• Execution Error 111 Line too Long - Greater than 256 Char
• FileDelete and Access Denied
• FileRead Error 1591
• FileRename 1025 Error
• General Protection and Invalid Page Fault Errors
• How do I trap errors
• How to Check Exit Status Code of Program
• How to Suppress Error Displays
• How to trap error 3033 GoTo label not found
• Ignore Error and Return From Called Script
• IntControl 73 Not Capturing Error
• Internal Dynalloc Tag Overwrite Error
• Percent Sign in Comment
• RunWait Failing Segment Load Failure
• RunWithLogon 1932 All Pipe Instances are Busy
• SNMPAPI Dll Problems
• Trapping Win32 Network Extender Errors
• User Defined WB Error
• WBERRORHANDLEROFFSET
• Win95 Error upon Exit from Logon Script
• Windows 98 Error Codes
• Write Variable Table To File Upon Error

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Windows 95 Error upon Exit from Logon Script

Keywords:  performed an illegal command	 

---

Question:

I converted our WFW logon script to one that will run on Win95. The compiled WBT executes as designed, however, upon termination, Win95 reports that the program has performed an illegal command. When viewing the details, it looks like either the network extender or radmin32 gets an exception.

This executable resides in the NETLOGON share along with the requisite DLLs (www95...,wb..., radmin.., rlocal...). I feel that the error occurs when the netlogon share, Z: is released upon completion of the logon script processing and something doesn't get cleaned up properly. I can attach to NETLOGON after the fact and execute the WIL program with no problems.

Any suggestions about placement of the DLLs, or should they be ok in the NETLOGON share along with the compiled WIL program?

Answer:

The illegal operation is from the \netlogon share being pulled out from under your script. Here's my .BAT file for nt & 95 logons:

@echo off
@if "%OS%"=="Windows_NT" set NTLOGSW=/HIGH
@path=%PATH%;%0\..\SUPDLL
@start /w /max %NTLOGSW% %0\..\tstlogon.exe

The START /w eliminates the illegal operation, so long as you are only doing RunWaits (not waiting for a WinBatch program to finish will cause the problem again).

One way to eliminate these illegal operations is to explicitly connect \netlogon to LASTDRIVE-1 and do any runs from that drive. The drawback is that the drive is connected through the whole session.

The %NTLOGSW% helps a little bit with execution time on NT.
The SUPDLL in the path lets you take the .DLLs out of the \netlogon subdir, and then you can put them locally (you'll want a refresh routine in your script though). The idea is that \supdll protects you from missing DLLs letting you get WinBatch up (so you can replace them).

Regarding LMSCRIPT.$$$: a 0 length file with this name finishes the logon script. But leave a calling card so the LMSCRIPT closes on its own:

FLAG=Strcat(WINDIR,"\lmscript.$$$")
BLOWOFF=FileOpen("%FLAG%","WRITE")
FileClose(BLOWOFF)

I think the strange WFW behaviour might be related to the netlogon share persistency. If WFW doesn't think that the logon script has finished, then you'll have problems. (I had trouble with 95 and NT initially as I was just blowing the logon script window away.)

---

Article ID:   W12982

Filename:   Win95 Error upon Exit from Logon Script.txt

File Created: 2001:01:02:12:22:56

Last Updated: 2001:01:02:12:22:56