Results 1 to 10 of 10

Thread: Dual booting with windows

  1. #1
    Senior Member registered user
    Join Date
    Nov 2003
    Posts
    203

    Dual booting with windows

    Seems that windows is making it more difficult to dual boot with Linux. I use knoppix 6.2 to get around that on my eeepc's. Install knoppix to a flash drive and configure the netbook bios so that it will boot from flash. Repartition the netbook hard drive so that you have a large enough partition for the linux stuff. Make it ext3. The first time you boot knoppix, use the tohd cheat code and target the newly created ext3 partition. Tell it to create a persistent storage area. Only use half the space so that you have room for a backup. Now each time you boot using the flash drive, use the fromhd cheat code. After booting you can remove the flash and just run from disk.

  2. #2
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    What you describe works but if you want to boot from harddisk only, alternative bootloader 'grldr' will make life slightly easier. This is my boot.ini :-

    Code:
    [boot loader]
    timeout=5
    REM default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
    default=C:\grldr
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
    c:\grldr="Knoppix(Linux)"
    And this is my 'menu.lst' :-
    Code:
    ######################################################
    # GvR Sept 30th 2004
            color black/cyan yellow/cyan
            timeout=5
            default=0
    
    title Knoppix on Internal HD (squashfs, normal)
            kernel /boot/syslinux/linux squashfs i915.modeset=1 lang=us apm=power-off nosound nomce loglevel=0 quiet dma noeject
            initrd /boot/syslinux/minirt.gz
            boot
    title Knoppix on Internal HD (cloop, normal)
            kernel /boot/syslinux/linux i915.modeset=1 lang=us apm=power-off nosound nomce loglevel=0 quiet dma noeject
            initrd /boot/syslinux/minirt.gz
            boot
    With the above I could menu select whichever I want to boot.

  3. #3
    Senior Member registered user
    Join Date
    Nov 2003
    Posts
    203
    Where does this boot loader reside? If it's in the mbr, then that's what vista etc seems to object to.

    If it's not in the mbr then what triggers it once you turn on the machine?

  4. #4
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    There is no need to mess with the existing bootloader of NT. The new ( chain- ) bootloader is installed as a file on the NTFS. The existing NTLDR is the one responsible for running 'grldr' - only if the user menu select it or if is a defaulted selection. As you can see from boot.ini.

    To boot NT :-
    NTLDR ---> (XP/Vista/Whatever...)

    To boot KNOPPIX:-
    NTLDR-->GRLDR (grub)--> KNOPPIX

  5. #5
    Senior Member registered user
    Join Date
    Nov 2003
    Posts
    203
    I wonder if m$ has checksumed the boot.ini, with md5sum say, so that any modifications would get detected and complained about?
    Last edited by turbine; 12-05-2010 at 07:17 PM.

  6. #6
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    The boot.ini is protected from casual modification by keeping the file as hidden and readonly. If you use the NT to unhide and modify boot.ini, you might get a few warnings. Apart from that there is nothing else because NTLDR allows for multiboot NT versions, and a typical NT installer might automatically/programmatically edit boot.ini during the installation process. It's an allowed feature.

  7. #7
    Senior Member registered user
    Join Date
    Jul 2004
    Posts
    143
    Quote Originally Posted by kl522 View Post
    The boot.ini is protected from casual modification by keeping the file as hidden and readonly. If you use the NT to unhide and modify boot.ini, you might get a few warnings. Apart from that there is nothing else because NTLDR allows for multiboot NT versions, and a typical NT installer might automatically/programmatically edit boot.ini during the installation process. It's an allowed feature.
    You and turbine seem to be talking at cross purposes. You are talking about dual booting with Windows XP/NT/2000. turbine mentioned Vista.

    The XP approach doesn't work with Vista /Windows 7 because, amongst other things, there isn't a boot.ini.

    However, it is possible to dual boot with Vista or Windows 7 without touching the MBR.

    Use of EasyBCD and neogrub is one way.

    Another way is to follow the instructions here:
    http://www.sysresccd.org/Sysresccd-m...s_Vista.2F2008

    in the section:

    update your boot loader: Windows Vista/2008

    (the menu.lst is as suggested here - not on the sysresccd site).

  8. #8
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    Quote Originally Posted by ICPUG View Post
    The XP approach doesn't work with Vista /Windows 7 because, amongst other things, there isn't a boot.ini.

    However, it is possible to dual boot with Vista or Windows 7 without touching the MBR.
    Thanks for the correction. Obviously I am left behind already.
    I did not know they removed the boot.ini thingie.

  9. #9
    Senior Member registered user
    Join Date
    Nov 2003
    Posts
    203
    Actually I do also want to dual boot with an xp machine so kl522's suggestions are most welcome. I haven't tried to implement them yet because my google search of grldr turned up several negative comments implying that it was a linux app that windows just did not like. I will still look into using it.

  10. #10
    Senior Member registered user
    Join Date
    Dec 2009
    Posts
    423
    grldr is ***NOT*** a linux app. Certainly there are many false information on the internet, but the true ones should be more than the false one in this case, but I wonder why you only managed to read the false information. grldr is a DOS program.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 16GB RAM No HDD's picture

HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 16GB RAM No HDD's

$299.00



HP Proliant MicroServer Gen 8 2.3GHz CPU 16GB RAM NO DRIVES/CADDIES INCLUDED picture

HP Proliant MicroServer Gen 8 2.3GHz CPU 16GB RAM NO DRIVES/CADDIES INCLUDED

$179.99



HP ProLiant HSTNS-5151 Micro Server 8GB RAM No Drives/Key/Caddies *READ* picture

HP ProLiant HSTNS-5151 Micro Server 8GB RAM No Drives/Key/Caddies *READ*

$94.99



HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 8GB RAM No HDD's picture

HP ProLiant MicroServer Gen8 Server Xeon E3-1220L 8GB RAM No HDD's

$229.99



HPE ProLiant MicroServer Gen 10 Plus, Xeon E-2224, 16GB DDR4, 1TB M.2 NVMe SSD picture

HPE ProLiant MicroServer Gen 10 Plus, Xeon E-2224, 16GB DDR4, 1TB M.2 NVMe SSD

$750.00



ProLiant MicroServer Gen8 Intel Xeon E3-1220L V2 2.3GHz CPU 8GB RAM picture

ProLiant MicroServer Gen8 Intel Xeon E3-1220L V2 2.3GHz CPU 8GB RAM

$170.00



HP ProLiant MicroServer Gen8 Server Intel Xeon E3-1220L v2 16GB DDR3 (4) 4TB HDs picture

HP ProLiant MicroServer Gen8 Server Intel Xeon E3-1220L v2 16GB DDR3 (4) 4TB HDs

$399.00



HP ProLiant N36L Micro Server 633724-001 AMD Athlon II Neo N36L - No HDDs picture

HP ProLiant N36L Micro Server 633724-001 AMD Athlon II Neo N36L - No HDDs

$102.59



HP ProLiant Microserver Micro Server HSTNS-5151 untested picture

HP ProLiant Microserver Micro Server HSTNS-5151 untested

$75.00



HPE ProLiant MicroServer Gen10 Plus v2 Ultra Micro Tower Server P54644001 picture

HPE ProLiant MicroServer Gen10 Plus v2 Ultra Micro Tower Server P54644001

$849.99