forum.vdsworld.com

[vtol]

Is there a DLL that can put VDSrun50.dll in a vds5 homemade EXE so it can run without the VDSrun50.dll externally?

I read a while back where an older DLL for $69 could do it, but cant remember its name or what it was for.

I wonder if GadGetX can do this...

Converting a VDS5 EXE to run in DOS would be nice too

Thanks

[FreezingFire]

While it's not a DLL, PGWARE's Alloy program can bundle different files into one single EXE file.

-FF

[vdsalchemist]

vtol,
GadgetX cannot embed the VDS runtime DLL into the Exe. The reason GadgetX would not be able to do this is because the VDS Exe loads GadgetX after it loads the VDS runtime DLL. FreezingFire is correct about the only program I know of that can combine the VDS runtime DLL into a VDS Exe is Alloy by PGWARE.
As for making a VDS 5 Exe into a DOS exe this is not possible since VDS 5 makes Win32 Exe's. However you can make a VDS 5 application run as a console 32bit application using my VDSConsole package here VDSConsole The package has a VDS tool that will convert the VDS Win32 Exe into a console application. It also includes a DSU that allows you to create the console window and read/write to that window.

[jules]

VDS 6, if it ever sees the light of day, will have the capability to do this (both integrated EXEs and Win32 console EXEs.) Personally I could never see the point of integrating the runtime, when a VDS EXE + runtime took up exactly the same amount of space, plus of course if you have more than one VDS EXE you immediately start saving space by having just one copy of the runtime instead of each program having its own copy. If every one of my VDS EXEs had its own copy of the runtime I'd probably need a second hard drive!

[FreezingFire]

Jules,

I can see where you're coming from and I agree with you that having only one copy of the runtime saves a lot of space.

However, I'm very glad that VDS 6 will have the option of integrating the runtime, because there are often situations that I need to distribute a single executable, which may need to be run in read-only situations where it cannot extract the runtime (if the runtime were extracted upon runtime). It also gives me peace of mind knowing the option is there when I need it.

-FF

[vtol]

yeah alloy, thats the one, couldn remember its name, thanks..

Concerning runtime DLL etc:
I meant I would also just use this feature very seldem, but when I use it it would also be handy everything in 1 EXE in certain situations where they dont want to mess with an installer or think about more than 1 file during use, maybe I'm just crazier than I first though

Will that console run in win98 DOS ?, Since XP doesnt have a place to stop and use a console before boot up, just curious, and what would a console be used for if not?

[jules]

A console application is just a Windows application that doesn't have a user interface. It's also a 32-bit application, so it can run in the 32-bit command window of NT/XP/Vista (just type "cmd" in the Run box.) The Windows 9x DOS is 16-bit, so that's why it won't run 32-bit console apps, though it can probably start them and they will run in their own separate command window (don't know for sure as it's years since I used that obsolete OS).

[vdsalchemist]

Vtol,
As Windows XP is starting press and hold the F8 key. If you catch it at the right time you will get a menu that will allow you to login via a command console.

Jules,
I think you are correct as far as Win9x systems go. There is a difference between a Windows PE file and a Windows 32bit console application's PE file which I am sure you are aware of
As far as integrating the runtime DLL goes there is 1 application that I have always wanted to build with VDS but have not been able too since version 2.5 and that is a Setup program. I really hate the fact that I have to use some other language to build a setup program with.

Ok I found a little program that will allow you to run Win32 console apps in DOS. Take a look at this DOS extender HX.

[jules]

I wrote a setup program in VDS. Since it was mainly intended for use installing VDS applications it uses the copy of the VDS runtime that is extracted to the temporary folder along with all the other stuff before the install starts. This makes for a nice small installer, only 44KB, plus I got the SFX stub down to about 19K (it's the one that comes with the official VDS Zip toolkit, with a few bits that aren't used hacked out.)

I have compiled my installer with the integrated runtime so I could use it with non-VDS apps. But then the installer overhead is about the same as using Inno Setup, which is a lot more functional. The non-integrated version could still be used if you don't mind including an otherwise redundant copy of vdsrun50.dll with your program - it doesn't take up any more space.

[vdsalchemist]

Thanks jules for the info... Size is not an issue as far as I am concerned... Ease of use by me and my customers is more of a concern for me. I currently use Inno setup and I can't stand it. It has it's on language which is not user friendly at all. VDS 5 is capable of doing everything that Inno setup can do with the exception of the fact that VDS 5 cannot integrate it's runtime. Now that I am done with my DLL I really can't stand writting code in other languages they just seem like a waist of time to me. I perfer VDS over all others due to the fact that it is simple and quick to build programs. The biggest problem I have with most setup programs is that they ask too many freaking questions. Who cares where you put the program just load it and lets go...

[DaveR]

[PGWARE]

I'd recommend against dismissing Innosetup so easily. It has been out on the market for several years and has been tested by several million users which have used installer applications to try various programs. I've found it to be one of the better installers out there which can properly install and uninstall applications on systems without errors.

There is a lot of work involved in creating an installer application that works no matter what system it is on and is as full featured as Innosetup. Sure it may pack a larger stub but people running Windows XP and higher likely do not have a 1 gb harddrive and for the most part are using higher speed connections.

[vdsalchemist]

PGWARE,
Hey I have no issues with the way that Inno Setup works. It is one of the best out there but it's not VDS. My point is why put all your effort into learning a programming languge just to need another programming language to install your software.

[vtol]

I forgot about XP F8, but if I remember if you use the DOSprompt selection, you have to wait for XP to load, then for it to load all the DOS drivers and then unload, then you finally get a DOS prompt (if your lucky) with the wrong CDROM DOS drivers

Yeah I use INNO, its great, and I wrote a VDS installer like Jules mentioned except it use's my regeistered version of Winzip self extractor.

Speaking of INNO does anyone know the line to delete a registry key during INNO uninstall? and a line to put a key in registry during INNO install would be nice too.


Thanks you all for your time and information

[PGWARE]

vtol for inno registry: