Jump to content
CCleaner Community Forums

sb2k

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sb2k

  • Rank
    Newbie
  1. If you properly read the above comments you will see that I made no such accusation. Rightly or wrongly, it was suggested that SafeBoot had a tool to recover a screwed up SafeBoot disk - and I was being denied this tool because you were unlikely to make any more money from me. The key selling point to the enterprise version of SafeBoot, is that security is centrally managed (i.e. fully under IT's control). The suggestion that every time a user's password needs to be reset, someone has to phone SafeBoot support to obtain the "code-of-the-day" is simply ludicrous.
  2. Are you saying Cheese, that recovery of a corrupt SafeBoot disk depends on whose chequebook was used to buy it? I thought I knew Simon as well, but was a little disappointed with his reply of "sorry, you're fcuked". If you're saying that a solution to this problem exists, but is only available to enterprise customers, then please state this in your reply.
  3. Thanks for the information Tyorty, but unfortunately my problem relates to a different version of SafeBoot. A few years ago, Control Break decided to enter the 'consumer encryption' market and launched a product known as SafeBoot Solo. Priced at around $100, they sold many copies. The program was based on the same source code as the enterprise version, but most of the features you mention, were stripped out of it. About a year after its launch, Control Break pulled-the-plug and stopped selling Solo. Some speculate that Solo was pulled because it was damaging sales of its enterprise
  4. Thanks for the suggestions Cheese. Unfortunately, the IT dept are not going to be of much help here. Safeboot was a private purchase. We also have no agreements with McAfee for support, as we don't appear to use any of their products. The helpdesk have no experience with encryption software as no-one outside of IT has this type of software installed. The person I spoke to at Safeboot was Simon Hunt, their Chief Technology Officer. He told me that without the recovery disk there was nothing I could do. Perhaps I caught him at a bad time and was given the 'easy' answer? As I'm stil
  5. I haven't heard anything from ebssales yet, but I did manage to find the email address of one of the developers of SafeBoot from alt.security.scramdisk. He replied quite promptly that without a file called SBCONFIG, I was up a stream without a paddle. This file contains the actual AES key required to decrypt the disk and is protected by the password you enter to logon to SafeBoot. Unfortunately there was a bug with SafeBoot at the time I bought it that caused the file to bloat to over 5MB, making it impossible to write to a 1.44MB floppy disk. When I installed the program and created the r
  6. YoKenny, my day-job involves databases and writing interfaces that exchange data with clients and suppliers. My company has allowed me to work-from-home a few days a week, so long as I can show that any data on my PC is secure. Hence the need for Safeboot. I'm sorry, but I have neither the time nor energy to debate the merits of encryption with you right now. Hazelnut, thanks for keeping this discussion on-topic. I also appreciate your suggestion of emailing encryption solutions. I will give that a go and see what develops. I haven't been too diligent in my backups of
  7. The problem and error code are documented in the following article - https://knowledge.mcafee.com/article/989/61...SAL_Public.html Problem When booting up a client machine with SafeBoot Device Encryption installed, you see the following error indicating that SafeBoot is corrupt: SafeBoot is corrupt, Error 92H Change or Cause This is due to a corruption or relocation of the SafeBoot file system. Their solution involves creating a bootable floppy and running their recovery application 'SafeTech'. However, what the article does not tell you is that you are req
  8. Safeboot is an OTFE program written by CBI. McAfee recently bought them for $750m and claims to have an installed-base of over 5 million users. HP also offers it as an option on its range of laptops. From what I can gather, Safeboot replaces the MBR with its own version. The Safeboot MBR loads the decryption driver which unlocks the drive and allows Windows to start up normally. I am assuming that the modified MBR points to the physical location on the HDD where safeboot.fs is stored. As this file has been moved, the Safeboot MBR does not know where to find it. My theory is tha
  9. Hi I have a small problem. Ran Defraggler last night, now my PC won't boot up. After a couple of hours Googling, I think I've found the cause of the problem. There are a couple of system files which should never be moved (http://support.microsoft.com/kb/227350) - > Moving the following files (if present) can cause desktop problems: > > Safeboot.fs > Safeboot.csv > Safeboot.rsv > Bootsec.doc As the error message reads "Safeboot has been corrupted (error 92h)", I presume it relates to the safeboot.fs file referred to above. This message is shown before
×
×
  • Create New...