Compose your message:
Email Address :
Password:
OR
Your Name :
REAL Email Address :
(PRIVATE)
Subject :
Please type in your message (no HTML codes) :
[quote]On 04/10/2011 @ 13:34, Nate wrote : Made some more progress on this and now have some questions. The code currently lets you do the following by editing the text dump of an image: : : * Read/write .nib or .g64 : * Insert, change, delete GCR bytes : * Change SYNC length, delete SYNCs, add them, etc. : * Format is 5:4 bytes (GCR to decoded), two sets of these per line (10 bytes GCR) : : There are also commands to do the following: : : * Shift track: output 7 .nib or .g64 files with rotates of 1 to 7 bits for a given track # : : I'm looking at adding support for these features but uncertain which ones are most useful: : : * Align a given track (rotate in image), based on the following: : : - First sync found (10 bits of 1) : - Sector number (does some decoding) : - GCR pattern : : Are there any others that would be useful? Start track at longest sync? : : Of course, you can implement arbitrary track-to-track alignments with this by rotating track 1 to start at sector 0, track 2 to sector 15, or whatever. : : * Density conversion -- How should this be done? I understand that if you want to convert a range of data from higer density to lower, you just discard bits. But I think there's no way to go from lower to higher. : : For density, I support the g64 per-byte extended map so you can set arbitrary density for byte ranges within each track. Of course, you lose that info if you write out a .nib. : : Comments welcome. -- [/quote]
File to attach:
(limit 250000 bytes)
SECURITY QUESTION
I had 10 scotch bonnet peppers and then I found 9 more.
How many do I have now?
: