White Peak Software Blog

Mis-identification by McAfee Resolved

kirbyt — Thu, 25 Dec 2008 14:33:45 +0000

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

kirbyt — Wed, 24 Dec 2008 14:38:50 +0000

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

kirbyt — Fri, 12 Dec 2008 02:38:52 +0000

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.

Another New Release for the CSV File Editor, Killink CSV

kirbyt — Sat, 15 Nov 2008 05:59:02 +0000

Even though Killink CSV Editor version 1.13 is only a few hours old, I decided to squeeze in one more new feature resulting in the release of Killink CSV Editor version 1.14. As always, this is a minor update and is a FREE update for all licensed users.

What’s New:

Replace All and Count can be restricted to the selected cells. More information on this new feature is available here.

Download at:
http://www.whitepeaksoftware.com/killink-csv-download

Killink CSV File Editor Version 1.13 Ready for Download

kirbyt — Sat, 15 Nov 2008 03:59:00 +0000

I made a somewhat embarrassing mistake. I forgot to post version 1.13 of Killink CSV Editor. I’ve been working on version 2 and between that and other things my mind has been elsewhere. Still no excuse for not getting this version out sooner especially considering that it contains the bug fix for the find and replace feature. I sincerely apologize to the Killink CSV users out there for this delay.

With that said, I’m happy to announce the immediated availability for version 1.13 of the Killink CSV Editor. This update is free to all licensed users and contains the following updates:

Fixes the find and replace bug.
Adds the shortcut key Ctrl+Home to move to the top left most cell.
Adds the shortcut key Ctrl+End to the move the bottom right most cell.

Download this version at:
http://www.whitepeaksoftware.com/killink-csv-download

Where Is Killink CSV Editor 2.0?

kirbyt — Thu, 13 Nov 2008 15:49:20 +0000

I’ve talked about the next major release for Killink CSV Editor for a long time now and I’m sure the one reader out there is wondering, “Where is Killink CSV Editor 2.0?” Well, it’s coming. Bet you didn’t see that one coming. Seriously though, I am activity working on version 2.0 of my favorite csv editor. Version 2.0 is basically a re-write of the previous version which is why it is taking so long to complete. Unfortunately I can’t give a time frame for the release of version 2 but I’m hoping to have the first beta ready sometime soon. Post a comment to this blog entry or send me an email if you are interested in beta testing Killink CSV Editor 2.0.

Labor Mate 1.1 is Available

kirbyt — Tue, 04 Nov 2008 20:54:00 +0000

I just received word from Apple that Labor Mate version 1.1 is now available for purchase in the iPhone App Store. I’m sure it will take a bit longer to propagate but existing users should be getting update notices soon.

This new release includes 2 new features:

Email the contraction log to anyone
See the contraction date and time

Users, keep sending me your suggestions and I’ll do my best to incorpoate them as quickly as possible.

Still Waiting on Labor Mate Update 1.1.1

kirbyt — Thu, 30 Oct 2008 13:34:47 +0000

First let me say “Arghhhhh!” Okay, that helped a little.

At the beginning of the week I saw that 2 Labor Mate users requested new features. The 2 features are:

Display the date and time of the contraction.
Add ability to email contraction log.

Always being the one who wants to keep customers happy I implemented these 2 features right away. I posted the update to Apple and it has been waiting in the review queue for the last few days. While waiting in review I discovered and fixed a memory leak. It was a minor leak but a leak nontheless.

Since the previous update, version 1.1, was still in the review queue I decided to manually reject it and post the latest and greatest, version 1.1.1. This has the 2 requested features and the memory leak fix. But now I’m encountering another issue.

It seems by manually rejecting the previous update I have now prevented myself from being able to post a new update to the application. Frustrating to say the least. Users have requested new features. I implemented those new features immediately. And after 4 days those new features are still not in the hands of users.

I have contacted Apple about the issue. As soon as the issue is resolve I will post the latest update, version 1.1.1. And once it has been reviewed, which hopefully will not take long, users will be able to update their copy. Stay tune for more.

Update: The update was finally resubmitted as version 1.1. Hopefully it will be available in the App Store soon.

Labor Mate Tracks a Woman’s Labor Contractions

kirbyt — Sat, 18 Oct 2008 12:16:02 +0000

I’m very happy to announce that Labor Mate, a specialized stopwatch designed to track a woman’s labor contractions on the iPhone and iPod touch, is now available for purchase from the iPhone App Store.

Labor Mate is an easy-to-use stopwatch for the iPhone and iPod touch that tracks a woman’s labor contractions with a simple push of a button. With Labor Mate you can view the length of each contraction as well as the time between contractions. You can also view the average length for contractions and the average time between contractions, which is helpful in determining when it is time to call the doctor or head off to the hospital.

Labor Mate cost $0.99 USD and is available for purchase through the iPhone App Store.

Click here for more information about Labor Mate.

Standard Error Report Window

kirbyt — Thu, 25 Sep 2008 16:04:40 +0000

When something goes bad in SMTP Diagnostics or Killink CSV you should see the standard error report window (as shown below). By “bad” I mean some unexpected error has occurred within the program. Ideally you will never see the standard error report window but given the wide variety of computer systems, configurations, favors of Windows operating systems, and so on you just never know what will happen with the program is released out into the wild.

So what should you do if you see the standard error report window? The best thing you can do is click the Send button. This will send the error report to the White Peak Software tracking database and I receive an immediate alert. The information contained in the error report will help me trouble shoot the problem faster which means getting the fix completed sooner. You can also include additional notes with the error report by adding your comments to the “What were you doing when the problem happened?” text area.

Also, you can optionally include your email address. In doing so you will receive a return email with a case number and URL. This case number and URL allows you to follow the progress of the work to resolve the issue.

So if you ever see the standard error report window, and I hope you never do, please send the report. This will help make the program that much better.