I have noticed that loading the history at first TCC instance startup using HISTORY /R seems to be quite slow. My current history.sav file is ca 500KB large and contains about 10,000 entries. When TCC starts up and loads this file it keeps the CPU at 90-100% load for some ten seconds. This seems to be a bit slow for modern machines (1.5 - 3GHz Pentiums with 2GB RAM). The process pegging the CPU is TCC.EXE. It's not a particular problem for me since I use SHRALIAS which means it usually happens only after a reboot. Still something that could easily(?) be improved. My history is configured so it uses unique entries which should force each line in the history file to be checked for uniqueness as it's read, but if a hashtable is used this should not be a slow operation.