Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Yes, ssh for a bootloader may be too much overhead; nevertheless the LUKS way works fine. I don't need a powerful all-in-one bootloader, I just need something that works with Windows like LUKS does with Linux.
    – speakr
    Commented Aug 18, 2012 at 15:36
  • I disagree about a network KVM-adapter being teh only possibility for achieving the OPs result. Using VirtualBox or VMWare for hosting the Windows installation inside a minimal linux dist would probably be the way I'd solve this issue since this gives you access to the system console even during the boot process. It doesn't have to be a large dist however. You could strip it down to just some kind of X and an autoloader for virtualbox/vmware. However, the security of this dist should also be considered since OPs way in might become a source to future security breaches.
    – simme
    Commented Aug 21, 2012 at 5:31