05-15-2020, 08:38 PM
The code to write is the same. The output pulse duration is selected randomly for each write instead of having the same exact 4us pulse each time. You should definitely NOT use the older version because it can show false positives. If there was a failure to write at all (like a SCP hardware failure), reading the same disk would always show the write was successful when it fact nothing might have been written at all.
In your case, it most definitely shows the issue with the drive you are using, which should NEVER have the 'red' (no flux area) data stream preceeding the track. This same thing will happen when writing data to any disk during a copy. There is only one write routine and one read routine. Those routines are called by ALL of the functions in the software.
In your case, it most definitely shows the issue with the drive you are using, which should NEVER have the 'red' (no flux area) data stream preceeding the track. This same thing will happen when writing data to any disk during a copy. There is only one write routine and one read routine. Those routines are called by ALL of the functions in the software.