forum.vdsworld.com

kc7aad

OK.. Another dumb question maybe, but I can't seem to figure out how to include a DLL into my script.. Or if I need to..

I ahve a created a small GUI for a DOS Program. I went to try and install it on a machine, and said it couldn't find VDSRUN50.DLL. So I cheated and copy and pasted the dll file to the other machine.

My question is... Is there a way to add it to the program when it is compiled, and have it put this file in the \WINDOWS\SYSTEM directory automatically??
I am using Inno Setu for a n installer to add the DOS Program files and scripts that I am using for this GUI, so I have it send all of the files to C:\IPERF. But then I have to go and put the dll where it needs to be in order for the program to work. Maybe Inno can add it where it needs to be too??? I haven't figured out how if so.

Thanks for all of your helps already! Have been browsing thru post from the last few years about all sorts of stuff, with already more luck than any other programming language!!

Rod

webdaddy · Posted: Sun Oct 16, 2005 11:28 pm Post subject: VDS Runtime

You dont need to include it in the script. You have to place the dll either in the path (Windows Directory) so your compiled EXE can find it or in the install directory along with your program. You do not need to load the DLL as it is loaded automatically as long as its in the path or same directory as your compiled binary file.

WD

webdaddy · Posted: Sun Oct 16, 2005 11:29 pm Post subject: Inno Setup

I also use Inno setup. You can simply copy the DLL to your program directory and then in Inno setup include the entire directory and tell it to include all files underneath it. Once you build your setup.exe file it will then be included in your distribution.

WD

vdsalchemist · Posted: Mon Oct 17, 2005 12:03 am Post subject:

kc7aad,
The vdsrun50.dll is the runtime DLL that is required for the Exe to run. Webdaddy is correct you do not need to directly load or include this DLL in your script. Most VDS users use either a setup program or they use a program called Alloy. You can purchase Alloy from http://www.pgware.com
Alloy will allow you to combine the runtime dll with the Exe to make a single Exe. This is the option that I use for simple utilities and small applications that do not require lots of files to be delivered with the application.

kc7aad · Posted: Mon Oct 17, 2005 3:57 am Post subject:

So it DOES NOT need to be in the SSTEM Directory?? It could be in the c:\IPERF Directory where all of my other files and scripts this GUI uses are???

ShinobiSoft · Posted: Mon Oct 17, 2005 4:04 am Post subject:

That is correct Smile

vtol · Posted: Mon Oct 17, 2005 8:44 am Post subject:

I like having INNO SETUP put it in the C:\WINDOWS\SYSTEM32 while installing my program, you just need to add the line below to the [Files] section and adjust your source folder C:\redist-v502 to where ever your vdsrun50.dll is located.

SnarlingSheep · Posted: Mon Oct 17, 2005 4:59 pm Post subject:

Keeping the vdsrun dll in the system directory prevents scattering the same dll all over a user's system. If they use more than one VDS program from you, they will have the vdsrun in each program's folder that they got from you.

PGWARE · **Web Host** Joined: 29 Dec 2001 Posts: 1565

* sends dragonsphere a royalty check for the Alloy promotion *

kc7aad · Posted: Mon Oct 17, 2005 8:44 pm Post subject:

Thanks VTOL.. I was thinking that you could do it thru INNO, but couln't figure it out!

Thanks for your help again, folks!!!