Re: [hatari-devel] SCSI emulation

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


> > What does not work for me is launching an application (HDDRUTIL.APP
> > from this image) or loading one of the text files. When trying to
> > launch HDDRUTIL the desktop reappears and HDDRUTIL is not started,
> > and when trying to load a text file (README or LIESMICH) from that
> > image, Thing reports "Diese Anwendung kann das angegebene Object
> > nicht finden".
> > 
> > What I noticed is that START/STOP UNIT is sent from HDDRIVER, which it
> > would usually not do, unless triggered by the status returned by a
> > device.
> 
> I've never seen this problem here. For example with the
> hddrdemo101_big_endian.img from your website, I can also successfully
> read the LIESMICH file in that image when I double-click on it on the
> desktop.
> 
> What options are you using? I'm starting Hatari like this:
> 
> hatari --machine falcon --tos tos404.rom -log-level debug \
>   --scsi hddrdemo101_big_endian.img --trace scsi_cmd

I'm using

hatari --machine falcon --tos /opt/atari/tos404.img --scsi 1=/home/us/hatari/scsi.img --trace scsidrv,scsi_cmd

scsi.img is a copy of hddrdemo101_big_endian.img. With other images I have
the same problem, with similar log output. I have the impression that this
happens when more than one READ SECTOR command is required to load a file.

Note that I am not booting HDDRIVER from this image, but I am running
HDDDRIVER.PRG from C:/AUTO. Just tried to boot from the image, but this
did not work. The log shows:

HDC: Unsupported command (t=1, lun=0, opc=8, cnt=0x1, ctrl=0x0)!
HDC: Unsupported command (t=1, lun=0, opc=8, cnt=0x1, ctrl=0x0)!

When I map the image to SCSI ID 0 it's the same error when booting:

HDC: Unsupported command (t=0, lun=0, opc=8, cnt=0x1, ctrl=0x0)!
HDC: Unsupported command (t=0, lun=0, opc=8, cnt=0x1, ctrl=0x0)!

Best regards

Uwe



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/