In message <2d26028f4e.jonkeates@xxxxxxxxxxxxxxxxxxx> Jon Keates <jonkeates@xxxxxxxxxxxxxxxxxxx> wrote: > [...] > Before the above error there were 21 Tasks Active but after the error there > was only 20 Tasks Active, the Missing Task was : > > SysLog &2014BBB4 &1300387C 0K &1 > > ==> Help on keyword SysLog > Module is: SysLog 0.20 (16 Jun 2003) © DoggySoft Ltd., 1995, > 1996, 1997 > Well, I'm not sure what to make of all this, it seems like SysLog crashed > and MessageTrans reported the error, no other MessageTrans problems. But > what was trying to use SysLog, was it USBinfo or the SCSI side of things ? > > Although SysLog is always run, nothing has ever produced a Log yet 8-( > > can anyone explain the cause of the problem, is SysLog to blame? It is well possible that SysLog has nothing to do with it. Whenever there is an error in the background the current foreground task is quit, and this hits whichever task happens to be currently paged in. In most cases, there is no relationship between the error and the task that is quit. Martin -- --------------------------------------------------------------------- Martin Wuerthner MW Software lists@xxxxxxxxxxxxxxx --------------------------------------------------------------------- --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support