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
  •  


IBM System x3550 M4 Server 2 x Intel Xeon E5-2609 36GB RAM No HDDs picture

IBM System x3550 M4 Server 2 x Intel Xeon E5-2609 36GB RAM No HDDs

$149.99



IBM Power 720 POWER7 00E6516 3.6GHz CPU 64GB RAM Server  picture

IBM Power 720 POWER7 00E6516 3.6GHz CPU 64GB RAM Server

$209.98



IBM Power S822 12-Bay Server System Power8 Core 3.42Ghz DVD-Rom Drive 64GB No HD picture

IBM Power S822 12-Bay Server System Power8 Core 3.42Ghz DVD-Rom Drive 64GB No HD

$499.99



IBM 7944AC1 System x3550 M3 Server 1*Intel Xeon X5650 2.67GHz 4GB SEE NOTES picture

IBM 7944AC1 System x3550 M3 Server 1*Intel Xeon X5650 2.67GHz 4GB SEE NOTES

$27.25



ibm server z series picture

ibm server z series

$16000.00



IBM SYSTEM x3200 M2 Server - HDD wiped, No OS picture

IBM SYSTEM x3200 M2 Server - HDD wiped, No OS

$75.00



IBM Power S822 8284-22A 12SFF Power8 3.89GHz 6-Core 64GB RAM No Bezel/HDD Server picture

IBM Power S822 8284-22A 12SFF Power8 3.89GHz 6-Core 64GB RAM No Bezel/HDD Server

$399.99



IBM Lenovo X3650 M5 2U 8x 2.5” CTO Rack Server – 2x HS, 2x 750W picture

IBM Lenovo X3650 M5 2U 8x 2.5” CTO Rack Server – 2x HS, 2x 750W

$199.00



IBM System X3500 M4 7383AC1 (E5-2650 v2 2.60GHz - 192GB RAM - M2000 - NO OS/HDD) picture

IBM System X3500 M4 7383AC1 (E5-2650 v2 2.60GHz - 192GB RAM - M2000 - NO OS/HDD)

$294.92



IBM SYSTEM x3650 M4 Xeon E5-2609 2.40GHZ 16GB DDR3-1066MHZ 2x 550W PSU TESTED picture

IBM SYSTEM x3650 M4 Xeon E5-2609 2.40GHZ 16GB DDR3-1066MHZ 2x 550W PSU TESTED

$109.95