I tried out the latest beta of Apple’s Safari web browser, and I have to say I’m impressed. I’ve never cared for Safari at all, but the latest version in my mind brings it’s features, layout and usability up to fighting level. I don’t really care for the cover-flow eye candy, and aside from that everything else it boasts as new have been in Opera and/or Chrome already, but it seems a pretty decent browser.
Lifehacker have updated their browser comparison charts, and Safari fares fairly well. However, Google Chrome is still proving itself to be the new hotness overall.
Which urks me. I love Chrome. It’s an absolutely fantastic browser. But I don’t trust Google at all. They’re the devil, I’m pretty sure. So I really wish I didn’t love Chrome as much as I do.
In any case, I think it’s just about time to move away from Firefox. It’s tiring me. The insane memory usage and weekly browser crashes are taking their toll. Oh, speaking of browser crashes… one thing Safari has definitely got WRONG is it’s lack of tab process isolation. Chrome and IE8 are both half a step ahead of the pack in this regards, giving each browser tab their own process. This has the positive benefit of allowing one tab to crash without bringing down the whole browser. As web apps become increasingly sophisticated, memory intensive, and poorly written (this isn’t going to change), tab isolation will become more and more important. Firefox and Safari both need to jump on this train… I don’t recall if Opera is doing it yet.
In years gone by we’ve used Great Plains Dynamics as our financial software at work. We transitioned off it in 2006, but still have to keep it around for auditing purposes. We had a power failure a little while back, and the machine that GP is running on died, and on reboot Great Plains didn’t work. In my busyness I didn’t really bother with it, until I got a call that we had an audit coming up on some ancient history.
When opening GP, we received the error: “Your path to the data is incorrect. Please enter the location of you Pathnames File.” I took a look around, but couldn’t find any obvious solutions. We were using Pervasive SQL on the backend, which I’m told is really a flat file DB.
I called Microsoft support, but they’ve stopped supporting our version of Great Plains of course. Thankfully, after digging through old records and talking to previous employees, I was able to get in touch with Rimrock Corporation. They’re situated in Toronto and are Great Plains support experts. Evidently they set us up when we first started with Great Plains Dynamics.
So, after just a couple of minutes looking around, their support agent had me set the pathnames file to “C:\Dynamics” which is were the main GP Dynamics install was. After that it prompted for a drive mapping, but it had everything listed that it needed… another OK click, and we were in. Fully functional again… just in time for the audit.
So big thanks to Rimrock Corporation. If you’ve got a problem with Great Plains Dynamics, especially an old version (version 6 in our case), they’ll save your life.
Recent Comments