6 replies
by gralfus
by blitzsonik
by joseph moore
To go along with what gralfus posted:
Open My Computer and go to C:\Documents & Settings.
That is the root folder for all user profiles in Win2K (if this machine was originally NT4 Workstation upgraded to Win2K, then the path is different, FYI). You're gonna see folders with names like Default User, All Users, Administrator, etc.
There should be at least one with the name that matches your husband's login name (let's say it's BOB, for example).
What happens sometimes is that when you log in, Windows gets confused and is not able to open the correct user profile. When this happens (and I don't know why; it just does sometimes), the local machine will make a new copy of the user profile in the Doc&Set folder. But, since there already is a profile folder with that name, it makes a new one, with .000 appended to the folder name.
So, let's say BOB has logged in and already has the folder C:\Documents & Settings\BOB
Then one day on logging in, Windows freaks out and decides to make a new profile for BOB.
It looks at the C:\Documents & Settings directory, and already sees the BOB folder. Well, it can't then make another BOB folder, since the profile creation process can't overwrite.
So, it makes BOB.000 (or BOB.001, etc).
And so when it's done, and the Desktop is displayed for BOB, he is actually seeing the BOB.000 profile structure.
The original BOB folder is still on the machine, intact, just not being used.
So what you can do in this case is do some adjustments.
Log in as another Administrator-level account (not as BOB).
Go to the C:\Documents & Settings folder, and Rename BOB.000 to something else (BOB.IDONTCARE).
Then rename the BOB folder to be BOB.000
Windows has decided to reference the BOB.000 folder with the BOB login name.
If you just name the old BOB folder with the new BOB.000 name, then that tricks Windows into using the old profile!
by joseph moore
Reboot after this (I'm old fashioned this way!), and have BOB log in. He should then reference his old profile (with the new BOB.000 folder name).
And all should be well!
We never did get the problem solved; I think the support folks at hubby's job had hosed something up. But this was good information for the future--thanks!
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending