Archive for December, 2008

Mis-identification by McAfee Resolved

Thursday, December 25th, 2008

Great news!  As of this morning, December 25, McAfee has resolved the mis-identification issue affecting Killink CSV Editor.  Customers effected by this problem should update McAfee with the latest virus protection update then re-install Killink CSV Editor.

The re-install of Killink CSV Editor is necessary since McAfee forcibly removed the program file killinkcsv.exe.  Optionally, you may be able to restore the program through the McAfee Security Center but I cannot guarantee this will work since individual configurations of McAfee may be different.

You can download the latest version of Killink CSV Editor from here.

Sorry for any inconvenience this problem may have caused.  Hopefully it will not happen again.


McAfee Virus Scan Reporting False Positive

Wednesday, December 24th, 2008

It has come to my attention that within the last 24 hours the McAfee virus scanner is reporting that Killink CSV contains the Trojan Backdoor-CEP.  I have triple checked the program files and there is no virus or trojan in the Killink CSV program available from the White Peak Software web site.

I have filled a report with McAfee alerting them of the issue.  Unfortunately there is no good workaround to the problem short of not using McAfee, but I do not recommend turning off virus protection for Windows users.  I will provide updates as I get them from McAfee.


Making Progress on Killink CSV Editor

Thursday, December 11th, 2008

I am slowly but surely making progress on version 2 of Killink CSV Editor. I’m focusing most of my attention right now on huge (aka, very large) file support.  You know, files greater than 1GB.  My goal is to support up to 4GB file sizes under the 32-bit version of Windows XP and Vista.  However, a major challenge is how to handle sorting.  Image opening a very large file, say 3GB, highlighting columns B, D, and G, and sorting on all three columns.  With what will most likely be millions and millions of rows in the file, sorting is going to be a little slow, so I need to really ramp up the sort algorithm to ensure descent performance.  And I need to make sure memory usage is low at the same time.  Definitely fun challenges to tackle with version 2.