«

Loosing account settings seems kinda scary... therefore I am gonna make a
backup account... and try this method/fix to copy as much stuff as possible
to backup account just to see if it will work for most stuff:

(My main account does look a bit weird: NTUSER.DAT is 37 MB ?!?)

http://www.modernstreet.com/windows/...in-windows-xp/

Most important information from that link:

"
You can start by creating new user profile on the computer:

•Log on as the Administrator or as a user with administrator credentials.
Any profile that does not have administration rights will not be able to
make the required changes.
•Go to Start > Control Panel > User Accounts


•Click the Advanced tab, and then click the advanced button.
•In the left section of the window, click the Users folder.
•On the Action menu, click New User.
•Enter the user information that corresponds with your networks naming
conventions, and then click Create. Naming your user account is very
important. If the name does not match your networks current naming
conventions it can cause trouble down the road with regular administration
duties.
Creating a new user profile on a workgroup computer:

•Log on as the Administrator or as a user with administrator access rights.
•Go to Start, and then choose Control Panel > User Accounts
•Under pick a task, choose Create a New Account.
•Type a name for the user information (be sure this matches your current
naming conventions as well), and then click Next.
•Select an account type, and then click Create Account.
The following steps will tell you how to get your old profile copied into
your new profile without losing any of the information. This will not copy
your outlook profile; only your windows profile. It is important that you
back up any office profiles separately.

•Log on to a profile that is not the same one that you are trying to copy
from.
•In Windows Explorer (not Internet Explorer), click Tools > Folder Options.
•Click the View tab > Show hidden files and folders > Clear the Hide
Protected Operating System Files check box, and then click OK. Ignore any
warning message for this time.


•Find the C:\Documents and Settings\corruptprofile folder, C is the Windows
XP hosting drive, and “corruptprofile” is the name of the profile you want
to copy the user profile from
•Copy all the files in that folder except the following files:
?Ntuser.dat
?Ntuser.dat.log
?Ntuser.ini
•Find the C:\Documents and Settings\newprofile folder, where C is the drive
on which Windows XP is installed, and “newprofile” is the name of the user
profile that you created.
•Now paste in the data you just copied from your old profile. Be careful not
to copy and paste the above files that were supposed to be left out.
•Restart the computer and log on to your new profile.
This should correct typical problems you may have experienced as a result of
a corrupt user profile. If this option seems a little extreme for you, a
System Restore might be able to fix the problem as well, but System Restore
is usually a better option for a stand alone system rather than for a
networked machine.
"

Bye,
Skybuck.

Hmmm the copy failed... it said: "Cannot find 2 v 2 dolfins"...

I searched this file... it's a Red Alert 3 Replay of zero bytes...

Maybe the file got destroyed or was corrupted or was never created...
it does not have a creation date or modification date... it's kinda
weird.

I shall make a screenshot just for the fun of it...

I shall now delete this file and see what happens

On 21 okt, 23:47, Skybuck <skybuck2...@hotmail.com> wrote:
> Hmmm the copy failed... it said: "Cannot find 2 v 2 dolfins"...
>
> I searched this file... it's a Red Alert 3 Replay of zero bytes...
>
> Maybe the file got destroyed or was corrupted or was never created...
> it does not have a creation date or modification date... it's kinda
> weird.
>
> I shall make a screenshot just for the fun of it...
>
> I shall now delete this file and see what happens

Hmm even more interesting this file cannot be deleted I shall make
another screenshot to capture the error message,

It says:"Cannot delete file: Cannot read from the source file or
disk."

That sounds kinda bad like a bad sector maybe ?!? Hmm...

Bye,
Skybuck.

This link contains a solution hopefully:

http://blog.dotsmart.net/2008/06/12/...-file-or-disk/

It explains what the problem might be... NTFS allows all kind of weird
folder and filenames, long ones too which is good.

But Win32API sometimes not...

The filename probably ends with spaces or a dot... how it was created
I don't know... maybe by some special red alert 3 api call or path
convention... kinda funny.

Seems today I am fixing lot's of bugs with the OS

Fingers crossed... now I am gonna try the solution, I try to copy
paste the text here in case that website goes down:

Solved: “Cannot read from the source file or disk”
Posted June 12, 2008
Filed under: Windows |
I’ve finally solved a problem that’s been bugging me for years. One of
our file shares ended up with several undelete-able files. Attempting
to delete them results in “Error Deleting File or Folder – Cannot
delete file: Cannot read from the source file or disk“.



Even going to the file’s properties to check permissions presented a
very blank properties dialog. And a CHKDSK didn’t sort thing out
either.

It turns out the problem was: the filename ended with a dot, e.g. it
was something like “C:\Temp\Stuff\Sales Agreement.“. As far as Windows
is concerned this is an invalid file name: so although it gets
reported in a directory listing, the standard Windows APIs for
manipulating files subsequently deny its existence.

So how did this file get created in the first place? The answer: a
Mac. The file was on a file share which had been accessed by a Mac
user. Macs tend to write all sorts of metadata to extra “._DSStore”
files and suchlike and had left this file behind.

So if Windows doesn’t appear to allow these file names, how did they
get to be created? Well, it turns out that NTFS allows all sort of
file name/path weirdness that Windows, or specifically the Win32 API,
doesn’t allow. For example, NTFS actually allows file paths up to 32K
but Windows restricts file paths to no more than 260 characters
(MAX_PATH). I suppose this is all for DOS/Windows 9x backwards
compatibility. As these files were being accessed over a file share I
guess the usual Win32 checks are bypassed.

But thankfully you can get Win32 to ignore these checks by prefixing
your file paths with \\?\, (ie. C:\Temp\SomeFile.txt becomes \\?\C:
\Temp\SomeFile.txt) which I discovered after reading this blog post
about long paths in .NET.

So at a command prompt I was able to delete the file using:

del "\\?\C:\Temp\Stuff\Sales Agreement."If it’s a folder/directory
you’re trying to delete use the rd or rmdir command, e.g.:

rd /s "\\?\C:\Documents and Settings\User\Desktop\Annoying
Folder."Tip: as you’re typing the file/directory name use the TAB key
to auto-complete the name (press TAB repeatedly to cycle through
possible names).


--------------------------------------------------------------------------------
Of course the corollary of all of this is that you could really annoy
somebody by doing this:

echo Hi > "\\?\%USERPROFILE%\Desktop\Annoying file you can't
delete."But you wouldn’t do that would you?

"

(clipboard had some problems copieing from after (ie.C:\) I fixed the
posting a little bit hopefully it all got through )

Bye,
Skybuck.

Something very strange was going on with the Battlefield 2\cache
folder in "my documents"

"My documents" is also a very strange folder which does not show up in
windows explorer... I am not sure if that's normal or if it's because
of corruption... I also hate the way windows and applications store
stuff in this folder which becomes one big junk folder.

However the problem with the battlefield 2 cache folder is that it
kept copieing and copieing and copieing this folder as if there were
millions of files ?!?

Windows explorer only show 23 items...

Either the copieing was buggy, or there are millions of files in
there ?!?

Whatever the case may be it seems windows and windows explorer in XP
x64 is horribly bugged ?!

Now a new problem has arisen with this copieing technique:

Cannot copy "featuredvm": Access is denied.

It's kinda annoying that windows breaks of the copieing... so now I
would have to re-do the copieing ?

If it did not copy this file it might not be so bad... now I have to
somehow manually get rid of it from the selection which might actually
be impossible ?!

Bye,
Skybuck.

On 22 okt, 00:23, Skybuck <skybuck2...@hotmail.com> wrote:
> Something very strange was going on with the Battlefield 2\cache
> folder in "my documents"
>
> "My documents" is also a very strange folder which does not show up in
> windows explorer... I am not sure if that's normal or if it's because
> of corruption... I also hate the way windows and applications store
> stuff in this folder which becomes one big junk folder.
>
> However the problem with the battlefield 2 cache folder is that it
> kept copieing and copieing and copieing this folder as if there were
> millions of files ?!?
>
> Windows explorer only show 23 items...
>
> Either the copieing was buggy, or there are millions of files in
> there ?!?
>
> Whatever the case may be it seems windows and windows explorer in XP
> x64 is horribly bugged ?!
>
> Now a new problem has arisen with this copieing technique:
>
> Cannot copy "featuredvm": Access is denied.
>
> It's kinda annoying that windows breaks of the copieing... so now I
> would have to re-do the copieing ?
>
> If it did not copy this file it might not be so bad... now I have to
> somehow manually get rid of it from the selection which might actually
> be impossible ?!
>
> Bye,
> *Skybuck.

What I feared has become true... the problem seems maybe even worse:

Search cannot find: "featuredvm"

It does find:

featuredvm.ini
and
featuredvm.png

What does this mean ? Maybe featuredvm is an invisible file because of
windows explorer limitations ?!?

I am going to give up on this copy method... I could try a batch file
and get rid of the file.. but it's too much work...

I doubt it's gonna work at all..

So screw this...

Gonna delete the account and the folders to get rid of it... for
now...

Hopefully microsoft will introduce a "repair profile" tool because
this right now kinda sux !