Boxcar support is changing

Posted June 19th, 2014 by dojonorth with No Comments

If you use an iPhone or iPad, along with WindowSMART or Home Server SMART, you may be familiar with an app called Boxcar. We’ve supported disk health alerts via Boxcar for roughly two years.

Yesterday I received an email from the folks at Boxcar indicating they were shutting down the legacy platform, in favor of their version 2 platform. Last year, Boxcar was purchased by Process One, and they developed a new notification platform.

The end-of-life date for the Boxcar “v1″ platform is July 1, 2014. After this date, it is unlikely you will receive any notifications via Boxcar. This

Meet Kermit Gosnell, MD — a man the mainstream media doesn’t want you to know

Posted April 13th, 2013 by dojonorth with No Comments

This story will turn your stomach. It doesn’t matter if you’re red or blue, conservative or progressive, God-fearing or atheist. This affects us ALL, as a nation, regardless of party affiliation or religious beliefs. This is a story about a doctor who butchered hundreds (perhaps more) babies born in his filthy clinic, and the mainstream media that finds such a story to be unworthy of reporting. I hope you will spread the word that the media won’t. Please feel free to share this story with your friends, whether it’s by copying this blog post into an email, sharing on Facebook or by simple discussion.

This past week, thanks to Facebook, I learned about a man I never heard about before. If you haven’t heard about him, you’re not alone. The mainstream media (MSM) has done a damn fine job making sure you don’t find about him.

Who is this mystery man? His name is Kermit Gosnell, MD, an abortionist from Philadelphia who operated a clinic at 3801 Lancaster called the Women’s Medical Society. With a clinic name like that, it sounds pretty snooty, doesn’t it? Sadly, it’s far from snooty—not first class, not second class and not even third class.

The purpose of this blog is not to bash on abortions (that’s another issue for another day), nor is it about religion. This is about GREED and one man’s lust for easy cash at the expense of babies born alive in his clinic, and the mothers who gave birth to them. I am pro-life and a Christian, yes, but I’m not here to talk about the lawful abortions that took place in the Women’s Medical Society (WMS). I’m here to talk about all the other things that took place at 3801 Lancaster, the location of Gosnell’s WMS from 1972 until it was finally shut down in 2011.

The MSM loves to talk about Adam Lanza, and emblazon his ugly mug every time there’s new talk about guns. He is consistently front-page news. While his slaying of 20 elementary school youngsters and 6 adults was grisly, the actions of Adam Lanza pale in comparison to what Dr. Gosnell did in his small office at 3801 Lancaster.

Dr. Gosnell provided services that catered primarily to minorities and the poor, locals of the inner-city neighborhood in which WMS was located. WMS started out not only as an abortion clinic, but also a family practice. Over the years, Dr. Gosnell’s greed was of paramount importance to the safety, well-being and comfort of his patients. His clinic was routinely cited for violations—filthy, unsanitary equipment, outdated equipment, filthy facilities, unlicensed staff, etc. For some reason, the Commonwealth of Pennsylvania never shut him down, despite repeated, uncorrected violations, and after 1993, his clinic was never inspected by the Commonwealth again.

The WMS and Dr. Gosnell developed a bad reputation in the neighborhood, so most of the patients came from surrounding cities, out of state and even other countries. Dr. Gosnell’s clinic became a pill mill by day and an abortion clinic by night. The clinic dealt in cash. So-called “patients” could come during the day with cash in hand and walk out with prescriptions for OxyContin and Percocet, and in the evenings, women could seek late-term abortions.

While the majority of abortions performed by Dr. Gosnell were likely “legitimate” (legal as defined by Pennsylvania law), there were hundreds, if not thousands, that were not. Dr. Gosnell developed a reputation and thus attracted patients seeking “unlawful” abortions. In Pennsylvania, the point-of-no-return is 24 weeks. At 24 weeks, women may not legally receive abortions and providers may not legally provide them. At 24 weeks, babies are considered viable outside the womb. Most reputable abortion clinics won’t provide abortions beyond 20 weeks, four weeks less than the statutory cut-off.

Dr. Gosnell was different – he would provide abortions at ANY point in a pregnancy. Twenty-five weeks? No problem—just bring cash. Thirty-two weeks and a big baby? Still no problem—just bring MORE cash. Dr. Gosnell charged his patients by the size of the baby. The later the term and the bigger the baby, the more cash he expected. He even offered a “menu” of medications from which his patients could choose. The more comfort the patient wanted, the more cash the patient had to pony up. Dr. Gosnell became known as the go-to guy if you wanted to terminate a pregnancy at any time.

Dr. Gosnell’s clinic was staffed with ZERO properly trained or licensed staff. He hired people whom he could pay low wages, and yet these folks were given the full authority to medicate patients with sedatives, narcotics and painkillers—even while Dr. Gosnell wasn’t there! Abortion seekers often arrived at 10:00am and started receiving meds from the unlicensed staff, receiving repeated doses of powerful drugs such as Demerol, even though Dr. Gosnell often didn’t arrive until 8:00pm. Dr. Gosnell even had a 15-year-old high school student working in his clinic, and she too oversaw and medicated patients. Dr. Gosnell explained to the staff that the Commonwealth had a “grandfather clause” that allowed him to circumvent licensing requirements because he personally “trained” them.

The saddest, and most grisly part of Dr. Gosnell’s operation, however, was his practice of “snipping.” Most of his office staff has already pleaded guilty to participating in the “snippings,” and indicated that hundreds of “snippings” were performed by him over the years, and many of the staff also performed these “snippings” if Gosnell wasn’t present.

What is a “snipping?” The last paragraph on page 4 of the report by the Grand Jury explains it best: “There remained, however, a final difficulty. When you perform late-term ‘abortions’ by inducing labor, you get babies. Live, breathing, squirming babies. By 24 weeks, most babies born prematurely will survive if they receive appropriate medical care. But that was not what the Women’s Medical Society was about. Gosnell had a simple solution for the unwanted babies he delivered: he killed them. He didn’t call it that. He called it ‘ensuring fetal demise.’ The way he ensured fetal demise was by sticking scissors into the back of the baby’s neck and cutting the spinal cord. He called that ‘snipping.’” It continued on page 5, “Over the years, there were hundreds of ‘snippings.’ Sometimes, if Gosnell was unavailable, the ‘snipping’ was done by one of his fake doctors, or even by one of the administrative staff.”

Gosnell destroyed most of his files, which unfortunately prevents the prosecution for most of these “snippings.” He is, fortunately, facing first-degree capital murder charges for seven “snippings.” One such victim was Baby Boy A, who was 30 weeks in utero, when delivered. Baby Boy A was six pounds, breathing and moving when Dr. Gosnell severed his spinal cord and placed him in a plastic shoebox for disposal. A medical examiner testified to the grand jury that just because the spine was severed did not preclude pain, and that he likely died an excruciatingly painful death over several minutes. Another baby, Baby C, was moving and breathing for 20 minutes before an assistant cut the spinal cord, just the way she’d seen Gosnell do so many times.

Gosnell reserved the “really big ones” for Sundays, that even he was afraid to perform in front of his staff. Only his wife Pearl was allowed to participate in these slayings. The grand jury could not pin an exact number on how many of these occurred.

Dr. Gosnell did not just murder several hundred babies over the years—and by “murder” I’m referring only to the “snippings” of babies born alive, not abortions performed legally. At least two women patients were known to die at his hand. He punctured or perforated many women’s uteruses, cervixes and colons. He left appendages—arms and feet—of aborted babies inside of mothers. Many of the women were rendered sterile. He was sued more than 40 times in 30 years of practice.

Dr. Gosnell’s clinic was full of jars, milk jugs, water bottles and even cat food containers full of fetal remains. Several jars were full of severed baby feet.

The clinic itself was a deplorable place, described by the grand jury as follows: “There was blood on the floor. A stench of urine filled the air. A flea-infested cat was wandering through the facility, and there were cat feces on the stairs. Semi-conscious women scheduled for abortions were moaning in the waiting room or the recovery room, where they sat on dirty recliners covered with blood-stained blankets.” Investigators described the surgical procedure rooms as resembling a “bad gas station restroom.” Instruments were not sterile. Equipment was rusty and outdated. Lifesaving equipment was inoperative or unavailable. Tubing used for suction tubing for abortions was also used to provide oxygen to patients.

Dr. Gosnell’s capital murder trial started on March 18, 2013, and the court appropriately reserved many rows for the press, anticipating an enormous turnout for this grisly story. A scant few reporters showed up. Most of the section reserved for the press remained empty.

How is it that a man who committed acts so heinous, so barbaric and so grisly—akin to Josef Mengele, the “Angel of Death” at Auschwitz, and the media shows no interest? And yet whenever there’s a chance to talk about guns, they quickly feature Adam Lanza’s picture—not the 20 children—again and again? Dr. Gosnell butchered 20, 30, 40, maybe even 50 times as many living, breathing babies outside the uterus, and the mainstream media doesn’t want to talk about it. The MSM’s excuse? It’s “just a local crime story.” Well, Trayvon Martin was also “just a local crime story,” but the MSM ate it up, and continues to talk about it to this day.

In the end, I cannot help but wonder why the MSM doesn’t want us to know about Kermit Gosnell? He single-handedly killed more living babies—babies who had been delivered alive in his clinic—than Timothy McVeigh killed in Oklahoma City AND all of the mass shooters since Columbine combined! Only once the MSM was shamed into reporting on Gosnell, did the trial get any attention, although that attention was minimal. As of April 12, 2013, CNN devoted exactly 24 seconds to Kermit Gosnell’s capital murder trial, but CNN did spend over 18 minutes this past Tuesday discussing controversy over a song by Brad Paisley and LL Cool J. That’s 45 times more coverage for a song that didn’t kill, maim or injure a single person! (It should be noted that Anderson Cooper indicated he would discuss the trial in more detail on CNN, after the April 12 story was published.)

It seems to me that the mainstream media is trying to brainwash us. Fast and Furious got a free pass from the MSM. Benghazi got another free pass. The MSM does not want us to think on our own, but are instead a propaganda machine that bears a disturbing resemblance to the Nazi propaganda machine. They want to spoon-feed us stories that they think are important, and to them, the gruesome slaying of LIVING babies and reckless endangerment of the lives of the mothers—and the death of two mothers—isn’t important. They do, however, think that the Paisley/Cool J song Accidental Racist is worthy of our undivided attention. Had Gosnell been “snipping” puppies this would’ve been front-page news.

WAKE UP AMERICA!!!

References:
– Court of the Common Pleas, First Judicial District of Pennsylvania, Criminal Trial Division report of the Grand Jury XXIII, MISC. No. 0009901-2008 (attached as PDF) – http://www.phila.gov/districtattorney/pdfs/grandjurywomensmedical.pdf
– We’ve Forgotten What Belongs on Page One, op-ed by Kirsten Powers of USA Today – http://www.usatoday.com/story/opinion/2013/04/10/philadelphia-abortion-clinic-horror-column/2072577/
– CNN Barely Mentions Gosnell Trial; Spent 45 Times More Coverage on Braid Paisley-LL Cool J Song – http://newsbusters.org/blogs/matt-hadro/2013/04/12/cnn-barely-mentions-gosnell-trial-spent-45-times-more-coverage-brad-pais
– Gosnell Abortion Worker: It would Rain Fetuses – http://www.nbcphiladelphia.com/news/local/Gosnell-Abortion-Clinic-Trial-Unlicensed-Doctor-Chaos-201515061.html
– Shocking Photo Shows Empty Media Benches at Kermit Gosnell Trial – http://www.lifenews.com/2013/04/12/shocking-photo-shows-empty-media-benches-at-kermit-gosnell-trial/

Dojo North Software, LLC firearms policy

Posted April 9th, 2013 by dojonorth with 2 Comments

I received an email last week from a gun owner who said he could not find an official firearms policy on our website. As a small business that conducts most business online, via email or over the phone, we don’t normally get a lot of client visits. If anything, we’re visiting client sites, instead of the other way around. Needless to say, we never posted a firearms policy–because we didn’t have one. However, since the question came up, I wanted to clear up any concerns.

I am a law-abiding gun owner, CCW licensee and hunter. I am a firm believer in the Second Amendment and the right of law-abiding citizens to be able to carry, either open or concealed.

Therefore, it is the policy of Dojo North Software that all law-abiding gun owners are welcome to “open carry” when visiting our office, and if the gun owner possesses a non-expired CCW license issued by the State of Michigan or honored by Michigan, he or she may carry concealed.

All we ask is that gun owners please keep their weapons holstered unless the need to use it arises. If such a need should arise, judicious marksmanship is very much appreciated.

Law-abiding gun owners, and their guns, are always welcome here.

CSMI / SAS support not far off

Posted March 25th, 2013 by dojonorth with No Comments

If you have a high-end desktop or a “workstation” there’s a good chance it makes use of SATA or SAS disks that make use of CSMI (common storage management interface). The current release of WindowSMART 2013 doesn’t support CSMI.

However, that’s all about to change. CSMI support is fast approaching, and internal development builds have CSMI support working in Windows 8 and earlier versions of Windows. Windows 8 (and Server 2012) pose the biggest challenge because we don’t have CSMI support working yet for disks participating in Windows 8/2012 Storage Spaces.

If you’d like to give one of our internal beta builds a try, please let us know and we’ll send you a link to download the beta. If you try the beta and provide us feedback, we’ll gladly provide you with a discount code for the Professional edition of WindowSMART!

Storage Spaces reports a Phantom Disk after reboot – not a bug

Posted March 5th, 2013 by dojonorth with No Comments

A couple of folks emailed since the last WindowSMART release and they were concerned that WindowSMART had a bug. They said that a computer which contained a Windows 8 (or Windows Server 2012) Storage Space was rebooted, and after the reboot WindowSMART reported a phantom disk in the storage space, but at the next polling interval (default 10 minutes) the alert cleared itself.

This is not a bug. It is by design.

The main component of WindowSMART 2013 is a Windows service, which runs continuously, whether a user is logged in or not. When Windows reboots, many Windows services will start automatically–those set to Automatic and Automatic (delayed start) startup. If any of these service depend upon a Manual service, that Manual service will start as well.

WindowSMART 2013 starts as an Automatic service, and once it starts, it gets to work immediately.

Storage Spaces are a part of the Windows storage subsystem, and it is very possible for WindowSMART to start and be fully ready before the Storage Spaces are online. If disks participating in the Storage Space are encrypted by BitLocker Drive Encryption, it may take them even longer to report ready in Windows.

When WindowSMART polls the disks, Windows does not return a message saying, “Hold on a sec, this disk will be ready in a moment.” Instead, it returns a status indicating the disk is not available. Both Windows and WindowSMART do, however, know some information about the disk, so the disk is reported as a phantom. That said, WindowSMART is behaving as it was designed to do–if Windows reports that a Storage Spaces disk is not available, then WindowSMART treats it as a phantom until such time as the disk either becomes available again or you choose to remove it from the pool.

Phantom disks are always alerted at a Warning level, never a Critical level.

New version posted; maintenance release; what’s next?

Posted February 27th, 2013 by dojonorth with No Comments

Version 3.0.14.26 of WindowsSMART 2013 and Home Server SMART 2013 are now available for download. This release is primarily a maintenance release–it was never intended to be big on new features. Instead we combed through user feedback and tested it repeatedly to shake out additional bugs or things that worked but “just didn’t seem quite right.”

Probably the most significant bug was related to Windows 8/Server 2012 Storage Spaces. If a user physically removed a disk from a Storage Space (or the disk failed, lost power, etc.), then a condition we call a “phantom disk” exists. A phantom disk still exists within Windows, but WindowSMART would display an ugly error message to the user over and over, making the main UI really cumbersome. Our products are supposed to be simple, not a burden, so fixing that was a priority.

We cleaned all that up, and make phantom disk handling a normal part of the program’s operation. If a phantom disk is detected, an alert is generated. In most cases, users are swapping disks in a Storage Space pool and may neglect to remove the replaced disk’s record from the pool. Removing the record from the Storage Space or returning the disk to the pool will cause the phantom disk alert to clear.

Another item wasn’t a bug, but rather a request that came in fairly often. Folks wanted the WindowSMART window to be re sizable. You can now re-size the window, as well as maximize it. While we’re on the UI, we fixed an item that’s been in WindowSMART since the first release–when you click Query Disks or Fast Refresh, the buttons remain clickable. If you click Query Disks, which triggers an operation that can take several seconds to complete, it is possible to click Fast Refresh. This can cause irregular results to be returned. While it doesn’t cause a crash, it’s still not right, so that is fixed.

We made some additional improvements to the debug reporting, including enhancing how system administrators can control user submission of reports. Lastly, we updated the internal list of known virtual disks to accommodate changes made to Hyper-V and Drive Bender.

So what’s next for WindowSMART 2013 and Home Server SMART 2013?

Barring a major bug report that warrants a fix, there is a good chance it may be two or more months before the next release. The goal of this release was to ensure WindowSMART and HSS are as robust as we can make them. You’ve come to trust WindowSMART and HSS and we want to ensure that trust is solid. Now we can begin work on some significant new features.

We’ve gone through user feedback to see what users want to see in our products. The three most commonly requested items are support for disks attached to SAS controllers, multi-language support and graphs that display disk health over time.

Each one of these items is a significant endeavour. We’ve already invested time into SAS, so that will likely be the first item we address. However, we may or may not make available a release with just SAS support, but rather wait until we get two or all three features integrated and tested. If it looks like multi-language and graphs will take months to address, we would probably make available the SAS release so people aren’t kept waiting. On the other hand, if it looks like we could get multiple features implemented in a shorter time frame, then we may withhold a release until it was a multi-feature release.

I wish I could give you an ETA with absolute certainty. If I had to give a rough guess, it will probably be April before we have an SAS-capable build available. Since SAS is a major change, we are considering offering a public beta for those with SAS controllers who want to test. This would help us improve our software and give you an opportunity to get your hands on the bits early.

So what exactly does an “unsupported” configuration mean?

Posted February 23rd, 2013 by dojonorth with No Comments

No doubt you’ve seen the term unsupported when it comes to something related to computers. Whether it’s an operating system, a piece of hardware or a specific piece of software, the vendor may list configurations that they support and/or they may call out explicit configurations as being unsupported. A vendor may also imply something is unsupported by virtue of not classifying it as supported.

For example, walk into a store that sells used computer games and you may find a legacy title that says it supports Windows 95, 98, 98SE and Me. Does it work with Windows 2000? What about XP? Will it work in Windows Vista, 7 or 8?

The term unsupported generally has two definitions when it comes to the world of computers.

  1. The vendor does not provide support for the configuration in question. (Examples – ATI may only provide drivers for Windows XP and Vista, but not for Windows 7, for a certain video card. Dojo North Software does not support Windows XP SP-2 or earlier.)
  2. The configuration in question will not work.

The former definition is almost always true when it comes to something being unsupported. This definition does not necessarily mean that something won’t work, but rather that the vendor doesn’t officially provide support for that configuration. You’re free to go ahead and try, but if it doesn’t work, don’t expect the vendor to help. If ATI says that a video card isn’t supported in Windows 8, and you call their helpdesk because you can’t get the Windows 7 driver to work for it in Windows 8, they’ll simply tell you they don’t support that configuration and end the call. You’re just out of luck.

The latter definition is sometimes true. In many cases, unsupported configurations work just fine. I recall installing Windows Server 2008 on an ancient Compaq server, even though the last version of Windows HP/Compaq supported on that model of server was Windows 2000. That’s right–I was able to get Windows Server 2003 to work, and 2008 as well. However, when it came to Windows Server 2008 R2, it was not only unsupported by the vendor (HP/Compaq) but also unsupported in that it didn’t work. The reason in this case was that the server was 32-bit, and starting with 2008 R2, Microsoft stopped making 32-bit Server editions of Windows.

In most cases, however, I’ve gotten unsupported configurations to work just fine. In many cases, the vendor chooses to stop supporting a configuration because they want you to upgrade. If they always kept providing support for older and older configurations, people would have less incentive to upgrade. And if people aren’t upgrading, the vendor isn’t selling new products and therefore isn’t making any money.

When it comes to WindowSMART 2013, we do not support Windows XP SP-2 and earlier or Windows Server 2003 SP-1 and earlier. In these cases, WindowSMART doesn’t work. This is because WindowSMART utilizes some capabilities of Windows that were not present until XP SP-3 and later, or Server 2003 SP-2 and later. Of course, Windows Vista, Windows 7 and Windows 8 are fully supported, as are their Server edition counterparts (2008, 2008 R2 and 2012).

iPhone 4S suddenly ripping through the battery

Posted February 22nd, 2013 by dojonorth with No Comments

I’ve had an iPhone since late 2008, starting with a 3G, then a 4, and most recently a 4S when the missus and I switched to Verizon. We’ve both been very happy with them, and with a few exceptions, have no complaints.

A few days ago, without any warning, my iPhone 4S started ripping through the battery like a hot knife through warm butter. It’s not uncommon for me to run the battery down over the course of a day, but I use the phone a lot. However, this past Tuesday was different. The phone had about 80% battery remaining when I set it down, and just a few hours later I picked it up and it said 9% remaining. Half an hour later, it was dead.

I recall my wife’s 3G a few years ago had a similar problem, and I took it over to the local Apple Store’s Genius Bar. The tech there showed me that if you go into Settings > General > Usage, the standby and usage times since the last full charge were identical. What this means is that when you press the power button in the upper right corner to put the phone to sleep, it’s not actually sleeping. The display might be off, but otherwise the phone is not sleeping, but rather operating at full power.

The technician said that most likely this was database corruption that “typically results from installing an app and then using the app without rebooting.” The only course of action was to wipe the phone and reinstall the apps. I asked if we could restore a backup, and he said that restoring the backup would restore the problem. A fresh start was the only fix.

That was 3 years ago. I was hard-pressed to believe that 3 years hence that wiping your phone clean and reinstalling all your apps from scratch–and thus losing any data they contain (unless they’re iCloud aware)–was the only course of action.

My first thought was to consider what changes I had made. None on that particular day. I used Foursquare and the Gas Buddy app, did some surfing in Safari, browsed and posted on Facebook and swapped a bunch of messages with my wife through iMessage. All in all, a normal day. I didn’t install any new apps. Interestingly, I noticed an iOS update, version 6.1.2, suggesting a battery life fix for Exchange-based mail accounts. I got the battery all charged up, installed the update, but alas, the phone wasn’t feeling the love.

Ever hear the expression, “Google is your friend”? On Wednesday, I took to Google and tried searching on “iPhone battery life standby usage same”. This will lead you to several different threads in the Apple forums. I found posts aplenty where people said that you can try hard resetting the phone (hold the bottom and power buttons concurrently for about 10 seconds)–this reboots but doesn’t wipe the device. I tried that, but no luck.

Many folks found that the only thing that worked was to wipe the phone clean and reinstall the apps. I wasn’t buying that. It’s 2013, not 1985. A from-scratch rebuild should not be the only course of action.

And then I thankfully found this post: https://discussions.apple.com/thread/2481216?start=0&tstart=0

The long and short of the post was this – delete ALL email accounts from your phone. IMAP, POP, iCloud, Exchange, Google, etc. Get rid of all of them. Then, add them back. I had several POP accounts, my iCloud account, my Gmail account and my Hotmail (Microsoft Live) account.

I deleted them all, and then put the phone into standby. Fifteen minutes later I checked it, and right away the standby and usage times finally showed a difference! Putting the phone to sleep actually made it sleep! I decided to add back only the accounts I deemed the most important–iCloud, my AT&T Yahoo account and two of the POP accounts. So far, so good.

The downside was that all of my ringtone customizations for my contacts reverted to defaults, so I had to reset all of those. My photo stream also had to re-download itself, but that wasn’t a big deal. I’m just glad I didn’t have to rebuild the phone from scratch!

If I had to guess, most likely either the Gmail or Live account was the guilty party. Since I rarely checked those on my phone, I wasn’t worried about not having them.

So, if you find your iPhone 4/4S/5 is ripping through the battery with reckless abandon, try whacking the email accounts first.

WindowSMART 2013 version 3.0.14.7 re-released

Posted February 15th, 2013 by dojonorth with No Comments

Sorry for the inconvenience, but we found a problem in our installer package for WindowSMART 2013, including the lightweight editions, that was causing operational problems for some users. If users had the Microsoft VC++ 2010 runtime installed for their platform (32- or 64-bit), then this problem did not affect them.

The problem was that we failed to include one of the VC++ merge modules in the installer, and so if you didn’t have the full VC++ 2010 runtime, a rather important DLL file, MFC100.dll, would be missing. The result? WindowSMART would not collect SMART data from USB or FireWire disks, and you wouldn’t be able to run any disk self-tests.

We take the quality of our software very seriously, and as soon as we discovered there was a problem, we fixed it and re-posted version 3.0.14.7. We didn’t change the version number, since WindowSMART itself didn’t change. Only the installer package changed.

If you downloaded WindowSMART prior to February 14, but it’s working correctly, no action is required. However, if you are having the problems described above, please visit the Downloads page and download the updated installer. Users running our December 2012 or January 2013 build may also be experiencing this problem. Downloading the current build from the Downloads page will resolve the problem.

Again we apologize for the inconvenience and thank you for your support.

WindowSMART v3.0.13.5 Posted!

Posted January 5th, 2013 by dojonorth with No Comments

Yesterday we posted v3.0.13.4 but we followed it up today with v3.0.13.5.

The former resolved a number of bugs, most notably the “not found” error that appeared in Windows 8 and Server 2012 when third party drive pooling software like Drive Bender or StableBit is used. The other biggie was that sorting the list of disks would cause the list to disappear for 5-10 seconds before reappearing. There were a few other minor tweaks and fixes.

Unfortunately, the build we released in December introduced a bug in the update checker code. After yesterday’s build was posted, this became apparent. Several users contacted us about getting an alert every 2 hours that an update was available. The update checker should check at most twice per day, not 12 times per day. Most users indicated that twice per day is too much, and so we revised it to once every 4 days.

And so version 3.0.13.5 contains all of the fixes from yesterday’s build, plus fixes the broken update checker.

  • Recent Posts

  • Recent Comments

  • Categories