ReBoot Time [2]

nope he said boots from being off. I call BS

really. Im surprised. Seems very fast. Must have some seriously nice Hardware to do that.

I have a samsung 840pro ssd in my laptop Samsung i7 and my reboot is 21 sec.

A cold start takes time doing things which a Reboot omits.

After a prolonged shut-down all the hardware is ready for hardware initialisation upon startup,
and amongst other things :-
my WDC HDD has a "spinup time" of 5.1 seconds, and becomes disk 0;
my Samsung HDD has a "spinup time" of 8.1 seconds, and becomes disk 1;
my OCZ SSD never spins and takes much longer doing whatever SSD's have to do before they are ready for Windows to enumerate and call this thing Disk 2.

A Reboot never extinguishes the "running lights" and there is no general hardware reset on all hardware that needs it.
With Windows 7 the result of a Reboot is that the SSD is "enumerated" a bit quicker and becomes either Disk 1 or Disk 0 and the HDD's make way for it, which confuses the totals and averages produced by HDS when monitoring total reads and writes.
Some years before Windows 95 I had a PC with a serial interface card,
and sometimes the card would crash a a Reboot never fixed it, it only recovered after a shutdown.

A prolonged delay between Power on and Windows 7 launching is something else,
with perhaps a 2% probability that flaky enumeration may introduce a race hazard,
and Windows confused my GPT style 600 GB WDC HDD with my MBR style 930 GB Samsung HDD,
and thought that they both had the same Disk ID (which is illegal),
so Windows stupidly knocked my MBR style HDD "offline" and then "fixed" my GPT style HDD as an MBR style and wrote a new MBR style Disk ID.
Essential partitions and folders on the Samsung HDD were "offline" and unusable.
Download and archive partitions and folders on the WDC HDD all became RAW DATA.

Windows 7 does not give me daily BSOD's like early versions of Windows,
but when it goes wrong it is more disastrous.

Sorry for the rant,
but Microsoft's KB acknowledging that SATA disk numbering is something they never got right and will never fix has really annoyed me.

One shot attached.

Originally I looked for a way to change the disk ID from an MBR number to a GPT GUID,
but nothing that was safe worked for me,
and I fear that if I force a GPT format on the drive this would destroy all data.

As you can see, Disk 0 is now showing chunks of Free Space and Unallocated.
Disk Management originally showed chunks of RAW,
but this was before I changed the Disk 0 status from "online" to "offline" as a "write protect" measure.
Windows properties STUPIDLY declare :-
The Device is working Properly,
and
Partition Style Master Boot Record (MBR)

I "write protected" the disk before I unleashed "Data Recovery" utilities on the problem.
I determined that I would NOT allow any of them to modify the contents of the disk,
but did not trust them to obey my wishes.

Over 60% of 400+ GByte of data was Macrium Partition image backup files,
and all but the most recent one had been copied to an external backup,
and although I really do not need that particular backup,
it was a matter of personal honour that I recover it.

None of the freeware solutions could detect any files on the Disk

Then I tried a $69 professional solution which rescued this 400+ GB of data.
Unfortunately the "crucial" latest backup failed validation so I tried more freeware.
I estimate that this particular 6 GB file had been saved onto very second hand free space,
and as a result the 6 GB was probably in 200 fragments,
and obviously one or more fragments was assembled in the wrong order so that MD5 hash checksums rejected as invalid.

I looked at more freeware

I am happy to say that all my 400+ GB of data was rescued AND VALIDATED perfectly with the freeware
Lazesoft Recovery Suite Free, Free Windows System Recovery, Free Data Recovery, Free Windows Password Recovery, Free Disk Clone

I intend very soon to post my testimony for Lazesoft in
FREE Great Programs for Windows 7 [2]

Regards
Alan