Oric Blake's 7 and ENCOUNTER game load issues on Jasmin Disk Controller (FTDOS) and Preservation Questions

Anything related to the tools Tap2Wav, Tap2CD, Tap2Dsk, Sedoric Disc Manager, Tape Header Creator, WriteDsk, and generaly speaking tools related to the management of Oric data files and devices.
User avatar
iss
Wing Commander
Posts: 1951
Joined: Sat Apr 03, 2010 5:43 pm
Location: Bulgaria
Contact:

Re: Oric Blake's 7 and ENCOUNTER game load issues on Jasmin Disk Controller (FTDOS) and Preservation Questions

Post by iss »

Congrats @mininaller! This is amazing! All credits are for you :).

Actually I was just thinking for something like the shielded IDE HDD cables.
They have 40 pins but in fact they are 80 wires with alternating signal,ground,signal,ground,...
20251201_004434.jpg
I think this will give better results. Unfortunately I don't have such 34-pin connectors with shields.
Will try find, hopefully they exist :).

Chema wrote: Mon Dec 01, 2025 12:12 am I thought the Jasmin had a 1773... this is surprising. Anybody knows what are the differences between the two chips? I bet some timings, but anything else?
It's 1770 for sure! I don't know what's exactly different and will RTFM ( Attached :) ) very careful.
btw, here is Atari discussion 'wd1772 vs. wd1770 vs. wd1773'. And the 2 first comments:

- "You can not replace 1772 in ST by 1770. This is tested."
- "In essence the 1770 and 1772 are fully pin-compatible, with the difference being the 1772 has faster step rates. The 1773 has the same step rates as the 1770 (and the 1793) but has a ready/enable precomp input versus the motor on output of the 1770 and 1772. The 1770 should be a drop-in replacement, but with slower step rates."
You do not have the required permissions to view the files attached to this post.
User avatar
iss
Wing Commander
Posts: 1951
Joined: Sat Apr 03, 2010 5:43 pm
Location: Bulgaria
Contact:

Re: Oric Blake's 7 and ENCOUNTER game load issues on Jasmin Disk Controller (FTDOS) and Preservation Questions

Post by iss »

@Chema and @mininaller: any news?

For the protocol: @Chema sent me testing Blake's-7 image with updated load functions. The new code seams to work and the games loads but even with short cable random errors occur which makes my tests very unreliable as basis for decision that the issues are fixed.

Because I'm taking "Jasmin" very very personal, last days I've made something ( hopefully not stupid :D ) and I am looking forward to see if there will be improvements. It's 2-parts adapter for 40-pin/80-wires IDE cable:
sm_white_top.jpg
The PCB are produced and already shipped. Let's see what will happen this time....
You do not have the required permissions to view the files attached to this post.
User avatar
Chema
Game master
Posts: 3259
Joined: Tue Jan 17, 2006 10:55 am
Location: Gijón, SPAIN
Contact:

Re: Oric Blake's 7 and ENCOUNTER game load issues on Jasmin Disk Controller (FTDOS) and Preservation Questions

Post by Chema »

I have been recovering from a cold and some unusual stress at work. Gimme a couple of days and I will try to clean the code to share.

The good thing is we now have a code that works on the real Jasmin, albeit with problems due to noise. It would be interesting to check how TDos works at all!

I would like to test the correct timings needed, but that will take quite some time due to trial and error...

Did you try to put aluminum foil and see if it also solves the problems in your case?
User avatar
Dbug
Site Admin
Posts: 5293
Joined: Fri Jan 06, 2006 10:00 pm
Location: Oslo, Norway
Contact:

Re: Oric Blake's 7 and ENCOUNTER game load issues on Jasmin Disk Controller (FTDOS) and Preservation Questions

Post by Dbug »

On the topic of cables, but not Jasmin related, yesterday I found out that one of my cables between the Greaseweazle and the 3" drive was not 100% properly crimped, and that resulted in random errors on some tracks between 20 and 36. By keeping pressure on the cable the errors vanished, and replacing the cable fixed the problem.

I was really not expecting this type of error due to a cable, generally it was a all or nothing, not just "mostly works until it does not anymore". That's scary!
Post Reply