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.

RunWait Failing: Segment Load Failure

Keywords: RunWait Failing Segment Load Failure

---

Question:

When using RunWait, why does WinBatch continue before the program has finished loading?

Answer:

The @wait flag simply holds the next WIL instruction until the EXE launched by RunShell has completed. Note: This can be fooled by what we call the "loader program problem". For testing purposes, add a message statement immediately after the RunWait or RunShell(..@wait) statement to verify that the message box pops up at the expected time. If it pops up early, then you are probably dealing with a loader program problem.

Many programs now have "Loader" programs which call the REAL EXE, launch it and then exit. When the "Loader" EXE exits, WinBatch continues with the script. Then, if your next command is a detach, the network connections are being deleted before the REAL EXE has had a chance to finish loading. This can cause a "Segment Load Failure", or at the very least doesn't work as expected.

You can fix this in one of two ways:

1. Find out the real name of the EXE. You can launch the WinBatch.exe, from there you can select "Determine Owning EXE File" from the list of options. Put the mouse pointer on the program and the dialog box will display the REAL EXE name. Then use this EXE name in the AppWaitClose function, as follows:

           Run("xxx.exe", "")
           delay(3)
           AppWaitClose("EXEname.EXE")
   

2. Instead of using RunWait, use a Run function in conjunction with a WinWaitClose.

           Run("xxx.exe", "")
           delay(3)
           WinWaitClose("MainWindowName")
   

Another Segment Load Failure Question:

Why am i getting a wbcmpl16l.dll cause segment load failure in wbdbfl16i.dll 0008:00002286 error?

Answer:

Because either your script or something else is breaking a network connection between the compiled winbatch script and its DLL. Make sure you're putting the WinBatch DLL in the same directory as the compiled WinBatch EXE so that WinBatch can find its DLL.

---

Article ID:   W12980

Filename:   RunWait Failing Segment Load Failure.txt

File Created: 1999:04:15:16:50:56

Last Updated: 1999:04:15:16:50:56