PDA

View Full Version : Automatic Login (WXP-Home)



waldo6050
04-28-2004, 06:02 PM
I am running the demo version of Tweak Manager 2.1. I used the program to try to Automatically Login to my Windows XP Machine. I checked the box which says "Login Automatically at System Startup." Note: This is the only box I checked. This process works exactly once, whether I reboot or startup from a shutdown. At that point the check mark disappears, and all subsequent reboots/startups take me to the "Welcome" screen, which asks me to chose between the two users on my machine. I don't have a User Name password set-up. Any ideas

tommytx
05-03-2004, 01:28 PM
I am not sure this will help, but here is some food for thought.
To permit auto logon, absolutely no accounts other than you the administrator can exist.
Also the guest account must be turned off.

To turn off the guest account, start-settings-ctrl panel-user accts and double click user accts. Double click guest and turn it off if not already off.
Make sure no other accounts exist. Careful, don't remove any existing accounts just for test, as they will be destroyed.
Heee is one last thing. and maybe some one can help us with this. You may have an ASP.NET account shown and that may be stopping the auto logon. I have one and don't know where it came from. I am afraid to delete it. Does anyone one know what it is? Could it be a network administrator acct. I did not set it up but I did install a router. that may have set it up automatically.
Can anyone shed light on this?

Brf
05-03-2004, 02:10 PM
The ASP.NET account is created along with the .NET framework. You should not delete it, although you can disable it.

Patrick O'Brien
05-03-2004, 06:57 PM
Hello waldo6050,

Welcome to the WinGuides Forums!

Thank you for your interest in <a target="_blank" href=http://winguides.com/tweak/> Tweak Manager! </a>

Yes, in order for the <a target="_blank" href=http://winguides.com/registry/display.php/13/> Automatic Logon to Windows NT, 2000 and XP tweak </a> to work properly, an existing Windows XP username and password must be entered into the applicable textbox fields displayed within the Tweak Manager tweak itself.

If you are needing any future assistance, please visit <a target="_blank" href=http://www.winguides.com/support/submit.php?ref=1-1-5&custom_Product=Tweak+Manager&subject=Product+Support&guide=tweakmgr> Tweak Manager Technical Support </a> to open a service ticket with our Help Desk as we are more than willing to help in any way we can.

Regards,

Patrick O'Brien
Technical Support Representative
WinGuides Support Team
---
WinGuides Network - http://www.winguides.com/
Empowering Windows users since 1998

lj50
05-03-2004, 09:10 PM
Why shouldn't I delete asp.net and the netframework 1.1. I deleted both a long time ago and didn't have any problems.

Brf
05-04-2004, 04:52 AM
If you are running .NET applications you will need the framework installed. Apparently you havent encountered any of these yet. The ASP.NET usercode is used by .NET servers and by the development programs for .NET applications.

.NET is the replacement for VB, so we will see more of these applications in the future.<P ID="edit"><FONT class="small">Edited by Brf on 05/04/04 03:53.</FONT></P>

tom_keefer
05-04-2004, 08:22 PM
An example of what Brf is talking about would be PowerQuest's (now Symantec) Drive Image 7. It needs .NET Framework in order to function. But, you know that going in with Drive Image 7 because it tells you. If you decide to uninstall Drive Image, .NET Framework doesn't get zapped in the process. When I was using Drive Image 7 I deleted the ASP.net user account and the program still functioned as advertised.



<font color=purple>Tom</font color=purple>

ya'aa'tey

Brf
05-05-2004, 08:24 AM
I found out about the ASP.net user when I started developing in .NET 1.0. That earlier version didnt create the user, but the Visual Studio would check to see if that user exists. If it didnt find the user, it would start checking all servers in the entire Enterprise looking for it.... delaying VS from starting for about a minute. The early solution was to create a disabled ASP.net domain user. Later versions of .NET, from 1.0sp2 on, create the ASP.net user when installed.