Search results

I am not sure I follow. Install Windows where his lost data is?

You just cannot transfer that much data, hence 600 is the number used to describe the speed in MB/s.

You need to calculate it like this: 6000000000 / 8 * 0.8 = 600000000 There is overhead. SATA speeds are also always refered to as 150, 300 and 600 MB/s.

2048, your numbers are a bit high, it is more like 150, 300 and 600.

It will be 60. It will be something else after you convert the numer to a different system.

Sure, but in my first post I said the zeroes began with Vista :)

Well, you did mention quick vs full :-)

http://support.microsoft.com/kb/941961 "The format command behavior has changed in Windows Vista. By default in Windows Vista, the format command writes zeros to the whole disk when a full format is performed."

I am talking about "full format". It writes zeroes.

I did. You can verify it, if you try it. Microsoft also has a kb about it somewhere.

Nobody has yet given a proof of concept that recovery after a single overwrite is possible. That depends. Microsoft changed how full format works in Vista.

After a format, all the old sectors which were oppucied by files are no longer referenced. Those files can be recovered, if not overwritten. A tool that overwrites unreferenced sectors will make the old and unreferenced files disappear. Quick vs full format: Since Vista, a full format writes...

In general yes, but it was brought up in this thread that mbr-partitioning is enough, if you just split the drive up in more than one partition.

The uefi-thing comes to play when you need to boot from such a drive. You don't need it for a data-only drive. I made a comment about that. Where?

It is mbr vs gpt. The latter is needed for larger than 2 TiB drives. To boot from a gpt partitioned drive you need the new kind of bios. You can split a mbr-style drive up as much as you want, but you will never get it past 2 TiB with 512 byte sectors.

It is ntldr vs bootmgr. You need the boot sector on the active partition to load ntldr. Fixboot from xp's recovery console can do that. Note that the problem doesn't lie in the mbr.

How is it password protected? Truecrypt?

Technically it is: mbr pbr (boot record on the active partition) bootmgr kernel system registry boot device drivers

No, after 2 comes bootmgr

If the applications request that much memory, they will get it. The lower 2 GB virtual address space is not shared among them.