Partitions get formatted, Fdisk can delete and re-create partitions, unless the partition table information is incorrect
So - to survive all partitions being deleted and re-created to occupy ALL the drive space, the code must be in the MBR (replaceable by Fdisk) or on a portion of the drive not considered part of the allocatable space.. That's spare tracks used to replace bad ones Then - how is the software to get executed either by the OS - which you will have re-installed after clearing and redoing the partitions on the drive or by the boot process that gets started by the MBR code So stopping the MBR being altered may be why it didn't install properly and note the first word of : 'normal format or fdisk commands' What are abnormal commands - /mbr perhaps or resetting the available drive space after the partition tables have been modified to be non-standard The only reasonably reliable phone-home is one that is imbedded into the system - e.g. within the MOBO Bios JimB ----- Original Message ----- From: "Bill Kingsbury" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, January 31, 2006 10:06 PM Subject: PC Phone Home /computer tracking security products > Who's got a favorite "phone home" computer tracking app? > > I need to replace "PC Phone Home" (from Brigadoon Software), > because they are not responding to requests for paid-user > assistance to reverse a failed install, of their own making: > > Brigadoon sent me the (unregistered) Enterprise reinstaller, > representing it as the (registered) "Home" (aka: "Professional") > reinstaller. After running their incorrect reinstaller, it is > impossible to uninstall -- and it does not work (because it > is unregistered). Worse, they are refusing to respond to my > e-mail requests for an uninstaller, or other appropriate > instructions (although the president did respond once, 20 days > ago, by asking a question, which I had previously answered). > > The exe code says: > > " PC PhoneHome Pro cannot be removed by unauthorized parties > and CANNOT be removed by normal format or fdisk commands. " > > In my case, I believe the boot record was NOT altered, because it > was write protected by the BIOS. > > ( Is their "cannot be removed" advertising a bluff ?) > > What is the best Install Monitor, to track down all of the file > and registry changes -- if I should run the (correct and incorrect) > installers over again -- to debug this mess on my hard drive? > > Or is it ILLEGAL to debug their "patented" mess on my hard drive ? > > > Bill > > -- ---------------------------------------- To Change your email Address for this list, send the following message: CHANGE WIN-HOME your_old_address your_new_address to: [EMAIL PROTECTED] Note carefully that both old and new addresses are required.
