 |
|
| Dangerous Knowledge! |
|
|
By Daren Scot Wilson - Posted on May 11, 2002 - 20:38:37 (#1390)
Current version when comment was posted: 1.0 |
|
|
Such powerful tools do not belong in the hands of the unwashed masses! Maybe you should sell it for $15,000...
|
|
| Peace of mind. |
|
|
By 7 - Posted on March 9, 2002 - 23:26:11 (#577)
Current version when comment was posted: 1.0 |
|
|
I recently had a BFS crash due to a bad sector on my system.
I recovered the system, but was worried about what kind of corruption could have happened.
If there were some files with trinary bits in them, it could have caused system instability. I know this because I looked through the fs and kernel disassembly and found there was no code in there to handle that case.
Thankfully Mathias has created a program to check if any of the bits are not 1 or 0.
I let the program run on my whole system, and while it took a long time, I was relieved to find that I had no errors.
Thanks! The peice of mind that this application has brought me is priceless.
I think that the OpenBeOS team should include this as a background kernel process in the thier version of the OS.
Ease of use: A++
Features: A++
Price: A++
Overall Grade: A++
A must have peice of software for anyones system.
Alan
|
|
| Read(&byte, 1), yeah right. |
|
|
By ralfoide - Posted on March 9, 2002 - 13:34:46 (#571)
Current version when comment was posted: 1.0 |
|
|
The whole app is insanely slow in performances. Why not reading a whole 64k block of the file at once and unrolling the bit check loop?
Are you sure you tried that on your whole drive? Must have taken days!
What's the point of using an uint64 for the bit_value since you're testing a char * bytePtr?
This is a shameful waste of 56 bits of memory.
Plus to be really sure of the bit value, you can't trust the C++ compiler, you should do the test by yourself in PPC assembly.
my 2 cents
R/
|
|
|
|
|
