[RESOLVED] strange vb6 error

I was playing around with manifest files and the VB6 Resource Editor Addin. I made sure i deleted any resource files i added to my VB6 project (lets call it myApp). Now everytime I do ANY of the following:

1) start VB6 fresh (no projects open)
2) double click to start any vbp whatsoever
3) compile myApp.exe
4) run myApp.exe

I get the message "Please wait while Windows configures myApp". I click OK and then get the error(s):

"Error 1334. The file 'xxx' cannot be installed because the file cannot be found in cabinet file 'Instal01.cab'. This could indicate a network error, or an error reading from the CD ROM, or a problem with this package"

The message repeats while I hit cancel maybe 5 times.

Is this related to my playing around wiht manifest files and the vb6 resource editor adding? Anyone know how i can fix this?

Im running Windows7 and have tried rebooting.

Thanks in advance for any insight into this.

OK, I fixed the problem. I was, in fact, missing a true dll that myApp needed.

However, it still doesnt make sense to me why just starting VB6 would cause Windows to try to install it.

VB6 automatically (re)registers components etc when you open a project, presumably to eliminate errors based on them not being registered - which would be a far more common issue than the one you had.

The 'warning' you got was far from obvious, but unfortunately that is one of the joys of using a product that was replaced many years ago.

That sounds like the symptom you see when you try to use a component registered as "advertised."

Quote:

---

An advertised install is essentially a setup that runs without copying any files. Any registry entries, shortcuts, file types that are installed by your setup will be created - except the copying of the actual files. Because shortcuts are created and file types are associated with the application, the install seems complete to end-users.

Later, when an actual file type is opened or a shortcut clicked, the Windows Installer service automatically copies the necessary files and finalizes the installation.

---

In other words it is expected behavior, though it is possible for partial uninstals to trigger it unintentionally as well.

This has nothing to do with VB6 itself, and could just as easily occur with a program written using any other language.

thanks guys. Im a dinosaur, I know. :)