I have a dilemma. I am trying to create a package for sale to potentially computer illiterate people. I am trying to making the process bullet proof. I am hitting my head against a brick wall. My application involves add on data files which need to be installed in the same directory as the program files. I decided I would write the location of the install to the registry. Then when I subsequently install I could read the registry to figure out where to do the second install. The problems are:
#1 - if they don't have the VB6 runtime installed, how can I read the registry to find out if and where they have installed my code? I could do this with Windows Scripting Host but they might not have that installed either. If I attempt to run a VB app without the run time package installed, I can't even trap the error to determine the runtime is missing - can I??
#2 - In typing this it just dawned on me that using the Package and Deployment wizard, I won't have the ability to write the location to the registry anyway - or is there something I don't know about the ability of PDW?
#3 - I have two computers and can't get a package to create on either one right now. My new machine says that it can't find setup.exe, setup1.exe, st6unst.exe, and vb6stkit. The old machine worked a couple of days ago - but now I am getting an error that the cab file can not be created and I should check the amount of disk space and access rights. I have 2.5 gig available. Is this a conspiracy to drive me freaking crazy? I have been working on this program for over a year and am finally ready to cut an install CD and I can't create the freaking package!