In article <f096d6b04e.rik-mail@xxxxxxxxxxxxxxx>, Rik Griffin <rik.griffin@xxxxxxxxxxxxxxxxxxx> wrote: > In message <4eb08caf9cgary@xxxxxxxxxxxx> > Gary Locock <gary@xxxxxxxxxxxx> wrote: > > > Which doesn't prove anything of course, but maybe there's an > > > interaction between some other OS component and EtherK. > > > > Indeed; and in our case it couldn't be limited to just OS components. I > > doubt if it is anything particularly recent either. 'Big file' copies > > have always had the potential to freeze up the Iyo, and of course, once > > frozen, there is no realistic way of finding where the problem might have > > been. It has been a /lot/ less troublesome than it once was, pre-0.19, > > but the occasional episode just serves to show that the problem hasn't > > completely gone away. > If you're having the same problem as me (interrupts being disabled due to > some internal error) then the machine probably won't totally freeze. But if > the interrupt in question is shared by a USB device, the mouse and/or > keyboard will probably stop working. > Next time it happens, try switching the mouse / keyboard to a different USB > port, and see if it starts working again. OK, worth a try. > The difference between our setups I guess, is that you're probably running > a load of 3rd party software, while I'm running a totally clean > installation with just the OS and our software on it. So the same problem > might cause some software on your machine to lock up, even if the OS > doesn't. Indeed. But the machine which gets the most problems serves Acorn Access to the rest of the network, and also hosts a backup caddy (for itself and also a number of !Packdir image files- created elsewhere, but copied onto the caddy once per week. It is copying these image files onto the caddy over the network from the linux box where they are first saved which most often causes the freezes.) Being a server, it runs fewer applications than any other machine on our network, but yes, still far from 'clean.' Another source of occasional problems is client/server-ing a Datapower database hosted on that same machine. No apparent crashes at either end, but the Access link goes down and can only be restored by a restart. Of course, this isn't necessarily your etherk problem either, because the other network traffic to the server is not generally affected AFAICS. ATB Gary -- Gary Locock, Network Manager, Bablake Junior School Coundon Road, Coventry CV1 4AU School Website: http://www.bablakejs.co.uk Private mail: g a r y (at) l o c o c k . c o . u k --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support