Unable to access files that I created outside of Windows XP...

[Ant]

Hi.

I had a problem with accessing files that I made outside of XP (DOS
bootable CD with old Norton Ghost 2003 for DOS [not Windows]).

H:\Images\C-07142008>dir
Volume in drive H is AFA64-H

Directory of H:\Images\C-07142008

07/19/2008 08:51 AM <DIR> .
07/19/2008 08:51 AM <DIR> ..
07/14/2008 05:41 PM 2,147,464,817 C-071001.GHS
07/14/2008 05:42 PM 598,245,376 C-071002.GHS
07/14/2008 05:46 PM 349,705,127 C-071003.GHS
07/14/2008 05:46 PM 2,147,466,450 C-07152008.GHO
07/19/2008 08:35 AM 106 readme.txt
5 File(s) 5,242,881,876 bytes
2 Dir(s) 11,520,425,984 bytes free

H:\Images\C-07142008>dir
Volume in drive H is AFA64-H

Directory of H:\Images\C-07142008

07/19/2008 08:51 AM <DIR> .
07/19/2008 08:51 AM <DIR> ..
07/14/2008 05:41 PM 2,147,464,817 C-071001.GHS
07/14/2008 05:42 PM 598,245,376 C-071002.GHS
07/14/2008 05:46 PM 349,705,127 C-071003.GHS
07/14/2008 05:46 PM 2,147,466,450 C-07152008.GHO
07/19/2008 08:35 AM 106 readme.txt
5 File(s) 5,242,881,876 bytes
2 Dir(s) 11,520,425,984 bytes free

H:\Images\C-07142008>attrib
A H:\Images\C-07142008\C-071001.GHS
A H:\Images\C-07142008\C-071002.GHS
A H:\Images\C-07142008\C-071003.GHS
A H:\Images\C-07142008\C-07152008.GHO
H:\Images\C-07142008\readme.txt

I can create, delete, rename, edit, etc. with the readme.txt I added
earlier today, but not the *.GHS and *.GHO files. I even made a new
folder/directory in H:\Images\C-07142008\ without any problems. I ran
chkdsk h: and had no errors and problems. I used Unlocker tool to see if
any files were used, nope. I tried logging off from my "Ant"
administrator account and logged in as "administrator" and I cannot eevn
access H:\Images\C-07142008\ directory\folder at all ("access is denied").

I rebooted and went to safe mode with my "administrator" account based
on http://support.microsoft.com/kb/823306 ... I also got the error, but
it said I could take over the ownership, audits, etc. (with
Administrators) since XP didn't know who owned these files. I applied to
Administrators and now I can access, rename, move, etc.

I made these *.ghs and *.gho files from a Norton 2003 (12/24/2003) DOS
version [not the Windows version since I don't trust Windows]. I backed
up my C: drive before upgrading XP Pro. SP2 to SP3 in case anything goes
wrong.

Any ideas why this happened? I don't recall this happening in the past
(2006 and earlier). Was there a change in XP SP3 or some KB updates to
cause this in NTFS? I used the same exact Ghost DOS and method many
times from the past. Is there a fix or this?

Thank you in advance.
--
"I love ants. Do they have uncles? Ha Ha!" --Elmo from Sesame Street
(unknown episode)
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: (e-mail address removed)
( ) or (e-mail address removed)
Ant is currently not listening to any songs on his home computer.

 

[Shenan Stanley]

I had a problem with accessing files that I made outside of XP (DOS
bootable CD with old Norton Ghost 2003 for DOS [not Windows]).

H:\Images\C-07142008>dir
Volume in drive H is AFA64-H

Directory of H:\Images\C-07142008

07/19/2008 08:51 AM <DIR> .
07/19/2008 08:51 AM <DIR> ..
07/14/2008 05:41 PM 2,147,464,817 C-071001.GHS
07/14/2008 05:42 PM 598,245,376 C-071002.GHS
07/14/2008 05:46 PM 349,705,127 C-071003.GHS
07/14/2008 05:46 PM 2,147,466,450 C-07152008.GHO
07/19/2008 08:35 AM 106 readme.txt
5 File(s) 5,242,881,876 bytes
2 Dir(s) 11,520,425,984 bytes free

H:\Images\C-07142008>dir
Volume in drive H is AFA64-H

Directory of H:\Images\C-07142008

07/19/2008 08:51 AM <DIR> .
07/19/2008 08:51 AM <DIR> ..
07/14/2008 05:41 PM 2,147,464,817 C-071001.GHS
07/14/2008 05:42 PM 598,245,376 C-071002.GHS
07/14/2008 05:46 PM 349,705,127 C-071003.GHS
07/14/2008 05:46 PM 2,147,466,450 C-07152008.GHO
07/19/2008 08:35 AM 106 readme.txt
5 File(s) 5,242,881,876 bytes
2 Dir(s) 11,520,425,984 bytes free

H:\Images\C-07142008>attrib
A H:\Images\C-07142008\C-071001.GHS
A H:\Images\C-07142008\C-071002.GHS
A H:\Images\C-07142008\C-071003.GHS
A H:\Images\C-07142008\C-07152008.GHO
H:\Images\C-07142008\readme.txt

I can create, delete, rename, edit, etc. with the readme.txt I added
earlier today, but not the *.GHS and *.GHO files. I even made a new
folder/directory in H:\Images\C-07142008\ without any problems. I
ran chkdsk h: and had no errors and problems. I used Unlocker tool
to see if any files were used, nope. I tried logging off from my
"Ant" administrator account and logged in as "administrator" and I
cannot eevn access H:\Images\C-07142008\ directory\folder at all
("access is denied").
I rebooted and went to safe mode with my "administrator" account
based on http://support.microsoft.com/kb/823306 ... I also got the error,
but it said I could take over the ownership, audits, etc. (with
Administrators) since XP didn't know who owned these files. I
applied to Administrators and now I can access, rename, move, etc.

I made these *.ghs and *.gho files from a Norton 2003 (12/24/2003)
DOS version [not the Windows version since I don't trust Windows].
I backed up my C: drive before upgrading XP Pro. SP2 to SP3 in case
anything goes wrong.

Any ideas why this happened? I don't recall this happening in the
past (2006 and earlier). Was there a change in XP SP3 or some KB
updates to cause this in NTFS? I used the same exact Ghost DOS and
method many times from the past. Is there a fix or this?

Thank you in advance.

You didn't own the files and/or have permissions to them. Why you did not
own them - I cannot say with 100% certainty. Especially since you probably
did not originally write these GHO files onto an NTFS directory - unless you
did it over a network share?

 

[Ant]

I had a problem with accessing files that I made outside of XP (DOS
bootable CD with old Norton Ghost 2003 for DOS [not Windows]).

H:\Images\C-07142008>dir
Volume in drive H is AFA64-H

Directory of H:\Images\C-07142008

07/19/2008 08:51 AM <DIR> .
07/19/2008 08:51 AM <DIR> ..
07/14/2008 05:41 PM 2,147,464,817 C-071001.GHS
07/14/2008 05:42 PM 598,245,376 C-071002.GHS
07/14/2008 05:46 PM 349,705,127 C-071003.GHS
07/14/2008 05:46 PM 2,147,466,450 C-07152008.GHO
07/19/2008 08:35 AM 106 readme.txt
5 File(s) 5,242,881,876 bytes
2 Dir(s) 11,520,425,984 bytes free

H:\Images\C-07142008>dir
Volume in drive H is AFA64-H

Directory of H:\Images\C-07142008

07/19/2008 08:51 AM <DIR> .
07/19/2008 08:51 AM <DIR> ..
07/14/2008 05:41 PM 2,147,464,817 C-071001.GHS
07/14/2008 05:42 PM 598,245,376 C-071002.GHS
07/14/2008 05:46 PM 349,705,127 C-071003.GHS
07/14/2008 05:46 PM 2,147,466,450 C-07152008.GHO
07/19/2008 08:35 AM 106 readme.txt
5 File(s) 5,242,881,876 bytes
2 Dir(s) 11,520,425,984 bytes free

H:\Images\C-07142008>attrib
A H:\Images\C-07142008\C-071001.GHS
A H:\Images\C-07142008\C-071002.GHS
A H:\Images\C-07142008\C-071003.GHS
A H:\Images\C-07142008\C-07152008.GHO
H:\Images\C-07142008\readme.txt

I can create, delete, rename, edit, etc. with the readme.txt I added
earlier today, but not the *.GHS and *.GHO files. I even made a new
folder/directory in H:\Images\C-07142008\ without any problems. I
ran chkdsk h: and had no errors and problems. I used Unlocker tool
to see if any files were used, nope. I tried logging off from my
"Ant" administrator account and logged in as "administrator" and I
cannot eevn access H:\Images\C-07142008\ directory\folder at all
("access is denied").
I rebooted and went to safe mode with my "administrator" account
based on http://support.microsoft.com/kb/823306 ... I also got the error,
but it said I could take over the ownership, audits, etc. (with
Administrators) since XP didn't know who owned these files. I
applied to Administrators and now I can access, rename, move, etc.

I made these *.ghs and *.gho files from a Norton 2003 (12/24/2003)
DOS version [not the Windows version since I don't trust Windows].
I backed up my C: drive before upgrading XP Pro. SP2 to SP3 in case
anything goes wrong.

Any ideas why this happened? I don't recall this happening in the
past (2006 and earlier). Was there a change in XP SP3 or some KB
updates to cause this in NTFS? I used the same exact Ghost DOS and
method many times from the past. Is there a fix or this?

You didn't own the files and/or have permissions to them. Why you did not
own them - I cannot say with 100% certainty. Especially since you probably
did not originally write these GHO files onto an NTFS directory - unless you
did it over a network share?

Norton Ghost created them via a DOS bootable CD. Ghost can handle NTFS.
I never had this problem before. Maybe it's a new thing in SP3 or KB
updates? Now, that I think about it. I don't remember it doing this in
SP2 before I upgraded to SP3.
--
"I once heard the survivors of a colony of ants that had been partially
obliterated by a cow's foot seriously debating the intention of the gods
towards their civilization" --Archy the Cockroach from Don Marquis'
"Archy and Mehitabel" book ("Certain Maxims of Archy" poem)
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: (e-mail address removed)
( ) or (e-mail address removed)
Ant is currently not listening to any songs on his home computer.

 

[Shenan Stanley]

Norton Ghost created them via a DOS bootable CD. Ghost can handle
NTFS. I never had this problem before. Maybe it's a new thing in
SP3 or KB updates? Now, that I think about it. I don't remember it
doing this in SP2 before I upgraded to SP3.

Ghost cannot 'write' to NTFS - or read from NTFS. Ghost is an application
used for making images. There are DOS and Windows (and so on) versions of
Ghost. You can create a bootable media for Ghost - but what that bootable
media can do depends on your choice of what to make it out of. If you did
it using a DOS boot disk/image - then it cannot natively read/write from/to
NTFS. There are other products that make this possible - but it cannot do
it directly.

Now - if you wrote to an NTFS formatted disk (locally connected when you
made the image) and you did it from DOS - then you either have one of those
products installed or what you are saying is not entirely accurate (it is
not a DOS bootable CD - but something else.) If you wrote to the NTFS
formatted media over the network - then it doesn't matter what you boot with
as long as your networking works. The file format is irrelevant if writing
to it over the network.

So - when you made these images - did you map a network drive after booting
and write these images to a network shared area or did you write to a
direct-connect area (CD, DVD, external USB/Firewire drive, internal hard
disk drive, etc.)?

I make ghost images practically a half-dozen times every week and apply them
to many different machines as well. I have not had any trouble with
permissions.

 

[Galen Somerville]

Ghost cannot 'write' to NTFS - or read from NTFS. Ghost is an application
used for making images. There are DOS and Windows (and so on) versions of
Ghost. You can create a bootable media for Ghost - but what that bootable
media can do depends on your choice of what to make it out of. If you did
it using a DOS boot disk/image - then it cannot natively read/write
from/to NTFS. There are other products that make this possible - but it
cannot do it directly.

Now - if you wrote to an NTFS formatted disk (locally connected when you
made the image) and you did it from DOS - then you either have one of
those products installed or what you are saying is not entirely accurate
(it is not a DOS bootable CD - but something else.) If you wrote to the
NTFS formatted media over the network - then it doesn't matter what you
boot with as long as your networking works. The file format is irrelevant
if writing to it over the network.

So - when you made these images - did you map a network drive after
booting and write these images to a network shared area or did you write
to a direct-connect area (CD, DVD, external USB/Firewire drive, internal
hard disk drive, etc.)?

I make ghost images practically a half-dozen times every week and apply
them to many different machines as well. I have not had any trouble with
permissions.

I have backed up and restored NTFS partitions with Ghost 2003 many times.
This was done by booting up on a DOS disk and running Ghost. Also, by
running Ghost Explorer in WindowsXP, you can retrieve individual files.

But I went to Acronis because Ghost caused a lot of disk swapping if NTFS.

Galen

 

[Shenan Stanley]

I have backed up and restored NTFS partitions with Ghost 2003 many
times. This was done by booting up on a DOS disk and running Ghost.
Also, by running Ghost Explorer in WindowsXP, you can retrieve
individual files.
But I went to Acronis because Ghost caused a lot of disk swapping
if NTFS.

Galen,

No one said anything about being able to backup NTFS partitions with Ghost
(we all know one can do that.)

I was talking about saving those GHO and GHS files to an NTFS formatted
partition as you created them using a DOS boot media. A purely DOS boot CD
will not allow you to READ/WRITE from/to an NTFS partition directly.

 

[Galen Somerville]

Galen,

No one said anything about being able to backup NTFS partitions with Ghost
(we all know one can do that.)

I was talking about saving those GHO and GHS files to an NTFS formatted
partition as you created them using a DOS boot media. A purely DOS boot
CD will not allow you to READ/WRITE from/to an NTFS partition directly.

I just reread the original, (slaps forehead) sorry.

Galen

 

[Ant]

Ghost cannot 'write' to NTFS - or read from NTFS. Ghost is an application
used for making images. There are DOS and Windows (and so on) versions of
Ghost. You can create a bootable media for Ghost - but what that bootable
media can do depends on your choice of what to make it out of. If you did
it using a DOS boot disk/image - then it cannot natively read/write from/to
NTFS. There are other products that make this possible - but it cannot do
it directly.

Now - if you wrote to an NTFS formatted disk (locally connected when you
made the image) and you did it from DOS - then you either have one of those
products installed or what you are saying is not entirely accurate (it is
not a DOS bootable CD - but something else.) If you wrote to the NTFS
formatted media over the network - then it doesn't matter what you boot with
as long as your networking works. The file format is irrelevant if writing
to it over the network.

So - when you made these images - did you map a network drive after booting
and write these images to a network shared area or did you write to a
direct-connect area (CD, DVD, external USB/Firewire drive, internal hard
disk drive, etc.)?

No, I did not use any networks. Just three interl HDDs. I went from one
partition (C:; first physical drive) of a HDD to another HDD (H:; third
physical drive). All drives/partitions are using NTFS. AFAIK, Norton
Ghost DOS can read and write from/to NTFS drives. Here is PowerQuest's
PartitionMagic v8.0 information:

===========================================================================================================
Partition Information for Disk 1: 114,471.0 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
H: NTFS Pri 17,241.6 0 0 63
35,310,807
I: NTFS Pri 97,229.3 0 1 35,310,870
199,125,675


===========================================================================================================
Partition Information for Disk 2: 76,316.6 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
D: NTFS Pri,Boot 19,908.6 0 0 63
40,772,907
ExtendedX Pri 56,407.9 0 1 40,772,970
115,523,415
EPBR Log 56,407.9 None -- 40,772,970
115,523,415
G: NTFS Log 56,407.9 40,772,970 0 40,773,033
115,523,352


===========================================================================================================
Partition Information for Disk 3: 305,242.8 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
Unallocated Pri 47.0 None -- 63
96,327
C: NTFS Pri,Boot 107,003.3 0 0 96,390
219,142,665
E: NTFS Pri 99,002.1 0 1 219,239,055
202,756,365
F: NTFS Pri 99,190.4 0 2 421,995,420
203,141,925


===========================================================================================================
Boot Record for drive H: (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 35310806
17. MFT Start Cluster: 1471283
18. MFT Mirror Start Clust: 2206925
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0xFCBC11F2BC11A862
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive I: (Drive: 1, Starting sector: 35,310,870, Type:
NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 35310870 (0x21ACD16)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 199125674
17. MFT Start Cluster: 8296903
18. MFT Mirror Start Clust: 12445354
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x3A60C7FA60C7BAC1
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive D: (Drive: 2, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 40772906
17. MFT Start Cluster: 786432
18. MFT Mirror Start Clust: 16
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0xE32AD896AA0DE590
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive G: (Drive: 2, Starting sector: 40,773,033, Type:
NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 115523351
17. MFT Start Cluster: 786432
18. MFT Mirror Start Clust: 16
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x0810ECE0F689EEA1
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive C: (Drive: 3, Starting sector: 96,390, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 96390 (0x17886)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 219142664
17. MFT Start Cluster: 9130944
18. MFT Mirror Start Clust: 13958560
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x1014DDA214DD8B5C
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive E: (Drive: 3, Starting sector: 219,239,055,
Type: NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 219239055 (0xD11528F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 202756364
17. MFT Start Cluster: 8448181
18. MFT Mirror Start Clust: 12672272
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x7FC819D4BFA7D121
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive F: (Drive: 3, Starting sector: 421,995,420,
Type: NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 421995420 (0x1927239C)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 203141924
17. MFT Start Cluster: 8464246
18. MFT Mirror Start Clust: 12696382
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x38CAB625AA837964
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

I make ghost images practically a half-dozen times every week and apply them
to many different machines as well. I have not had any trouble with
permissions.

Weird. I wonder what happened for me. This was my first time ever.
However, I haven't used Ghost to back up drives since end of 2006.
--
"The life of an ant and that of my child should be granted equal
consideration." --Michael W. Fox, Vice President, The Human Society of
the United States, The Inhumane Society, New York, 1990.
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: (e-mail address removed)
( ) or (e-mail address removed)
Ant is currently not listening to any songs on his home computer.