31
Living Room / Re: Multibooting and Partitioning Experiments
« on: November 11, 2007, 08:32 PM »
Hi saikee,
I don't know how to put this, so it is probably best to apologize beforehand in case I annoy you: Sorry for my bad attitude, no offense intended. :-[ I just try to get things straight in my mind. And also I like to discuss rather than argue.
I hope that I don't come across as a smartassed Know-it-all, because I feel that I know much too little about multibooting to be able to give advice or even write tutorials like you have done. I appreciate the way you are sharing your knowledge and I am honored that you read this thread and answer my questions. :)
Greetings
Wolf
I don't know how to put this, so it is probably best to apologize beforehand in case I annoy you: Sorry for my bad attitude, no offense intended. :-[ I just try to get things straight in my mind. And also I like to discuss rather than argue.
... a Bios that will read off the first sector of the first hard disk it is asked to boot. The Bios goes into the 446th to 51oth byte position to read off the 4 primaries.I think, the BIOS will read the first sector of the hard disk, if it is asked to boot from it. Agreed. It seems to be ?standard? behavior to put it into RAM at location 0000:7C00. But the BIOS does not show any interest in the partition table (447th to 510th byte of the MBR). It is the Initial Program Loader (IPL = the first 446 bytes of the MBR) that copies the entire MBR (512 bytes =446 bytes IPL + 4*16 bytes partition table + 2 bytes signature) to a ?standard? location in memory (from 0000:7C00 to 0000:0600).
If a partition happens to be fat32 which is supported by virtually all OSes then every OS can read/write its content.Maybe I have a lot of old hardware with old OS, but I think FAT16 is supported by a lot more OS's than FAT32. Not even Windows 95 or Windows NT 4.0 supported FAT32, not to mention MS DOS previous to version 7.1.
fat16 filing system has a maximum address of 4Gb and putting it beyond the first 4Gb area in the hard disk means no OS can access it.I would like to repeat my statement of reply#6 of this thread:
I have tested my Windows 98 SE again, just to be sure. It is installed on a logical drive. That logical drive is located 12 GB past the start of the drive.And I want to add that it is a FAT16 formatted partition. It starts 12 GB past the start of the disk and ends 14 GB past the start of the disk. In case of interest, I can try to copy it to the very end of the hard disk (size is 250 GB or 240 GiB) and see if it is bootable. Actually I am interested myself now, so I will check it out and post the result.First physical sector = 25,430,958 (Cyl 1,583, Hd 1 , Sect 1)It boots OK.
Last physical sector = 29,623,859 (Cyl 1,843, Hd 254, Sect 63)
I am aware 256 primaries is no object by putting in a hard disk management layer.Would you mind very much if I took that technical phrase "hard disk management layer" and use it to describe my batch files? It makes it sound as if I knew what I am talking about.
What is good about installing a Linux as a virtual machine inside a Windows host if that Linux cannot communicate with other Linux partition and read/write information?I have VMware running on Windows XP. In there I can boot Linux from a CDROM (have not yet installed it to a virtual disk) and I get read/write access to my Ubuntu partition which is installed on a logical drive of my physical hard disk. After finishing this post, I reboot into that Ubuntu installation and post what damage I have done. (I have created an empty file: "/WolfWasHere"). Have I misunderstood that question?
I hope that I don't come across as a smartassed Know-it-all, because I feel that I know much too little about multibooting to be able to give advice or even write tutorials like you have done. I appreciate the way you are sharing your knowledge and I am honored that you read this thread and answer my questions. :)
Greetings
Wolf