Completely working again
I am glad to hear that .
Lots of devices have bad blocks, it\'s how those bad blocks are handled that is important.
If the device knows that the block is bad and doesn\'t attempt to use it, then there is no problem, you will just have a filesystem that is either one block smaller than the norm or that block will be substituted for \"slack space\". Some devices use \"slack space\" which is an area of the disk/memory that is reserved for \"replacing\" bad blocks and is totally transparent to the operating system above it.
I do not know how the zaurus handles bad blocks, I am talking about generic/standard ways of handling bad blocks here.
If the device is trying to read/write to a bad block that has either not been \"ignored\" or \"substituted\" then you will get corruption of your filesystem, which would normally end in error city on boot up :cry:
I presume making a \"perfect\" chip is similar to making a perfect hard disk surface, (ie nearly impossible at a price that is affordable).
All this depends on what level the zaurus is checking it\'s memory, if it is low level (ie physical) then you probably have nothing to worry about. If the checks are being done at a higher level, ie after any substiution may have been carried out then you may have a problem, but I think this likely to result in either a totally unusable system or constant and severe corruption to you data.
Does anybody know how the zaurus deals with bad blocks?
Peter.
