Disk conversion - with XP

[Symoon]

Some might recall I made a tape-based solution, that created DSK files from standard Sedoric disks.
The disk was read sector by sector on a real Oric, sent with CSAVE to the PC soundcard, the user had to make a WAV of it, then a script and special tapetool converted it back to DSK.
Quite slow but ran like a charm.

I tried to make it universal (all disks: Sedoric, Jasmin or whatever, even protected) by reading track by track with the help of Fabrice, but I noticed the track reading was quite random and generates or inserts many wrong bytes (tested on several drives, including NightBird's one); Fabrice and I tried to understand that last year but we had no time and it's another project in the vault so far.

Making it the other way (DSK to real disk) would be another challenge in trems of synchro between the PC sending data and the Oric writing it and possibly having write errors on disk, but one thing at time (or even somtimes, zero at time )

[Chema]

Hi,

About FUSE driver, you can do all what you want even mount a web site or a database.

I posted a message last year in this topic about such a tool for Oric dsk images.
More information can be found here (in french)

And I think I completely overlooked that message...

Maybe because it was Linux only and I can't read French at all...

I noticed you need to be registered in the French forum to get the files... any chance the tool could be uploaded here in DF too?

[Hialmar]

Here it is Chema:
https://www.dropbox.com/s/za34qll83gdzk ... 7.zip?dl=0

I just found out about the discussion on retrowiki.es and was too lazy to try to post a message with my broken Spanish

Edit: I attached it to this post. It's not too big.

[Chema]

Thanks!!

[Chema]

Hialmar... It seems that a file is missing (setuptools).

A Spanish guy is trying to set it up and he says that without that file it is not possible to try the package.

If you have it, would you mind posting it here too?

[Hialmar]

It's a Python module.
https://pypi.python.org/pypi/setuptools

Ah I forgot, if your friend is using Ubuntu (and a recent version of setuptools) he should use this archive instead.

[Chema]

Thanks Hialmar. Ron (who was testing this) made it work finally.

Apparently after adding removing files in the dis image, it stopped working on the emulator (gives an I/O error).

Any idea?

[christian]

@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

[Chema]

It was not me who made the tests (I don't have a Linux box). It was a Sedoric 3 dsk and the OS was Debian.

After adding files with FUSE, and unmounting it, the DSK became unusable giving a I/O error "track 14 sector 1 read fault 10" when issuing a DIR command. I am quite sure that the emulator was Oricutron.

[christian]

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.

[christian]

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 the mounted filesystem:

Code: Select all

cat .h0t20s01?dump

and check the result?
should be something like

Code: Select all

bash-4.1$ cat .h0t20s01?
0000   D2 D2 D2 D2 40 64 00 0A 00 94 20 53 45 44 4F 52    ....@d.... SEDOR
0010   49 43 20 20 56 20 33 2E 30 30 36 20 20 90 4D 45    IC  V 3.006  .ME
0020   4E 55 20 20 20 20 20 20 20 20 20 20 20 20 20 20    NU              
0030   20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20                    
0040   20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20                    
0050   20 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00              ......
0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0070   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0080   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0090   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00A0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00B0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00C0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00D0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00E0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00F0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

Bytes $00->$03: $D2 = $52 +$80 (82 tracks, double sided) one for each possible drives
Byte $04: Keyboard type
Bytes $05->$06: Default first line number (RENUM command)
Bytes $07->$08: Default step (RENUM command)
Bytes $09->$1D: Volume name
Bytes $1E->$59: INIST commands
Bytes $5A->$FF: null

[christian]

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:

Code: Select all

cat .h0t20s02?dump

and post or check the result?

Something like:

Code: Select all

0000   FF 00 09 00 34 00 2A 11 04 AA 00 00 00 00 00 00    ....4.*.........
0010   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0020   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0030   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0070   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0080   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
0090   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00A0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00B0   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
00C0   00 F8 FF FF FF FF FF FF FF FF FF FF FF FF FF FF    ................
00D0   FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF    ................
00E0   FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF    ................
00F0   FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF    ................

The first byte must be $FF

[Symoon]

Not very sure when it comes to FDC, but this really looks like a FDC error, not Sedoric.
My guess is that the disk structure has been altered, or maybe a side 1 / 2 problem?

You should check if the "error 10" is decimal or hexa - and see if you can find out in FD1793 specs it meaning.

[Chema]

I know ron (the guy testing this) from another retro forum, and he took a quick look at your tool when discussing possibilities to edit DSK files. I could drop him a message in the forum, but I doubt he still has the broken disk image. He is quite good with retro so I doubt he touched any hidden file or made anything strange.

He reported he just tried to add a file to the DSK (don't know which file, but maybe from another DSK image or a tap file from a game... cannot tell) and he got the error from the emulator.

You can follow the discussion here (in Spanish, but the error screen is a dump from oricutron):
http://www.retrowiki.es/fororw/viewtopi ... 8&start=20

However I Symoon might be right. It may not be a problem with Sedoric or the bitmap contents, but with the disk structure itself... If this 10 code means bit 4 is set, it may indicate a seek error in the status register of the FDC
http://oric.free.fr/HARDWARE/Fdc.txt

[Hialmar]

If the dsk was generated with tap2dsk the problem may be there as well.

Tap2dsk generates dsk that you cannot modify for some unknown reason (at least to me).
I have never managed to add files to them.

On the other hand, if I add/remove files to a dsk that was converted with readdsk I have no problem at all. That's what I use for Tyrann 3. I use tap2dsk to generate dsk and copy the files to the Sedoric3.dsk image found on Fabrice's website.
Currently I do this in Oricutron because I'm too lazy to launch a Linux VM and do it with OricFS but it worked all right when I did that with OricFS.

I will try to translate this in Spanish and post it on retrowiki.es.