See something odd? Please report it here. Thanks!
Beta .90
Found a possible bug in the analyzer. Load a track 2 revs, switch to flux view, find the center marker in yellow, switch back to GCR - the analyzer takes you back to the top of the track. You lose your position of the center marker in yellow from flux to GCR.
That's just for your version!
Thanks for the report. I knew I broke the MFM place holder, but I didn't know I broke the GCR place holder too.
(12-21-2013, 08:38 AM)admin Wrote: [ -> ]That's just for your version!
Thanks for the report. I knew I broke the MFM place holder, but I didn't know I broke the GCR place holder too.
I like my broken version - think I'll keep it! lol
Thanks Jim!
With v0.96, if you read or write a disk image through the copier, then change to the analyzer and press the Flux Display button, it crashes with an error. Usually a divide by zero error, but sometimes an overflow error.
Also, when browsing through the tracks of an image in the analyzer (disk imaged with index mode, standard 80 tracks), it won't let you go past track 79 head 0. If you try to view past this, error "subscript out of range". This error does not occur when reading from physical disk. Hope this doesn't mean the image itself is chopped off at 79/1.
Not sure if this is a bug, or intended behaviour, but when looking at a 3 revolution track in the analyzer, it shows the vertical red line on the left, followed by one revolution of flux data, then the red line again, then all 3 revolutions packed into the right-hand side of the window. I always thought the red line indicated the start of track within the image (index hole if it was read aligned to that), so that I would see 3 of these lines if there were 3 revolutions in the image.
Thanks for the report. I have never seen the crash when switching between the copier and analyzer, and I do that quite often. I will try it exactly as you have stated.
I have never looked past track 79/head 1 with an image. It's not cut off because there is space for the entries in the file format (I just went through testing that, but I looked at the generated file with a hex editor, not the analyzer). I will check that out.
The red line is just thrown out there... ignore it for now. I am reworking the flux display to hand strongbits and will also add the position and zoom functions, and the ability to turn on/off the separators (in their correct positions) as well.
OK, I can't generate the error switching between the copier and analyzer, after copying or not - but I have an idea what might cause that because you shouldn't be able to click on anything because nothing has been initialized yet. I will fix that.
I did see the problem you reported when making an image file that used tracks 0/0-82/1 with 3 revolutions. I opened the file with the analyzer and had a problem when going from 81/1 to 82/0. So, I will look into that over the weekend.
The image file I created was a standard 0/0 to 79/1, but I couldn't look at 79/1 as it topped out at 79/0 before giving the error, although the scroll bar showed it could go further.
Oddly enough, I can't reproduce the problem again. The slider now correctly shows 79/1 as the last track and won't go past it. Perhaps something got confused when switching back and forth between analyzer and copier before.
The "delete byte" button in the analyzer doesn't work correctly. It removes the entry from the flux window, but if you change to the GCR window, no changes are apparent, and then moving back to the flux window shows the deleted bytes have returned.
Insert byte works properly.
Insert byte should do nothing as well. These options are only for GCR and MFM and do not affect the flux data.