search

davidgiven / fluxengine

PSOC5 floppy disk imaging interface
MIT License
356 stars 68 forks source link

Greaseweazle v4 and brother format #440

Open ZHolyhell opened 2 years ago

ZHolyhell commented 2 years ago

The greaseweazle v4 does not appear to want to write the brother 120 or 240 formats.

It writes and verifys 6 times then posts error: write failed: uncorrectable error during write.

davidgiven commented 2 years ago

Are you using an HD or DD disk? You can't write Brother formats to HD disks (the pulse intervals are too wide). I can verify here that I can write DD disks but not HD disks, which produce the symptoms you describe.

ZHolyhell commented 2 years ago

It appears you are correct it was the disk (none of my disks have density labels and they came with the word processor) but what was written when I found a disk that wrote the image had 3 corrupted files (including the spreadsheet itself) though the original works fine. I will try writing again next.

On Wed, Feb 2, 2022, 14:02 David Given @.***> wrote:

Are you using an HD or DD disk? You can't write Brother formats to HD disks (the pulse intervals are too wide). I can verify here that I can write DD disks but not HD disks, which produce the symptoms you describe.

— Reply to this email directly, view it on GitHub https://github.com/davidgiven/fluxengine/issues/440#issuecomment-1028438271, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXI5ZEI7TKMMYAO3DLN2L5DUZGZWZANCNFSM5NM3TU2A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

davidgiven commented 2 years ago

HD disks have two holes at the top; DD disks only have one.

Did I understand you correctly that you imaged the original disk, wrote it back to another disk, and got corrupt files? That shouldn't happen...

ZHolyhell commented 2 years ago

Yes I did have that happen it appears that sometimes it does not completely read the diskette and will sometimes miss a spot in a write repeating a few times over the same disks worked out though

I wound up having to read 3 times to get an image that had the most bits on docs contained within and write that image to another disk twice to get it to produce a successful image on it

davidgiven commented 2 years ago

If it fails partway through, try increasing the number of retries --- --decoder.retries=10 or so.

ZHolyhell commented 2 years ago

It never told me it failed it just wasn't 100% the first time reading or writing I would recommend it compare file created/read from to disk after creation though it would take longer to complete overall it would be a little more user friendly overall and ensure accuracy of both

davidgiven commented 2 years ago

Interesting. You should be seeing a 'Unrecoverable error, giving up' message. Could you attach the log from a failed run?

ZHolyhell commented 2 years ago

Well I sent all I could to your cowlark email since github didn't seem to like the files

davidgiven commented 2 years ago

I have actually obtained a WP-1, and discovered that the brother120 encoder was horribly broken. I've fixed it. Could you upgrade to the latest development build and try again, please?

ZHolyhell commented 2 years ago

Uh my brother wp-2410 may use .wp1 word processor files but it uses the brother240 disk format

davidgiven commented 2 years ago

You said you were writing 120kB disks?

ZHolyhell commented 2 years ago

I was testing to see if it could since the 240 wasn't working we solved (i had the wrong disks) that part this is still open for the fragmentation/corruption issue which isn't just happening with brother files the ones I sent you showed the same sort of problem on ibm1440 disks