>> I'm trying to install linux and windows 95 on a 1.2 Gig C drive.
>> I install DOS, install the DM (disk manager from Quantum - which creates
>> my partitions for me: 750 Meg for Dos and 500 for linux) and then install
>> Windows. NO problem.
>> Then, I got the 3.0 boot/root disks and booted up Linux.
>Disk manager is a dynamic drive overlay - it loads from the master boot
>record of the first hard drive (I think)
Quote:>system. The purpose of the overlay is to use hard drives bigger than 528
yes that is the primary reason for its existance.
even if it isnt required for this, it does have some advantages.
Quote:>MB on older computers that don't support them. Any boot manager such as
it has other advantages
it uses 32 bit instructions on VLB cards
it uses multiple mode if it can .
it supported the secondary interface.
it controls read ahead and other features of EIDE drives.
you can get these advantages even if you dont need Disk manager
7 to access all of a drive.
Quote:>LILO or OS/2 boot manager occupies the master boot record so it is extremely
>difficult to use both (I'd say impossible except I heard someone actually
DM occupies the physical MBR.
DM creates a partition which holds a complete virtual
hard drive. MBR, partition table etc all in place ..
once DM is run from the physical MBR , DM boots the (old) logical MBR
and hangs around in memory like a virus, and installs itself into
DOS if umb's are available (so it frees up low memory )
If you dont have dos umb services available, DM is just like BIOS.
(to go into the upper memory, it loads a dos driver and releases itself. )
What this means is that while the first attempts to support DM in the linux
kernel may have confused lilo, there isnt any reason lilo wont work.
similarly OS/2 may have had trouble.
and using lilo from a floppy without DM installed wont work
as lilo will have to assume DM is installed. (maybe it can test such
things these days ? there isnt any reason why it cant)
Quote:> If the overlay isn't loaded then none of the partitions can be
>seen. Disk manager should give you the option of booting from a floppy
>after it loads - start the computer without a floppy in the drive, wait
>for the disk manager message to tell you to press a key or something to
>boot from floppy and stick the boot disk in. I don't know if Linux is
>even compatible with this overlay,
compatibility came in about version 1.3.30 or something
use loadlin from dos to get to linux if you dont want to mess with lilo.
Quote:> but if it is you could boot Linux from
>floppy each time you want to use it.
>I don't suggest this though; first, overlays are cheap software fixes for
>a hardware problem
WAAH ! its a software problem ! the bios is software , and the bios
is broke ! DM just fixes it.
in fact DM just replaces bios . bios is software, DM is software.
overlays are software fixes for software problems.
(an analogy. word processors are software fixes for a hardware problem.
go buy a electronic typewriter with network access, laser /bubble /thermal/
dot matrix printing, fax capabilities,modem, 8 gig storage ,
ok, i think you are scared of the unknown. you dont know what DM
is doing, so you are saying avoid it. before linux supported DM,
we had to avoid it. at the same time ontrack introduced a DM
mode that was compatibile with linux, linux became compatible with
the standard DM mode .. so i use DM and linux together quite happily.
the reason DM hides the partitions one big DM partition is so that
broken DOS wont scramble the partitions IF you dont have DM loaded.
DM7 has an option to use 'bios compatible format' which means
that the partitions are not hidden. There is only one MBR which is for
DM in this format. but lilo doesnt need to go on the mbr !
this bios compatible format means that old versions of linux ,etc will
be able to access the partitions ok. but if you boot dos from a floppy
without DM , you can scramble data on all partitions and scramble the
partition table... DOS is broken !
but it means that you can put lilo on a floppy
( or on a partition (but not the MBR when using bios compatible mode !!!! ) )
and lilo will work whether DM is loaded or not.
(so lilo could be fixed for this too. dont know whether it yet. )
Quote:>, second, multiple operating systems (especially Linux)
>and the overlay are a bad mix. Go buy a new EIDE controller with an
>on-board BIOS so you don't need disk manager. You might have to repartition
>after you remove disk manager (meaning backing up and restoring EVERYTHING),
>but I don't think so.
DM will cooperate with the interface's bios ..
that means that you just plug the drives onto the new controller and
DM will still boot and install ok.
DM has a non-reversable remove option.
so you use the remove option then install the drivers for the vesa eide
controllers. (or fiddle with bios options or jumpers on the card or whatever)
(DM supports mode 3,4 for some vlb controllers, so you wouldnt even
have to drop DM or use the card's drivers or bios... these drivers and bios's
can be silly (and broken) software fixes (or breakages) for hardware (or software)
problems. and as such should be avoided.)
Quote:>By the way, if you only wanted to use Linux you wouldn't need either the
>drive overlay or a new controller -
true. linux cant use the dm services.
linux can do for itself anything dm does.
Quote:> entering the boot paramater overrides
>any settings in your computer's BIOS, which is what limits you to 528 MB.
but new kernels dont need boot parameter overrides.
use a newer kernel which identifies the drive from
c. the drive identify command. (so the drive tells linux what it is.)
the drive identify results are used if they look ok.
except fdisk and lilo ask for the bios geometry ..
(so linux can only guess about the drive geometry of drives supported by