Here's the problem: I have 2 HD with this setting:
HDA -> Primary Master
1. Win FAT 32 LBA <Win98SE>
2. VFAT Extended LBA
- Win FAT 32 LBA <Data>
- Extended
- ReiserFS <Mandrake 8.0>
- Extended
- Linux Swap
- Extended
- Linux Native <\home>
HDB -> Primary Slave
1. Win FAT32 LBA <Primary partition, Win98SE>
2. Win FAT32 LBA <Primary partition, Data>
3. Win FAT32 LBA <Primary partition, Data>
I use graphical LILO and if I boot to HDA1 all my FAT32 partitions can
be seen by Win98SE. But, if I boot to HDB1, partition HDB2 & HDB3 will
be changed to hidden partition, and after that, if I boot to my HDA1
again, HDB2 & HDB3 won't show up again. So, I have to change them to
back to normal FAT32 again using Ranish Partition Manager 2.40
<www.ranish.com>.
I've tried adding the following lines to my lilo.conf before the first
"image=" :
change-rules
reset
But it seems to have no effect. I've read the documentation but still
don't understand how to configure lilo so it won't hide my partitions
again. I've tried grub, but it behaves just like lilo.
Any suggestion/ideas how to stop lilo/grub from hiding my partitions?
Best regards,
Yayan.
>HDA -> Primary Master
> 1. Win FAT 32 LBA <Win98SE>
> 2. VFAT Extended LBA
> - Win FAT 32 LBA <Data>
> - Extended
> - ReiserFS <Mandrake 8.0>
> - Extended
> - Linux Swap
> - Extended
> - Linux Native <\home>
>
>HDB -> Primary Slave
> 1. Win FAT32 LBA <Primary partition, Win98SE>
> 2. Win FAT32 LBA <Primary partition, Data>
> 3. Win FAT32 LBA <Primary partition, Data>
Due to a DOS/Windows bug you cannot have more than one visible primary
FAT partition on one disk if the last partition in any extended
partition is not a FAT partition. If you create an extended partition
on hdb: If the last partition in an extended partition is not a FAT
partition, all extended partitions (recognized by DOS) must have the
same type, usually hex 0F.
--
Svend Olaf
Um. Windows gets confused if it sees more than one primary FAT
partition. Did you do this intentionally? FDISK.EXE will make an
extended partition and create logical partitions within this extended
partition if you use FDISK.EXE to create your Windows partition table.
I am suprised you can run your 'Doze system in that configuration and
not suffer really weird problems.
>I use graphical LILO and if I boot to HDA1 all my FAT32 partitions can
>be seen by Win98SE. But, if I boot to HDB1, partition HDB2 & HDB3 will
>be changed to hidden partition, and after that, if I boot to my HDA1
>again, HDB2 & HDB3 won't show up again. So, I have to change them to
>back to normal FAT32 again using Ranish Partition Manager 2.40
><www.ranish.com>.
>I've tried adding the following lines to my lilo.conf before the first
>"image=" :
>
>change-rules
> reset
>
>But it seems to have no effect.
Find all the "change" sections within lilo.conf and get rid of them all,
then rerun /sbin/lilo. If no "change" sections exist, LILO should not
fiddle with the partition table. There should be no need to fiddle with
the partition types with your setup (I think.) At most, you'd need the
"map-drive" commands to boot 'Doze from /dev/hdb , like so:
other=/dev/hdb1
label=dos
map-drive = 0x80 to = 0x81
map-drive = 0x81 to = 0x80
table=/dev/hdb
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / That which does not kill us
http://www.brainbench.com / makes us stranger.
-----------------------------/ --Trevor Goodchild, "AEon Flux"
Actually, HDB is my old HD, it used to be set as Primary Master and I
could run Win98SE just fine with all the partitions could be seen by
Win98SE. I don't use FDISK.EXE, I always use my favorite freeware
Ranish PM 2.40. ;)
> >I've tried adding the following lines to my lilo.conf before the first
> >"image=" :
> >
> >change-rules
> > reset
> >
> >But it seems to have no effect.
>
> Find all the "change" sections within lilo.conf and get rid of them all,
> then rerun /sbin/lilo. If no "change" sections exist, LILO should not
> fiddle with the partition table. There should be no need to fiddle with
Originally, there's no "change" sections exist, but someone said (in
other NG) that adding those two lines might solve the problem. But
they aren't.
> the partition types with your setup (I think.) At most, you'd need the
> "map-drive" commands to boot 'Doze from /dev/hdb , like so:
>
> other=/dev/hdb1
> label=dos
> map-drive = 0x80 to = 0x81
> map-drive = 0x81 to = 0x80
> table=/dev/hdb
Yes, this is exactly what my lilo.conf looks like. Mandrake set it up
automatically.
Regards,
Yayan.
>Windows gets confused if it sees more than one primary FAT
>partition.
I've never found this.
What kind of Windows?
I have two FAT primary partitions under NT-4.0 and under Windows-2000
(on two different machines),
and I've never had any trouble because of that.
--
Timothy Murphy
e-mail: t...@maths.tcd.ie
tel: 086-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
Argh, amend my previous post to say "95, 95OSR2, 98 and maybe 98SE"
then. Before I knew better, I had more than 1 primary FAT partition
under 98 along with several ext2 partitions, both primary and logical.
'98 insisted on recognizing /dev/hda2 (ext2 filesystem, partition type
0x83) as "D:", and reporting that it was 0 bytes in size. Eris only
knows what would've happened if I'd tried to run DEFRAG.EXE or a similar
lowlevel tool on that partition. Using cfdisk to fiddle the partition
table to Windows's specs eliminated that problem.
It doesn't surprise me that NT and 2K can handle these things better
than 9x, but the OP said "98SE", and I posted according to my experience
with 98....
lilo does *not* hide them for you unless you specifically tell it to do so.
> change-rules
> reset
>
> But it seems to have no effect. I've read the documentation but still
> don't understand how to configure lilo so it won't hide my partitions
because you had no change rules.
> again. I've tried grub, but it behaves just like lilo.
because it's not LILO nor grub misbehaving.
> Any suggestion/ideas how to stop lilo/grub from hiding my partitions?
>
Read svend-olaf's post again.
You've mixed to partitiontables that win9* cannot handle together.
Eric
Of course I didn't... ;)
> Read svend-olaf's post again.
> You've mixed to partitiontables that win9* cannot handle together.
Let's see...
If I boot to HDA1 <Win98SE>, all FAT32 partitions are visible. But if
I boot to HDB1 <Win98SE> via LILO, HDB2 & HDB3 will be hidden.
Fortunately, my BIOS can boot from any master or slave HD (from IDE0
to IDE3), so I tried to boot directly from IDE1 (HDB1), not via LILO.
And.... it works! No partitions are hidden. All visible...
Well, I still don't know HOW Win98 hide my partitions... ;)
I've been looking XOSL <www.xosl.org> but haven't tried. From the
manual, looks like it required me to hide all partition on HDA if I
want to boot from HDB. For now, changing BIOS setup is my workaround,
but suggestions are always welcomed.... :)
Thanx guys,
Yayan.
> Eric
The term 'hide' is meaningless WRT lilo. Lilo does not look for active
partitions. If you have lilo installed on the MBR of /dev/hda and you
cannot boot something, then your /etc/lilo.conf is misconfigured.
Win98 CANNOT see any type of partition except MSDOS partitions. Do you
expect Bill Gates to sell software which can see its competitors?
I'm sorry if I made myself unclear. What I mean 'All visible' is all
FAT32 partitions...
[deleted]
> The term 'hide' is meaningless WRT lilo. Lilo does not look for active
> partitions. If you have lilo installed on the MBR of /dev/hda and you
> cannot boot something, then your /etc/lilo.conf is misconfigured.
>
> Win98 CANNOT see any type of partition except MSDOS partitions. Do you
> expect Bill Gates to sell software which can see its competitors?
Well that's not what I meant (to see Linux partitions)...
(See above)
If you read the original post I think you'll understand that the main
problem is that I want to be able to boot to HDB1 <Win98SE, FAT32> and
still can see HDB2 <FAT32> and HDB3 <FAT32>.
All linux partitions <ReiserFS, Linux Swap and Linux Native> are
always invisible if I boot to HDA1 <Win98SE> or HDB2 <Win98SE> and I
don't have any problem with that.
Yayan.
If this behavior is not desired, the line:
change
(with no change rules specified)
in each "other=" section which specifies a M$ partition, will defeat the
"change automatic" behavior.
Starting with LILO version 22 (in beta test), the insertion of "change
automatic" becomes a compile-time option. Partition hiding, known as "change
rules", are documented in detail in the README in the LILO source
distribution.
lilo -T ChRul
will list the default change rule table, as updated or modified by your
lilo.conf file.
--John
LILO source code at http://brun.dyndns.org/pub/linux/lilo
Hi, John...
I tried your suggestion, but it doesn't have any effect. So I try
other approach by adding these lines in my "other=/dev/hdb1"
partition=/dev/hdb2
set=FAT32_lba_normal
partition=/dev/hdb3
set=FAT32_lba_normal
And still, has no effect.
Here's my complete /etc/lilo.conf:
----- start lilo.conf -------
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
vga=normal
default=Windows
keytable=/boot/us-latin1.klt
lba32
prompt
timeout=150
message=/boot/message-graphic
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label=Linux
root=/dev/hda6
initrd=/boot/initrd.img
append=" quiet"
vga=788
read-only
image=/boot/vmlinuz
label=Linux-nonfb
root=/dev/hda6
initrd=/boot/initrd.img
read-only
image=/boot/vmlinuz
label=Failsafe
root=/dev/hda6
initrd=/boot/initrd.img
append=" failsafe"
read-only
other=/dev/hda1
label=Windows
change
table=/dev/hda
other=/dev/hdb1
label=Windows-2
change
partition=/dev/hdb2
set=FAT32_lba_normal
partition=/dev/hdb3
set=FAT32_lba_normal
table=/dev/hdb
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80
other=/dev/fd0
label=Floppy
unsafe
------ end lilo.conf --------
Now, I'm downloading the source and the newest beta.
Thanks,
Yayan.