Monthly Archives: September 2014

Issues Running Spinrite for the First Time, and the Solutions.

I recently bought Spinrite for two reasons:

  1. To help support Mr Steve Gibson from GRC, the creator of Spinrite and also the host of my favourite podcast, Security Now!
  2. I love nerdy things, and I have many hard drives that I wouldn’t mind running some maintenance on.

I then used Spinrite to set up a bootable USB drive, and fired it up.  My computer began booting, and quickly stopped at an all-text screen with the error:

“…bad or missing command interpreter”

This is an issue with Freedos.  It can easily be fixed by creating a bootdisk based on MS-DOS.  The easiest way to do that is to grab a copy of “Rufus” (here), and using it to turn a USB into the MS-DOS bootdisk we need.

  1. Download Rufus
  2. Use it to turn a USB drive into a bootable MS-DOS disk
  3. Copy Spinrite.exe onto the root of your bootable drive

Now when you boot into MS-DOS via this new disk, simply type

> Spinrite.exe

And we can now let Spinrite run!

A while into a scan….

“Division Overflow Error!”

Spinrite has a known issue with large drives. But this can be fixed with BIOS settings.

If you have SATA drives, look for the settings in your BIOS that control the mode these drives are in.  For me, what worked was switching the mode from “IDE” to “AHCA”, but my Googling has lead me to believe that Legacy-type modes have worked for others, so try that one if AHCA doesn’t work.

And finally, after the above two issues, I was another very happy user of Spinrite.  Using it to gain significant performance out of my laptop.

Excluding Folders from Sublime Text 3’s “Find in Files”

Note: Scroll down to quickly find the solution.

Background

Today I needed to configure an instance of JBoss to connect to a postgres DB.  I remembered that I’ve done it before, but couldn’t remember much more than that.  So I thought I would fire up Sublime Text and take advantage of its “Find in Files” feature that, like many other programs that share similar functionality, will search within a given set of directories for a pattern.

It worked very well except there was a lot of noise in the results.  Turns out JBoss keeps a history of its configuration in a subdirectory.  The numerous copies upon copies of the same configuration files were slowing down the search and causing the same results to essentially repeat themselves.

In the GUI, when you go to add to your “Where” clause, telling Sublime Text which folders to search, there isn’t an obvious option to exclude specific folders.

SublimeFilterOptions“Add Exclude Filter” seems like a perfect candidate.  It will let you filter out files that you want to ignore, such as “*.log” to ignore all log files.  But what’s not immediately obvious is the pattern to ignore folders.

The Solution

Using a Linux style forward slash to denote directory structure, you can simply make use of the same asterisk to make it a pattern.  So to exclude every occurrence of the “standalone_xml_history” folder, the pattern becomes:

*/standalone_xml_history/*

And to negate it, meaning to exclude that folder, simply add a dash, just like a normal negating filter.

-*/standalone_xml_history/*

So my entire “Where” clause to search through JBoss config files ended up being the following:

C:JBossjboss-as-7.0.2.Final,C:JBossjboss-as-7.1.1.Final,C:JBosswildfly-8.0,*.xml,-*/standalone_xml_history/*