DrCoolZic wrote:IMPORTANT MODIFICATION
Currently Bit 5 of TrackFlags is marked as not used. But in fact it is used!
Sarnau describe it as: 5 - with PASTI 0.4b always set, if Bit 0 is set (= track protected)
Files that I have generated with Aufit did not have this bit set and the resulting file was not working.
I have looked at many stx files and here what I believe is the meaning of bit 5:
- If bit 5 is set (bit 5=1) then this is the new format that implies that the readTime from Sector Descriptor HAS to be used (i.e. this time must not be equal to zero) unless the sector has the RNF flag set in which case readTime=0
For example this is the case in Maupiti Island where you have
Track 00.1 6293 bytes 1 sect FuzBytes=No Flag=61 TImage SDesc RecSize=6328 (11102-11117)
Sector T=7 H=0 SN=7 S=183 CRC=6607 bitPos=440 Time=0 Flags=18 Off=0 (11118-11133)
- if bit 5 is not set (bit 5=0) this is old format and in that case he readTime behave as explained in the doc: value of 0 means normal sector, value !=0 means you have to use the provided value
This need to be confirmed before I modify the Pasti Doc
Any feedback is welcome
I haven't checked any file, so I can't confirm or not, but in that case, I don't see what information bit 5 is adding to the decoder library ?
Because in all cases, whether bit 5 is 0 or 1, you will always do :
if sector has RNF flag, stops and readtime is 0
else if readtime is != 0, use it directly
else if readtime == 0, use the standard delay for a sector
I don't see where bit5 is needed ; but maybe the meaning of bit5 is what you describe, it's just that from what I see so far in STX format, there's no extra bit added when information can be deduced from others values.
I will have a look at PASTI.PRG from PastiImgKit.zip to see how images are created, this will be the best way to get the answer (assuming images with bit5=1 were produced with v0.4 beta).