The trouble with USB, where using it to work with old serial is concerned, is that its designed to move very large volumes of data at a very high rate. The design of the system involves large buffers (not the same as the serial ones you set up in the serial port driver) that are emptied in bursts of high speed comms. The data volume from ALDL is tiny by the standards of USB and so is the rate. So the data goes into the USB buffer and isn't released to actually go to the RS232 comm port for some time. This causes problems for ElanScan because it adds timestamps and compares checksums as it goes. So if the data hasn't appeared by the time ElanScan is due to ask for the next data packet it shrugs and gives up (showing the error). This is compounded by the fact that when ES does get the data it gets the answer to about 400 queries all at once and/or the ECU gets about 800 queries at once.
So most USB -> serial converters do not work with ElanScan (or other ALDL programs for that matter). However, one USB->serial chip manufacturer put a clever feature in the driver that gets round the problem. In converters that use the FTDI chip you can set the driver to empty the USB buffer (i.e. send the data to the serial port) after each millisecond of inactivity - this is the latency setting - and that pretty much solves the problem.
So in short not all USB -> Serial interfaces will work in this application. It has to be one with an FTDI chip in it. They sell converters themselves
here.