emusonacid! legacy

So i removed HDD from E6400 ultra and i connected HDD to my PC. Obviously in Windows Explorer i don't see a thing. But i was expecting that Chickensys Translator can see what is on that HDD ???

I have Translator for a long time so i know how to use it. ASPI drivers are installed proerly. I even see that HDD inside chickensys translator drive option. HDD is installed properly and i see it in XP device manager. When i open XP disk manager it can "see" that HDD. Of course every time i start XP disk manager i have that window tellin me that i should initiate that HDD as dynamic (now is basic) but i don't want to do that. I don't want to loose samples...

Any tips...

So i managed to loose all my data on HDD i did not do anything. HDD has been connected to PC. Translator started but i did not do anything...well one thing. i copied HDD content to my PC via translator but that is all. I doubt this killed my content but if it is then i will throw that chicken crap out of this place..

Now when i fire up e6400 i only see Root folder and nothing else. I believe that content is somewhere inside but how can i restore it back?

Sad day...

Edit: i just found that "initialization" in XP will lead to system loss.
viewtopic.php?t=943&highlight=disk+repair

But i doubt that data is lost. C'mon there are few gb of data...something just need to be restored...aaaaaahhhhh

If you let XP initialize the drive, its going to re-write the FAT32 table and master boot record.

Was it a FAT32 formatted drive or an EOS formatted drive?

It sounds like it was EOS formatted (since XP asked to initialize it)- in which case, it will be difficult to recover data as the pointers to the hard disk structure (i.e. files) have been over written. EOS is proprietary. you might want to email Chicken sys about it....and your situation.

If its FAT32 however, you MAY be able to recover the files using a recovery or unerase tool.

I would however strong recommend somehow taking a binary image of the drive bit for bit before you do anything and better still, use only recovery tools on the copy, not the damaged original.

M