DrCoolZic wrote:New release of Aufit v1.2 August 12, 2015
Jean : will you release a stand alone version for this release, or maybe in the next versions ?
Jeff_HxC2001 wrote:DrCoolZic wrote:PS I have tested reading DM with HxC floppy emulator and the content of sector 7 seems to be correctly decoded. However the .stx file generated is incorrect (seems like HxC does not handle fuzzy bytes in STX?).
Y a qu'a demander
Here is the latest version with the STX fuzzy bytes export support :
http://hxc2001.com/download/floppy_driv ... t_beta.zip
The STX created from the Dungeon Master SCP dump work perfectly with Steem.
- The number of fuzzy bytes detected by HxCFloppyEmulator 126.96.36.199 on DM/CSB is around 176. This seems a very high number. Aufit 1.1 was detecting fuzzy bytes by just comparing two revolutions and the number was around 30-40. Gothmog pointed out that Pasti imager was usually generating around 70-90 fuzzy bytes in the mask. So new version 1.2 of Aufit now combines all fuzzy bytes by comparing one revolution with ALL other revolutions and indeed the number is now around 70-90.
Can you explain why you find such a high number of fuzzy bytes? This is not really a problem just a question.
The .stx file generated by HxCFloppyEmulator does not contains track data and this results in a .stx file with a small size of about 415KB. In the case of DM/CSB this is correct and actually perfect.
The question is the following: knowing when to generate track data (used by read track) is extremely difficult in some cases. For that reason the latest versions of Pasti imager ALWAYS generates track data (to be on the safe side). Only the Ijor personal version of the Pasti imager (using the Discovery Cartridge hardware) had the capability to generate .stx without track data. In released Aufit the track data are also always generated. Gothmog just tested Aufit v1.3 with the capability to manually indicate not to generate track data. Should be able to do that automatically on a track basis when "master analysis" will be implemented in Aufit.
In HxCFloppyEmulator when/how do you decide not to generate track data?
related question: stx format support an optimization of not writing sector data when already present in the track data. Aufit support this capability which is a pain to implement but allows to generate smaller file. Does HxCFloppyEmulator support it? Again not a problem just a question
DrCoolZic wrote:By the way HxCFloppyEmulator DPLL seems to be be doing quite a good job, apparently better than Aufit in one marginal test case
DrCoolZic wrote:Otherwise for portable version visit http://info-coach.fr/atari/software/pc- ... p#download
Thanks for the good work : any standalone version planned for the v1.3 + batch ?
DrCoolZic wrote:As indicated it is here
Otherwise for portable version visit http://info-coach.fr/atari/software/pc- ... p#download
Users browsing this forum: No registered users and 3 guests