Same for you - missed you comment - sorry.
HaQue wrote:
1) the format could be different than straight .wav
2) post processing done by decoder to not use all of the .wav spec or in a different manner than intended
I was able to reciver the not deleted fie from the NAND dump. There was some special handling required to extract the file but the format was correct.
Quote:
3) your dump included information such as SA bytes or ECC or something that further needs to be stripped out
That's done by etfsctl to get a device independent representation of the etfs content.
Quote:
4) files are not stored in a totally concurrent fashion... I have seen recently while hacking some games consoles that ROM files for example have a block of DATA and if the ROM is bigger than this, the next block is stored somewhere else, not straight after.
I assume all the data is stored in the NAND.
Quote:
5) your dump might be ok, but not ECC corrected, so bit errors are present. (Linux systems that use NAND should have this built in though at a driver level)
Extraction of non deleted files was possible and I detected no ECC errors
Quote:
6) may be some binary to ascii conversion happening, but I would think files would be totally screwed up if this were the case (thinking like specifying BINARY option in some rudimentary older protocals)
I had to use little endian format and everything was OK.
Quote:
kudos or getting this far. I remember when I first got a prompt from a Microvax 3400 after a friend came across 2 complete but disassembled systems. right at the start of accessable internet, searching was in infancy, and I had help from a Tafe college lecturer that correctly identified the plug that looked like a LAN port as a terminal adapter port. not knowing anything about unix, terminals etc. this opened up a whole new world
Yes, I was glad when I managed to enter the Unix system via console and to find some doc and C code in the net about etfs and etfsctl.