I am dealing with a massive legacy program written in VB6. On start up, the program displays a splash screen and then calls a few COM DLLs to do some housekeeping like retrieving the user's registration info, default data paths, retrieving report headings, etc. On very rare occasions, if the user has (or had) Autocad installed, one of the calls to one of the COM DLLs results in the firing up of the Autocad installation server.

The user's computer will sit there until a disk with Autocad.msi is inserted or the user cancels.

What gives? I have no idea where to even begin to track this problem down. HELP!

Thanks,
Karl