This content has been marked as final. Show 10 replies
1. get the current version,57xx is very old, maybe a year?
2. don't use any of the compatibility options unless you really need to - certainly the Update MBR is only needed in very specific cases.
Are those "specific cases" documented somewhere?
You mean in "kc.mcafee.com"? No, it says only that it is for "There are some MBRs that do not work when SafeBoot is installed."
But there is no list of computer models/types that have above problem and need "Update MBR....".
Thank you for your quick reply... Yes, I intended to get the most recent version as that is what I normally tell other people myself. As for the compatibility options I don't have any clear indication of what is or isn't needed beyond the default File selections. We have many different brands & models of laptops so I feel like this is a crap-shoot.
Before I tried the latest version I wanted to first reproduce the problem consistently and see if:
A) Could I determine what is causing the problem in case it persists on newer versions.
B) Is there a way to recover from it?
B is much more important to me because I cannot deploy this product until I know how stable it is and feel fairly sure that we can recover from any crash and burns. If we lost the data of someone "really important" it would not be good, and backing up or imaging every laptop prior to installing or upgrading EEPC is not always practical.
Given the scenario from my original post, what would be the procedure for recovering the laptop if it appears that EEPC is installed yet you get a "Missing Operating System" and "SafeBoot Disk Driver Not Present" errors? Any help with this is APPRECIATED.
if you are getting driver not present, then your WinTech disk is probably bad - you must have missed out one of the drivers. You should be able to mount the drive and copy the data off.
BUT, saying that, you picked some nasty compatibility options (update MBR etc) so things might not be plain sailing.
If you've not enabled encryption yet, you can always try restore original MBR from Safe/WinTec to put the original boot sector back, but missing OS usually means the partition table in the MBR is bad (or the disk is still encrypted).
If it was encrypted, and you did the fixmbr etc, then you wiped out the information regarding what was, and what was not encrypted, so then you have to go work that out, could be the whole partition, or only a part of it. Once you've worked that out you can use the force decrypt.
try loading the machine export into Safe/WinTech, them see if you get a valid disk information screen with crypt regions. If so, then that's great, you can simply use the safe decrypt method to unwind.
As long as you have the keys in EEM, there's no reason to ever loose data.
Or, log a ticket with your platinum support person.
Thanks for another quick reply..! As I said, this is a test environment and the goal is to learn the product and its quirks as well as possible before deploying publicly. Having said that, it's easy for me to recreate the problem by simply re-imaging the drive and reloading EEPC. So, I can try things without scrambling the data with FIXMBR.
When you say the WinTech disk is probably bad, I'm not certain what you mean? I don't remember reading anything about loading specific drivers for WinTech to access the drive - I thought you just put the plugin into BartPE and it worked (aside from possibly loading the machine export info)?
As for BartPE drivers, I can see the drive and access the data directly from the A43 File Manager (actually "My Computer"; I am using UBCD for Windows which is built on BartPE) because I was only testing configuration options and had not encrypted the drive.
So, it seems that if the drive isn't encrypted then it should be fairly simple to uninstall EEPC or somehow repair the MBR if EEPC corrupted it? Are advance recovery options documented somewhere (KB, etc.)? I am more a hands-on person and don't mind trying things and wading through it if there is a trail I can follow!
You mentioned that I selected some nasty compatibility options - are the options documents in more detail anywhere else? Would be nice to know what to stay away from or when something might be needed.
In your experience, would you say that the vast majority of EEPC installs do not need any of the compatibility options?
Thanks for your patience and help in this.
No, the vast majority don't need anything at all. Only the machines with specific problems, and they should be documented in the release notes.
There is a WinTech guide, but most things will come out of professional services and training sessions.
Check your BIOS for the settings on the SATA hard drive. Make sure they are set to IDE, not ACHI. In some BIOS, the setting is also called Native or Compatability Mode. Basically, just try changing it to the opposite of what it is currently. That might help.