The use of the file \dx4win\dx4win.dxb which is deleted when a normal termination takes place is quite useful to recover from crashes in cases where the log file has not yet been written to disk.
However when a control-s is done and the program subsequently crashes with no changes to the log, the dx4win.dxb file really gets in the way. In DX4Win 5.03 the online help says that the file \dx4win\dx4win.dxb is used as a backup in case of abnormal termination and that dx4win.dxb will be made identical with the log file \dx4win\save\n2la.dxl (in my case) after a save or control-s. After experimentation, this does not happen and the two files are not conformed after control-s. My practice is to do frequent control-s so that in case of a crash the log file is up to date. However, since the two files are not the same I have to go through the cumbersome process of loading both files and trying to see which has more contacts. Is my program acting abnormally? If the dx4win.dxb and my log were the same size it would be easy to check with a simple batch file after a crash. Or is it possible that both the log and dx4win.dxb contain the same information in a slightly different format? Being binary I cannot easily peer into them. Here's a thought: Shouldn't a control-s delete or rename dx4win.dxb until the next entry or change is made since the log is as up to date as possible after a control-s? Has this behavior changed in any way in 6.01? Larry Alkoff N2LA This causes a problem when dx4win terminates abnormally. Larry Alkoff N2LA - Austin TX
