From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Load NTLDR from GRUB?
Date: Sun, 28 Oct 2007 14:29:43 +0100 [thread overview]
Message-ID: <d257c3560710280629g1aa6666er74ca7d970bd97faf@mail.gmail.com> (raw)
In-Reply-To: <200710281241.57646.shrdlu@unlimitedmail.org>
[-- Attachment #1: Type: text/plain, Size: 3966 bytes --]
2007/10/28, Etaoin Shrdlu <shrdlu@unlimitedmail.org>:
>
> On Sunday 28 October 2007, Beso wrote:
>
> http://www.goodells.net/multiboot/
>
> The article is about multibooting, but it also does a good job of
> explaining how windows boot.
hmmm i still didn't understand :-( maybe this is something like a religious
mystery....
I have /dev/hda1 ext2, /dev/hda2 ext2, /dev/hda3 HPFS, then various logical
partitions up to /dev/hda12. /dev/hda4 is the extended partition. Grub
cannot start Win XP. I don't see how that fits this theory.
hmmmm.... what's your windows partition?! i can only see exts and hpfs,
which is not meant to work with windows xp:
Windows 95 <http://en.wikipedia.org/wiki/Windows_95> and its successors Windows
98 <http://en.wikipedia.org/wiki/Windows_98>, Windows
ME<http://en.wikipedia.org/wiki/Windows_ME>could only read/write HPFS
when mapped via a network share, but could not
read it from a local disk. They listed the
NTFS<http://en.wikipedia.org/wiki/NTFS>partitions of networked
computers as "HPFS", because NTFS and HPFS share the
same filesystem identification number in the partition table.
Windows NT 3.1 <http://en.wikipedia.org/wiki/Windows_NT_3.1> and
3.51<http://en.wikipedia.org/wiki/Windows_NT_3.51>had native
read/write support for local disks and could even be installed
onto an HPFS partition.
Windows NT 4 <http://en.wikipedia.org/wiki/Windows_NT_4> still could read
and write from local HPFS formatted drives however, using HPFS was
discouraged starting with Windows NT 4 and in subsequent versions. Starting
with Windows 2000 <http://en.wikipedia.org/wiki/Windows_2000> the filesystem
driver pinball.sys enabling the read/write access was removed from the
default installation. Pinball.sys was included on the installation media for
Windows 2000 and could still be manually installed and used with some
limitations.[*citation
needed<http://en.wikipedia.org/wiki/Wikipedia:Citing_sources>
*] Later Windows versions did not ship with this driver.
Windows XP Professional allows to read and write like Windows 2000 Since the
they are similar in code.
so if you're using winzoz xp with hpfs of course you cannot boot inside
it.... the driver for the fs support lacks with xp. of my experience from xp
sp2 you cannot use any fs that is not ntfs, or be forced to have a difficult
experience.
I believe the partition number is not really important, as long as:
- the partition is set as bootable (grub might be able to do that
automagically)
- all the win boot files reside fully inside the first 1024 cylinders of the
drive (so preferably: the partition itself should start and end in those
first 1024 cyls.)
or something to that effect.
don't be to obscure!!!! for windows xp to work there are 2 important things:
1. install it before linux
2. have the partitions on hd removed except the unix ones (ext,reiserfs acc)
that aren't supported by windows, or manually hide them with some tool
3. install linux, install grub and configure it to boot from (hd0,1) with
chainloader+1 if your windows partition is the second.
ps. installing xp from extended partition is nonsense, if that's the only
windows partition in the system. it still needs a primary bootable partition
in which to insert the ntldr and some other stuff.
pps. USE THE FOLLOWING AT YOUR OWN RISK:
the last option of installing xp is to have a linux /boot partition
formatted with fat32 and install the ntldr and the system files of windows (
config.sys and the ones that are in the c:\ directory) inside there. but in
this way you could experience a really bad experience if windows does
something inside there (it needs to have full access to that partition or it
will not boot) and makes your system unbootable. so, after you've considered
a lot this workaround and want to try it be sure at 110% that you have at
least 3-4 working /boot backups and that you'd be able to boot inside a
linux enviroment to fix the partition.
--
dott. ing. beso
[-- Attachment #2: Type: text/html, Size: 5077 bytes --]
next prev parent reply other threads:[~2007-10-28 13:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 22:14 [gentoo-amd64] Load NTLDR from GRUB? Julien Cassette
2007-10-27 22:30 ` Beso
2007-10-28 8:22 ` Peter Humphrey
2007-10-28 9:20 ` [gentoo-amd64] " Duncan
2007-10-28 10:05 ` Peter Humphrey
2007-10-28 10:57 ` Beso
2007-10-28 11:24 ` Thierry de Coulon
2007-10-28 11:30 ` Beso
2007-10-28 11:41 ` Etaoin Shrdlu
2007-10-28 13:29 ` Beso [this message]
2007-10-28 11:44 ` Peter Humphrey
2007-10-28 12:00 ` Mathieu Seigneurin
2007-10-28 13:55 ` Duncan
2007-10-28 12:38 ` Thierry de Coulon
2007-10-30 8:55 ` Peter Humphrey
2007-10-30 9:53 ` Beso
2007-10-28 10:13 ` Peter Humphrey
2007-10-28 14:56 ` Duncan
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=d257c3560710280629g1aa6666er74ca7d970bd97faf@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox