🚀 go-pugleaf

blekken@fwi.uva.nl (Erwin 'Yaaah' Blekkenhorst (I88)) writes:

>I have a Lingenuity SCSI interface (shouldn't have bought it in the first
ace)

I have the same problem as far as this goes. Will there ever be a firmware
upgrade?

>[seagate discs deleted]

I have been using Rodime 200 MB disks. All I had to do to get them working
again under RiscOS 3.1 was delete-poweron the computer and reconfigure the
standard options and the Lingenuity SCSI options. Everything worked first time.
Don't try to use the RiscOS 3 scsi_filer module, it is only for the Acorn
SCSI.

>I know this has got something to do with the disc not being formatted in the
>right RISC OS 3 recognisable way. Reformatting the disc should cure this.

Unless subsequent damage has occured, wiping and reconfiguring the CMOS
values should fix it. If it is very old Lingenuity firmware, they might
have made a mistake that has since been fixed. I think I'm running the
1.3 firmware. Apart from the obvious hassles with directory size and filename
length, the only noticeable omission is that the new method of showing the
disk free-space is not supported. And of course the old gripe that it is
not possible to remove SCSIFSlinks, so the only way to remove a disk icon
after removing a disk unit is to poke the CMOS values directly or
R-poweron and reconfigure.

--
Adam David (adamd@rhi.hi.is)

In article <5847@krafla.rhi.hi.is> adamd@rhi.hi.is (Adam David) writes:
>blekken@fwi.uva.nl (Erwin 'Yaaah' Blekkenhorst (I88)) writes:
>
>>I have a Lingenuity SCSI interface (shouldn't have bought it in the first
>ace)
>
>I have the same problem as far as this goes. Will there ever be a firmware
>upgrade?
>
I don't know if Lindis will ever support an firmware upgrade but
someone with an EPROM-programmer might help you with it. Lindis
usually supplies an ROM-image on their support disks.

>Unless subsequent damage has occured, wiping and reconfiguring the CMOS
>values should fix it. If it is very old Lingenuity firmware, they might
>have made a mistake that has since been fixed. I think I'm running the
>1.3 firmware. Apart from the obvious hassles with directory size and filename
>length, the only noticeable omission is that the new method of showing the
>disk free-space is not supported. And of course the old gripe that it is

The latest version I know about is the 2.43 or the like; it runs well on
my old (1.2? or 1.30) hardware. Versions 1.87 is a stable version
that ran well.

The free-space "problem" may be fixed by an alias:
set alias$free showfree -fs SCSI %*0
{this should be refined by testing on command mode or using
<FS$temporaryFS> }

Success
-- 
--- Peter W. Roozemaal --- Email: witaroo@dutinfh.twi.tudelft.nl --------------
-------------------------- Smail: Geitenkamp 45 -------------------------------
--- tel. +31-15-611389 ---------- 2623 BB  Delft ---------- If it's urgent, ---
--------------------------------- the Netherlands --------- don't phone me! ---