Now if somebody could fix X1000's to accept Polaris cards!

Don't hangup with oo.library a more likely candidate is Jansson.library i would suggest to look into that if you have duplicates or an older version than the requested 2.12.1

There is an issue on timing related to the setting and clearing of breakpoints. What kasie and billyfish is trying to do is to clear the instruction cache and is hoping, that this will establish a safety point to rely uppon, when execution of the sub-process is re-initiated. Only problem is : We have not established this. Unless we know how to rely and/or not rely on a function like IMMU->CacheClearE(), we have no grounds for assuming, that it works in one way or another.

In my initial work with db101 (and Qt as well), I needed to constantly check the minutest details about how the different functions of the system expressed their reliability-matrices. This resulted in a rather large battery of test-apps - all written in c - that might still reside on some harddrive somewhere. This is of course not an attempt to elicit some kind of awe-inflicting "historical value"-argument on my old harddrives. It is rather to say, that if you guys want to make progress, you need to isolate problems, and you need to go small - very small. I'd say, unless you can create a test-application in less than 5 lines for the main() function, and unless you can make that test app absolutely certainty-locked-hammered-and-closure-proven show, that your case is clear as a polished winter morning in your favorite fairytale fantasy - then you still have work to do.

Keep going, I know you can fix this.