forum.defence-force.org

It will not work, in co65 source code (co65/convert.c) /* For now, we do only accept o65 files generated by the ld65 linker which ** have a specific format. */ if (!Debug && D->Header.mode != O65_MODE_CC65) { Error ("Cannot convert o65 files of this type"); } So Header.mode must be...

In co65 source file o65.h is /* The mode word as generated by the ld65 linker */ #define O65_MODE_CC65 (O65_CPU_6502 | \ O65_RELOC_BYTE | \ O65_SIZE_16BIT | \ O65_FTYPE_EXE | \ O65_ADDR_SIMPLE | \ O65_ALIGN_1) which is 0x0800 (in fact the value of O65_ADDR_SIMPLE as all flags are 0x0000) xa defines ...

Hello, So you want to convert a file from o65 to xo65 and use it with cc65/cl65, right? Maybe you can try with co65 which can do some conversion, but you have to modify the byte at offset 7 from $10 to $08 in the object file created by xa for co65 to recognize the file (it's the mode type) co65 crea...

Hi, maybe something like this: CMP #$A4 ; (2 cycles) ROL ; Put C in b0 of ACC (2 cycles) EOR #$01 ; Invert b0 (2 cycles) ROR ; Put b0 in C (2 cycles) ROR $2F ; ROR C to $2F (2 cycles) Total 10 cycles Only Carry inverted, and ACC not modified (if i'm right)

Hi Xeron, I think i've found 2 bugs in oricutron both located in tape.c file: First bug: in function tape_load_tap // TAP else if (memcmp(oric->tapebuf, "\x16\x16\x16", 3) == 0) { oric->rawtape = SDL_FALSE; // I give up trying to do anything clever. // Just allow an extra byte for broken t...

I think the last version is FT-DOS 3.2, first versions were called T-DOS without the F (for Fast), at least T-DOS 2.26

I'm not sure it depends on Sedoric's version because if I format a single sided Sedoric v3 disk with 17 sectors and 21 tracks, the second bitmap at T20 S03 is filled with $00, but 16 sectors and 24 tracks single sided fill the second bitmap with last available sector number and so on. My assumption ...

I answer to my own question: Track #20 Sector #03 can be filled with $00 if the disk is single sided, so I must modify OricFS accordingly. I finally succeeded in formatting a Sedoric Disk with Euphoric, Oricutron can't format Sedoric disks which is a bit strange because it can format FT-Dos disks......

What I did: tap2dsk welcome.tap test.dsk old2mfm test.dsk oricutron -d disks/sedoric3.dsk (then insert test.dsk in drive B) Oricutron can read the dsk and can save a file on it OricFS can read the dsk but can't add file, so I think there is something else. The reason why OricFs can't add a file is t...

I found 2 different versions of tap2dsk, one in http://miniserve.defence-force.org/svn/ ... n/tap2dsk/ and one in http://miniserve.defence-force.org/svn/ ... c/tap2dsk/
I think the one in odsk directory is the last, right?

Until now, I can't raise the same error.
I will test with a disk created by tap2dsk and see if it's ok or not

The wrong sector may be Track #14 Sector #02 (first bitmap)... Can you tell your friend to type the following commands in the mounted filesystem: cat .h0t20s02?dump and post or check the result? Something like: 0000 FF 00 09 00 34 00 2A 11 04 AA 00 00 00 00 00 00 ....4.*......... 0010 00 00 00 00 00...

Can't find what means "read fault 10", if somebody can help. Anyway, Track #14 Sector #01 should not be modified by OricFS except if you modify the hidden file .source in the mounted filesystem. If you can't send the disk image, can you tell your friend to type the following commands in th...

Ok, I will check Sedoric manual to see what means "read fault 10".
Do you know if the disk image is a fresh one generated by OricFs or by another tool?

Maybe you can send me the disk image so I could see what's wrong.

@Chema: can tell me

• the OS version on the image disk (ie Sedoric 2 / FT-DOS 3.2,...)
• the operations you do (was it adding and removing the same file, was it with the emulator or through OricFs,...).
• The emulator you use

So i can try to reproduce this issue.
Thanks