🚀 go-pugleaf

In article <B14C08F39668C71FE@foakes.demon.co.uk>,
null@foakes.demon.co.uk (Andrew Foakes) wrote:

>I know you've solved your problem when updating to 7.6.1, but there is
>another gothcha it could have been (and might bite you later).
>
>The Jaz driver is held in 2 places - the system folder and the disk itself.
> If you're booting from the Jaz drive, the system needs a driver before
>it's read in the system folder, so it's the one on the disk that's used. 
>On the other hand, if you turn the Jaz on without a disk in, the driver is
>loaded from the system folder and automatically mounts the disk without
>having to refer to the disk's driver.

I take it this means that the system folder on the *internal* CPU hard
disk, since there's nothing to read in the Jaz drive.  If so, my machine
goes ahead and boots from the internal HD since it can see no external
alternative. 

>Often, when updating drivers, people forget to check what's on the disks
>and an incompatible driver/system version can result.  This usually occurs
>when people upgrade their OS to, for example, 7.6.1 and beyond, which came
>with driver version 5.0.3 (Ithink - I'm using 5.1.1 with B8.0), which
>causes problems with 7.6 (I think 5.0.1 was the last driver that could run
>comfortably with 7.6), but forget to ensure that the drivers on the disk
>itself are updated.  I suspect you have the reverse problem.

An extra snag for the Jaz IDE drive is that it uses an non Apple driver
(Anubis in my case).  So, when I formatted the drive, the Installer refused
to update the driver on System 7.6.  The range of compatibility of Anubis
driver versions may not match exactly those of Apple, I imagine.  Might win
some and lose others, perhaps.

>Sorry to be late and irrelevent to the discussion.

Glad to have the information.  Like Dr Johnson who said if it rained
knowledge he would put out his hand.  (Might get the occasional passing
seagull's contribution now and then.)

Keith


Keith Crook
keith@valperga.demon.co.uk