All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike <mjwestkamper@weiinc.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Query/Suggestion
Date: Mon, 07 Feb 2005 14:28:53 -0500	[thread overview]
Message-ID: <4207C175.5030709@weiinc.com> (raw)
In-Reply-To: <4207AB9B.1080004@list.ru>

Thanks Vladimir,

If I had enough documentation I would give it a try. Alas I have other 
priorities as well.

Mike
 
Serbinenko Vladimir wrote:

> Mike wrote:
>
>>
>> Will Grub2 boot Windows w/o NTLDR?
>>
>> If not, it would ba nice feature, for a bunch of reasons, not the 
>> least of which is to boot from non-traditional devices and in to an 
>> embedded environment.
>>
>> Mike
>>
> I thought about it but when I saw the size of ntldr and ntdetect.com I 
> gave up the idea to rewrite it. But I thought about the kind of 
> adaptor that forces ntldr to read kernel from specificed memory 
> location instead of file. Other idea is to have a llok at freeloader 
> of ReactOS but I don't know if it's compatible with kernel of Windows 
> from Microsoft. Anyway I have other prioritary features to realise at 
> the moment. Later after some other things I'll try but not right now
>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>
>> .
>>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>





      reply	other threads:[~2005-02-07 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 17:32 Query/Suggestion Mike
2005-02-07 17:55 ` Query/Suggestion Serbinenko Vladimir
2005-02-07 19:28   ` Mike [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4207C175.5030709@weiinc.com \
    --to=mjwestkamper@weiinc.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.