New install on new drive - access denied for old folders...

[Christoph]

Due to my MB dying last week, I had to reinstall XP. In
doing so, I decided to install fresh onto a brand new HD,
making my original primary OS HD a slave.
So now XP is installed on my new HD and I try to access
my old "Documents and Settings" folder (on the slave) and
I'm getting access denied errors. Why? I'm logged in as
an administrator account and those folders should no longer
be viewed as personal system folders. So why am I getting
access denied? And is there any way to turn that off? I
would really like to retrieve what is in my old "Documents
and Settings" folder.

Any suggestions on how to rectify this problem would be
greatly appreciated!

thnx,
Christoph

 

[ByTor]

Due to my MB dying last week, I had to reinstall XP. In
doing so, I decided to install fresh onto a brand new HD,
making my original primary OS HD a slave.
So now XP is installed on my new HD and I try to access
my old "Documents and Settings" folder (on the slave) and
I'm getting access denied errors. Why? I'm logged in as
an administrator account and those folders should no longer
be viewed as personal system folders. So why am I getting
access denied? And is there any way to turn that off? I
would really like to retrieve what is in my old "Documents
and Settings" folder.

Any suggestions on how to rectify this problem would be
greatly appreciated!

thnx,
Christoph

Here's my first question.......When you installed XP fresh did you leave
the old drive attached?
Your description of what you did opens an avenue for **many*
questions....Reason I'm asking is you may have created a scenario that
can possibly give you more troubles in the future.......

 

[Christoph]

Here's my first question.......When you installed XP fresh did you leave

the old drive attached?

Yes, I did. However, windows is not using the old directories as
far as I can tell. When I save anything to "My Documents", it is
saving the file into my new "My Documents" folder on the C:
drive and not on my slave.
Also, I moved everything from the root of the slave to a new sub
directory. So now instead of "Documents and Settings" being
off the root of the slave it's now in a subdirectory off the root.
So windows would have to be doing alot of assuming as a result...

Your description of what you did opens an avenue for **many*
questions....Reason I'm asking is you may have created a scenario that
can possibly give you more troubles in the future.......

Such as?

thnx,
Christoph

 

[ByTor]

Yes, I did. However, windows is not using the old directories as
far as I can tell. When I save anything to "My Documents", it is
saving the file into my new "My Documents" folder on the C:
drive and not on my slave.
Also, I moved everything from the root of the slave to a new sub
directory. So now instead of "Documents and Settings" being
off the root of the slave it's now in a subdirectory off the root.
So windows would have to be doing alot of assuming as a result...


Such as?

thnx,
Christoph

Do you have a dual boot environment? Leaving an "active" OS on the
system, even if it is a slave, a clean install will see this,
compensate, & think your are "adding" an OS.........

 

[Christoph]

Do you have a dual boot environment? Leaving an "active" OS on the

system, even if it is a slave, a clean install will see this,
compensate, & think your are "adding" an OS.........

No, it's not a dual boot environment. Also, now that I think about it,
the slave is connected but to a RAID card that the OS didn't (or
couldn't) see until I installed the drivers for it. The very first time I
actually got to the GUI and opened windows explorer, the slave did
not appear as a drive. And when I went into the device manager, it
showed the RAID card with a yellow question mark. So I don't think
that the install could have seen anything on the slave during the install.
Plus, when the machine boots up, I'm not given an option for which
"Windows" I want to boot to. With that being the case, how could
the install think I was "adding" an OS? If it did, wouldn't it create an
additional entry in the boot.ini to allow me to select my old OS?

thnx,
Christoph

 

[Guest]

Follow this link...
http://support.microsoft.com/default.aspx?scid=kb;en-us;810881&Product=winxp

 

[ByTor]

No, it's not a dual boot environment. Also, now that I think about it,
the slave is connected but to a RAID card that the OS didn't (or
couldn't) see until I installed the drivers for it. The very first time I
actually got to the GUI and opened windows explorer, the slave did
not appear as a drive. And when I went into the device manager, it
showed the RAID card with a yellow question mark. So I don't think
that the install could have seen anything on the slave during the install.
Plus, when the machine boots up, I'm not given an option for which
"Windows" I want to boot to. With that being the case, how could
the install think I was "adding" an OS? If it did, wouldn't it create an
additional entry in the boot.ini to allow me to select my old OS?

thnx,
Christoph

Good point, did not know that, wasn't stated in your original post. Just
a thought is all I was establishing.... ;0)
As far as your original issue I have no answer at the moment.....Sorry.

 

[zibby]

Try to take ownership of the files.

Open Explorer
go to Tools > folder options>view
turn off "use simple file sharing..."
hit ok

Right click on files, select properties
go to security tab > advanced > owner
it will show you current owner (your profile from last windows
installation )
and on bottom windows new owners (admin and all users)
select admin or your user name and hit ok, ok

That should fix problem, unless you had installed personal certificate and
didn't make copy of it.