Hi Paul



 PM>> Sounds like you've got a stray pointer corrupting memory. You're

 PM>> probably getting away with it under some circumstances but not

 PM>> others.



 RM> Quite likely.



 PM>> I would have thought TD386 would be able to trap that

 PM>> problem though.



 RM> But TD386 won't run in the setup that the program fails under.



 PM> I was thinking that TD386 would pick up an invalid memory reference

 PM> even though it wouldn't necessarily cause the program to fail.

 PM> Possibly it doesn't though. You'd need something like Memcheck to pick

 PM> it up I guess. Or OS/2 of course :-)



I get a strange reaction from the TD from BC4-Win now. Very early

in the program, the debugger reports an exception. I accept its

little msg, and it then allows the program to run normally.

Unstoppably. I interrupt it, and tell the debugger to Run|Reset,

and instead of going back to the beginning, it picks up the program

where it left off and merrily chugs away. I can't stop it without

exiting the debugger. Fun. Anyway, RS runs in my non-dv config, so

it's sorta usable.



It's been pushed onto a lower priority at the moment, I got a

Paradox mini-app and a C black-box-interrogation program to do

first. Expect slow progress...



Cheers



--- PPoint 1.80