Hi Charles,
> I have Hugo aplenty:
>
> /temp> tr -c Hugo \\n <IMAGE.000|grep -b Hugo
> 92520:Hugo
> 92544:Hugo
> 220028:Hugo
> 220052:Hugo
> 300334:Hugo
> 300358:Hugo
> 380752:Hugo
> 380776:Hugo
> 461188:Hugo
> 461212:Hugo
> 541596:Hugo
> 541620:Hugo
Good. Here's the location of mine split into sector number and offset
in sector, preceeded by numbers of sectors since the last Hugo.
$ tr -c Hugo \\n <hi | grep -b Hugo |
> awk -F: '{print int($1 / 256), $1 % 256}' |
> awk '{print $1 - l, $1, $2; l = $1}' |
> xargs printf '%6d %6d %3d\n'
39080 39080 1
7 39087 251
$
Hugo comes in pairs; one near the start of a directory and one near the
end. My `blank' hard disc has just the root directory, $. The first
Hugo is always 1 byte from the start of the sector, the second 251.
For your Hugos above...
361 361 104
0 361 128
498 859 124
0 859 148
314 1173 46
0 1173 70
314 1487 80
0 1487 104
314 1801 132
0 1801 156
314 2115 156
0 2115 180
You always have two in the same sector, always 24 bytes apart. And the
first one isn't at an offset of 1.
Now Hugo can appear as normal data in a file, or a filename. And I
suspect this was just the start of your Hugos. But this still looks
odd.
What's
od -A x -t x1 -j $((1801 * 256)) -N 2048 IMAGE.000
give?
Cheers,
Ralph.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
arcem-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/arcem-user
