I don't believe you, sorry. sad.gif
I dont know how it happened, surely it was a mistake on my part but that is what I observed. I did not at any point specify a FAT16b format but at some point that is what Beeblebrox indicated while at the same time disk management indicated NTFS. mabey because I did not disconnect and re-connect, it seems that is required after making changes to MBR on USB Im not sure.
As soon as you had at least valid MBR data, you did everything in your power (and even more) to fiddle with that stick in "random" or "semi-random" ways. w00t.gif
I was anxious but I think I could get back to "at least a valid MBR data" by retracing the steps you have provided.
Start with the normal MBR, with the (hopefully) right MBR DATA.
* a BOOT.INI with at least two entries in it
I made it this far from instructions on USBoot for pre-test prior to running USBoot and can report success
Make a copy of the MBR and bootsector.
I will start over, I thought when I saved MBR it included the Bootsector.
Add this TC PBA.
WHAT does it change?
must first have an OS to install TrueCrypt (TC) then its Pre Boot Authentication (PBA)
so in order for me to get to the PBA I have to run USBoot to copy OS to USB then install TC.
I can compare MBR and Bootsector after adding USBoot OS and then again after adding TC PBA
have you tried with a smallish partition (smaller than the 8 Gb limit)?
is it possible that the problem is an incompatibility of some kind with larger partitions?
yes, originally I started with a 4GB flash drive. it boots with TC PBA on my desktop but fails on the notebook. I have left it as-is since it works and because it is flash, experimenting with it slows everything down so I started over with USB HDD. if I procceed with it again I need to learn how to image it (RAW format according to reports since it is encrypted) then re-produce that image on another device to be sure. I am not sure if I can image the 4GB in RAW and reproduce that image on a different size stick. I dont have another 4GB stick only an 8GB
now that I have experimented with DiskCryptor a little bit I have been able to get it further along than the blinking cursor. with DiskCryptor I can get as far as loading the USBoot arcguard then it freezes blue screen with "UNMOUNTABLE_BOOT_DEVICE"
at this point it DiskCryptor seems more compatable than TC
it is also true opensource where as TC according to wiki is not
The TrueCrypt Collective License does not meet the Open Source Definition, and thus has not been approved by the Open Source Initiative. It is considered "non-free" by all the major GNU/Linux distributions (Debian, Ubuntu, Fedora, openSUSE, Gentoo). The license is considered "non-free" mainly because of distribution and copyright-liability reasons.
DiskCryptor also seems to have more accessable developers to contact and they apear to be willing to work with these types of issueshttp://diskcryptor.n...x.php/Main_Page
for those of us that have compatibility issues with booting TC on USB we may have a better shot at "Whole Drive Encryption" (WDE) booting from USB with DiskCryptor.
Im willing to go in which ever direction you recomend Jaclaz.