your unknown partition overlaps your D partition, so it would seem to be a malformed partition table - perhaps a relic from your image process?
Are you using something like GPT drives, mapped drives etc perhaps? EEPC only supports classic MBR drive layouts with proper drive letters.
Is it Windows 7 perchance?
Hi, thanks for the replies.
We use ghost - whole disk images (not partition images) and I'm sure they don't use GPT drives.
Its XP i'm afraid.
Why would the standalone disk see it properly and not the other EETech disk?
Another question- if i was to force decrypt the drive would i use the correct information i got from the standalone disk, even though the normal EETech disk says otherwise?
difficult to say - I would look at the region list first, if that's valid, that's exactly the information you need, otherwise I would use the D: information, as the unknown partition is most likely a logical drive or a relic.
You could look around though using the workspace and work out whether the 63 sector difference is encrypted or not - I expect not though as EEPC would never encrypt an unknown partition type.
here's the region list
(finally found a screen capture for my bartpe!!)
I looked at all the sectors of the unknown partition and there was only a few characters in the very first sector and when i decrypted it it doesn't look (to me ) like anything ...useable?
do you think that i should use the two partitions as stated in the info from the standalone disk then to do a force decrypt:
P0- SS: 63 SC:76228362 C: P1-SS:76228488 SC:40965687 D: as this appears to tie in with the region list?
And do you know why the standalone disk only sees the presumably correct info?
1 of 1 people found this helpful
I think if the region list is there, you should ignore the partitions completely and follow that - why don't you just do a standard "Remove" - it would seem that the disk information is intact?
You don't even need to consider this for an eBoot even?
That sector was not encrypted to start with - there are NO patterns to encrypted data (thats the point), so a sure sign of no encryption is any runs of the same char, even zeros.
Thanks Simon, I'm not allowed to touch it at the moment, but when I do, I'll try a Remove EE first.
I have noticed that as mentioned previously that when you do a force decrypt (and get an "error getting disk info" error) you take the disk offline first; is it better to take the disk offline before doing a "Remove EE"- or doesn't it matter.
Its just that I've previously had many "Remove EE" actions hang and wondered if it was a good idea to take the disk offline first or won't it matter? as that would relate to the disk info not being intact rather than the disk being online