I've searched the documentations extensively. Seems there is no way to save to file (I have a HP windows only printer so printscrn key won't work) a trace sequence recorded by a BPRW mod-name T???
I've tried closing the code window and modify the bp to read "BPRW mod-name R DO 'x' ". This would then place the breaking instructions in the command window so it can be saved through loader's save command history feature.
This quickly overflowed my command history (set at 356k)
I don't enable this breakpoint until my "bmsg hwnd wm_Lbuttonup" triggers and then disable when "bpx messageboxA" (failed) or "bpx mcisendcommanda" (passed) triggers. Don't know how much further I could isolate the suspected code.
Since I have a valid serial for one of the cars in this program,my thinking is a simple file comparison of a trace that passed with one that failed would show the decision points that need to be modified to get an "always pass" situation.
I'm not too keen on the idea of hand copying 5000 lines of trace buffer code

you may want to give icedump and its tracer engine a try as well. when you enable logging, you will have the option to log every traced instruction or only those that can change the execution flow. it won't log disassembly, only cs:eip/ss:esp, but that should be enough information.