I have a VB6 program which I sell for designing certain kinds of lathe
projects. My development base is an XP2 machine with MSDN installed.
Naturally, nothing fails on my machine.

Recently I added automatic program updating to the programs features using
the Internet Transfer Control (MSINET.OCX). MSINET.OCX is included in my
installation process and the program works fine on XP based machines. It does
not run on all Vista machines. On the erroring machines the message displayed
is "Component MSINET.OCX or one of its dependencies not correctly regestered:
a file is missing or invalid". Now I know that the component is present in
the same folder as the application and I know that wininet.dll is also
present on the target machines. Dependency Walker, run on my development
machine tells me nothing of interest even in the profiling mode and I don't
have a Vista machine to check on.

Can anyone help

Hi Bill

I don't mean to bounce you around, but there are some excellent MSDN Vista
Developer forums where you can speak directly to the Microsft Vista
developers.

MSDN Developer Forums:
http://forums.microsoft.com/MSDN/def...ID=24&SiteID=1


--

Ronnie Vernon
Microsoft MVP
Windows Desktop Experience


"Bill Kandler" <Bill Kandler@discussions.microsoft.com> wrote in message
news:C32CF1F5-31CE-4658-BAD2-2A0842ECC5A0@microsoft.com...
>I have a VB6 program which I sell for designing certain kinds of lathe
> projects. My development base is an XP2 machine with MSDN installed.
> Naturally, nothing fails on my machine.
>
> Recently I added automatic program updating to the programs features using
> the Internet Transfer Control (MSINET.OCX). MSINET.OCX is included in my
> installation process and the program works fine on XP based machines. It
> does
> not run on all Vista machines. On the erroring machines the message
> displayed
> is "Component MSINET.OCX or one of its dependencies not correctly
> regestered:
> a file is missing or invalid". Now I know that the component is present in
> the same folder as the application and I know that wininet.dll is also
> present on the target machines. Dependency Walker, run on my development
> machine tells me nothing of interest even in the profiling mode and I
> don't
> have a Vista machine to check on.
>
> Can anyone help

Not a very helpful response, but I'll take a look.

I've since revised my process to work with wininet.dll directly and I
believe that has solved the problem. Along the way, I discovered and fixed a
bug in the sample code provided on the MSDN library disc.

I've also learned that if the program is started using a right click on the
shortcut and the 'Run as Administrator' option is selected, the problem goes
away. User class dependent registration? Interesting concept for keeping
people away from where they don't belong but the error message received is
not at all useful.

"Ronnie Vernon MVP" wrote:

> Hi Bill
>
> I don't mean to bounce you around, but there are some excellent MSDN Vista
> Developer forums where you can speak directly to the Microsft Vista
> developers.
>
> MSDN Developer Forums:
> http://forums.microsoft.com/MSDN/def...ID=24&SiteID=1
>
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Desktop Experience
>
>
> "Bill Kandler" <Bill Kandler@discussions.microsoft.com> wrote in message
> news:C32CF1F5-31CE-4658-BAD2-2A0842ECC5A0@microsoft.com...
> >I have a VB6 program which I sell for designing certain kinds of lathe
> > projects. My development base is an XP2 machine with MSDN installed.
> > Naturally, nothing fails on my machine.
> >
> > Recently I added automatic program updating to the programs features using
> > the Internet Transfer Control (MSINET.OCX). MSINET.OCX is included in my
> > installation process and the program works fine on XP based machines. It
> > does
> > not run on all Vista machines. On the erroring machines the message
> > displayed
> > is "Component MSINET.OCX or one of its dependencies not correctly
> > regestered:
> > a file is missing or invalid". Now I know that the component is present in
> > the same folder as the application and I know that wininet.dll is also
> > present on the target machines. Dependency Walker, run on my development
> > machine tells me nothing of interest even in the profiling mode and I
> > don't
> > have a Vista machine to check on.
> >
> > Can anyone help
>
>