Windows XP SP3 upgrade affects GINA

  • Thread starter Thread starter Lisa L
  • Start date Start date
L

Lisa L

Has anyone seen or read any problems with upgrading from Windows XP SP2 to
Windows XP SP3, which results in removing a third party GINA?

Not only is the GINADLL entry in the Registry reset to MSGina.dll, but third
party GINA product has its uninstall called to fully remove it.

Is this a known issue?

Lisa
 
I recently upgraded a friend's PC to SP3 after a Clean Install of XP SP1.
In this case it's LinkSys's GTgina.dll that was causing a problem and I had
to remove it. For the record I installed SP3 first and then installed the
LinkSys
software.
 
The third-party software is software that we produce.
Our log file shows that our "uninstall" was run.
It is claimed, that upgrading to Windows XP SP3 caused the uninstall for our
GINA product to be activated and completed.
 
Thank you JS.

I am fammiliar with all that information.

I am trying to see if there is anything about Windows XP SP3 that when
upgraded to would remove existing gina's and restore the MSGina.dll.

Is there some Windows setting that if configured would force the
removal/uninstall of the non-default GINA during the upgrade to XP SP3?

Lisa
 
When you install your version does it have the same
(identical) dll name?

Also check the registry for your gina vs msgina.dll
do you find two separate reg entries or only one?
 
JS

the name of our GINA is ginastub.dll, not msgina.dll.

the uninstall.log for our product shows that the uninstall procedure was
run, as if it was done from the Add/Remove programs.

The user tells us that Windows XP SP3 was being upgraded at the time that
the corresponds in our uninstall.log. The user claims that he did not run
the uninstall and that it must have been Windows XP SP3.

This seems impossible to me, but I am not an expert by any means on the
various things that can or can't happen with Windows XP SP3 upgrading.

Lisa
 
I taking a leap of faith on this as I don't know
what the software product is, but here goes.

You gina has "stub" as part of the name, which
normally means it's serves as a stub. More clearly it is:
"A data file or program that stands in for the original file"
suggesting it was designed by your software developers
to at least intercept some or all of the calls to Microsoft's
msgina.dll

Microsoft's msgina.dll was updated as part of Service Pack 3.
Now doubt that during the SP3 install process msgina.dll was
re-registered in the registry. This would override you ginastub file.

As to why it was physically uninstalled I'm really taking a leap of faith
here
but I suspect your software product may use an .MSI installer and
somehow the uninstaller is being evoked. Without looking at you install and
uninstall .msi file I can't tell you any more.

One thing you could try is install your product on a test pc
that has XP SP2 installed. The rename your uninstaller file.
Install XP SP3 and see what happens, I suspect your application
will still be broken because of the registry change by SP3 but your
ginastub.dll should still be located in C:\Windows\system32 where
I suspect your software team installed it.
 
JS

thank you for your leaps of faith.

Our GINA is a pass-thru GINA.

We, however, use InstallShield to install it.
That is not to say that someone can't put an MSI around it to push it out
and silently install the kit.

When we did our testing of Windows XP SP upgrades on a system with our GINA
on place, we did not see this problem.

I will seek to get confirmation on whether our GINA was pushed out with MSI
to see if there is a chance that your "leap" has 'legs'.

Lisa
 
Back
Top