[<<]Message[>>] [<<]Author[>>] Subject [<<]Thread
Number : 9177 Date : 2004-11-09 Author : Kan Yabumoto Subject : about BOOT.INI Size(KB) : 6
This is a follow up to my previous post (msg #9163) under a different subject line. I just want to clarify the BOOT.INI file's role in the XP boot sequence. (Please bear with me on this subject with the technical subtleties. I hope this discussion may help others in the future.) Pat wrote: > You pointed out that xxcopy c:\ d:\ /backup /bc0 > and XXClone c: d: /backup0 /bc0 /start are equivalent. > I have no problem with that at all. I am afraid that my comments that appeared later in my long message was not properly understood (or more precisely, I did not present the difference in the most unambiguous way), I would like to rephrase the key point: --------------------------------------------------- The following two are similar but the second one should be used: Pat's method: xxcopy c:\ d:\ /backup/b0 xxclone c: d: /backup0 /bc0 /start My suggestion: xxclone c: d: /backup1 /bc7 /start (/bc7 is for a standard, freshly-initialized disk but should be adjusted when needed) --------------------------------------------------- If you know the purpose and the function of BOOT.INI to the fullest extent, you may use the first method. Otherwise, let XXCLONE customize the BOOT.INI file on the target volume. > Thought everything was OK so connected everything up, > switched on. Up came my three line Boot.Ini which is > Default to option 1 which boots to the Source Drive. > In a matter of moments XP was up and running. When two or more drives are attached to a system, it is not always apparent to the user as to which disk's MBR is used for the initial stage of booting and also in which partition the root directory of the initial key files (NTLDR, BOOT.INI, etc) resides. Unfortunately, the lines in a BOOT.INI file can be interpreted differently depending upon the disk- configuration at that time ---- The same line in the BOOT.INI file may reference a different drive. Therefore, the user must be very alert about this. Let me give you an example: BOOT.INI ---------------------------------------------------- ... [Operating System] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=" .... multi(0)disk(0)rdisk(1)partition(1)\WINDOWS=" .... ... ---------------------------------------------------- Here, the first line "rdisk(0)partition(1)" will reference Disk0 and the second line "rdisk(0)partition(1)" will reference Disk1 *AT THAT MOMENT* (which may vary depending on the disk-configuration), regardless of what you find in the boot menu --- the wording of the boot menu (the quoted string in the BOOT.INI file after the equal(=) sign) must be carefully written so that you won't be fooled. This exactly why XXCLONE generates a line with explicit [d:0, p:1] parameter. Here's how Pat's original boot menu shows up: C:XP Home Edition: Windows (Original Vol.) [d:0,p:1] D: XXCLONED XP: Windows (Target Volume) [d:1,p:1] Here, the wording "Original Vol." may or may not reflect what you are accessing. The important parameter is rdisk(0)partition(0) to the left (you won't see on the boot menu) and therefore, when you edit the BOOT.INI file, you should make sure that rdisk(x)partition(y) really matches the visible part of the line [d:x,p:y]. Furthermore, when you look at the boot menu displayed, discount the "English" part (Original Vol) and (Target Volume). Rather, the [d:x,p:y] part is what you should pay attention. In essence, my warning here is -------------------------------------------------------- Don't be fooled by what appears on the boot menu. Even if the line says "Target Volume", it may not be the one XXCLONE has created. It could be the original (source) volume if the BOOT.INI file was improperly transferred from one volume to another. -------------------------------------------------------- My hunch in what really happened in Pat's ordeal was due to his illusion that led him to believe he was selecting the "Target volume" while the system was using the original volume (I did not accept Pat's explanation at face value). Furthermore, Pat probably would have regained the system control using the Quick Boot Diskette rather than resorting to the time-consuming full-installation of the XP. XXCLONE generates the BOOT.INI file in the target volume with a line [d:0,p:1] as the "Target Volume" because in 99% of the time, the BOOT.INI file will only be accessed in the context where the particular drive is attached as Disk0 which refers to its own volume as "Target Volume". The point I made above is the reason why BOOT.INI should not be casually copied from one drive to anther. If you use the "XXCOPY/XXCLONE hybrid solution" and let XXCOPY to propagate the BOOT.INI from the source to the destination and then disallow XXCLONE to re-initialize the BOOT.INI file on the target is therefore a misguided practice. That is why the straight XXCLONE method is far superior in the treatment of BOOT.INI file. Although this is way too redundant, let me once more say the most important point in different wording. ------------------------------------------------------- When you examine the BOOT.INI file generated by XXCLONE on the target volume, you will find a line with [d:0,p:1] (Target Vol.) which may look strange if you think the target volume is Disk1 (not Disk0) at present. But, you need to realize that this BOOT.INI file will only be accessed when the target volume is attached as the boot disk (in 99% of the time, as Disk0). Therefore, [d:0,p:1] designation in the target BOOT.INI file to refer to its own volume is appropriate. ------------------------------------------------------- Again, if you have problem in booting up an XP system and get the dreaded "HAL.DLL" error message from XP, you should pay particular attention to BOOT.INI (which one is responsible and how the line in the boot menu is interpreted by the system). I strongly suggest the use of the Quick Boot Diskette with all the likely permutations of disk number, partition number and the windows directory name (e.g., \WINDOWS vs \WINNT). Kan Yabumoto
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.