home.social

#flashfloppy — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #flashfloppy, aggregated by home.social.

  1. @robdaemon even the 34-pin cable is just a 26-pin with extra bits to do more than 1 floppy on one ribbon [it works like a primitive bus]...

    And with you should be able to make that just work versatile...

  2. @robdaemon even the 34-pin cable is just a 26-pin with extra bits to do more than 1 floppy on one ribbon [it works like a primitive bus]...

    And with #FlashFloppy you should be able to make that #GOTEK #FloppyEmulator just work versatile...

  3. @robdaemon even the 34-pin cable is just a 26-pin with extra bits to do more than 1 floppy on one ribbon [it works like a primitive bus]...

    And with #FlashFloppy you should be able to make that #GOTEK #FloppyEmulator just work versatile...

  4. Ultimately, what got me on the right path for Centurion floppy emulator was realizing that the Kryoflux images I was looking at would reflect some unknown amount of write postcomp by the drive and media. By writing tools to inject additional write precomp into the Kryoflux image, I was able to figure out that ~350ns of total write precomp was enough to confuse FlashFloppy. Inserting a 2nd order PLL with a natural loop frequency around 715kHz was plenty to recover a stable enough clock to decode MFM correctly.

    #retrocomputing #flashfloppy #floppyemulator

  5. Ultimately, what got me on the right path for Centurion floppy emulator was realizing that the Kryoflux images I was looking at would reflect some unknown amount of write postcomp by the drive and media. By writing tools to inject additional write precomp into the Kryoflux image, I was able to figure out that ~350ns of total write precomp was enough to confuse FlashFloppy. Inserting a 2nd order PLL with a natural loop frequency around 715kHz was plenty to recover a stable enough clock to decode MFM correctly.

    #retrocomputing #flashfloppy #floppyemulator

  6. Ultimately, what got me on the right path for Centurion floppy emulator was realizing that the Kryoflux images I was looking at would reflect some unknown amount of write postcomp by the drive and media. By writing tools to inject additional write precomp into the Kryoflux image, I was able to figure out that ~350ns of total write precomp was enough to confuse FlashFloppy. Inserting a 2nd order PLL with a natural loop frequency around 715kHz was plenty to recover a stable enough clock to decode MFM correctly.

    #retrocomputing #flashfloppy #floppyemulator

  7. Ultimately, what got me on the right path for Centurion floppy emulator was realizing that the Kryoflux images I was looking at would reflect some unknown amount of write postcomp by the drive and media. By writing tools to inject additional write precomp into the Kryoflux image, I was able to figure out that ~350ns of total write precomp was enough to confuse FlashFloppy. Inserting a 2nd order PLL with a natural loop frequency around 715kHz was plenty to recover a stable enough clock to decode MFM correctly.

    #retrocomputing #flashfloppy #floppyemulator

  8. Ultimately, what got me on the right path for Centurion floppy emulator was realizing that the Kryoflux images I was looking at would reflect some unknown amount of write postcomp by the drive and media. By writing tools to inject additional write precomp into the Kryoflux image, I was able to figure out that ~350ns of total write precomp was enough to confuse FlashFloppy. Inserting a 2nd order PLL with a natural loop frequency around 715kHz was plenty to recover a stable enough clock to decode MFM correctly.

    #retrocomputing #flashfloppy #floppyemulator