Basically, the purpose of this program is to minimize the amount of files downloaded from my web site to save bandwidth, and speed the install process for my users. For example, our company produces AdsGone popup killer from www.adsgone.com. It's 2.5 MB. Probably 2MB of this file is dlls and ocx's that are on most target systems already. What i'd like to have is a tiny stub program download to the client machine first instead of the full [url removed, login to view] install program. The first thing the stub program does is request a config file from my server. For example, this config file might be located at [url removed, login to view] This config file might look something like this: [system] [url removed, login to view] [url removed, login to view] regserver 1/1/2003 [url removed, login to view] [url removed, login to view] regserver 1/2/2001 [url removed, login to view] [url removed, login to view] regserver 2/1/2000 [url removed, login to view] [url removed, login to view] regserver 2/1/200 [url removed, login to view] [url removed, login to view] regserver 1/6/1999 [url removed, login to view] [url removed, login to view] regserver 1/6/2000 [windows] [run] [url removed, login to view] First of all, the format of this file can be changed. This is just a rough idea. Each entry names the zip file name but also the actual unzipped content name and a file date (one file in each zip file). This way you don't have to download the file before simply checking the name and date against what the user already has on the system. You would only download those items that needed to be downloaded (not there or out of date). The [system] section means all files should be unzipped to the windows system directory. Somehow, we need to make sure we can unzip the file on the target system (not sure on this, any ideas welcome) The "regserver" parm means the contents of the zip need to be registered e.g. regsvr32. The [run] section means this file needs to be downloaded last and run (which in this case would be the adsgone install that had NONE of the components in the install (would probably be 700KB or so). This way, the stub did the work of downloading only the components that were out of date or not on the target system. For example, the vbruntime dll compresses to about 600K but I think most windows systems already have this (not sure though). More below...
The stub downloader / installer would have to look something like a common installshield type dialog ith a status bar with status text like "downloading xyz.ocx..." "installing xyz.dll.." The program has to be smart enough that if the connection was lost, it would know enough to continue by downloading the last file it was working on (i'm not talking about parts of files, just don't do the entire list of downloads again). This would probably take care of itself since if it successfully downloaded the file before, it would already be on the target system. I would assume it best to create this program using only the most native windows api calls probably using c or c++ so this "stub" would be very tiny and require no install (just download and run). < 100KB would be great. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased.
needs to run on 98,me,nt sp6,xp,win2k should probably be written in C or C++