I hate these things, it's Friday and sunny outside and I am stuck with this thing. Anyone know the best way to remove the drive?
Have a good weekend everyone
Not sure about this particular model but if its anything like my own Vaio, you'll want to unscrew all the screws in the bottom of the case, this will release the keyboard and allow you to remove it. But there are a coupld of little catches at the top of the keyboard holding it in place. If you use an ipod tool you should be able to slide these out without causing any damage.
Then you'll need to detach all the minor connections below the keyboard. The hard drive should be just under the keyboard.
Hope this is useful.
pm sent
Just to follow this up, after a deep breath and a coffee, it struck me that I had missed the pretty obvious point that this model has BIOS USB support, so shoved a USB drive in and imaged in DOS,
thanks anyway
<snip>shoved a USB drive in and imaged in DOS
That is the best answer since, apart from having to reduce the thing to its component nuts and bolts, it has tiny three eared security screws that are real fun.
now this pain in the backside is imaging in DOS onto an external USB drive but very very slowly, it's a 100 Gig drive and after 14 hours it looks to have done around 25 Gig. It's a long time since I did an aquisition in DOS but I don't remember them being this slow. (I have not requested compression)
Following a colleagues experience, it crossed my mind that the drive was locked and Encase is seeing consecutive read failures and then responding by filling the image with zeros but Encase saw an NTFS partition which surely it could not have seen if the drive was locked?
Perhaps I will have to get the screwdrivers out after all….
As ever, grateful for any input
now this pain in the backside is imaging in DOS onto an external USB drive but very very slowly, it's a 100 Gig drive and after 14 hours it looks to have done around 25 Gig. It's a long time since I did an aquisition in DOS but I don't remember them being this slow. (I have not requested compression)
Following a colleagues experience, it crossed my mind that the drive was locked and Encase is seeing consecutive read failures and then responding by filling the image with zeros but Encase saw an NTFS partition which surely it could not have seen if the drive was locked?
Perhaps I will have to get the screwdrivers out after all….
As ever, grateful for any input
Are you sure you've got USB 2.0 support? Mind you, even if it was USB 1.1, it would be good for slightly more than 1 MB/sec which would give about 50 GB in 14 hours…
?
well, I gave up on the DOS image and eventually got the drive out,
connected to FTK imager via USB writeblocker, it is now imaging at 0.029 MB/sec , vey weird
well, I gave up on the DOS image and eventually got the drive out,
connected to FTK imager via USB writeblocker, it is now imaging at 0.029 MB/sec , vey weird
Maybe the drive is about dead. I'd try and let it finish.
yes, it did speed up a little and I did manage to get a full image but have advised client to replace drive as something is obviously wrong,
end of story,
on to the next challenge….