| View previous topic :: View next topic |
| Author |
Message |
tim6389
Professional Member
Joined: 01 Aug 2002
Posts: 790
|
 Posted: Fri Aug 02, 2002 2:02 am Post subject: loading dll's |
 |
|
hello
i'am trying to run a script for the first time i donwload the ddl's i need BUt when i try to run the script i get extreanl libary not avaible how do i get the dll to work?
thanks |
|
| Back to top |
|
 |
SnarlingSheep
Professional Member
Joined: 13 Mar 2001
Posts: 759
Location: Michigan
|
| Posted: Fri Aug 02, 2002 2:18 am Post subject: |
|
|
when loading a dll without specifying a path(EXTERNAL vdsipp.dll), VDS looks in the folder the script is in and also in the Windows System folder. So you need to do one of the following.
1.) Move the DLL to the same folder as your script.
2.) Move the DLL to the System folder
3.) Specify the path to the DLL(EXTERNAL C:\Folder\Folder\vdsipp.dll
I don't recommend number 3 if other users will be using a program you make as they might not have the same path.
_________________
-Sheep
My pockets hurt... |
|
| Back to top |
|
|
Tommy
Admin Team
Joined: 16 Nov 2002
Posts: 746
Location: The Netherlands
|
| Posted: Fri Aug 02, 2002 2:30 am Post subject: |
|
|
Personally I would recommend the following:
| Code: |
directory change,@path(%0)
external vdsipp.dll
|
VDS tries (part of copied from the Windows 95 Programmers Guide):
1. The directory from which the application is loaded (if running in the IDE, this is
the directory of VDS.EXE, not the script's directory!);
2. the current directory (not neccesarily the script's directory!);
3. Windows 95: The Windows system directory.
Windows NT: The 32-bit Windows system directory.
4. Windows NT: The 16-bit Windows system directory.
5. The Windows directory.
6. The directories that are listed in the PATH environment variable.
I use "directory change" so that the current directory is changed to the script's
directory. Then I use "external" without any path so that the directory could be
located either in the current directory, or one of the other paths such as the
system directory.
If I were to use "external @path(%0)vdsipp.dll" directly, the DLL could only be
found in the script's directory, and not one of the alternatives such as the system
directory.
Tommy |
|
| Back to top |
|
|
tim6389
Professional Member
Joined: 01 Aug 2002
Posts: 790
|
| Posted: Fri Aug 02, 2002 2:35 am Post subject: thanks |
|
|
thanks guys i got it to work  |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
@vdsworld