This content has been marked as final. Show 21 replies
We're in the planning and testing phase for SafeBoot v5 also. Here's what I've run into so far:
Win XP x64 does not work with Safeboot
BIOS incompatibilities - Solved by upgrading the BIOS
Compression-enabled Hard Drives - Disable HD compression, then encrypt
We get the 0xe002000a error on several new Lenovo T400 and T500. We have an open case at McAfee support about this issue.
If we get a solution from McAfee, I will post it her.
Are you using Safeboot 516 or safeboot 513? I got the same encryption algorith error on the Dell E series latitudes, bot the 4200 and the 6500. I think it has to do with the SATa driver as if I change the SATA modes I get a different kind of problem (IRRT Mode, SATA mode, and AHCPI mode) Safeboot 513 had no issues on the E series, only the newer version.
we are using Safeboot 513. We will be moving on to the E series soon.
We had issues with 5.13 and certain laptops. They'd encrypt and reboot and then be unusable. The issue appeared to be fixed in 5.15
Our tests shows that's the AHCI, which is enable in BIOS, is causing this issue. Workarround to this issue, is to set it to "compatibility mode". This has to be done before Device Encryption is installed on the laptop.
0xe002000a - Disk information not present
We are seeing the "Disk Information not present" error message on our Lenovo T400 and T200 series. McAfee states that we must disable AHCI to resolve the issue. We're none too happy with this solution as it slows the computer Disk I/O down from what we've seen.
Hopefully McAfee can resolve this issue in the next release. You would expect that SafeBoot would support the latest laptops from one of the major global laptop suppliers..
We do not have any problems with this, so it may be a model or BIOS revision specific issue.
About your comment, I would not make such statements about "major global laptop suppliers". SafeBoot/McAfee does a good job working with the hardware vendors to address issues and make sure the product works on a large variety of hardware platforms. Each vendor (HP, IBM, Panasonic, Dell, etc) have several models and sub-models, running different BIOS revisions, hardware components, and features. If a hardware vendor makes a change to their BIOS settings or changes their hardware specs, I doubt they send a memo to McAfee. I would assume that SafeBoot first discovers these incompatibility problems by customers who report them, then they reproduce the problem and create a fix or solution.
And how long after an issue is discovered (AHCI on T60/T400/T200 and Turbo memory on T400/T200's) do you suggest I wait before posting in the support forums?