1 |
2007/10/28, Etaoin Shrdlu <shrdlu@×××××××××××××.org>: |
2 |
> |
3 |
> On Sunday 28 October 2007, Beso wrote: |
4 |
> |
5 |
> http://www.goodells.net/multiboot/ |
6 |
> |
7 |
> The article is about multibooting, but it also does a good job of |
8 |
> explaining how windows boot. |
9 |
|
10 |
|
11 |
hmmm i still didn't understand :-( maybe this is something like a religious |
12 |
mystery.... |
13 |
|
14 |
|
15 |
|
16 |
I have /dev/hda1 ext2, /dev/hda2 ext2, /dev/hda3 HPFS, then various logical |
17 |
partitions up to /dev/hda12. /dev/hda4 is the extended partition. Grub |
18 |
cannot start Win XP. I don't see how that fits this theory. |
19 |
|
20 |
|
21 |
|
22 |
hmmmm.... what's your windows partition?! i can only see exts and hpfs, |
23 |
which is not meant to work with windows xp: |
24 |
|
25 |
Windows 95 <http://en.wikipedia.org/wiki/Windows_95> and its successors Windows |
26 |
98 <http://en.wikipedia.org/wiki/Windows_98>, Windows |
27 |
ME<http://en.wikipedia.org/wiki/Windows_ME>could only read/write HPFS |
28 |
when mapped via a network share, but could not |
29 |
read it from a local disk. They listed the |
30 |
NTFS<http://en.wikipedia.org/wiki/NTFS>partitions of networked |
31 |
computers as "HPFS", because NTFS and HPFS share the |
32 |
same filesystem identification number in the partition table. |
33 |
|
34 |
Windows NT 3.1 <http://en.wikipedia.org/wiki/Windows_NT_3.1> and |
35 |
3.51<http://en.wikipedia.org/wiki/Windows_NT_3.51>had native |
36 |
read/write support for local disks and could even be installed |
37 |
onto an HPFS partition. |
38 |
|
39 |
Windows NT 4 <http://en.wikipedia.org/wiki/Windows_NT_4> still could read |
40 |
and write from local HPFS formatted drives however, using HPFS was |
41 |
discouraged starting with Windows NT 4 and in subsequent versions. Starting |
42 |
with Windows 2000 <http://en.wikipedia.org/wiki/Windows_2000> the filesystem |
43 |
driver pinball.sys enabling the read/write access was removed from the |
44 |
default installation. Pinball.sys was included on the installation media for |
45 |
Windows 2000 and could still be manually installed and used with some |
46 |
limitations.[*citation |
47 |
needed<http://en.wikipedia.org/wiki/Wikipedia:Citing_sources> |
48 |
*] Later Windows versions did not ship with this driver. |
49 |
|
50 |
Windows XP Professional allows to read and write like Windows 2000 Since the |
51 |
they are similar in code. |
52 |
|
53 |
so if you're using winzoz xp with hpfs of course you cannot boot inside |
54 |
it.... the driver for the fs support lacks with xp. of my experience from xp |
55 |
sp2 you cannot use any fs that is not ntfs, or be forced to have a difficult |
56 |
experience. |
57 |
|
58 |
I believe the partition number is not really important, as long as: |
59 |
- the partition is set as bootable (grub might be able to do that |
60 |
automagically) |
61 |
- all the win boot files reside fully inside the first 1024 cylinders of the |
62 |
drive (so preferably: the partition itself should start and end in those |
63 |
first 1024 cyls.) |
64 |
|
65 |
or something to that effect. |
66 |
|
67 |
don't be to obscure!!!! for windows xp to work there are 2 important things: |
68 |
1. install it before linux |
69 |
2. have the partitions on hd removed except the unix ones (ext,reiserfs acc) |
70 |
that aren't supported by windows, or manually hide them with some tool |
71 |
3. install linux, install grub and configure it to boot from (hd0,1) with |
72 |
chainloader+1 if your windows partition is the second. |
73 |
|
74 |
ps. installing xp from extended partition is nonsense, if that's the only |
75 |
windows partition in the system. it still needs a primary bootable partition |
76 |
in which to insert the ntldr and some other stuff. |
77 |
pps. USE THE FOLLOWING AT YOUR OWN RISK: |
78 |
the last option of installing xp is to have a linux /boot partition |
79 |
formatted with fat32 and install the ntldr and the system files of windows ( |
80 |
config.sys and the ones that are in the c:\ directory) inside there. but in |
81 |
this way you could experience a really bad experience if windows does |
82 |
something inside there (it needs to have full access to that partition or it |
83 |
will not boot) and makes your system unbootable. so, after you've considered |
84 |
a lot this workaround and want to try it be sure at 110% that you have at |
85 |
least 3-4 working /boot backups and that you'd be able to boot inside a |
86 |
linux enviroment to fix the partition. |
87 |
-- |
88 |
dott. ing. beso |