09 October 2013
I determined that the log window is not a DriveWire log window. It is a VCC log window. ccIRC connects, but instead of giving me the motd, it gives me trash and crashes VCC.
08 October 2013
I began writing ccIRC in 2010. Aaron Wolfe helped me with the connect routines, and he also helped making it work with DriveWire. When I came back to it, I found that there is a connection problem with freenode that did not exist in 2010. Freenode is currently the only IRC network ccIRC will connect to. I believe that there were changes to freenode's connect routines, and this may be causing the problem. I am not entirely sure of this. The log file is DriveWire4's log. I do not know what it means. Pausing the output in ccIRC, I found that it is reporting UNKNOWN API errors from freenode. I thought the log window was written to a file, but apparently not. When I find out how to make a log file, I will provide one.
The following image shows what the log window contains when ccirc is first run. This window contains nothing else, and nothing gets added after the initial startup of the program. If I leave VCC running, the screen will become corrupted and VCC sometimes loses the display window, even though it is still running.
Wayne