Fixes 429 ksm files dont reload right

The change here was not related to the bug, but was a fix to an error I saw in the logic as I was examining the problem.

The error was this:  The previous way it worked, BOTH the range check had to be true AND the harddisk had to be currently null in order to trigger BOTH the copying of the boot file and the initilizing of the harddisk.

This was wrong because the harddisk should get initialized to be non-null regardless of the range.  The range check should apply ONLY to whether or not to copy the boot file after the harddisk is made.  That's why I split the two checks into separate conditions.