Fun with Dell Laptop WiDI

I was messing around with the WiDi driver to stream the Grateful Dead show tonite and disabled the Intel Video driver. At this point, the machine started up, did POST, did the swirly page and then a blue dim (not BSOD) screen came up and nothing. HD activity, not much else.

 Could NOT get safe mode to launch per (Fixya) How to get into safe mode
Using this article, (Dell) Inspiron 17R will not boot (5720) – I tried to change the UEFI boot to legacy boot and was able to run diagnostics and setup.
Then used Pre-boot assessment error 2000-0332, Inspiron 7720  to run the Pre Boot Assessment
After messing around, I was able to see
2000-0332 Video memory – Video memory integrity test discrepancy ePSA diagnostics detected a video memory failure. Please reset the system memory and update the BIOS to most current version/
  • Update to the latest BIOS.
  • Reseat the system memory
  • Turn off your computer and reconnect your LCD cable.
  • Repeat the ePSA diagnostics..
  • If failure continues contact Technical Support
It said to update the Bios, I was at A18, the latest was A19  (Dell) Inspiron 5720 System BIOS
I used (Dell) How to Create a Bootable USB Flash Drive using Dell Diagnostic Deployment Package (DDDP) to create a bootable flash disk. I then copied the new flash utility to the flash image, ran the program to create the flash booter. Booted fine, and ran the installer from the DOS command line. Success.
Reset the boot mode to UEFI or windows would not boot.
It came up with the same blue screen. I started whomping on the LCD/CRT key, thinking I had put the video to external CRT, and I got the login screen. Whew.
Now I need to turn on the safe mode boot option before I try again…
Now why didn’t I want a MacBook???

Dirty Printer Test Page

I started getting vertical dark lines in my ADF scans on the the highly great Canon MF4570dw Laser/Multifunction.

Use this to determine location of small bits of dust on your scans. Then clean the glass under the ADF guide, slide it out carefully.

Print the OpenOffice file Dirty Printer Test Sheet and then feed the ADF. Your white streaks can be located and the cleaning intensified at that location. Takes several tries in my experience.

See: Black vertical line on scans and inspired by the suggestion from Fixya Lines when scanned

lineman-angular updated to ng-annotate

We use LinemanJS to automate the build process of various AngularJS projects. Two newer projects use the most excellent UI-router package, and I had some issues. The resolve section required manual protection for minification; ngmin, the automatic minify protector included with lineman-angular, did not handle resolves correctly. So this code:

resolve: {
     liveConfig: function(ServerConfigService) {
       return ServerConfigService.fetchFutureConfig();
     liveLocations: [ "PickSchoolService", function(PickSchoolService) {
        return PickSchoolService.fetchSchools();

would not work, as the minifier would convert the ServerConfigService object to, say, a, and that would obviously not match the injected service. Blam.

 liveConfig: function(a) {  // what the heck is a??
      return a.fetchFutureConfig();

There has been a feature request outstanding on this for a while, So yesterday on a longer car ride, I finally got ng-annotate to work on my local project. I was all ready to grab the source for lineman-angular and submit a PR, and found davemo beat me to it:

davemo authored replaces ngmin with ng-annotate 2386ab76016b485a03dfbf684c4639e9235f8a4d

updated my local package.json to 0.3.0 and lineman build. Nice. Now I can rip out all that icky brackety stuff.

Now to make sure – I found that chaining

angular.module("app", ["ui.router", "", "ngStorage"])

.run(function ($rootScope) {
.run(function($log, $state, $localStorage, $timeout) {
.run(function ($rootScope, $state, $log, PickSchoolService) {
.config(['$logProvider', function ($logProvider) {
.config(['$httpProvider', function ($httpProvider) {

also had issues in minification. I had to break some files up with the explicit module statement for it to work.

angular.module("app")  // require redeclaring for ng-min support
    .config(function($httpProvider) {

angular.module("app")  // require redeclaring for ng-min support
    .run(function ($rootScope) {

I mashed them back together. Seems to work great now. Nice work, all.

17 pounds and 4 inches of Carbon Neutral

Bing bong! Who is that disturbing my workout? After opening the door, I hear the UPS getaway truck speeding into the distance. Look down. See the shrink wrapped pile.

8 catalogs. 17 pounds. 4 inches thick – at least two Sears Catalogs thick from the good ol’ days.

And the phrase below the barcode: UPS CARBON NEUTRAL SHIPMENT.

The shipment may be carbon neutral. I don’t see how 17 pounds of glossy paper is anything but a ridiculous waste.


Intellij IDEA SCSS File Watcher

I use IntelliJ IDEA on a Centos VM for AngularJS development at work, and I have a FileWatcher configured to compile the SCSS files from the designer into CSS when they change. It stopped working one day.

After days of bad behaviour because I did not have the correct CSS, I compared configs. Mine looked like (from the exported file):

<option name="arguments" value="compile $ModuleFileDir$/src/main/webapp/ui/src" />
<option name="checkSyntaxErrors" value="true" />
<option name="description" value="Compiles .scss files into .css files" />
<option name="exitCodeBehavior" value="ERROR" />
<option name="fileExtension" value="scss" />
<option name="immediateSync" value="false" />
<option name="name" value="SCSS" />
<option name="output" value="$ModuleFileDir$/src/main/webapp/ui/src" />
<option name="outputFromStdout" value="false" />
<option name="passParentEnvs" value="true" />
<option name="program" value="/usr/bin/compass" />
<option name="scopeName" value="Project Files" />
<option name="trackOnlyRoot" value="false" />
<option name="workingDir" value="$ModuleFileDir$/src/main/webapp/ui" />

Hers, as it turns out, did not check for syntax errors:

<option name="checkSyntaxErrors" value="false" />

And as it turns out, the designer just started delivering SCSS files with errors last week. So mine never got compiled. Fixed. Duh.