Working on making a dual boot again, WinXP & Ubuntu 515
On Wed, 22 Feb 2006 21:52:09 -0800, donstockbauer Now comes the "canned" speech about what's wrong with GG posting. It's offered as a learning tool, to help...
Arno Wagner
I'm reaching a bit - and my brain is starting to hurt :-) - but I have (hd0,0)) -- I guess it's because of my GRUB 'chainloader +1' entry for windoze that causes that small bit of grub code in the MBR to seek out it's 1.5 and 2.0 stages - which then pbuttes control to the DOS IO.sys file in 98 (located at hda1, offset by 63 heads(?), which also contains an 'active' flag -- I guess in essence, an Extended boot record or EBR)....BTW - this can get very complicated once you start looking at the buttembly language, offsets, and jump code -- note; FAT32 uses a larger BPB than FAT16, and NTFS uses some 'reserved' bytes (4-6 bytes) between the 440bytes of the MBR code and the 64bytes of the MPTs.
Has anyone been looking into the way the newer EFI (Extensible Firmware Interface) interacts, since it will shortly replace our typical BIOSes
Doing my best folks to find out the inter-operability about these things... I would like to post some output of files, but I want to be brief...
On Fri, 24 Feb 2006 07:00:47 -0800, iforone Really? ;-) Not enough horsepower (CPU and RAM) for KDE to run smoothly. Here are the basic rules...
Douglas Mayne I know, I know, - no need to rub it in ^ ^ See last comment...;-) it's funny - I know all that stuff for years now - just the Ext'd (under Linux) was throwing me...as you...
and also even a mini kernel image;
breastle Debian GNU-Linux, kernel 2.6.8-2-386 (recovery mode) root (hd0,6) kernel boot-vmlinuz-2.6.8-2-386 root=-dev-hda7 ro single initrd boot-initrd.img-2.6.8-2-386 savedefault boot
I don't yet fully understand all the possibilities yet, but here's some man initrd info ------------------------------------------------------------------------------------- The special filedev-initrd is a read-only block device. Devicedev-initrd is a RAM disk that is initialized (e.g. loaded) by the boot loader before the kernel is started. The kernel then can use the the block devicedev-initrd's contents for a two phased system boot-up.
In the first boot-up phase, the kernel starts up and mounts an initial root file-system from the contents ofdev-initrd (e.g. RAM disk initialized by the boot loader). In the second phase, additional drivers or other modules are loaded from the initial root device's contents. After loading the additional modules, a new root file system (i.e. the normal root file system) is mounted from a different device. -----------------------------------------------------------------------------------------
I haven't yet looked into the standard Legacy GRUB vs GRUB 2.0 differences yet.....I only mention to avoid confusion - and to clarify just what we are discussing (note; That's why I'm sure to mention the 98 vs NT diffs too).
The Information Operations Roadmap
Linux groups from Newsgroups