>Not from that. Is there not any more? AFAICT, it hasn't tried to _do_ >anything yet. I guess you have snipped off the trace too soon, we don't >see it close the comm port. If that is all there is, maybe >+comm,+file,+relay would give an idea what it doesn't like. Lawson >---oof--- There is little else, right after this it opens an windows error boks that say "unknovn comunications problem" It closes the comm port right after you press the "ok" button on the message. I used +comm,+file,+relay and got this: Call kernel32.BuildCommDCBA(42d1e1b0 "COM2 96,n,8,1",405c4f18) ret=0043dfc3 trace:comm:BuildCommDCBAndTimeoutsA (COM2 96,n,8,1,0x405c4f18,(nil)) Ret kernel32.BuildCommDCBA() retval=00000000 ret=0043dfc3 Call user32.LoadStringA(00400000,000005de,42d205cc,00000064) ret=00404203 Ret user32.LoadStringA() retval=00000019 ret=00404203 Call user32.LoadStringA(00400000,000005e2,42d205cc,00000064) ret=00404203 Ret user32.LoadStringA() retval=00000028 ret=00404203 Call user32.MessageBoxExA(00010023,42d1a124 "Unknown Communications Problem with\"COM2\"",42d20088r the1trex _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
