Re: RE: (Fwd) Re: cbm 9060/9090 scsi command set

Date: Thu, 14 Nov 2013 23:31:14 +0100 (CET)
Message-ID: <24016346.561740.1384468274216.JavaMail.www@wsfrf1212>
Bonjour, Didier

Je voulais te laisser un mail l'autre jour lorsque j'ai vu ta contribution sur le site d'André Fachat au sujet de Procep et des ROM AZERTY; je vais certainement avoir besoin de "tes services" pour mon 8096; mes ROM son peut-être HS. Par ailleur, j'en ai trouvé une qui trainait dans le boitier du 8096; si je la mets en UD11 et que je lance à l'adresse de début +2 (les 2 premiers octets sont à 0 ?!) j'ai EDEX 4.4 (c) 198 ... et ca plante. Ceci de dit peut être quelque chose ?

Par aileurs, je vois que tu as des projets autour du 9060/9090 ... J'en ai un qui est (était) opérationnel à la maison; peut être est-ce que ca peut t'aider, j'ai aussi divers trucs en SCSI1 ou 2. Dans quel coin es-tu ? Je suis près de Rouen mais je vais "tous les jours" travailler sur Paris. Tu peux me joindre au 0652076501.


Cordialement, Hervé WARIN


Tous vos emails en 1 clic avec l'application SFR Mail sur iPhone et Android - En savoir plus.


Message du : 14/11/2013 22:55
De : "didier derny " <>
A :
Copie à : 
Sujet : RE: (Fwd) Re: cbm 9060/9090 scsi command set

 Btw do you know any usb to scsi 2 cable working with windows 7 64 bits...

At some time, I will have to experiment with real hardware...

I found several adapters but without 64 bits drivers...


-----Message d'origine-----
De :
[] De la part de Nate Lawson
Envoyé : jeudi 14 novembre 2013 20:24
À :
Objet : Re: (Fwd) Re: cbm 9060/9090 scsi command set

On Nov 14, 2013, at 8:12 AM, Ethan Dicks wrote:

>> a second solution could be to replace the EPROM by one with my own 
>> content; not having to use this weird SASI protocol, it would 
>> simplify the interfacing.
> I think it might be possible to tweak the ROM code to properly support 
> SCSI command packets, but it would probably take a lot more tweaking 
> to support partial sector writes to a drive that was formatted to 512 
> bytes per sector. The DOS 3.0 filesystem maxes out around 16MB anyway 
> (if you were to rewrite the code that expects a ~300-cylinder drive 
> with 32 sectors per track and either 4 or 6 heads) so there's no real 
> loss in giving up half of each sector. Even my smallest embedded SCSI 
> drive is 50MB, so I couldn't address every block.
> I see two approaches to the same destination - put a SCSI bus analyzer 
> on a working drive and watch the transactions for format, reads, and 
> writes, and disassemble the DOS Board ROMs and look for every command 
> packet that the board sends to the SASI-MFM board. It's probably only 
> about half a dozen kinds. Once we know what the SASI commands are, 
> that's a long way to sticking a replacement on the bus.

Early SCSI is extremely simple. You don't have complex commands like READ
DEFECT DATA or the like.

With an Atmel with USB support, you could easily emulate the SASI interface
on one side and talk to a USB flash drive on the other. You could do this
either at the filesystem level (generate FAT commands to write to a storage
file) or the raw level (using only 20 MB out of a 4 GB drive, hehe) via
command translation. The former would pretty much be sd2iec but for SASI.


 Message was sent through the cbm-hackers mailing list

 Message was sent through the cbm-hackers mailing list

       Message was sent through the cbm-hackers mailing list
Received on 2013-11-15 02:01:21

Archive generated by hypermail 2.2.0.