> > > > I've got the same problem but never used GBA-Renamer...
> > > >
> > > >
> > > > Old Japanese saying: Monitors may still work with a dead cap, but they
> will
> > > not
> > > > withstand a shotgun shell after I fall in the crocodile pit in Shadow
> Dancer
> > > 20
> > > > times in a row.
> > > >
> > >
> > >
> > > As I say in the post just below, it ALL went right after I ran the VPinmame
> > > SETUP.EXE file.
> > >
> > > Strange but that's life :)
> > >
> > Didn't work for me
> >
> I had this problem when the last set of vbs script files were updated...
> After downloading an active x manager to see what components
> needing updating i still had the same problem so i then had a look at the visual
> basic build visual pinball was using.
> If you look at Microsofts technical support page. URL
> http://support.microsoft.com/support/kb/articles/Q181/8/54.ASP you will see a
> patch for visual basic 5 which acts as a
> fixfile for this error (symptom 4 in the notes).
> I downloaded and ran this file and this error has yet to reoccur for me.(It
> updates some active x components).
> I am not sure if this was just luck but you might like to try it to see if this
> helps...
> Thanks to all at the WPC mame and Visual Pinball Forums for
> the great tables and to Shiva for his great support for all
> things pinball..
>
That didn't work for me the problem still occurs every time