Doe's anybody knows how to...
Quote:
>>> >Hello!
>>> >Doe's anybody knows how to make only one installation disk for VB 4.0
>>> >application? I have much experience, but I can't put all the dll's
>>> >into a 1456 kb diskette. sux.
>>> Limit the amount of controls that you use. You can cut down on many
>>controls
>>> if you know the API equilavents (which will result in considerably more
>>> coding).
>>Sorry, Kevin. That won't cut it. In VB4, the minimum install doesn't fit
>>on a 1.44M floppy, even with no custom controls, JET access, or external
>>DLLs of any kind. This is because of the OLE files that need to be
>>installed along with the app.
>>Most of these files are primarily for WinNT 3.51 (or earlier) and Win3.xx
>>systems. WinNT4 and Win95 have the OLE files already installed. If you
>>are certain that your users already have these files, you don't have to
>>include them in your install disk set. Personally, I consider this too
>>risky. My best advice: use a CD-ROM to install from, instead of floppy
>>(or use Delphi or VC++ instead).
>>--- Nick
>Am I missing something in this continuing thread? Or misunderstanding
>something?
>I created an application for a car lot. It keeps track of inventory,
>moves sold cars out of inventory, keeps track of sales, etc. reads and
>writes to files, and has a pretty complex search engine within the
>code. (about 30 pages of small print)
>I did as was recommended and stripped out ocx files and refrences to
>unneeded libraries. (it's a 16bit application)
>Granted, I know the user has the correct VBrun - but it compiled to
>680k. nothing fancy, but it works.
>Am I missing something, when so many people say its not possible?
>clair rasmussen
The additional file space are other files besides the EXE. Your EXE file may
be smaller than 1.44 but other helper files may be needed (they may not), but
it is safe to include them. I think this is the idea behide previous posts.
-brian
Brian Davis
www.cis.com/briand
