Yesterday, in the context of testing the Telenor “Mobilt Bredbånd” connection client, I also checked up on the latest version of 3's 3Connect. I’ve done that before, so what I saw came as quite a surprise.
As stated in the previous article about this issue, logging to LogFile.txt is still present but is also still possible to turn off.
But when I turned off the logging last night and ran the application with ProcessMonitor on, I saw that there was still a lot of access to the wilog.exe file (the 3Connect application). In other words, not only is the logging still there, but there’s also a new form of disk access. So, it’s more excessive on the hard disk use than ever.
What does this mean to you as a user? Well, it’s basically the same problem and consequences as the Telenor case: it means a lot of excessive use of your hard disk and therefore a performance hit on your computer. In other words, I'm worried by your hard disk, here...
The following Excel file shows output from ProcessMonitor while running 3Connect. One pane is shows output with logging on, the other with logging off (log Errors only). 2009-09-22 3Connect file access 2003.xls (2,81 mb)
This information has been forwarded to Birdstep Technology, creators of 3Connect for 3. 3Connect is based on Birdstep Technology's EasyConnect, which is also used by T-mobile, TMN and Turkcell. Therefore, I presume that these customers are experiencing the same problems as 3's customers.
(File I/O reproduced on two separate laptops, and ProcessMonitor output sanity checked by Björn Johansson.)
