Last-modified: 22-Aug-95
Hope this makes it easier for Our Regular Readers ;-)
Follow the instructions in SETUPK.TXT exactly. The files actually belong in two separate directories. Not placing them correctly can create strange and unusual side effects -- none of them good(!)
Set all involved EXE, DLL and VBX files to Read-Only so that the setup program doesn't modify them. [Charles F. Mulks (21667cfm@msu.edu)] A *very* good tip. Actually, make all executables on your system read-only. If not, you can get a sharing violation if you try to run the same DOS executable twice at the same time. Also, the source code for a SETUP program is *included* with VB3 Pro. It is quite trivial to tailor it to your specific needs.
The question remains: Is SetupWiz good? No! Good enough? Perhaps.
[Top of Page][Table of Contents][Top of FAQ]
There have been some rumours on the newsgroup that you can't redistribute programs written with VB freely. This is nonsense. All applications created with VB can be redistributed freely without royalties (as long as you don't distribute proprietary external files).
The rumours probably originated when Microsoft announced that they will not sell kits allowing third-party software to include the Visual Basic for Applications (VBA) system.
[Top of Page][Table of Contents][Top of FAQ]
There are also a few global variables you will want to change. All of this is contained in the comments in the code.
Using this, and the distribution information in the manual telling you about which files to distribute with your app will make things much easier than using the setup wizard (IMNSHO). There are also several third party setup products available. [George Tatge (gat@csn.org)]
[Top of Page][Table of Contents][Top of FAQ]
[Top of Page][Table of Contents][Top of FAQ]
[Top of Page][Table of Contents][Top of FAQ]
Your setup program will need to create a .BAT file to expand and then copy these files. Then, it will need to shutdown Windows (see ExitWindowsExec API call) and run the .BAT file. Then it will need to restart windows and continue your setup program. Your setup program should delete the temporary .BAT file that is no longer needed. [George Tatge (gat@csn.org)]
[Top of Page][Table of Contents][Top of FAQ]
If you have written private VBXs or DLLs that will never be used by any program but yours, you can install them in the same directory where you install your application files.
There are lots of good reasons for doing this, but it makes a short novel to rehearse them all. [George Tatge (gat@csn.org)]
[Top of Page][Table of Contents][Top of FAQ]