nemo_outis wrote:

> Nomen Nescio <nobody@dizum.com> wrote in
> news:8bfad53b8d4b69cd8d27311d874867f6@dizum.com:
>
> > nemo_outis wrote:
> >> The entire disk IS encrypted, with the exception of the boot stub on
> >> track 0.
>
> > Tell you what, why don't you go right ahead and shrink your main
> > bootable partition on your first hard drive and create another
> > partition on that drive (if you don't have one there already) and then
> > use Truecrypt to encrypt that entire drive as a single device so the
> > entire disk IS encrypted. Let us know how that works out for you.
> >
> > Hope you have backups. ;)
>
> You really are a whining caviller. However, lest others be misled, I will
> explain why I am 100% correct.

You're not correct, and you're own waffling words prove it....

> You see, the space on a HD, as conventionally set up, consists entirely of
> the following: the boot track and one or more partitions. (This excludes
> the rare cases where there is unallocated unpartitioned space on the drive,
> and arcana such as the HPA and manufacturer's reserved space).
>
> So, if you encrypt all partitions on such a drive (as Truecrypt v5 now
> allows you to do, even if it is the boot/system drive) you have encrypted
> the **whole drive** - with the exception, of course, of the small

Yes, you've encrypted the **whole drive** with noted exceptions, but not
the "whole disk" as a contiguous piece of real estate as true whole disk
encryption tools do (including the partition table). Even you realize
this, and stated so in spite of your continued argumentative tone and
hurling of insults. There is a difference, and you've been provided
cites and examples to show why for some people this may be an issue. No
amount of quibbling over your queer interpretations of terms can change
that, or the fact that even Truecrypt acknowledges the difference.