#f37d — Public Fediverse posts

@spacemoai MSXTurboR, DOS1

Anyway I've managed to make it work with PHYDIO. The problem happens only with #f37d + #2f call.

@spacemoai MSXTurboR, DOS1

Anyway I've managed to make it work with PHYDIO. The problem happens only with #f37d + #2f call.

@spacemoai MSXTurboR, DOS1

Anyway I've managed to make it work with PHYDIO. The problem happens only with #f37d + #2f call.

@spacemoai MSXTurboR, DOS1

Anyway I've managed to make it work with PHYDIO. The problem happens only with #f37d + #2f call.

@spacemoai MSXTurboR, DOS1

Anyway I've managed to make it work with PHYDIO. The problem happens only with #f37d + #2f call.

@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).

@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).

@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).

@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).

@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).

I'm having issues with a #MSX disk reading routine. If a use DSKI$ from the BASIC, I get what I expect. But if I use the BDOS call (through #F37D) I read a different sector of the disk (even if the logical sector number is the same in both cases).

Shouldn't be BDOS #2F function and DSKI$ internally the same thing? It is like if the MSX DISK BASIC used a pure logical numbering but the #2F function used a physical numbering. NOTE: it's a single-sided disk.

Any ideas?

I'm having issues with a #MSX disk reading routine. If a use DSKI$ from the BASIC, I get what I expect. But if I use the BDOS call (through #F37D) I read a different sector of the disk (even if the logical sector number is the same in both cases).

Shouldn't be BDOS #2F function and DSKI$ internally the same thing? It is like if the MSX DISK BASIC used a pure logical numbering but the #2F function used a physical numbering. NOTE: it's a single-sided disk.

Any ideas?

I'm having issues with a #MSX disk reading routine. If a use DSKI$ from the BASIC, I get what I expect. But if I use the BDOS call (through #F37D) I read a different sector of the disk (even if the logical sector number is the same in both cases).

Shouldn't be BDOS #2F function and DSKI$ internally the same thing? It is like if the MSX DISK BASIC used a pure logical numbering but the #2F function used a physical numbering. NOTE: it's a single-sided disk.

Any ideas?

I'm having issues with a #MSX disk reading routine. If a use DSKI$ from the BASIC, I get what I expect. But if I use the BDOS call (through #F37D) I read a different sector of the disk (even if the logical sector number is the same in both cases).

Shouldn't be BDOS #2F function and DSKI$ internally the same thing? It is like if the MSX DISK BASIC used a pure logical numbering but the #2F function used a physical numbering. NOTE: it's a single-sided disk.

Any ideas?

I'm having issues with a #MSX disk reading routine. If a use DSKI$ from the BASIC, I get what I expect. But if I use the BDOS call (through #F37D) I read a different sector of the disk (even if the logical sector number is the same in both cases).

Shouldn't be BDOS #2F function and DSKI$ internally the same thing? It is like if the MSX DISK BASIC used a pure logical numbering but the #2F function used a physical numbering. NOTE: it's a single-sided disk.

Any ideas?