Computer Help and Spyware Removal Computer Help and Spyware Removal Computer Help and Spyware Removal Computer Help Forums Windows Startup Programs Database Spyware and Malware Removal Guides Computer Tutorials Uninstall Database File Database Computer Glossary Computer Resources
 

Welcome Guest ( Log In | Click here to Register a free account now! )



Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

8 Pages V  < 1 2 3 4 5 > »   
Reply to this topicStart new topic
> Cannot Logon, One of my accounts remains a black screen
usasma
post Mar 15 2008, 07:02 AM
Post #31


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



The only thing that I saw in the startups list that you posted was an Acronis Timeout Monitor - and it's just a hunch on my part. I'd suggest disabling all the Acronis stuff to see what happens. If it doesn't fix it, then just re-enable it.

I'm still monitoring the TechNet link - but don't expect a bunch of help from it (it seems to be posted in the Exchange Server section). I'll post it in a more appropriate place there.

In this link ( http://technet.microsoft.com/en-us/magazine/cc138019.aspx ) about 1/3 of the way down the page (just after figure 6) it states:
QUOTE
For example, an application that tests the account in which it’s running for membership in the Administrators group might otherwise work, but won’t run if it’s not in that group.
So, in this case, if it's an issue with the video driver that's got it's permissions corrupted, then it might not run for a Standard User (which would make your Admin account's behavior suspicious).

Where did you get the driver to update your video card? Was it from the PC manufacturer's website, or from the ATI website? Have you tried the Catalyst uninstaller to remove all traces of the video driver before installing the new video driver?

Another link here seems to describe the same problem ( http://forums.microsoft.com/TechNet/ShowPo...4&SiteID=17 ) but no solution


--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post
usasma
post Mar 15 2008, 07:12 AM
Post #32


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



Created another thread here for more exposure: http://windowshelp.microsoft.com/communiti...p;cr=US&p=1



--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post
usasma
post Mar 15 2008, 07:39 AM
Post #33


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



Try reading this link: http://content.zdnet.com/2346-12354_22-64715-2.html
And check for errors in the boot performance log when your Standard Account tries to load (maybe you can run "eventvwr.msc" or "eventvwr.exe" from the Task Manager in that account?)


--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post
I_am_CanadianEh?
post Mar 15 2008, 09:22 AM
Post #34


Senior Member
****

Group: Members
Posts: 354
Joined: 6-January 06
Member No.: 49,094



USASMA

Thanks very much for all your efforts thus far! thumbup2.gif

I will read those links you posted and try some of the other suggestions, but give me a few days. I have a busy schedule this week, so I may be slow in responding. smile.gif

QUOTE
So, in this case, if it's an issue with the video driver that's got it's permissions corrupted, then it might not run for a Standard User (which would make your Admin account's behavior suspicious).

Where did you get the driver to update your video card? Was it from the PC manufacturer's website, or from the ATI website? Have you tried the Catalyst uninstaller to remove all traces of the video driver before installing the new video driver?


That was one of my hunches as you can see in one of my earlier posts. I haven't tried that yet, but I think I will.

My DELL originally came with XP installed and an ATI Radeon X300 card. I wanted to upgrade my video card so I purchased at a retail outlet a Radeon X1600 which was compatible with Vista.

When I installed Vista, it already had a driver for this card, but I did download and install the latest driver from ATI's website (both the driver and Catalyst Control Centre). This was back in September 2007. I then updated my chipset, SATA Controller drivers as well as download the 8.2 Version of this ATI driver (Jan. 2008). I completely removed the ATI software, and installed the latest.

I now see that version 8.3 is available. http://game.amd.com/us-en/drivers_catalyst.../common-vista32

Looking at the release notes, it mentions something about a Black sreen issue being resolved. About 1/4 of the way down it mentions:

QUOTE
Resuming from hibernation mode with HDMI display connected no longer results in a black screen with only a mouse cursor being displayed. Further details can be found in topic number 737-31149


So, I'm going to completely remove the current ATI driver and re-boot. Vista should then automatically install the appropriate driver from its driver database. Then I'll check the Standard account again. If it works, then I'll try installing version 8.3 from the website and check again.

However, I tried booting into the Standard User account in Safe Mode. I still had the black screen even though in Safe Mode, only the standard VGA driver loads, so maybe it isn't a video card problem??

Event Viewer

I went to the Standard Account, hit Task Manager, Run - New Task and typed in Eventvwr.msc. I got an error saying it wasn't a valid MMC snap-in or I didn't have permission to run it. So, yes, I've tried accessing Event viewer in the Std. Account. How can I run this as an administrator from a Run box?

Also, my black screen is now a blue screen!! Not a "blue screen of death" just a blank light blue screen with the mouse only.

I'll let you know what else I come up with. Thanks again. wink.gif

Go to the top of the page
 
+Quote Post
I_am_CanadianEh?
post Mar 15 2008, 09:32 AM
Post #35


Senior Member
****

Group: Members
Posts: 354
Joined: 6-January 06
Member No.: 49,094



Sorry, another thing I tried.

Did the "Perfmon /report" command (without the quotes):

1) With normal Admin account, it had no significant failures.

2) With the problem Standard User, I typed the command from a Run (New Task) box and I got a minimized window and everything on my screen started to flash very quickly. Not the monitor, but the Task Manager window, the minimized Performance Monitor window, and my mouse cursor. I had to hit the "X" button at the top right corner of the window very quickly, several times before I could close it!

What the hell just happened? crazy.gif

Go to the top of the page
 
+Quote Post
usasma
post Mar 15 2008, 09:46 AM
Post #36


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



Well, that's progress (from black to blue screen)! I'm not 100% sure about the standard VGA driver tho' - things have changed a lot in Vista.

This is looking more and more to be a video driver issue. Normally we suggest updating the drivers - but, technically, this isn't actually what we want to do. We use "update" when we really mean is we're trying to remove a corruption in the drivers by resetting the video drivers to the factory default state (which is usually most easily accomplished by updating them).

When you remove the driver, Vista will use the default Microsoft driver for the video - this may result in your screen being too large or small. And, in most cases you won't be able to adjust this (don't have much experience with it in Vista, but this was the case in XP). You should also be prompted (via Windows Update) to download and install the updated driver for the ATI card. I'd suggest avoiding this option as it's caused problems for me in the past. I recommend downloading the drivers directly from the ATI website (which you posted the link to in your last post).

I would recommend using the Catalyst Uninstaller before installing any new drivers ( http://support.ati.com/ics/support/default...questionID=1447 ) to make sure that most traces of the driver are removed.

Other than this, I'd have to think that taking ownership of all files and registry entries related to the ATI drivers, then giving permission the User group full control "MIGHT" work - but that's a lot more work than backing up your stuff and reinstalling Vista.


--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post
usasma
post Mar 15 2008, 09:49 AM
Post #37


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



Interesting topic at the ATI knowledge base: http://support.ati.com/ics/support/default...uestionID=21875
Relates to issues between some Dell PC's and your video cards. Not exactly your problem, but may be worth a try to see if they'll fix it.


--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post
usasma
post Mar 15 2008, 11:42 AM
Post #38


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



A post on the Vista newsgroups suggests this: http://support.microsoft.com/kb/313222


--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post
webewitch
post Mar 16 2008, 02:03 PM
Post #39


New Member
*

Group: Members
Posts: 1
Joined: 16-March 08
Member No.: 196,787



I had the same problem - I found this solution somewhere :
-------------------------------------------------------------------
HERE IS THE FIX

1. Navigate to
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"

2. If there is a key named "OldUserinit", delete the "Userinit" key and rename the "OldUserinit" key to "Userinit".

3. The "Userinit" key should now say
"WINDOWS_PATH\system32\userinit.exe,"

"WINDOWS_PATH" is relative to where you have your windows installed.
Mine would be "C:\WINDOWS\system32\userinit.exe,"

Now you can log in again
--------------------------------------------------------------------------
On mine there was no 'Olduserinit' but I changed the 'userinit' key to match the above (on mine there was another address before) and it worked fine.

I hope this may help.
Go to the top of the page
 
+Quote Post
I_am_CanadianEh?
post Mar 16 2008, 02:52 PM
Post #40


Senior Member
****

Group: Members
Posts: 354
Joined: 6-January 06
Member No.: 49,094



Webewitch,
Thanks for your input.

I looked into this key but I did not have an "Olduserinit" key, only a Userinit one. And it already had a value of "C:\Windows\system32\Userinit.exe,"
so I didn't change anything.

Usasma,
I'm going to look at your several suggestions, but in the meantime, I've exported some specific registry keys and attached them here. The file names basically describe where in the registry I was looking. Let me know if you see anything unusual.

I'm going to login to a non-functional Standard user account and see if I can export a key from the registry to see if there are any differences from an account with admin priveleges.




Attached File(s)
Attached File  HKCU_Software_MS_Windows_NT_Winlogon_me__admin.reg ( 536bytes ) Number of downloads: 11
Attached File  HKLM_Software_MS_Windows_NT_Winlogon.reg ( 19.72k ) Number of downloads: 16
Attached File  HKLM_System_CCS_Services_RpcSs.reg ( 4.45k ) Number of downloads: 17
 
Go to the top of the page
 
+Quote Post
I_am_CanadianEh?
post Mar 16 2008, 03:16 PM
Post #41


Senior Member
****

Group: Members
Posts: 354
Joined: 6-January 06
Member No.: 49,094



QUOTE
I'm going to login to a non-functional Standard user account and see if I can export a key from the registry to see if there are any differences from an account with admin priveleges.


I can open the registry from a Run-New Task box, but I cannot save or export a key as no dang Window comes up to allow me to do this. AAArrgh!! killcomp.gif

Around the time I logged in to the standard account, I found this in the Event Viewer.

QUOTE
Level Date and Time Source Event ID Task Category
Error 3/16/2008 3:59:27 PM Microsoft-Windows-WMPNSS-Service 14332 None Service 'WMPNetworkSvc' did not start correctly because CoCreateInstance(CLSID_UPnPDeviceFinder) encountered error '0x80070005'. Verify that the UPnPHost service is running and that the UPnPHost component of Windows is installed properly.


I have several instances of these. But it references Windows Media Player. What does this application have to do with my problems??
Go to the top of the page
 
+Quote Post
usasma
post Mar 16 2008, 03:23 PM
Post #42


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



Just a stab in the dark, but go to the Start button and type "cmd.exe" (without the quotes), then right click on the cmd.exe that appears at the top of the search box and select "Run as administrator".

Once in the command prompt, type:

RegSvr32 oleres.dll and press Enter

then type:

RegSvr32 WRLogonNTF.dll and press Enter

Test to see if this has fixed it (and cross your fingers!) smile.gif


--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post
I_am_CanadianEh?
post Mar 16 2008, 04:51 PM
Post #43


Senior Member
****

Group: Members
Posts: 354
Joined: 6-January 06
Member No.: 49,094



OK, here's what I did now:

1) RegSvr32

Followed your instructions and I got these errors:

a) The module "oleres.dll" was loaded but the entry-point "DLLRegisterServer" was not found. Make sure "oleres.dll" is a valid DLL or OCX file and then try again.
cool.gif The module "WRLogonNTF.dll" was loaded but the entry-point "DLLRegisterServer" was not found. Make sure "WRLogonNTF.dll" is a valid DLL or OCX file and then try again.

So no luck there...

Then I tried an earlier suggestion.

2)
QUOTE
A post on the Vista newsgroups suggests this: http://support.microsoft.com/kb/313222


This completed with errors. Here is the log file below.

QUOTE
-------------------------------------------
Sunday, March 16, 2008 5:27:12 PM
----Configuration engine was initialized successfully.----

----Reading Configuration Template info...


----Configure User Rights...
SeImpersonatePrivilege must be assigned to administrators. This setting is adjusted.
SeImpersonatePrivilege must be assigned to SERVICE. This setting is adjusted.
Configure S-1-5-21-3388724875-1920495993-728804679-1000.
remove SeLockMemoryPrivilege.
Configure S-1-5-21-3388724875-1920495993-728804679-1003.
remove SeServiceLogonRight.
Configure S-1-5-21-3388724875-1920495993-728804679-1005.
remove SeChangeNotifyPrivilege.
remove SeIncreaseQuotaPrivilege.
remove SeBatchLogonRight.
remove SeServiceLogonRight.
remove SeAssignPrimaryTokenPrivilege.
Configure S-1-5-19.
Configure S-1-5-20.
Configure S-1-5-32-544.
Configure S-1-5-32-551.
Configure S-1-5-32-545.
add SeTimeZonePrivilege.
Configure S-1-1-0.
Configure S-1-5-6.
Configure S-1-5-21-3388724875-1920495993-728804679-501.
Configure S-1-5-32-555.

User Rights configuration was completed successfully.


----Configure Group Membership...
Configure Users.
remove Dell5150\elva.
remove Dell5150\tim.
remove Dell5150\brendon.

Group Membership configuration was completed successfully.


----Configure Registry Keys...
Configure users\.default.
Configure machine\software.
Warning 1336: The access control list (ACL) structure is invalid.
Error setting security on machine\software\Licenses.

Configuration of Registry Keys was completed with one or more errors.


----Configure File Security...
Configure c:\program files\common files\speechengines\microsoft\tts.
Warning 2: The system cannot find the file specified.
Error setting security on c:\program files\common files\speechengines\microsoft\tts.
Configure c:\programdata\microsoft\windows\drm.
Configure c:\programdata\microsoft\windows\drm\cache.
Configure c:\windows\repair\default.
Warning 3: The system cannot find the path specified.
Error setting security on c:\windows\repair\default.
Configure c:\windows\repair\ntuser.dat.
Warning 3: The system cannot find the path specified.
Error setting security on c:\windows\repair\ntuser.dat.
Configure c:\windows\repair\sam.
Warning 3: The system cannot find the path specified.
Error setting security on c:\windows\repair\sam.
Configure c:\windows\repair\security.
Warning 3: The system cannot find the path specified.
Error setting security on c:\windows\repair\security.
Configure c:\windows\repair\software.
Warning 3: The system cannot find the path specified.
Error setting security on c:\windows\repair\software.
Configure c:\windows\repair\system.
Warning 3: The system cannot find the path specified.
Error setting security on c:\windows\repair\system.
Configure c:\windows\system32\wbem\mof.
Configure c:\windows\system32\windows media.
Warning 2: The system cannot find the file specified.
Error setting security on c:\windows\system32\windows media.

File Security configuration was completed successfully.


----Configure General Service Settings...
Configure sysmonlog.
Error 1060: The specified service does not exist as an installed service.
Error opening sysmonlog.
Configure SamSs.
Configure ntmssvc.
Error 1060: The specified service does not exist as an installed service.
Error opening ntmssvc.
Configure netddedsdm.
Error 1060: The specified service does not exist as an installed service.
Error opening netddedsdm.
Configure netdde.
Error 1060: The specified service does not exist as an installed service.
Error opening netdde.
Configure dmserver.
Error 1060: The specified service does not exist as an installed service.
Error opening dmserver.
Configure clipsrv.
Error 1060: The specified service does not exist as an installed service.
Error opening clipsrv.
Configure Browser.

General Service configuration was completed successfully.


----Configure available attachment engines...

Configuration of attachment engines was completed successfully.


----Configure Security Policy...
Configure password information.
Administrator account is disabled.
Guest account is disabled.

System Access configuration was completed successfully.
LSA anonymous lookup names setting : existing SD = D:(D;;0x800;;;AN)(A;;0xf1fff;;;BA)(A;;0x20801;;;WD)(A;;0x801;;;AN)(A;;0x1000;;;L
S)(A;;0x1000;;;NS)(A;;0x1000;;;S-1-5-17).
Configure LSA anonymous lookup setting.
Configure machine\software\microsoft\windows nt\currentversion\setup\recoveryconsole\securitylevel.
Configure machine\software\microsoft\windows nt\currentversion\setup\recoveryconsole\setcommand.
Configure machine\software\microsoft\windows nt\currentversion\winlogon\cachedlogonscount.
Configure machine\software\microsoft\windows nt\currentversion\winlogon\forceunlocklogon.
Configure machine\software\microsoft\windows nt\currentversion\winlogon\passwordexpirywarning.
Configure machine\software\microsoft\windows nt\currentversion\winlogon\scremoveoption.
Configure machine\software\microsoft\windows\currentversion\policies\system\dontdisplaylastusername.
Configure machine\software\microsoft\windows\currentversion\policies\system\legalnoticecaption.
Configure machine\software\microsoft\windows\currentversion\policies\system\legalnoticetext.
Configure machine\software\microsoft\windows\currentversion\policies\system\scforceoption.
Configure machine\software\microsoft\windows\currentversion\policies\system\shutdownwithoutlogon.
Configure machine\software\microsoft\windows\currentversion\policies\system\undockwithoutlogon.
Configure machine\software\policies\microsoft\windows\safer\codeidentifiers\authenticodeenabled.
Configure machine\system\currentcontrolset\control\lsa\auditbaseobjects.
Configure machine\system\currentcontrolset\control\lsa\crashonauditfail.
Configure machine\system\currentcontrolset\control\lsa\disabledomaincreds.
Configure machine\system\currentcontrolset\control\lsa\everyoneincludesanonymous.
Configure machine\system\currentcontrolset\control\lsa\fipsalgorithmpolicy\enabled.
Configure machine\system\currentcontrolset\control\lsa\forceguest.
Configure machine\system\currentcontrolset\control\lsa\fullprivilegeauditing.
Configure machine\system\currentcontrolset\control\lsa\limitblankpassworduse.
Configure machine\system\currentcontrolset\control\lsa\lmcompatibilitylevel.
Configure machine\system\currentcontrolset\control\lsa\msv1_0\ntlmminclientsec.
Configure machine\system\currentcontrolset\control\lsa\msv1_0\ntlmminserversec.
Configure machine\system\currentcontrolset\control\lsa\nolmhash.
Configure machine\system\currentcontrolset\control\lsa\restrictanonymous.
Configure machine\system\currentcontrolset\control\lsa\restrictanonymoussam.
Configure machine\system\currentcontrolset\control\print\providers\lanman print services\servers\addprinterdrivers.
Configure machine\system\currentcontrolset\control\session manager\kernel\obcaseinsensitive.
Configure machine\system\currentcontrolset\control\session manager\memory management\clearpagefileatshutdown.
Configure machine\system\currentcontrolset\control\session manager\protectionmode.
Configure machine\system\currentcontrolset\services\lanmanserver\parameters\autodisconnect.
Configure machine\system\currentcontrolset\services\lanmanserver\parameters\enableforcedlogoff.
Configure machine\system\currentcontrolset\services\lanmanserver\parameters\enablesecuritysignature.
Configure machine\system\currentcontrolset\services\lanmanserver\parameters\requiresecuritysignature.
Configure machine\system\currentcontrolset\services\lanmanserver\parameters\restrictnullsessaccess.
Configure machine\system\currentcontrolset\services\lanmanworkstation\parameters\enableplaintextpassword.
Configure machine\system\currentcontrolset\services\lanmanworkstation\parameters\enablesecuritysignature.
Configure machine\system\currentcontrolset\services\lanmanworkstation\parameters\requiresecuritysignature.
Configure machine\system\currentcontrolset\services\ldap\ldapclientintegrity.
Configure machine\system\currentcontrolset\services\netlogon\parameters\disablepasswordchange.
Configure machine\system\currentcontrolset\services\netlogon\parameters\maximumpasswordage.
Configure machine\system\currentcontrolset\services\netlogon\parameters\requiresignorseal.
Configure machine\system\currentcontrolset\services\netlogon\parameters\requirestrongkey.
Configure machine\system\currentcontrolset\services\netlogon\parameters\sealsecurechannel.
Configure machine\system\currentcontrolset\services\netlogon\parameters\signsecurechannel.

Configuration of Registry Values was completed successfully.
Configure log settings.

Audit/Log configuration was completed successfully.


----Configure available attachment engines...

Configuration of attachment engines was completed successfully.


----Un-initialize configuration engine...


What now??
Go to the top of the page
 
+Quote Post
I_am_CanadianEh?
post Mar 16 2008, 04:57 PM
Post #44


Senior Member
****

Group: Members
Posts: 354
Joined: 6-January 06
Member No.: 49,094



Also, after I did these 2 options and rebooted, my son's account disapperared from the logon screen!! ohmy.gif Thank heavens, I backed up his files!
When I logged on to my admin account, I browsed "My Computer" and still found his folder under users.

I then moved his entire folder to the recycle bin, rebooted, logged into my account and tried to re-create his account with the same name. Now it tells me that the name I chose is invalid because it has illegal characters (like *, /, \, etc.). But I deleted the #$%^& thing!!

Soooo....I tried to create an standard account called "test" (without the quotes). It allowed me. Logged off, tried to logon to test, same result.

Go to the top of the page
 
+Quote Post
usasma
post Mar 16 2008, 05:19 PM
Post #45


Still visually handicapped, new avatar :0)
******

Group: Global Moderator
Posts: 15,531
Joined: 2-October 05
From: Southeastern CT, USA
Member No.: 35,824



Well, it appears that we may be making some progress. Here's what I think is the clue: "Warning 1336: The access control list (ACL) structure is invalid. "

So, you're going to have to try and fix the ACL listing. Here's some links on "how to":
http://support.microsoft.com/?kbid=178170
http://support.gradient.com/private/doclib...ef/Comref95.htm
http://support.microsoft.com/kb/237399
http://www.mydigitallife.info/2007/04/30/i...to-manage-acls/
http://support.microsoft.com/kb/223441
http://itsvista.com.s38146.gridserver.com/2007/03/icacls/
http://www.windowsreference.com/windows-vi...ce-pack-2vista/

This is way, way outta my league, and it appears to be dangerous to use the icacls.exe (so backup everything!).

BTW - during my searches, one user mentioned that a defective video card was the actual problem for him not being able to login - but the differences were enough that I can't be sure this has any bearing on your case.

Good luck!



--------------------
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **
BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!)
Go to the top of the page
 
+Quote Post

8 Pages V  < 1 2 3 4 5 > » 
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: