WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

DLLs

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

Use of Newer Network Extenders with Older Versions of Winbatch

Keywords:   Winbatch 97 98 99 Network Extenders 903 extender error newer version

Note: inorder to avoid these types of problems, we have renamed all the DLLs for the 2001A release.


Question 1:

I just got the 98 version of Winbatch. I see there are a flurry of new DLLs that go along with that. Will the WB98 Network extenders work with my EXEs compiled with versions of WB prior to 98?

Answer 1:

No. But here's the trick.

Rename your new WB98 Networking DLLs, for ex: WWN3X32I.DLL, WWN4X32I.DLL, WWW9532I.DLL and WWWNT32I.DLL to something like: 98WN3X32I.DLL, 98WN4X32I.DLL, 98WWW9532I.DLL and 98WWWNT32I.DLL, and then in your WBT files, where you use the AddExtender function, use the new 98 names for your AddExtender function. Then you can put the new DLLs out on your network along with your older DLLs and EXEs.

Question 2:

I have a TON of WinBatch scripts I compiled with version 97D of the WinBatch+Compiler, with the small EXE option for networked PCs. I updated to version 99C of the WinBatch+Compiler. When I updated, and tried to run an exe I compiled with the 97D version I recieved the error "WIL Extender Error: 903 wwwnt32i.dll :Need newer version of WIL Dll." I have both the old and new WIL DLL's (WBDBP32I.DLL and WBDBS32I.DLL) in the directory in which I am running the script from. The directory happens to be the NETLOGON directory.

It seems to me that the newer version of WWWNT32I.DLL, will not Run if the script is compiled with an older version of WinBatch! Yikes. I really do NOT want to, have to RE-Compile ALL my scripts with the newer version!....

ANY IDEAS?

Answer 2:

Same trick as previously mentioned.....

Rename DLLS:
Rename your new 99C Networking DLLs, for ex: WWN3X32I.DLL, WWN4X32I.DLL, WWW9532I.DLL and WWWNT32I.DLL to something like: WWN3X32I_99C.DLL, WWN4X32I_99C.DLL, WWW9532I_99C.DLL and WWWNT32I_99C.DLL, and then in your WBT files, where you use the AddExtender function, use the new "99" names for your AddExtender function. Then you can put the new DLLs out in the NETLOGON directory, along with your older DLLs and EXEs.
*See NOTE below regarding WWWNET32I.DLL

Or

Create a subdirectory:
You can put all of the 99 network extender dlls in their own subdirectory called 99_Extenders, then any new scripts that are compiled with the 99 version can point to the subdirectory in the AddExtender line:

AddExtender("\\Server\99_Extenders\extender.dll")

Note:

If you plan to use the the GENERIC network Extender WWWNET32I.DLL...
WWNET32I.DLL is a special "wrapper dll". Its job is to determine what platform the script is running on, and loads the appropriate platform specific extender. Therefore RENAMING this extender, doesn't necessarily work. The WWWNET32I.DLL only recognizes the filenames WWWWNT32I.DLL and WWW9532I.DLL. It is not going to recognize RENAMED network extender DLL's (WWWWNT32I_99.DLL and WWW9532I_99.DLL).

The way to solve this problem is to create a subdirectory with all of the networking dlls and point to the subdirectory in the Addextender statement, as mentioned above.


Article ID:   W13928
Filename:   Use of Newer Network Extenders with Older Winbatch.txt
File Created: 2001:03:01:12:14:08
Last Updated: 2001:03:01:12:14:08