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

• 1488 error when accessing -open with -wordpad menu option
• Adding Windows Filetype command to Right-Click Menu
• Assign FileMenu-entries To Drives
• Clipboard tricks problem
• Clipboard Tricks
• Error Too Many Menus
• FileMenu 32-bit on 64-bit
• FileMenu AddExtender Not Found
• FileMenu and 64 Bit Windows
• FileMenu and Variables
• FileMenu associate problem with exe files
• FileMenu Crash Win 8_1
• FileMenu Does Not Appear
• FileMenu Error
• FileMenu for all file types Problem
• FileMenu For Folders
• FileMenu Item Expanded Out and Duplicated
• FileMenu Running Slow
• FileMenu Usage and Limitations
• FileMenu with Explorer giving 3 Errors
• Full FileNames To Clipboard
• Get file extension association
• Remove Filemenu
• Running WBT from FileMenu
• Use FileMenu to Get FilePath and Copy File
• WinBatch FileMenus take up whole screen
• WinGetActive in FileMenu

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

FileMenu AddExtender Not Found

 Keywords:  FileMenu AddExtender File DLL Not Found 1394

---

Question:

I'm running 2005G on Windows XP but scripts called by Filemenu which use Addextender are throwing an error. This is only occurs with Filemenu. I've done some test scripts using Addextender and they run fine when executed directly.

I did a reinstall of Winbatch but the problem persists. There are not many called scripts involved so I've revised them to use the full filename in the Addextender lines but I would like to know if there is a fix for this behaviour.

Answer:

WinBatch performs extender dll searches in the following locations and order per MSFT documentation of the underlying APIs

1. The directory from which the application loaded.
2. The system directory.
3. The 16-bit system directory.
4. The Windows directory.
5. The current directory.
6. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. The App Paths key is not used when computing the DLL search path.

If the dll is not in one of the above locations, it will not be found unless path information is supplied. Also keep in mind that the Windows Shell is the reference application for FileMenu and not WinBatch.

---

Article ID:   W17880

Filename:   FileMenu AddExtender Not Found.txt

File Created: 2011:06:22:10:59:54

Last Updated: 2011:06:22:10:59:54