CodeMercs Forum

yes, this has worked for me since. Rather than modify IOWarriorLib.c, i created these alternatives to IOWarriorWriteToInterface() and IOWarriorReadFromInterface().
just call openInterface0() once and then use readfromIOW or writetoIOW subsequently.

void openInterface0()
{
IOReturn ioReturnValue ...

i think i've found a possible fix/woraround. In IOWarriorLib.c in IOWarriorWriteToInterface() and IOWarriorReadFromInterface() the device is opened and closed every time. I removed te open/close calls from these functions and open/close only once rather then every read/write. This seems to have ...

one more thing, i'm doing 50 reads and writes every second. Could this be too much?

I'll give it a try and see if it helps.

this is on 10.3.7. And it doesn happen right away, but after a while ,having done a lot of calls to IOWarriorWriteInterface0() and IOWarriorReadInterface0(). It seems to be rather unpredictable when it happens.

I've had a few kernel panics on 10.3 and I suspect that it has something to do with the IOWarrior40. Here's the panic log:

Tue Jul 19 02:26:45 2005


panic(cpu 0): zalloc
Latest stack backtrace for cpu 0:
Backtrace:
0x00083878 0x00083D5C 0x0001EDA4 0x00039038 0x000241A0 0x000131F0 0x00013918 ...