ginadll -- dotnet academic

dotnet academic : ginadll

Jamie
9/21/2003 9:04:14 PM

My machine set the default login to my account and now xp always opens to
that account. My roommate sees everything I do. Help me to disable it,
please. There is a winlogon section of the registry that is under
...HKLM/software/microsoft/windows nt/current version/winlogon which has all
my info in it...

How do I stop it?

Giac

Alfred C Thompson II
9/21/2003 10:19:45 PM

From the control panel go to user accounts. Once there change you account to
add a password. It's pretty straight forward once there.

[quoted text, click to view]

JoeShmoe
9/22/2003 7:21:56 AM

Alfred,
I already have a 16 character password. Error I receive, is connected to
installation of .NET academic pre-requisite which makes a copy of the
password to prevent the system from stopping each time it reboots during the
pre-requisite process. To do this, it uses a dll called ginamsi.dll In
the registry, there is a reference to this called GINADL
(HKLM/software/microsoft/windows nt/current version/winlogon). It contains
a reference to my login and (somewhere I presume), my password in an
encrypted form.

When I try to set the user account (from the Control Panel) to use
CTRL-ALT-DEL for login, XP Pro tells me to uninstall the program that put
ginamsi.dll into the registry. The last thing I want to do is call MS
again. I get the feeling they are ready to kill me for all the times I've
called so far.

I'm guessing the password switch did not properly uninstall. I can try
changing the password though which may cause the forced bootup to fail.
Thanks for the reply, it has given me a possible solution.

Giac

[quoted text, click to view]

Jay B. Harlow [MVP - Outlook]
9/22/2003 8:12:42 AM

Jamie,
Have you tried removing your info from that key?

The Automatic Logon feature is described here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;315231

Changing the AutoAdaminLogon key to 0 will disable the AutoAdminLogin
feature.

You don't need to but clearing the DefaultPassword & DeafultUserName fields
(clear do not delete) probably would not hurt!

Of course you also need a password on your account.

Plus you need to enable the 'Users must enter a user name and password to
use this computer' (described at the bottom of the article).

Hope this helps
Jay

[quoted text, click to view]

Peter van der Goes
9/22/2003 10:40:54 AM

[quoted text, click to view]
IIRC, you don't have to provide a password. You do so only if you don't want
to provide a login at each reboot during the install. As a last resort, you
may have to uninstall Visual Studio .NET, check and edit the registry as
needed to remove the .dll and it's contents, set up a login/password with
administrative privileges, then reinstall using that username/password
entered *manually* at each reboot.

I think that would do it for you.

--
Peter - [MVP - Academic]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet academic

View Other Months
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008

home · blog · groups

Questions? Comments? Contact the dn