It won't help - the slowdown isn't so much the booting of the image, it's the fact we have to keep going back to the BIOS within the image to read the hard disk.
We have to use the BIOS, as if we didn't, we'd need to build every possible SATA driver into SafeTech, and to be honest, there's just not that many available for OnTime.
the workaround of course is to use a WinPE image rather than SafeTech - the usefulness of that tool is really limited to Emergency Boot.
Thanks for the reply – I guess what really confuses me is the fact that I can use the same process, open “McAfee Endpoint Encryption Manager” click “Recovery > Create SafeTech boot disk” and select an old school 3.5” floppy. Connect a USB floppy drive to the “system in question”, boot off that floppy, and bam! Runs like a champ, no slowness whatsoever..? Which lead me to think the “/lba” option might be a solution…?
I’ve tried creating a USB disk using syslinux with memdisk to emulate a floppy, it loads the .img file that “Bootdisk.exe” creates, but again, it has the same slowness issue as the McAfee method. I’ve even tried various memdisk emulation options without luck..
The slowness issue is so bad, that I can’t effectively perform an Emergency Boot, which is all I ever use the SafeTech disk for -- well, that and verifying machine keys.
Which currently limits me to the CD I've created using the .img file, or floppy disk.. and since some new systems are not coming with either, I was hoping for a quick / working USB solution. ;-/
The challenge is accessing ANY drive, on any controller, from an OS which has no specific drivers for it - it's a bit like why you have to press f6 to load storage drivers into Windows setup. Unfortunately those drivers don't even exist for Ontime.