home.social

#c01e — Public Fediverse posts

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

  1. @spacemoai I can read the first 9 sectors. The 10th reads a different one (like if the system believed it's a 2DD disk and was accessing the other "side"). However, the same .DSK image with the same machine (OpenMSX emulating an A1GT) has a different behaviour on BASIC (DSKI$) than BDOS (#F37D). My code is executed from the boot sector (at #C01E).

  2. @spacemoai I can read the first 9 sectors. The 10th reads a different one (like if the system believed it's a 2DD disk and was accessing the other "side"). However, the same .DSK image with the same machine (OpenMSX emulating an A1GT) has a different behaviour on BASIC (DSKI$) than BDOS (#F37D). My code is executed from the boot sector (at #C01E).

  3. @spacemoai I can read the first 9 sectors. The 10th reads a different one (like if the system believed it's a 2DD disk and was accessing the other "side"). However, the same .DSK image with the same machine (OpenMSX emulating an A1GT) has a different behaviour on BASIC (DSKI$) than BDOS (#F37D). My code is executed from the boot sector (at #C01E).

  4. @spacemoai I can read the first 9 sectors. The 10th reads a different one (like if the system believed it's a 2DD disk and was accessing the other "side"). However, the same .DSK image with the same machine (OpenMSX emulating an A1GT) has a different behaviour on BASIC (DSKI$) than BDOS (#F37D). My code is executed from the boot sector (at #C01E).

  5. @spacemoai I can read the first 9 sectors. The 10th reads a different one (like if the system believed it's a 2DD disk and was accessing the other "side"). However, the same .DSK image with the same machine (OpenMSX emulating an A1GT) has a different behaviour on BASIC (DSKI$) than BDOS (#F37D). My code is executed from the boot sector (at #C01E).