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.

Error 1300: DLL file not loadable

Keywords: dllcall dll file not loadable error 1300

---

If you are getting Error 1300: DLL file not loadable, then the problem may be that you are DllCall-ing a 16-bit DLL with the 32-bit version of Winbatch, or vice versa. Make sure you're using the 32-bit version of both, or likewise, the 16-bit version of both.

For some reason the DLL could not be loaded.
32 Bit WinBatch can only load 32 bit DLL's. 16 Bit WinBatch can only load 16 bit DLL's.

The message indicates we can find the file, but that we do not like it for some reason. Possible reasons include:

1. Trying to load a 16 bit DLL from 32 bit WinBatch (or vice versa)
2. Dll file corrupt on disk
3. DLL file locked by another application (If this is the case set DLL to read only)
4. OS out of file handles (rare)
5. Other supporting DLL's not available.

In WinBatch version 96D and later versions of Winbatch, DllCall/DllLoad now also look for the specified DLL in the directory where the WIL Interpreter application is located.

Question:

I've created a compiled WinBatch exe which calls a 32-bit dll. Calling the "DllLoad" function when running the exe on a WinNT machine it works fine. Calling the "DllLoad" function when running the exe on a Win95 machine I get "Error 1300: DLL file not loadable".

The dll file in question I've written using VB50 and VisualDLL. It is purportedly a 32-bit dll. DLL and source available on request. Any suggestions you can provide would be appreciated.

Answer:

Seems like the DLL has been marked NT only somehow. Can you use it yourself in Win95?

Or otherwise, the DLL references other DLLs not on your Win95 system.

---

Article ID:   W12942

Filename:   1300 DLL file not loadable.txt

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

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