Search results for query: *

Nevermind about what I asked. When I rebooted my computer, it set my current account's Documents folder to "My Documents". That's strange, but it does what I want now. The login is extremely fast. I can get from the computer not on at all to my desktop in under 30 seconds... the way it should be...

I moved the account over. There are a few bugs, but nothing I can't iron out. What I am most concerned with, however, if only for cosmetic reasons, is the My Documents folder. That is only shown if you are the first user (the one created with WinXP setup), and not a second account. So, my new...

OK, it appears that you were right. There's no way I'm fixing this unless I move to another account. It must be that NTUSER.dat file that is messed up in this case. But at least I got a good cleaning by going through Application Data and the other folders. It's amazing the things uninstallers...

To my way of thinking if this has fixed the slow logon then there is something wrong with your profile. If you have a copy of all your username data why not delete your old profile and go forward with the new profile?" Wow... I don't know where my head was when I said something must not be...

There were no errors or warnings in Event Viewer in either System or Applications pertaining to my recent login (which was indeed slow). 816873 doesn't apply to me as I have no network devices mapped. I tried to "Disconnect Network Drives" in My Computer's Tool menu before posting this topic...

Thanks for the quick response! I will try all of this when I get home from work and let you know any results.

I have done a search of this forum and google for slow XP logons and found a lot of information. None of it applies to me, however. Whenever I log on to my computer (it is a local account, there is no domains setup or anything) it takes about 2-3 minutes after entering the password before it...

Thanks a lot! That actually did solve the problem. When I was opening the handle I specified the privileges as PROCESS_VM_READ or PROCESS_VM_WRITE, but changing it to PROCESS_ALL_ACCESS fixed my problem. I wonder why the first one didn't open it for Read/write access like expected...?

I am testing out the ReadProcessMemory and WriteProcessMemory functions just for fun (I believe I am going to have to use them in the future, so I am just practicing with them now), but ReadProcessMemory always returns an error. It only returns a 0, so I have no idea what that means or what went...