11-20-2013, 02:46 PM
Beta 0.44 changed invalid GCR checking to show all possible invalid values. When 0 bits span between two bytes, the nibbles of each byte are colored to show the invalid value is between bytes.
Made a new option under DRIVE SETTINGS called "Weakbits". This can be set to either Raw or Fixed. Using the Raw setting will not alter the GCR decoding. Using the Fixed setting (default mode) will correct weakbits so that it works with WinVICE. WinVICE's data separator does not handle weak bits properly. It expects at least one full nibble to be 0's for a weak bit to be on an even frame boundry, and appears that in some cases (depending on the g64 image's framing) needs the entire byte to be 00 in order for it to generate a random byte when encountering a weak bit.
Fixed issue with G64 and MNIB image files have flux start/end data if a real disk was read before hand. Other small clean ups.
Made a new option under DRIVE SETTINGS called "Weakbits". This can be set to either Raw or Fixed. Using the Raw setting will not alter the GCR decoding. Using the Fixed setting (default mode) will correct weakbits so that it works with WinVICE. WinVICE's data separator does not handle weak bits properly. It expects at least one full nibble to be 0's for a weak bit to be on an even frame boundry, and appears that in some cases (depending on the g64 image's framing) needs the entire byte to be 00 in order for it to generate a random byte when encountering a weak bit.
Fixed issue with G64 and MNIB image files have flux start/end data if a real disk was read before hand. Other small clean ups.