Soja, Otacon, Skidracer, Seldon, Inner and Bug Face - I appreciate your support.
It would seem that what I am trying to do in the way I was hoping cannot be easily acheived between PB and Blitz. It does seem as if that accessing RAM used by one application by another application is prohibited in Windows unless this can be disbled somehow. However, there must be a way to do it - as RAM drives do a similar thing but as a device managed by a DLL. I also understand that in C, windows wide global memory can be allocated.. I'll still try and give it a few more bashes and let you know.
Regarding the PB thread - 'not safe' issue - yes, I'm aware that PB uses a single buffer for all string operations - so when a thread begins using strings its using the same buffer as any other thread or the main PB program - hence corruption of the string eventually occurs. But as soon as a DLL built in PB creates a new thread (even with nothing going on in the thread) Blitz3D will crash.
It may be worth noting other PB DLL issues. You generally need to use the ProcedureCDLL instead of the ProcedureDLL - I've found that after about 3000 calls to a ProcedureDLL type DLL Blitz will crash also.
It would seem that what I am trying to do in the way I was hoping cannot be easily acheived between PB and Blitz. It does seem as if that accessing RAM used by one application by another application is prohibited in Windows unless this can be disbled somehow. However, there must be a way to do it - as RAM drives do a similar thing but as a device managed by a DLL. I also understand that in C, windows wide global memory can be allocated.. I'll still try and give it a few more bashes and let you know.
Regarding the PB thread - 'not safe' issue - yes, I'm aware that PB uses a single buffer for all string operations - so when a thread begins using strings its using the same buffer as any other thread or the main PB program - hence corruption of the string eventually occurs. But as soon as a DLL built in PB creates a new thread (even with nothing going on in the thread) Blitz3D will crash.
It may be worth noting other PB DLL issues. You generally need to use the ProcedureCDLL instead of the ProcedureDLL - I've found that after about 3000 calls to a ProcedureDLL type DLL Blitz will crash also.