| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 58622 | 2005-06-06 14:29:00 | Need to Access a Protected Folder | intelliagent (429) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 361716 | 2005-06-07 04:11:00 | Actually its because you're using FAT32, not NTFS. Its an NTFS Permissions thing - And yes, the INSERT Rescue CD will allow those to be reset. UNLESS the files are encrypted, but I dont know many people who use the built-in NTFS encryption. Chill. |
Chilling_Silence (9) | ||
| 361717 | 2005-06-07 04:14:00 | Thanx SurferJoe :), I always wondered cause Home is on relevant list... | amazonsister (8289) | ||
| 361718 | 2005-06-07 04:21:00 | Let me just clarify here: (1) Set the slave back to Master, and reinstall Windows XP Home? - will this damage the data on the drive? You can, but you risk making an easy mistake and formatting the drive or the likes . You can re-install Windows, but its not a good idea to go over top of itself . (2) Find a utility that will allow me access to the folders - around the protection (does a miracle utility such as this exist)? Yes, this is what the INSERT Rescue CD does . It'll let you view/copy/backup all the files on that HDD . (3) copy a new file of mup . sys & hope this works - and no other system files are corrupted? AFAIK it doesnt work like that . . . . :( |
Chilling_Silence (9) | ||
| 361719 | 2005-06-07 11:20:00 | If is realy important get GetDataBack for the link I posted above. | Rob99 (151) | ||
| 361720 | 2005-06-08 00:19:00 | Am I missing something here? If the HD from the stuffed Mobo is set as slave in another PC then why can one not take ownership. The HD might have XP on it but it is not booting off it so why would that matter? It is just another drive with data on it. I have done this before, taken ownership of the whole drive with the XP on it set as slave or just the folders I want access to and copied the files I want. | berryb (99) | ||
| 361721 | 2005-06-08 00:58:00 | In off-post communication with Chilling_silence, I think I might have some bad info as I too have had a real problem with trying to access data generated under XP, and then trying to use it in another tower . OK, let me tell what happened to me, and then I can be persuaded to see my mistakes: I had a RAID setup on a tower (actually called "JBOD"), XP-PRO the opsys, and data files (mp3's, iso, doc, etc) on the other drives . I decided to change the tower for a newer and hotter speed one, and I tried to transfer the opsys first . NO good at all! It got ignored and told me there was no operating system found . Now, I can handle that, and I went on and did an fdisk and installed (clean) XP-PRO on what I like to call my "OPSYS" hd . It is usually a small one, under 10giig . Here's where the real eye-opener was . I had the other disks in a new RAID array, and they too, although I could SEE THE FILES, could NOT ACCESS THEM!!!! I assumed (AND WILL SIT OR STAND CORRECTED IF I AM WRONG HERE) that I should be able to use them (access as in PLAY the MP3's, see the pictures or view the movie (DVD shrunk to . iso, WINRAR'd and POWER DVD played . ) NO WAY!!! Then I got told by smarter and very much younger children (mine) that I was trying to run files under a different opsys even though it too was XP-PRO . Seems, the said, that there is an ID that XP sets up (we used to call it a parity test) and is written to the zero sector or BAM or whatever it currently is called that will not allow it to work . I, (again) was told that this is a security grenade that M$ puts in to make it impossible to take a hd outta one machine and use it on another . OK . . beat me with a stick, but I still don't see how using a different mobo to read a file is supposed to work, especially if it came off a different tower with a different mobo/bios/bam/etc . I don't think a utility to do this exists, and if it does, I'm sure M$ will send out an SP-xyz to stop it . Just a thought . . . . . :2cents: Please don't use a big stick . :D |
SurferJoe46 (51) | ||
| 361722 | 2005-06-08 01:58:00 | There are many people here including me, who will slave a HD with another OS to gain access to the files for backup. If I cant access the files, taking ownership works most of the time, failing that I use GetDataBack. If you are trying to recover anything off 1 previously raided disk I think you would be luckie. Never used Raid and with my little knowledge with raid, I think it uses two or more disks and writes to both to speed up the reading and writing to disk. One file can be spread over both disks in Raid, therefor you will need both working to access the file. |
Rob99 (151) | ||
| 361723 | 2005-06-08 06:52:00 | SurferJoe. I agree with Rob. Your issue would be caused by RAID and depending on how you had it setup. RAID 0 implements a striped disk array, the data is broken down into blocks and each block is written to a separate disk drive. Hence trouble accessing files when one drive is taken out of the system. Raid 1 basically mirrors both drives, so all files (including OS) are on both drives. | berryb (99) | ||
| 361724 | 2005-06-08 10:41:00 | Im no whizz with RAID - Never done it in my life! However, berryb is right - You just need to assume ownership of the files. This can usually be done by root/administrator of the currently loaded OS. Booting INSERT or any Linux OS circumvents any ownership that may have been in place. Same thing happens if I were to boot it on my Gentoo box (Except /home could be encrypted.... ;). |
Chilling_Silence (9) | ||
| 361725 | 2005-06-09 04:06:00 | RAID using JBoD is Just a Bunch Of Disks. It is used to treat a whole lot of hard drives as one big one. It dosn't have any of the benifits of the other RAID modes. If you only have one disk atttached to a RAID adapter it usually sets up as JBoD array with only one disk. I think in the case described by JoeSurfer46 RAID is just being a distraction, because a JBoD array of one is the same as one disk attached normally. To solve intelliagent's problem, I would boot the computer using knoppix, then copy the data to a share. It has worked for me in the past, including where the take ownership method failed (the drive was dieing). -Qyiet |
qyiet (6730) | ||
| 1 2 3 | |||||