Help - Search - Members - Calendar
Full Version: Installing 3-multi OS from CD & ISO
The CD Forum > The CD Forum > Multibooting systems
Pages: 1, 2, 3
SBernheart
Jul 21 2011, 07:13 AM

Well, as some may know by now, the forum (and the most knowledgeable people in it wink.gif) went to GREAT lengths to give back to me a working XP booting just as it used to only now from a new disk.

I am ready for the next step -- installing Ubuntu and Puppy Linux behind it. I don't even know where to begin except to say that I tried to install Ubuntu once (with an original "10.04 LTS" CD) in a partition approx. 10GB in size, but I got "stuck" when getting to the part about whether Ubuntu was to *share* XP's MBR/PBR (or some portion of it) OR whether I needed to set up a file system all it's own. unsure.gif The message I got was, "No root file system is defined. Correct from partitioning menu." and the difference between the two choices depends on dual booting vs. multi-booting and I know this will be a multi-booting disk (with the three OS mentioned). happy62.gif

@jaclaz
Concerned about your MBR/PBR, does it make a difference that Ubuntu is 2nd behind XP? Specifically, would it "require" the dual-boot method until adding Puppy to the mix behind IT? If there's any question, Puppy could be 2nd instead, then Ubuntu WOULD be the 3rd, multi-OS -- doesn't really matter to me, I guess. rolleyes.gif

So, how do I begin? Besides the original Ubuntu CD (and an ISO for Puppy) to work with, I really don't want to be fishing around and take a chance on causing harm to XP. If any additional info is needed on my part, please let me know and I will provide it. Thanks....


SB sleeping.gif
jaclaz
Jul 21 2011, 01:31 PM
NO problem whatsoever.
Use a dedicated partition for Linux.
DO NOT let any Linux installer write to the MBR.
Normally Linux distro's won't install on NTFS partition, either format the 10 Gb partition as FAT32 or make the partition (actually volume in extended) under Linux (Ext2/Ext3 FS).
Let them install their boot code to the PBR (or nowhere, if possible).
Add grub4dos to BOOT.INI.
Add an entry to menu.lst to either chainload the Linux PBR or load directly kernel and initrd.
Read the grub4dos guide:
http://diddy.boot-land.net/grub4dos/Grub4dos.htm

You want to use this method to load grub4dos:
http://diddy.boot-land.net/grub4dos/files/...ws.htm#windows1

jaclaz
SBernheart
Jul 22 2011, 05:58 AM
QUOTE (jaclaz @ Jul 21 2011, 02:31 PM) *
Use a dedicated partition for Linux. <<<NO problem whatsoever.
DO NOT let any Linux installer write to the MBR. <<<NO problem whatsoever (I hope).
....format the 10 Gb partition as FAT32 <<<For the moment it is.
....make the partition (actually volume in extended) under Linux (Ext2/Ext3 FS). hmm.gif
Let them (?) install their boot code to the PBR (or nowhere, if possible). <<<BOTH Ubuntu AND Puppy via ONE extended volume? hmm.gifhmm.gif (Take this as meaning "double *hmm*")
Add grub4dos to BOOT.INI. <<<NO problem whatsoever.
Add an entry to menu.lst to either chainload the Linux PBR or load directly kernel and initrd. <<<YES, problem!

You lost me at "chainload the Linux PBR or load directly kernel and initrd" (I have NO idea how to do this). However, if I can get the Ext2 file system for Ubuntu, I would still be able to boot IT and Puppy too from same partition (I know NOT booted at same time)? The difference between "logical" drives and "primary" ones are to me like two sides of a coin. I have half right of one side and a bit only of the other.

I already have one "primary" partition with XP in it and set as "active".
I want Ubuntu in another partition.
I want Puppy in another partition??
I'd like an extended partition to place my files in (documents, pics, etc. to access/share between them all).

I understand that only three partitions can be "primary" ones and "active" only one at a time, BUT the extended can have in it (almost laugh.gif) as many "logical" volumes as I'll ever need. Isn't this what Ed_P was referring to -- a "dedicated" place to put a file system too? I know when I'm using Ubuntu via CD, I can mount my Win 7 drives and access my files, but I don't think Windows returns the favor (or maybe I have that backwards), but the point is that having folders/files in an extended partition can be seen (and used) by all, yes?

I managed to find help HERE regarding the "file system" bit, but I'm not sure how to create an Ext2 partition. Disk Mgmt doesn't offer it. Another thing -- why am I *not* allowed to extend/shrink a FAT32 partition? When I created one for Ubuntu to eventually reside, I couldn't add/subtract anything, so making sure this is set up correctly (size-wise) will be important. That's something for ME to think about, but right now I believe 10GBs is sufficient (especially if folders/files are in another partition wink.gif).

"BOOT.INI" as-is right now:

CODE
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /noexecute=optin
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP jaclaz" /sos /bootlog /basevideo
C:\grldr="Grub4DOS"

Any pointers? Order in which I should be setting this up, i.e., format/partition as Ext2 instead of FAT32? I'm assuming changes in ANYthing "Windows" (like changing the boot.ini) are all to be done on the new disk, though I *can* access the "boot.ini" from running Win 7. I've extracted Grub4DOS to new disk at "C:\GRUB4DOS" (even though at the moment XP's (C:) drive is NOT (C:)). I have access to EASEUS Partition Manager, but all I can see is the option to *convert* a partition to a "logical" one -- does this auto*magic*ally make this then an "extended" partition (of either Ext2/Ext3 FS)?

I tried booting new disk to check on Grub4DOS and it was listed at "boot.ini" choices, but when I chose this option, I got the following message (even though when checked on after, the "hal.dll" file IS there):

QUOTE
Windows could not start because the following file is missing or corrupt:
    <Windows root>\system32\hal.dll
Please re-install a copy of the above file.

Then, after having to power off, I restarted and at boot menu, chose the new disk (again), but this time I chose regular Windows XP at "boot.ini" choices and got a 7B BSOD. huh.gif Powered off once more to allow Win 7 to boot, BUT seeing Grub4DOS still listed on "boot.ini" there, I chose it and it lists "Parted Magic ISO". I chose Win 7 and got the h*ll out of Dodge. Can I use the ISO in Grub4DOS to create an extended partition? If yes, what about Puppy and/or the "Ext2 Installable File System For Windows" itself? Again if yes, I'll have to decide how much larger I'll need this partition to be if FAT32 doesn't allow resizing (and I don't know if an "Ext* FS" will either). unsure.gif

SBernheart rolleyes.gif
jaclaz
Jul 22 2011, 08:13 AM
Has "Either/or" have a difference meaning across the pond?
You have several options about which filesystem to use, like:
NTFS <- not good
FAT16 <- not good, too big a volume
FAT32 <- good
Ext2/3 <- good

Out of four listed possibilities we exclude first two and we remain with TWO available, you choose one out of the two.
If you choose FAT32 you can format the volume with Windows Disk Management, if you choose Ext2/3 you need to format the volume during the install of the Linux.

Let's start again with the concept of partitions.
You can only have either max 4 primary partitions or max 3 primary partitions + 1 extended (with in it how many logical volumes as you need/want).

That means that primay partitions are "precious" and you shouldn't really use one UNLESS really-really needed.

The advise was to create an extended partition and in it create a logical volume for Ubuntu.
Then, if needed, create another logical volume for Puppy linux.

Those can be formatted as FAT32 by Disk Management, simply assume that Ext2/3 is not possible and stop finding yourself non-existant obstacles to your path! ranting2.gif

Simplified:
FORGET about Ext2/3, and use FAT32!

FORGET your doubts, 10 Gb, as you have been told on the other thread is adequate, stop making a case about it!

FORGET about Easeus Partition Manager, Parted Magic or ANY other "Partition Manager", they are simply NOT needed for an install.

Delete the existing 10 Gb partition (that I presume you created as Primary).
Re-create a new extended partition the size of the rest of the disk (after the "XP" primary partition).
Create inside the extended partition a 10 Gb logical volume, and format it as FAT32).

It DOES NOT exist something like an "extended volume", there are either:
  1. Primary partition=volume
  2. Extended partition=container for logical volumes
  3. logical volume=volume

Volumes are formatted with a filesystem.

What the heck do you mean by:
QUOTE
I've extracted Grub4DOS to new disk at "C:\GRUB4DOS"

w00t.gif
You need to extract the file grldr from the grub4dos archive to the ROOT of the drive, didn't you notice that in BOOT.INI you have:
CODE
C:\grldr="Grub4DOS"

AND NOT
C:\GRUB4DOS or C:\GRUB4DOS\GRUB4DOS or C:\GRUB4DOS\grldr

Anything in this:
QUOTE
I tried booting new disk to check on Grub4DOS and it was listed at "boot.ini" choices, but when I chose this option, I got the following message (even though when checked on after, the "hal.dll" file IS there):

QUOTE
Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll
Please re-install a copy of the above file.


Then, after having to power off, I restarted and at boot menu, chose the new disk (again), but this time I chose regular Windows XP at "boot.ini" choices and got a 7B BSOD. Powered off once more to allow Win 7 to boot, BUT seeing Grub4DOS still listed on "boot.ini" there, I chose it and it lists "Parted Magic ISO". I chose Win 7 and got the h*ll out of Dodge. Can I use the ISO in Grub4DOS to create an extended partition? If yes, what about Puppy and/or the "Ext2 Installable File System For Windows" itself? Again if yes, I'll have to decide how much larger I'll need this partition to be if FAT32 doesn't allow resizing (and I don't know if an "Ext* FS" will either).


Is either nonsense, or written in a language that is not English, or describing something that simply cannot happen in the Universe as we know it, or all these together. hyper.gif
The only thing I can get out of it dubbio.gif is that you have possibly AGAIN ph34r.gif botched that install by doing random things without thinking first and knowing what you were doing BEFORE actually doing it. sad.gif

cheers.gif
Wonko
SBernheart
Jul 22 2011, 04:07 PM
QUOTE (jaclaz @ Jul 22 2011, 09:13 AM) *
Let's start again with the concept of partitions.
You can only have either max 4 primary partitions or max 3 primary partitions + 1 extended...
That means that primary partitions are "precious" and you shouldn't really use one UNLESS really-really needed.
The advise was to create an extended partition and in it create a logical volume for Ubuntu.
Then, if needed, create another logical volume for Puppy linux.

I already HAD a FAT32 partition created when I tried the first time to install Ubuntu in it until I got *stuck* as stated previously so I did not continue at that point. Cancelled the install and came here for help.

QUOTE (SBernheart @ Jul 22 2011, 06:58 AM) *
Any pointers? Order in which I should be setting this up, i.e., format/partition as Ext2 instead of FAT32?

THESE ARE POINTERS...

QUOTE (jaclaz @ Jul 22 2011, 09:13 AM) *
...if you choose Ext2/3 you need to format the volume during the install of the Linux.
Delete the existing 10 Gb partition (that I presume you created as Primary).
Re-create a new extended partition the size of the rest of the disk (after the "XP" primary partition).
Create inside the extended partition a 10 Gb logical volume, and format it as FAT32).

...THIS, NOT SO MUCH.

QUOTE (jaclaz @ Jul 22 2011, 09:13 AM) *
What the heck do you mean by:
QUOTE
I've extracted Grub4DOS to new disk at "C:\GRUB4DOS"
You need to extract the file grldr from the grub4dos archive to the ROOT of the drive...AND NOT
C:\GRUB4DOS or C:\GRUB4DOS\GRUB4DOS or C:\GRUB4DOS\grldr

I got it from Grub4dos Guide - Loading/Installing Grub4dos and Load via ntldr (Windows NT/2K/XP) - 1 as:

QUOTE
Copy C:\GRUB4DOS\grldr to the root directory of an existing windows install and add the following line to the [operating systems] section of the configuration file boot.ini

I opened 7-zip, extracted from "Grub4DOS-0.4.4-2009-10-16.zip" to WinXPSP3. I read instructions as "on the root of Windows, there should be a folder 'Grub4dos' with a file in it 'grldr' as in C:\GRUB4DOS\grldr".

QUOTE (jaclaz @ Jul 22 2011, 09:13 AM) *
...you have possibly AGAIN botched that install by doing random things

Well, I'll repeat the steps I did -- rightly or wrongly -- in reverse order to which they were performed. This means (in NO particular order):
    Remove the folder "GRUB4DOS" from the root of WinXPSP3 and...
My apologies -- this IS the ONLY alteration I made short of adding the one line to XP's "boot.ini" (C:\grldr="Grub4DOS") which simply added "Grub4DOS" at "boot.ini" choices.

What else can I say? poke.gif I'll get back to you.....

SB blush.gif
Ed_P
Jul 22 2011, 04:22 PM
Let me refine that quote for you.

QUOTE (SBernheart @ Jul 22 2011, 05:07 PM) *
QUOTE
Copy the file C:\GRUB4DOS\grldr to the root directory of an existing windows install and add the following line to the [operating systems] section of the configuration file boot.ini

It's referring to a file named grldr in the folder that the unzipped GRUB4DOS was placed. And once the file has been copied the folder itself can be deleted. Though personally I would copy the file menu.lst to the root also before deleting the folder.

Better?

And I would use FAT32 for your Linux partitions.
FM_81
Jul 22 2011, 11:50 PM
QUOTE (Ed_P @ Jul 22 2011, 11:22 PM) *
And I would use FAT32 for your Linux partitions.
If you want to use any linux as live-system: OK!
But for a complete linux-install as root-partition: NEVER!
An other way is, to let space unpartitioned. The linux installer will then do its work and give EXT2 or EXT3 or EXT4 or reiserFS or ...


@SBernheart: After copying 'grldr' to your Windows-root (means same place as 'boot.ini' and 'ntldr') and making the described entry in 'boot.ini', you should be able to enter the GUB4DOS-shell by selecting the new entry in windows bootloader. This should work as VERY, VERY FIRST! Then begin about thinking of any linux. (And as jaclaz said: no newer bootloader to MBR)


And to make confusion a little bit greater and only as example and not related, to the previous: When you install Ubuntu and use Puppy as live-system they can reside on the same EXT-partition (but must not).

Greetings, FM_81
SBernheart
Jul 23 2011, 01:33 AM
QUOTE (Ed_P @ Jul 22 2011, 05:22 PM) *
It's referring to a file named grldr in the folder that the unzipped GRUB4DOS was placed. And once the file has been copied the folder itself can be deleted. Though personally I would copy the file menu.lst to the root also before deleting the folder.

Thanks, Ed. It drives me absoLUTEly BATTY when:
  • There are NO instructions whatsoEVER (like with CloneDisk). huh.gif
  • There *appears* to be instructions, when in reality they state something like, "here's a car", "here's a boat", "here's a plane", "here's a train"...states what *things* are in instructions without actually *instructing* how to use any of them! ohmy.gif
  • There's a clearly defined (though *I* wouldn't use the term "defined") "manual" or my personal favorite moniker, "users guide" which doesn't seem to *guide* the "user" ANYwhere!! rant.gif
I've read some instructions that clearly states (much like jaclaz's answer to CloneDisk) that, "if you are HERE, I presume you are at an intermediate level..." and voila! I could expect degree of difficulty -- just saying. rolleyes.gif

QUOTE (FM_81 @ Jul 23 2011, 12:50 AM) *
An other way is, to let space unpartitioned. The linux installer will then do its work and give EXT2 or EXT3 or EXT4 or reiserFS or ...

Greetings back atcha, FM_81. I googled "Ext2/Ext3" and all I managed to dig up was what they were for -- NOT how to create them. I had no idea that with simply some advance preparation, I could use my Ubuntu installer to "do it's thing". When I reached a point where I thought it wanted to attach/interject something involving XP's MBR/PBR, it worried me. unsure.gif Just needed a little confidence (and the added help of FIRST dealing with Grub4DOS). happy62.gif

@jaclaz
I hope we're BOTH wrong about messing up the XP partition in ANY way, shape or form. crying.gif I'll soon find out and back here to report...

SBernheart blush.gif
FM_81
Jul 23 2011, 02:57 AM
QUOTE (SBernheart @ Jul 23 2011, 08:33 AM) *
I googled "Ext2/Ext3" and all I managed to dig up was what they were for -- NOT how to create them. I had no idea that with simply some advance preparation, I could use my Ubuntu installer to "do it's thing".
Same way, as Windows ask's during installation, the UBUNTU-installer will do so too. (But asking for linux-specific filesystems.)

QUOTE (SBernheart @ Jul 23 2011, 08:33 AM) *
When I reached a point where I thought it wanted to attach/interject something involving XP's MBR/PBR, it worried me. unsure.gif Just needed a little confidence (and the added help of FIRST dealing with Grub4DOS). happy62.gif
Create/formate/assign filesystems and installing bootloader(s) are different things (in windows, and much more in linux). That's why I asked first (VERY, VERY FIRST) for a successfull chainloading of GRUB4DOS from your existing 'boot.ini'. The later installed linux will ask for it's own bootloader too (today in most cases GRUB2 is used). Install this to the linux-rootpartition (PartitionBootRecord, PBR), NOT to MBR, if you want to keep your existing primary bootmechanism ...

Greetings, FM_81
jaclaz
Jul 23 2011, 06:04 AM
QUOTE (FM_81 @ Jul 23 2011, 09:57 AM) *
Install this to the linux-rootpartition (PartitionBootRecord, PBR), NOT to MBR, if you want to keep your existing primary bootmechanism ...


Yep smile.gif.

I really cannot see the difficult part:
QUOTE (jaclaz @ Jul 21 2011, 08:31 PM) *
Use a dedicated partition for Linux.
DO NOT let any Linux installer write to the MBR.
Normally Linux distro's won't install on NTFS partition, either format the 10 Gb partition as FAT32 or make the partition (actually volume in extended) under Linux (Ext2/Ext3 FS).
Let them install their boot code to the PBR (or nowhere, if possible).


I'll try again, if the Ubuntu installer asks you:
  1. if it should install bootloader to the MBR, say NO.
  2. if it should NOT install ANY bootloader say YES.
  3. INSTEAD of the latter if it should install to the PBR or volume or bootsector or partition, say YES, it is good as well.


  1. MBR BAD sad.gif
  2. Nowhere BEST (preferred) yahoo.gif
  3. PBR GOOD thumbsup.gif



cheers.gif
Wonko
FM_81
Jul 23 2011, 06:35 AM
QUOTE (jaclaz @ Jul 23 2011, 01:04 PM) *
2. Nowhere BEST (preferred) yahoo.gif
I'm not sure, if, in this case a 'menu.lst' or a 'grub.cfg' will be created? (Because I've never tested this.)
The 'menu.lst' or 'grub.cfg' can be useful later, to add entry's directly to GRUB4DOS's 'menu.lst', which would avoid to have to much "cascading" bootloaders.

Greetings, FM_81
SBernheart
Jul 23 2011, 07:43 AM
QUOTE (SBernheart @ Jul 22 2011, 06:58 AM) *
I tried booting new disk to check on Grub4DOS and it was listed at "boot.ini" choices, but when I chose this option, I got the following message (even though when checked on after, the "hal.dll" file IS there):
QUOTE
Windows could not start because the following file is missing or corrupt:
    <Windows root>\system32\hal.dll
Please re-install a copy of the above file.
Then, after having to power off, I restarted and at boot menu, chose the new disk (again), but this time I chose regular Windows XP at "boot.ini" choices and got a 7B BSOD.

According to Ubuntu help pages (and directed to this page at Microsoft Support), the "Invalid Boot.ini Error Message" is due to the changes made to "boot.ini" file. I'm hoping that's all it was -- fingers crossed.

As for the rest, I've only managed to set up the Ext3 partition and in it, two logical FAT32 volumes -- a 10GB one for Ubuntu and a 5GB one for Puppy (the latter of which CAN be deleted as it was only put there because I had access to do it at the time) and 10GB more for growing pains. See attached pic....

QUOTE (jaclaz @ Jul 23 2011, 07:04 AM) *
I'll try again, if the Ubuntu installer asks you:
  1. if it should install bootloader to the MBR, say NO.
  2. if it should NOT install ANY bootloader say YES.
  3. INSTEAD of the latter if it should install to the PBR or volume or bootsector or partition, say YES, it is good as well.

IT doesn't ASK for ANYthing. A popup message appears simply telling me:

QUOTE
No root file system is defined. Correct from partitioning menu.

Ubuntu's installer CD is still requesting the "root file system" and while I referred to certain help pages, it is ALL Greek to me (no offense). I'll pick up where I left off after much needed rest (isn't it always "much needed") and hopefully, I'll figure out how to make these "changes" to the Ubuntu partition and/or to the Grub4DOS files I have in XP (and yes, the "grldr" and "menu.lst" files are in the root folder (if it too is called a "folder") same as where the "boot.ini" file is). I don't even know how to *open* these files (if I *knew* what to even put in them) and while most updating from help pages is done at a command prompt, this doesn't give me much confidence either. Better luck later today gentlemen.....

SBernheart sleeping.gif
FM_81
Jul 23 2011, 09:00 AM
Two things:
1. This
CODE
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /noexecute=optin
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP jaclaz" /sos /bootlog /basevideo
C:\grldr="Grub4DOS"
is exactly the content of your C:\boot.ini (also with ENTER at end of last line)?

2. Please show contents of C: ...

Greetings, FM_81
Ed_P
Jul 23 2011, 09:39 AM
QUOTE (SBernheart @ Jul 23 2011, 08:43 AM) *
As for the rest, I've only managed to set up the Ext3 partition and in it, two logical FAT32 volumes -- a 10GB one for Ubuntu and a 5GB one for Puppy (the latter of which CAN be deleted as it was only put there because I had access to do it at the time) and 10GB more for growing pains. See attached pic....

I think you meant to say you've managed to set up the Extented partition and in it, two Logical FAT32 volumes.

BTW Windows can't see/access files in Ext3 partitions and Linux can't see/access files in NTFS partitions, last time I looked.

QUOTE (SBernheart @ Jul 23 2011, 08:43 AM) *
the Grub4DOS files I have in XP (and yes, the "grldr" and "menu.lst" files are in the root folder (if it too is called a "folder") same as where the "boot.ini" file is). I don't even know how to *open* these files (if I *knew* what to even put in them) and while most updating from help pages is done at a command prompt, this doesn't give me much confidence either.

You don't want to open the grldr file, it's an executable. The menu.lst file you can open with Notepad.
jaclaz
Jul 23 2011, 10:47 AM
QUOTE (Ed_P @ Jul 23 2011, 04:39 PM) *
... and Linux can't see/access files in NTFS partitions, last time I looked.

When was it?
Before the war? w00t.gif

wink.gif

@Sarah
If you have doubts, ASK about them, DO NOT assume.
Partitions can be:
  • Primary<- a primary partition is ALSO a volume
  • Extended<-an Extended partition may contain (logical) volumes

FAT12 FAT16, FAT32, EXFAT, NTFS, EXT2, EXT3 are FILESYSTEMS.

You FORMAT a volume by applying a FILESYSTEM to it.


cheers.gif
jaclaz
Ed_P
Jul 23 2011, 02:31 PM
QUOTE (jaclaz @ Jul 23 2011, 11:47 AM) *
When was it?
Before the war? w00t.gif

blush.gif Maybe I'm thinking DOS?? hmm.gif
SBernheart
Jul 23 2011, 03:56 PM
QUOTE (Ed_P @ Jul 23 2011, 10:39 AM) *
I think you meant to say you've managed to set up the Extented partition and in it, two Logical FAT32 volumes.

I stated "Ext3" in case it mattered *which* extended type it was. Otherwise, I don't understand the difference between what you stated and what I stated. huh.gif

QUOTE (Ed_P @ Jul 23 2011, 10:39 AM) *
BTW Windows can't see/access files in Ext3 partitions and Linux can't see/access files in NTFS partitions, last time I looked.

You can mount other drives/disks AND you can use something like "Ext2 Installable File System For Windows" (works for Ext3 too BUT it doesn't work with Win 7 at the moment AFAIK) which I plan on downloading for XP. Once Win 7's drive is mounted, I can access my folders/files there as well. happy62.gif Again AFAIK, Win 7 can view an attached, offline drive/disk like the new one with XP on it, so I don't see any reason for NOT being allowed to access folders/files on the partitions where I hope Ubuntu and Puppy will eventually reside, but I think Win 7 may NOT be able to access the Linux folders/files. Time will soon tell....

QUOTE (Ed_P @ Jul 23 2011, 10:39 AM) *
You don't want to open the grldr file, it's an executable. The menu.lst file you can open with Notepad.

I assume you mean I can change the extension for "menu.lst" to "txt" so I can open it with Notepad. hmm.gif Still wouldn't know *what* to put in it....

QUOTE (FM_81 @ Jul 23 2011, 10:00 AM) *
...is exactly the content of your C:\boot.ini (also with ENTER at end of last line)?
2. Please show contents of C: ...

Not sure what you're asking for, FM. Do you literally want to know the "names" of the folders/files that are in the root of (C:)? unsure.gif

QUOTE (jaclaz @ Jul 23 2011, 11:47 AM) *
If you have doubts, ASK about them, DO NOT assume.
FAT12 FAT16, FAT32, EXFAT, NTFS, EXT2, EXT3 are FILESYSTEMS.

You FORMAT a volume by applying a FILESYSTEM to it.

If that's true that FAT32 already IS a "files ystem", then why is the CD installer asking for one? wacko.gif

I have doubts about....
  • what to change/add in the "menu.lst" file
  • using command-line functions to change/add items in the "menu.lst" file
  • reformatting FAT32 for Ubuntu if a "file system" is STILL *missing*
  • how to use the list of options when/if choosing "Grub4DOS" from "boot.ini" choices on new disk
....asking, NOT assuming. rolleyes.gif

SBernheart crying.gif
Ed_P
Jul 23 2011, 04:22 PM
QUOTE (SBernheart @ Jul 23 2011, 04:56 PM) *
I stated "Ext3" in case it mattered *which* extended type it was. Otherwise, I don't understand the difference between what you stated and what I stated. huh.gif

One is a Windows filesystem, one is a Linux filesystem.

QUOTE
You can mount other drives/disks AND you can use something like "Ext2 Installable File System For Windows"

If the Linus FILESYSTEMs are FAT32 you don't need an addon to Windows to access the files and folders on them.

QUOTE
I assume you mean I can change the extension for "menu.lst" to "txt" so I can open it with Notepad. hmm.gif

No, I mean when you try to Open it and Windows asks you what to use you select Existing program then select Notepad.

QUOTE
Not sure what you're asking for, FM. Do you literally want to know the "names" of the folders/files that are in the root of (C:)? unsure.gif

That would be my interpretation. Do a dir c: > Cdir4FM.txt and zip or paste the results here if not overly long.
jaclaz
Jul 23 2011, 04:54 PM
@Sarah
What you wrote:
QUOTE
I've only managed to set up the Ext3 partition and in it, two logical FAT32 volumes -- a 10GB one for Ubuntu and a 5GB one for Puppy


An "Ext3 partition" does NOT (and CANNOT) contain volumes!

An Extended partition may contain volumes which can be formatted with a filesystem, as an example you can have in the Extended partition two volumes, the first formatted as FAT32 and the second formatted as Ext3.

Is this clear to you, now?

About your questions, they still completely fail to make sense.

Let alone menu.lst, and GRLDR (for the moment).


Your NEXT (and ONLY important) step is to start the Ubuntu install.


What is the difficult part?
https://help.ubuntu.com/community/WindowsDualBoot
QUOTE
Install Ubuntu after Windows


You want to NOT write to the MBR:
QUOTE
If you have a problem with changing the MBR code, you might prefer to just install the code for pointing to GRUB to the first sector of your Ubuntu partition instead. If you do that during the Ubuntu installation process, then Ubuntu won't boot until you configure some other boot manager to point to Ubuntu's boot sector.


Once you have installed UBUNTU as per above, we will talk of menu.lst, etc.

cheers.gif
Wonko
SBernheart
Jul 24 2011, 07:53 AM
QUOTE (jaclaz @ Jul 22 2011, 08:13 AM) *
Delete the existing 10 Gb partition (that I presume you created as Primary). <<<WAS actually FAT32 at 10GB, but deleted anyway to continue "re-creating"....
Re-create a new extended partition the size of the rest of the disk (after the "XP" primary partition).
Create inside the extended partition a 10 Gb logical volume, and format it as FAT32).

What a totally and utterly disappointing chain of events. I now have NO access to ANYthing remotely resembling my computer system with the slight (VERY slight) exception of the CD-ROM drive which, at the moment, has the Ubuntu CD running -- otherwise I couldn't even be doing THIS!!!!! ranting2.gif
  • I deleted the 10GB FAT32 Ubuntu partition I originally created (a LONG time ago).
  • I *thought* I created an Ext3 partition at 25GB AFTER the XP partition and in it, I created the two volumes, Ubuntu and Puppy, and left remaining 10GB for this partition empty.
  • Thinking that too, was wrongly executed (since I really MEANT "Ext3" with two volumes in it created with the Ubuntu CD -- NOT by the installer, but with Ubuntu's disk mgmt), I deleted THAT partition and started over per quoted instructions above.
I rebooted using the Ubuntu CD (and yes, THIS time, allowed the installer to do the work) and steps followed:
  • Re-created a new extended partition the size of the rest of the disk (after the "XP" primary partition).
  • IT (the installer) created a "device" referring to all the unallocated space AFTER the XP partition (XP was "sdb" OR "sdb1" and NOT included in anything AFAIK) and named the device "d9467894-f8e0-474c-8204-46514740072d".
  • IT created an extended partition (the same size as unallocated space; same size as IT's "device") and included in it:
    • An Ext4 file system (I did NOT *choose* this -- the installer did) named "ubuntu" approx. 400GB
    • A volume (?) named "linux-swap" approx. 10GB
    • Remaining unallocated/unused space at 1MB (I think)
  • It updated "Grub" (?) to "Grub2" (I did NOT *choose* this -- the installer did).
  • Installer finally made it past the "No root file system" crap and began installation (or rather, FINISHED installation).
I rebooted the new disk to find the disturbing message:
QUOTE
error: file not found.
grub rescue> (blinking cursor)

I rebooted Win 7 and MORE horror:
QUOTE
error: no such device: d9467894-f8e0-474c-8204-46514740072d <<<name given to refer to the *space* AFTER the XP partition IT called "device"....
grub rescue> (blinking cursor)

I unplugged the frickin' new disk and put the Ubuntu CD in again to boot up with and here I am -- back to square "before the times of the frickin' pyramids" celebrate3.gif , but so NOT a happy dance!
I'm deleting EVERYTHING except the XP partition and HOPING I get Win 7 back in the process -- I can still *see* the folders/files from Ubuntu's "File Browser", so....

Can't even BEGIN to think what the Hub will say when he gets up and finds out I lost Win 7 AGAIN, so trust me, JL -- ANYTHING bad you have to say will be spoken out LOUD shortly....

SB

BTW, FM -- I've attached the zip kindly referred by Ed_P that WAS my XP. God only knows what it (and Win 7) may be NOW....
jaclaz
Jul 24 2011, 08:37 AM
Very good. smiling9.gif (which means, very, VERY, VERY bad. sad.gif)

Last time I checked Ubuntu Install did not do things by itself, it did ask for confirmation. frusty.gif

§@ç#ing STOP doing SENSELESS things like "deleting everything".

STOP doing anything by yourself!

Now, follow this set of instructions ATTENTIVELY and EXACTLY:
  1. get the UBUNTU CD/DVD, put it in a drawer, close the drawer with it's key, throw the key in the dustbin, after having broken it in three or more pieces. (when you will be able to lockpick open the drawer then you will be ready for UBUNTU).
  2. boot the UBCD4WIN
  3. open a command prompt and run in it MBRFIX


CODE
MBRFIX /drive 0 driveinfo

and:
CODE
MBRFIX /drive 1 driveinfo


find out which disk is the "XP (external USB) and which is the "7" (internal).
Say that disk 1 is the XP and disk 0 is the 7, then run ONLY:
CODE
MbrFix /drive 1 fixmbr

(you want to make sure that the MBR code on the USB disk is the XP one)
and try booting from the USB disk.

Report what happens.

jaclaz
SBernheart
Jul 24 2011, 09:33 AM
QUOTE (jaclaz @ Jul 24 2011, 08:37 AM) *
Last time I checked Ubuntu Install did not do things by itself, it did ask for confirmation.

Hmm....I remember when the paging file "auto*magic*ally" jumped from one drive to another; then again from one disk to another DISK -- all by itself AND without asking me for confirmation. hmm.gif Just saying....

In any event, the fact that UBCD4Win doesn't allow internet connectivity, means I need to switch back and forth between IT and the Ubuntu CD (so I suppose the scenario you prescribed for the latter has to wait a while). rolleyes.gif I tried said instructions and results:

QUOTE
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

X:\I386\System32>MBRFIX /drive 0 driveinfo
'MBRFIX' is not recognized as an internal or external command,
operable program or batch file.

X:\I386\System32>CD X:\

X:\>MBRFIX /drive 0 driveinfo
'MBRFIX' is not recognized as an internal or external command,
operable program or batch file.

X:\>

Yes, the Hub is up and looking over my shoulder....

SB sad.gif
Ed_P
Jul 24 2011, 09:52 AM
With the USB drive detached the machine doesn't boot Win 7?

On the UBC4WIN isn't there a menu of items? Find MBRFIX in the menu and click on it. It's not something you run from a command prompt, as you found.

And for the record; Extended, Ext3, and Ext4 are DIFFERENT partition types. When jaclaz refers to an Extended partition he means a WINDOWS partition type, not a Linux one.
jaclaz
Jul 24 2011, 09:58 AM
Well, find where the heck MBRFIX is in the UBCD4WIN and navigate to where it is (which is NOT X:\I386\System32 or X:\) before running the command.
The good UBCD4WIN guys are quite organized thumbsup.gif, I would guess they put it in \Programs\mbrfix\ wink.gif

QUOTE (Ed_P @ Jul 24 2011, 04:52 PM) *
And for the record; Extended, Ext3, and Ext4 are DIFFERENT partition types. When jaclaz refers to an Extended partition he means a WINDOWS partition type, not a Linux one.

NO,NO, NO, NO, NO! frusty.gif
Extended is "OS agnostic" and is a partition type.
Ext2, Ext3 and Ext 4 are FILESYSTEMS, NOT "partition types".

Extended partition exists in DOS, Windows, Linux, and in ANY disk MBR based. ranting2.gif

cheers.gif
jaclaz
FM_81
Jul 24 2011, 10:06 AM
Only to make things clear to me: this nice picture http://www.911cd.net/forums//index.php?act...ost&id=1888 means: Disk 0 is internal and running Windows 7 and Disk 1 is an USB and has Windows XP? And grldr exists on USB only? Is this correct?

MfG, FM_81
Ed_P
Jul 24 2011, 10:07 AM
@jaclaz

So they are not all the same, which is the point I was trying to make. I think Sara reads them as being equals.
jaclaz
Jul 24 2011, 11:23 AM
QUOTE (Ed_P @ Jul 24 2011, 05:07 PM) *
@jaclaz

So they are not all the same, which is the point I was trying to make. I think Sara reads them as being equals.

And you wrote to the same effect, further confusing matters. ph34r.gif

Layman's example w00t.gif:
  • Screwdrivers, spanners, hacksaws are tools, you can say that they are different tool types, a "screw-driving" tool, a "bolt&nut-turning" tool and a "metal-cutting" tool.
  • You usually carry them in a toolbox.
  • Toolboxes are usually made of either metal or plastic, you can say that you have a "plastic type" toolbox or a "metal type" toolbox.
  • You don't normally say that you have a "plastic type" tool or a "metal type" tool.
  • Nor you say that you have a "screw-driving" toolbox, a "bolt&nut-turning" toolbox or a "metal-cutting" toolbox.
  • More than that you DO NOT try putting a tool inside a tool (like "I just put my screwdriver inside my hacksaw, and my hacksaw inside my spanner" whistling.gif).


A partition is a CONTAINER.
A partition can contain Volume(s).
A partition can be of two types: Primary and Extended.
A Primary partition can contain only one Volume (that is EXACTLY as big as the partiton, hence the terms are exchangeable)
An Extended partition can contain one or more (Logical) Volumes.
A Volume is formatted by applying a filesystem to it.

Meaningful:
NTFS (Primary) partition = NTFS Volume = Volume formatted with the NTFS filesystem = screwdriver inside (metal) toolbox
FAT32 (Primary) partition = FAT32 Volume = Volume formatted with the FAT32 filesystem = hacksaw inside (metal) toolbox
NTFS Volume (inside Extended partition) = NTFS Volume = Volume formatted with the NTFS filesystem = screwdriver inside (plastic) toolbox
FAT32 Volume (inside Extended partition) = FAT32 Volume = Volume formatted with the FAT32 filesystem = hacksaw inside (plastic) toolbox
EXT3 Volume (inside Extended partition) = Ext3 Volume = Volume formatted with the Ext3 filesystem = spanner inside (plastic) toolbox

Meaningless:
FAT32 (Logical) Volume (inside EXT3 partition) = A suffusion of yellow = hacksaw inside spanner = "metal-cutting" tool inside "bolt&nut-turning" tool w00t.gif


cheers.gif
jaclaz
SBernheart
Jul 24 2011, 11:28 AM
QUOTE (Ed_P @ Jul 24 2011, 09:52 AM) *
With the USB drive detached the machine doesn't boot Win 7?

BOTH -- tried first with USB HDD still connected, then with USB removed and received the error messages I reported.

QUOTE (FM_81 @ Jul 24 2011, 10:06 AM) *
Only to make things clear to me means Disk 0 is internal and running Windows 7 and Disk 1 is an USB and has Windows XP? And grldr exists on USB only? Is this correct?

Yes, yes and no -- grldr, grldr.mbr, menu.lst and a bunch of other stuff is on the Win 7 disk as well. Poor jaclaz worked with me for a very long time to get XP up and running on a new disk, so while I *am* familiar with the "names" of these files/programs/etc., what I am most often NOT familiar with is what to *do* with them. wink.gif

QUOTE (jaclaz @ Jul 23 2011, 04:54 PM) *
An "Ext3 partition" does NOT (and CANNOT) contain volumes!

An Extended partition may contain volumes which can be formatted with a filesystem, as an example you can have in the Extended partition two volumes, the first formatted as FAT32 and the second formatted as Ext3.

Is this clear to you, now?

Yes -- I only *thought* I created an Ext3 *partition* with two volumes in it when, in actuality, disk mgmt created instead an extended partition with two FAT32 volumes (and some extra space) in it. When the installer did it, it created an extended partition with all the unallocated space and then created a volume formatted as Ext4 for Ubuntu with almost the whole partition's space except for a "dash" of something (1MB) and 10GB of the "linux-swap" volume (?). I get *it* now, JL. It just needs to be trimmed down when Ubuntu creates these for me.

To the task at hand --

QUOTE
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

X:\I386\System32>CD X:\PROGRAMS\mbrfix

X:\PROGRAMS\mbrfix>MBRFIX /drive 0 driveinfo
Drive 0
Cylinders = 77825
Tracks (heads) per cylinder = 255
Sectors per track = 63
Bytes per sector = 512
Disk size = 640132416000 (Bytes) = 596 (GB)

X:\PROGRAMS\mbrfix>MBRFIX /drive 1 driveinfo
Drive 1
Cylinders = 60801
Tracks (heads) per cylinder = 255
Sectors per track = 63
Bytes per sector = 512
Disk size = 500105249280 (Bytes) = 465 (GB)

X:\PROGRAMS\mbrfix>MbrFix /drive 1 fixmbr
You are about to Fix MBR,
are you sure (Y/N)? Y

X:\PROGRAMS\mbrfix>

Rebooted to 7B error BSOD.

SBernheart help.gif
jaclaz
Jul 24 2011, 11:41 AM
QUOTE (SBernheart @ Jul 24 2011, 06:28 PM) *
Rebooted to 7B error BSOD.

No, you did NOT.
You rebooted to a BOOT.INI choice AND chose to boot windows XP.
Try again booting BUT choose to boot grub4dos this time.

BEFORE the above, boot again from the UBCD4WIN and this time run:
CODE
mbrfix /drive 0 fixmbr /win7


then try booting from the INTERNAL HD (the one with 7 on it).

If it boots allright, proceed to try booting from the USB and choosing grub4dos instead.
If it doesn't, report what happens and proceed anyway to try booting from the USB and choosing grub4dos instead.

cheers.gif
jaclaz
SBernheart
Jul 24 2011, 01:03 PM
QUOTE (jaclaz @ Jul 24 2011, 11:41 AM) *
You rebooted to a BOOT.INI choice AND chose to boot windows XP.
Try again booting BUT choose to boot grub4dos this time.
....try booting from the INTERNAL HD (the one with 7 on it).

If it boots allright, proceed to try booting from the USB and choosing grub4dos instead.
If it doesn't, report what happens and proceed anyway....

Of course, JL. I passed the "boot.ini' choices, chosing XP and THEN got BSOD. My bad....

QUOTE
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

X:\I386\System32>CD X:\PROGRAMS\mbrfix

X:\PROGRAMS\mbrfix>mbrfix /drive 0 fixmbr /win7
You are about to Fix MBR,
are you sure (Y/N)? Y

X:\PROGRAMS\mbrfix>

THIS time, I applied MBRfix to Win 7, switched out the CDs and rebooted Win 7 (the internal HD for those of you keeping score wink.gif). When I arrived at "boot.ini" choices, I chose GRUB4DOS and it's screen came up for me OK.

THIS time, when I arrived at "boot.ini" choices for XP, I chose GRUB4DOS and it's screen came up for me OK too.

Should I proceed to actually trying one of the OS? unsure.gif

SB
jaclaz
Jul 24 2011, 01:16 PM
How the heck did you manage to have "BOOT.INI" choices on the Windows 7 disk? w00t.gif

You should have at the most "BCD" choices, and one of them should be Windows 7.

Reboot (from the internal HD) and choose Windows 7.

OR choose grub4dos and at it's prompt type:
CODE
chainloader /BOOTMGR

[ENTER]

You can continue looping a bit before trying loading Windows 7 whistling.gif

Simplified: most probably the XP install on the USB disk is botched, in any case it is expendable as you have an image of it, the main thing is that the Windows 7 works.

cheers.gif
jaclaz


SBernheart
Jul 24 2011, 02:47 PM
QUOTE (FM_81 @ Jul 23 2011, 10:00 AM) *
CODE
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /noexecute=optin
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP jaclaz" /sos /bootlog /basevideo
C:\grldr="Grub4DOS"
This is exactly the content of your C:\boot.ini (also with ENTER at end of last line)?

I don't have "ENTER" in ANY of the ones we've used, but is not "Microsoft Windows XP Home Edition", "XP jaclaz" and "Grub4DOS" the "choices" we're always looking to "get to"? I'm not sure why you're surprised I got to the "boot.ini" choices (and ultimately, to choose GRUB4DOS AND get it's screen), I'm just thankful it worked.

I am now posting from running Win 7 and I certainly could NOT have done this withOUT you, jaclaz, BUT what's REALLY impressive is that you were helping me in real time. In other words, my Hub gave you props for replying back and forth the way you did so that HE could have his computer back. Obviously, my weird sleeping habits allow me all the time I need to do pretty much *what* I want, *when* I want. So he thanks you too and I'll be sure he adheres to the "CAREWARE LICENSE" (as will I wink.gif ).

I now must give up the machine that keeps him going during the day and the vampire that I am will return after hours to continue messing up everything, OK JL? I am concerned about XP, but I'm on overtime (I haven't even gone to sleep yet), so I'll pick this up again a little later. If you can think of something needing done like, what do I do with GRUB4DOS once I chose it (from XP's new disk, I mean). Is it just a test to see what's working and what isn't? Let me know and TY again....

SBernheart smile.gif
Ed_P
Jul 24 2011, 05:40 PM
QUOTE (FM_81 @ Jul 23 2011, 10:00 AM) *
2. Please show contents of C: ...
C:

QUOTE (Ed_P @ Jul 23 2011, 05:22 PM) *
That would be my interpretation. Do a dir c: > Cdir4FM.txt and zip or paste the results here if not overly long.
C:

QUOTE (SBernheart @ Jul 24 2011, 08:53 AM) *
BTW, FM -- I've attached the zip kindly referred by Ed_P that WAS my XP. God only knows what it (and Win 7) may be NOW....

QUOTE (Wdir4FM.zip)
Volume in drive W is WinXPSP3
Volume Serial Number is 800F-3FBB

Directory of W:\
W:

confused1.gif

BTW The XP volume directory shows a boot.ini but doesn't show a ntldr or NTDETECT.COM?? Can you show the results of an ATTRIB W:\*.* command?
jaclaz
Jul 25 2011, 01:03 AM
Yep smile.gif, for the record, being a husband myself, I simply had to do something to help your poor hubby in the name of WHU (World Husbands United). wink.gif.


Take care, have a nice day sleep, see you after dark w00t.gif.

cheers.gif
jaclaz
SBernheart
Jul 25 2011, 03:31 AM
QUOTE (FM_81 @ Jul 23 2011, 10:00 AM) *
Two things:
1. This
CODE
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /noexecute=optin
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP jaclaz" /sos /bootlog /basevideo
C:\grldr="Grub4DOS"
is exactly the content of your C:\boot.ini (also with ENTER at end of last line)?

2. Please show contents of C: ...

I took this to mean that inquiries were about the USB disk with XP on it since, this was the boot.ini file referred to. At the time of posting, the directory I *thought* you wanted, FM (may I call you "FM"?), was the (W:) drive. If it's not what you were looking for, I've attached a second zip which includes a fresh copy of the XP drive (W:) AND it's attributes and a new copy of the Win 7 drive (C:) AND it's attributes as well. Disk 0 IS the internal HD and running Windows 7 on it and Disk 1 IS the USB drive and has Windows XP on it. Hope this clears away ANY confusion between the two drives; the two disks.

QUOTE (Ed_P @ Jul 24 2011, 06:40 PM) *
BTW The XP volume directory shows a boot.ini but doesn't show a ntldr or NTDETECT.COM??

I don't know if Win 7 includes those two files or not (if NOT the same systems), but XP definitely has both of them listed in my Win Explorer though these are hidden files (even though I show them as NOT hidden when collecting the info requested). Both *are* there for XP, so no worries, Ed. Thanks for watching out.

sign06.gif
Just so you don't think of me even MORE looney than usual, wacko.gif the reason behind the *odd* drive letters stems back to when we were still working on getting my "original" XP working. Different pieces of my equipment have different parts included, i.e., a card reader on new PC and two readers on new enclosure, so I had to get a system down so I could count on certain drive letter assignments no matter which PC I was working with (or which enclosure I was working with). I went out of my way to keep everyone as much on the same page as I could hope to. Card Readers became "X", "Y" and "Z", for ex., so as NOT to load before "F" and "G" which jaclaz and I were used to seeing. Later, cdob wrote instructions where "U" stood for the "USB disk". Even my flash drives now get into the act to keep them too out of the way of people here trying to write specific steps involving specific code/instructions. So maybe it's not hard to understand why letter assignments may NOT be the norm, at least where SB is considered anyway.wink.gif Just saying....

@jaclaz
OK if I attempt to boot XP disk up to and past boot.ini choices since already getting the GRUB4DOS splash screen? BTW, my Hub sang your praises all afternoon. I never went to sleep. It was 3:45PM my time before I finished and I'm usually getting up by then. I saw no point in trying to rest as it would have screwed up my whole schedule (and it's already screwed up enough). Take this as a consolation for the aggravation and/or as my punishment (not to mention my Hub on my back all morning while you helped me get 7 back for him wink.gif) and it's good to see the brotherhood! Be careful though, as your "better halves" belong to the one TRUE sisterhood aptly named "WWW" (and it doesn't stand for "World Wide Web"). I'll give you a little hint.... wodoo.gif

SBernheart biggrin.gif
FM_81
Jul 25 2011, 03:33 AM
QUOTE (Ed_P @ Jul 25 2011, 12:40 AM) *
BTW The XP volume directory shows a boot.ini but doesn't show a ntldr or NTDETECT.COM?? Can you show the results of an ATTRIB W:\*.* command?
Confirm! Would missing these both too ...

May be also, the letter W: is a result of posting this from the Windows-7-system. In the earlier refered screenshot it is also W:, so it's possible that this didn't make any sense?

Greetings, FM_81

PS @ jaclaz: Would you confirm, that both MBR's (internal & USB) was overwritten by GRUB2-code during UBUNTU-installation? But not knowing why and how ...?
SBernheart
Jul 25 2011, 04:21 AM
QUOTE (SBernheart @ Jul 25 2011, 04:31 AM) *
I took this to mean that inquiries were about the USB disk with XP on it since, this was the boot.ini file referred to. At the time of posting, the directory I *thought* you wanted, FM (may I call you "FM"?), was the (W:) drive. If it's not what you were looking for, I've attached a second zip which includes a fresh copy of the XP drive (W:) AND it's attributes and a new copy of the Win 7 drive (C:) AND it's attributes as well. Disk 0 IS the internal HD and running Windows 7 on it and Disk 1 IS the USB drive and has Windows XP on it. Hope this clears away ANY confusion between the two drives; the two disks.

@FM_81
Take a peek at the OT bit and you'll see why there may have been confusion because of my crazy letter assignments, but you should now have the original zip with the XP directory and the latest zip that has the Win 7 directory as well as BOTH attribute listings from both HDDs.

@jaclaz
I had an idea, but now worrying that, based on what FM just posted, it may give me the same unwanted repeat of yesterday morning's events, I don't know if it's even worth the attempt....

Would the Ubuntu installer create everything it needs to become a working OS if it had it's own dedicated disk? What if I created only an extended partition of say, 50GB, on the old, otherwise *expendable* 465GB HDD? IF it can't hurt the running Win 7 and IF it can't *migrate* such headaches like possibly updating to GRUB2 EVERYwhere it saw fit throughout the rest of my system (even though it most certainly was NOT asked for, nor confirmed by me), would this be feasible? Mind you, I'm NOT trying to literally install it there from which to boot it from -- I'm just asking if Ubuntu would "fill in the blanks", so to speak, if only just allowing me to view it's contents from Win Explorer.

Must be the lack of sleep yesterday, but I thought of this as an alternative to "practicing" with the new disk and the "precious" XP partition. Simple YES or NO will do....

SB idea.gif
jaclaz
Jul 25 2011, 04:46 AM
QUOTE (FM_81 @ Jul 25 2011, 10:33 AM) *
PS @ jaclaz: Would you confirm, that both MBR's (internal & USB) was overwritten by GRUB2-code during UBUNTU-installation? But not knowing why and how ...?


I don't know. blush.gif

Since Sarah has this tendency to give a lot of details on needless things but has sometimes difficulties in providing needed info or gives them in a confusing way whistling.gif, I took shortcut #1:
  • no matter what CODE the MBR has, replace it with the one it should have wink.gif


Or if you prefer, the primary scope was not to "recover" the Ubuntu install or the previous "XP on USB", but to have the "main" hard disk booting 7, if while fixing the second the first came out "for free" and as "collateral damage" all the better. smile.gif

@Sarah
You should take some sleep/rest yawn.gif, then, after coffee.gif you'll probably see things in a much clearer way....
The "old, expendable" 465 Gb was the botched disk, if I remember correctly, if it doesn't work or is not reliable, it would be pointless to use it.

Linux systems and their installers are normally designed to create NOT havoc as it happened to you, so you must have done something wrong (or answered yes in the wrong place ph34r.gif).

Now, you have an image of the USB disk, right?
And you also have a copy of it's MBR BEFORE the attempt to install Ubuntu, right? (or anway there must be a copy uploaded on the board somewhere)
Try restoring the MBR copy to the USB disk, and try booting from it.
This should be enough to recreate the situation that was working before, as I doubt that the Ubuntu install overwrote anything in the "main" NTFS partition.
If not, we'll see how to fix it AS it was before the failed attempt.
Then we'll see how exactly to install Ubuntu in a volume inside Extended partition without creating problems to the other installs

cheers.gif
jaclaz
FM_81
Jul 25 2011, 05:10 AM
QUOTE (SBernheart @ Jul 25 2011, 11:21 AM) *
Would the Ubuntu installer create everything it needs to become a working OS if it had it's own dedicated disk? What if I created only an extended partition of say, 50GB, on the old, otherwise *expendable* 465GB HDD? IF it can't hurt the running Win 7 and IF it can't *migrate* such headaches like possibly updating to GRUB2 EVERYwhere it saw fit throughout the rest of my system (even though it most certainly was NOT asked for, nor confirmed by me), would this be feasible?
Most linux-installers provide an "auto-mode" and, in most cases, others (call it "semi-hand" or "do all by hand"; meaningless how it is called) But "auto-mode" (I assume it here ...) would NOT work with your "strange kind of partitioning and operation systems". So you should choice "do all by hand". May be, you've missed this point? Here you can define all:
    - what's your 'root'-partition (simply called / in linux)
    - what's your SWAP-partition (compare this with 'pagefile.sys' in windows)
    - would you create an additional /home'-partition (for userdata)
    - should an bootloader installed, and if yes, on which place
    - and so on and so on ...

May be also, this point "do all by hand", is a little bit hidden on the installer-CD!?
QUOTE (SBernheart @ Jul 25 2011, 11:21 AM) *
Mind you, I'm NOT trying to literally install it there from which to boot it from -- I'm just asking if Ubuntu would "fill in the blanks", so to speak, if only just allowing me to view it's contents from Win Explorer.
The normal files on an EXT2/3/4 system you will not see in Windows.

Greetings, FM_81

PS: A fully other approach can be, to use "WUBI". It creates an "containerfile" INSIDE the Windows-system (no matter which) and all linux-stuff runs from this. It also lets windows-loaders untouched. May be, it's easier in your case?
jaclaz
Jul 25 2011, 07:26 AM
This should be the "latest" installer screenshots:
http://www.psychocats.net/ubuntu/installing



What is behind the "Something Else" we will see..... and yes, Sarah you MUST choose "something else" wink.gif.... then, BEFORE doing ANYTHING you may later regret, describe which options you are given.....

These may help, as a reference:
http://www.linuxbsdos.com/2011/05/05/how-t...fs-file-system/


@Sarah
Let's see if this is clear:


  1. under Linux disks are designed with letters (NO, NOT "drive" letters, device letters), like /dev/hda, dev/hdb, dev/sda, dev/sdb, etc..
    As an example in the above example the hard disk (or \\.\PhysicalDriven) is called dev/sda .
  2. A partition or volume is designed with a number, in the above the partitions are dev/sda1, dev/sda2, dev/sda3.



The MBR is part of the disk, i.e. of dev/sdx.
The bootsector or PBR or VBR is part of the Volume or Partition, i.e. of dev/sdxn

When it says:
QUOTE ("Linux jargon")
Device for boot loader installation: dev/sda ATA VBOX HARDDISK (55,7 GB)


it actually means:

QUOTE ("Dos/Windows jargon")
Do you really want to write a new MBR on this hard disk?


cheers.gif
jaclaz
SBernheart
Jul 26 2011, 04:19 AM
QUOTE
Select the third option if you know a lot about partitions and want to manually configure stuff yourself. If you know enough to select the third option, you don't need a tutorial telling you what to do.

The quoted material states that you should already "know what you're doing", but in the absence of *other* options, what choice does this leave someone like myself? Personally, I find myself in the "Goldilocks Zone" -- knowing just enough to keep me in trouble, but not enough to go it alone. BTW, JL -- thanks for the useful links. I especially LOVED "the psycho cat on an HP Mini with Ubuntu". rofl.gif

I must admit that the one option for choosing *where* to put certain items, i.e., it's boot partition, threw me. I know that my XP was "sda" (or "sda1") and saw the partition clearly represented. I did NOT know whether *where* meant literally "Beginning" or "End" of the disk (as I did NOT want something attaching itself to the very beginning of the disk necessarily) -- if it places itself at "sdb1" and the next at "sdb2" with the actual Ubuntu at "sdb3", I can live with that, no problem. If I can now assume this should be the case AND XP is again booting ahead of time, the following should be alright steps -- regardless of which version I'm installing:
  • Create a large enough extended partition, "/dev/sdb", in which (for now) Ubuntu (and later, Puppy) can reside. (I would also choose NOT to format this partition just yet.)
  • In the extended partition, I would create/format an Ext2 FS (or Ext4?) of 250MB in size (though I would think 100MB is sufficient) at mount point "/boot". This would become "/dev/sdb1".
  • Next, create/format the swap file of unknown size (at this moment in time) at mount point "/linux-swap" (I think) that would become "/dev/sdb2".
  • For the actual Ubuntu bit (if you'll let me call it that), the third and final volume to be created could be of 10GB in size at mount point "/" (or "/home" should be OK too) using FAT32.
  • Any remaining space within this extended partition would be saved for future Linux OS.
  • Complete the installation and reboot.
Sound like a plan? happy62.gif

The only downside that I can think of off the top of my head (such a dangerous place on top of SB's head) is whether or not to use FAT32 for Ubuntu for the one and only doubt being that you cannot add/subtract space using that format AFAIK. If I'm honest, I haven't learned ALL the other options open to me, but if not FAT32, I would probably choose Ext3 JFS or even Ext4 (Ubuntu's default) in case of any growth spurt. Otherwise, it seems FAT32 is as equal to Extn as I need or care it to be (especially if Windows can share folders/files using FAT32?). Would that be good for now? If I've left anything out, let me know or, more importantly, if I've stated something stupid that should really be "something else" rolleyes.gif, please advise, OK?

In the meantime, I'm going over the hiccup I must have caused for my poor XP. At the moment, it is still showing me the 7B error BSOD. I'm looking for the most updated copy of the MBR/PBR I saved (or is posted) to see about applying a fix. I'll let you know what happens and get back to you....

SBernheart

PS -- If I cannot find the final MBR/PBR backup, could I use the last one I posted for you, JL? From this I could then apply your modifications 1, 2 and 3 to get me back to where it should be and the one that worked/booted properly, yeah?
jaclaz
Jul 26 2011, 05:13 AM
You are still mixing things. ph34r.gif

/dev/sda is a DISK
/dev/sda1 is a partition (or volume) INSIDE that disk.
/dev/sdb is AGAIN, a DISK (ANOTHER DISK)
a partition or volume in it may be /dev/sdb1, dev/sdb2, etc.

If you don't get this clear, you are still doomed to failure, I'm afraid. sad.gif

As a matter of fact:

  1. Partitions (or volumes) were once (as they should be) conceived to be CARVED IN STONE. w00t.gif
  2. You DO NOT need/want to pass your time resizing partitions or volumes, they are intended to be created (using some common sense) ONCE and never be resized, EVER.
  3. The fact that there are (yes there are, even for FAT32 wink.gif) utilities that allow the resizing of partitions, DOES NOT mean that it is a good idea.


Also you should actually try to listen to given advice, you have already been told (twice, by two different members of the board) how the idea of installing Puppy Linux on the same partition as Ubuntu is:
  1. WRONG
  2. FLAWED
  3. TOO DIFFICULT for your current (non-existing or meaningless) experience with Linux OS

and you are still insisting on that idea? w00t.gif

Use some Common Sense! ranting2.gif

http://i141.photobucket.com/albums/r56/Tai...ommon-sense.jpg

Do things ONE AT THE TIME, FOLLOWING given advice, or, as Ed_P puts it:
QUOTE
Baby steps, baby steps.


About the botched XP install, do re-start from here:
http://www.911cd.net/forums//index.php?sho...4161&st=642
ONLY copy the MBR MBR_HardDisk1_update_mod3.dat (and NOT the PBR!)
Then, the disk signature should be the same you had at the time (which unless you changed it later should be the right one).
Try booting, if still 0x0000007b, then re-do:
http://www.911cd.net/forums//index.php?sho...4161&st=688

cheers.gif
jaclaz
SBernheart
Jul 30 2011, 08:33 AM
Sorry it took me so long to post this, but I think I've got things pretty much squared away. Here's a preliminary look at what I've done today.
  • Always when booting ANYthing, the very first screen I get is HP's splash screen and the opportunity to:
    • Enter BIOS
    • Enter Boot Menu
    • Enter Diagnostics
    • Enter Recovery Console
    That said and unless specifically needed, I will NOT be including this screen in notes to follow -- assumption will ALWAYS be that this 1st screen IS the HP splash screen and always first screen I see, OK?
  • Immediately following the installation of Ubuntu, I rebooted the new disk as instructed by installer. I am presented with a new GRUB screen with the following choices:
    • Ubuntu, with Linux 2.6.32-33-generic-pae
    • Ubuntu, with Linux 2.6.32-33-generic-pae (recovery mode)
    • Memory test (memtest86+)
    • Memory test (memtest86+, serial console 115200)
    • Windows 7 (loader) (on /dev/sda1)
    • Windows Vista (loader) (on /dev/sda3)
    • Windows NT/2000/XP (loader) (on /dev/sdb1)
    I only have seconds (7?) in which to choose "something else" wink.gif , but Ubuntu is default OS so (for now) I allow it to boot and check that installation has been completed and it IS working OK.
  • I reboot, this time choosing "Win 7" from GRUB list and all seems fine.
  • I disconnect new disk and still running Win 7 doesn't have a problem with THAT and all seems fine.
  • Reboot Win 7 and all seems OK as well (withOUT new disk, I mean, trying to boot it).
  • Attached new disk and rebooted and normal Win 7 "boot.ini" choices were presented. Chose "Win 7" and all seems fine.
  • Rebooted again, this time entering BIOS to place new disk 1st in the "HDD Group" over the internal disk (when it's connected, of course, just as "CD-ROM Group" is 1st in ALL "groups", but only when there's a CD present before reboot).
  • Without entering Boot Menu, new disk presented first with choices listed above (shown in attached photo too). Chose "Win 7" and all seems fine.
  • With new disk still attached, rebooted (assumption that there was no need in checking BIOS for boot order OR Boot Menu to choose new disk) and was again presented with new GRUB screen. Chose "Win 7" and all seems fine.
  • Disconnected new disk and rebooted Win 7 and got a BSOD "C2" error. Also stated on this screen "BAD_POOL_CALLER" and "Dumping physical memory to disk: 100" and was forced to power off....
  • Powered back up and boot.ini choices were presented and I chose "Win 7", but a "Windows Error Recovery" screen came up. I chose to "Start Windows Normally" and all seemed fine EXCEPT, a popup appeared with the following reminder about BSOD:
CODE
Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    c2
  BCP1:    0000000000000007
  BCP2:    000000000000109B
  BCP3:    0000000000040004
  BCP4:    FFFFFA8006D40090
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\073011-14289-01.dmp
  C:\Users\SBernheart\AppData\Local\Temp\WER-28236-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
  • I saved this for you to peruse, but just to be certain *all* really WAS fine, I rebooted Win 7 and, yes, it still appears OK.
  • Reconnected new disk to now test IT's OS. I entered BIOS first and was surprised, actually, to see new disk still 1st in "HDD Group" priorities (though the "CD-ROM Group" is always 1st IF CD is in drive). This means, when new disk is connected, I won't have to enter Boot Menu every time I want to boot XP, Ubuntu or what have you, via new disk.
  • Exited BIOS and allowed new disk it's priority. At GRUB screen (the photo IS showing a new (or different ) GRUB, right?), Ubuntu (for now) is listed first (by default) and I allow Ubuntu to boot -- everything's looking OK AFAIK only it already has 2.75GB worth of updates it wants to install. For now, I ignore this.
    NOTE -- Included in the Ubuntu folders is one named "Windows" which was created as an afterthought as a 5GB FAT32 partition added after Ubuntu partitions were created. The installer didn't seem to appreciate my attempts at creating the Ubuntu partition as FAT32 stating, once again, "No root file system is defined. Correct from partitioning menu", so this was my *compromise* (for a lack of a better term). I can expand on this later. For now, my only concern is keeping the very "precious XP" as well as my Hub's Win 7 BOTH operational.
  • Rebooted to finally check on XP and from GRUB menu (yes, Ubuntu must have attached ALL disk choices here as seen in pic), I *quickly* chose "XP" and after initial XP splash screen, it continued to the next screen (blue screen with another XP logo on it). It's the screen you'd see before the logon screen (if you had one) and before you see your Desktop, but it doesn't go past this screen and instead, it appears to *hang* there. Had to power off....
  • Powered on with new disk connected still and chose "Win 7" at GRUB and booted without incident (and without errors).
  • Disconnected new disk (with Win 7 running) and rebooted "Win 7", again, without incident.
  • Confident now that Win 7 is OK and that when new disk is connected before reboot, the new disk WILL present GRUB first (and I *can* live with that) so I can choose which OS to boot -- Win 7, XP, Ubuntu, etc.
I wanted to get at least this much posted before retiring (for now), but I think I know why XP is "hanging" and I'll try to post ASAP to let you know what I found regarding this. Hopefully, with just a few more "tweaks", all should be good-to-go as far as XP and Ubuntu are concerned, OK? Till then....

SBernheart sleeping.gif

PS -- If screen pic is too small to read, you can check out a larger, clearer version HERE instead.
jaclaz
Jul 30 2011, 09:37 AM
Sarah, really, you should use LESS words and provide more DATA.

You don't mention WHAT/HOW/WHERE you installed UBUNTU, from what you write it seems like you installed it EXACTLY in the way that it was suggested you NOT to choose, i.e. installing GRUB2 to the MBR.

There are NO (and this is the nTH time I tell you this ranting2.gif ) "Win 7 BOOT.INI choices", there is actually NO file called BOOT.INI (or there SHOULD NOT be) on your internal disk, nor a NTLDR (which reads BOOT.INI and choices in it).

Sure, win7 is OK (as it was before, after you had botched it and I managed to get you fix it).
Sure, windows XP on external disk is KO (as it was before, after you had botched it).

The original suggestions were:
  1. DO NOT install GRUB 2 to the MBR <-ignored
  2. DO NOT install Ubuntu until the XP is fixed/revived <-ignored
    And more generally:
  3. Ask for help BEFORE doing things, instead of asking how to fix the mistakes you make <-ignored


Three out of three, not that bad as a score. whistling.gif, I have seen brick walls frusty.gif score worse at this game of listening to advice. w00t.gif

BTW, and just for the record, there is nothing actually "wrong" to have GRUB2 as main bootmanager, it only makes things unneededly more complex for you (and for me, and for your poor husband, that, should you go on experimenting WITHOUT a plan or without knowing what you are doing, will need a re-install of 7).

The tools you are playing with are a modern version of the proverbial box of matches in the hands of kids ninja.gif , and sooner or later someone will got burned.


cheers.gif
Wonko
Ed_P
Jul 30 2011, 10:55 AM
QUOTE (SBernheart @ Jul 30 2011, 09:33 AM) *
[*]Disconnected new disk (with Win 7 running) and rebooted "Win 7", again, without incident.

You don't mention using the Windows Safely Remove Hardware option when removing the new disk. Hopefully you use that.
SBernheart
Jul 31 2011, 05:30 AM
@Ed_P
Yes, of course. I always use the "Safely Remove Hardware" so from now on, this can be assumed. TY wink.gif

@FM_81
I get it even more now -- I think what you guys were trying to tell me (though I misunderstood previously) is that Ubuntu should occupy it's own EXTENDED PARTITION and within IT, I can have "x" number of logical drives. Then, for Puppy, it too should occupy it's own EXTENDED PARTITION and within IT, I can have "x" number of logical drives. So how many extended partitions can I have along side one Primary partition? Just asking....

@jaclaz
OK, I give up. I tried to "fix" things on my own, but apparently, I'm worse off than where I started "fixing" in the first place. All I was stating is that after applying the fixes you told me to apply, I went back to Ubuntu and started hunting for this supposed "it'll ask for approval" bit concerning the MBR/bootloader, but it wasn't present on my install CD (at least, not like the pic you posted where it seemed *obvious*). What WAS there (I finally found) was a button labeled "Advanced" and when clicked, took me to something resembling the Ubuntu pic your Post #40 referred to. From a drop-down list, I saw everywhere there could have been for the boot loader to install itself. First I chose the Ubuntu partition, but it wouldn't allow that choice. Next, I tried "/dev/sdb" thinking that it was better than it installing again on my Win 7 disk. I had kept my head during all of this and didn't panic. I remembered when you got Win 7 back up for the Hub what the error message was:

QUOTE
error: no such device: d9467894-f8e0-474c-8204-46514740072d
grub rescue> (blinking cursor)

I recognized that message and knew immediately that it had installed itself on "/dev/sda" again (this was before I found the "Advanced" button). Once I saw that error, I applied the appropriate MBR fixes you already mapped out, then went back to Ubuntu and changed the boot loader to install on "/dev/sdb" instead. It was the lesser of two evils, if you ask me, but then, no one ever does! blush.gif

QUOTE (jaclaz @ Jul 30 2011, 10:37 AM) *
There are NO (and this is the nTH time I tell you this ranting2.gif ) "Win 7 BOOT.INI choices", there is actually NO file called BOOT.INI (or there SHOULD NOT be) on your internal disk, nor a NTLDR (which reads BOOT.INI and choices in it).

I'm just so used to you telling me "up to "boot.ini" choices..." that the statement is permanently engraved in my memory. Call it as you like, to me I simply meant "to the screen where I can choose between "GRUB4DOS" or "Win 7" and I always choose the latter...." and nothing more.

As for XP, I went to your Post #42 and to the page pointed towards in Post #690 and began with the following steps:
  • queryUSB.cmd U:\windows\system32
  • set_registry_usb_boot.cmd U:\Windows
  • queryUSB.cmd U:\windows\system32
    (The first three are in first codebox below.)
  • usb_xp_init.cmd U:\WINDOWS\system32
    (This one is in the second codebox.)
  • C:\Tools\UsbBootWatcher>usb_xp_init.cmd U:\WINDOWS\system32 <<< did this one again to the path stated as opposed to "C:\Tools"
    (The final one is in the third codebox. Hopefully, there's no further confusion.)
Where I now find myself stuck on is the instruction to "copy modified NTDETECT.COM to USB root folder". I found the code alright and the other page it points to as well, but I wasn't sure about this bit, "Please remove all CR/LFs", so if anything "extra" is in the code I copied (yes, BOTH posts of code) then I don't know. I was able to paste it to a blank window and yes, remembered to change the data format from "text" to "hex". If you trust that this was done correctly, I'll delete the "NTDETECT.COM" I already have on XP (or copy it somewhere else first) and add the new, *modified* "NTDETECT.COM" to XP.

This is where I am -- short of having you look over the following data from commands listed above, the next step is the changing of "ntdetect.com". unsure.gif

CODE
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>CD C:\

C:\>CD C:\Tools

C:\Tools>queryUSB.cmd U:\windows\system32
The operation completed successfully.

ControlSet "ControlSet001" used.

usbehci Start REG_DWORD 0x0
usbehci Group REG_SZ System Reserved
usbuhci Start REG_DWORD 0x0
usbuhci Group REG_SZ System Reserved
usbohci Start REG_DWORD 0x0
usbohci Group REG_SZ System Reserved
usbhub Start REG_DWORD 0x3
usbhub Group REG_SZ Base
usbstor Start REG_DWORD 0x3
usbstor Group REG_SZ System Bus Extender
intelppm Start REG_DWORD 0x3
intelppm Group REG_SZ Extended Base

HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet001\Control\CrashControl
AutoReboot REG_DWORD 0x0


C:\Tools>set_registry_usb_boot.cmd U:\Windows
prepare offline windows registry, set USB boot drivers

1 file(s) copied.
The operation completed successfully.

ControlSet "ControlSet002" used.


set PCI#CC_0C0300 usbuhci
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.


set PCI#CC_0C0310 usbohci
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.


set PCI#CC_0C0320 usbehci
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.


set USB#CLASS_08 usbstor
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.


set USB#CLASS_09 usbhub
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.


set USB#ROOT_HUB usbhub
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.


set USB#ROOT_HUB20 usbhub
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
loaded_SYSTEM\ControlSet002\Services\usbehci : delete Perm. ACE 0 nt authority\s
ystem
loaded_SYSTEM\ControlSet002\Services\usbehci : new ace for nt authority\system
HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbehci : 2 change(s)


Elapsed Time: 00 00:00:00
Done: 1, Modified 1, Failed 0, Syntax errors 0
Last Done : HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbehci
loaded_SYSTEM\ControlSet002\Services\usbohci : delete Perm. ACE 0 nt authority\s
ystem
loaded_SYSTEM\ControlSet002\Services\usbohci : new ace for nt authority\system
HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbohci : 2 change(s)


Elapsed Time: 00 00:00:00
Done: 1, Modified 1, Failed 0, Syntax errors 0
Last Done : HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbohci
loaded_SYSTEM\ControlSet002\Services\usbuhci : delete Perm. ACE 0 nt authority\s
ystem
loaded_SYSTEM\ControlSet002\Services\usbuhci : new ace for nt authority\system
HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbuhci : 2 change(s)


Elapsed Time: 00 00:00:00
Done: 1, Modified 1, Failed 0, Syntax errors 0
Last Done : HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbuhci
loaded_SYSTEM\ControlSet002\Services\usbhub : delete Perm. ACE 0 nt authority\sy
stem
loaded_SYSTEM\ControlSet002\Services\usbhub : new ace for nt authority\system
HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbhub : 2 change(s)


Elapsed Time: 00 00:00:00
Done: 1, Modified 1, Failed 0, Syntax errors 0
Last Done : HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbhub
loaded_SYSTEM\ControlSet002\Services\usbstor : delete Perm. ACE 0 nt authority\s
ystem
loaded_SYSTEM\ControlSet002\Services\usbstor : new ace for nt authority\system
HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbstor : 2 change(s)


Elapsed Time: 00 00:00:00
Done: 1, Modified 1, Failed 0, Syntax errors 0
Last Done : HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet002\Services\usbstor
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.

C:\Tools>queryUSB.cmd U:\windows\system32
The operation completed successfully.

ControlSet "ControlSet001" used.

usbehci Start REG_DWORD 0x0
usbehci Group REG_SZ System Reserved
usbuhci Start REG_DWORD 0x0
usbuhci Group REG_SZ System Reserved
usbohci Start REG_DWORD 0x0
usbohci Group REG_SZ System Reserved
usbhub Start REG_DWORD 0x3
usbhub Group REG_SZ Base
usbstor Start REG_DWORD 0x3
usbstor Group REG_SZ System Bus Extender
intelppm Start REG_DWORD 0x3
intelppm Group REG_SZ Extended Base

HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet001\Control\CrashControl
AutoReboot REG_DWORD 0x0


C:\Tools>

CODE
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>CD C:\

C:\>CD C:\Tools

C:\Tools>usb_xp_init.cmd U:\WINDOWS\system32
prepare offline XP files, set USB boot drivers
running windows XP or Windows 7

1 file(s) copied.
The operation completed successfully.
sp driver cab: U:\WINDOWS\Driver Cache\I386\sp3.cab
x86\UsbBootWatcher.conf
x86\UsbBootWatcher.exe
2 file(s) copied.

C:\Tools>rem detect Clone control CurrentControlSet

C:\Tools>for /F "tokens=3" %a in ('reg.exe query "HKLM\loaded_SYSTEM\Select" /v
"Default"') do set /a ControlSet=%a

C:\Tools>set /a ControlSet=0x2

C:\Tools>set ControlSet=000002

C:\Tools>set ControlSetNNN=ControlSet002

C:\Tools>echo. & echo ControlSet "ControlSet002" used.

ControlSet "ControlSet002" used.

C:\Tools>set CriticalDeviceDatabase=HKLM\loaded_SYSTEM\ControlSet002\Control\Cri
ticalDeviceDatabase

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0C0300" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000
}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0C0300" /f /v "Service" /d "usbuhci"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0C0310" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000
}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0C0310" /f /v "Service" /d "usbohci"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0C0320" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000
}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0C0320" /f /v "Service" /d "usbehci"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#CLASS_08" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}
"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#CLASS_08" /f /v "Service" /d "usbstor"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#CLASS_09" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}
"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#CLASS_09" /f /v "Service" /d "usbhub"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#ROOT_HUB" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-444553540000}
"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#ROOT_HUB" /f /v "Service" /d "usbhub"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#ROOT_HUB20" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8056-44455354000
0}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\USB#ROOT_HUB20" /f /v "Service" /d "usbhub"
The operation completed successfully.

C:\Tools>rem add IDE and ATAPI

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0101" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-08002BE10318}"

The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#CC_0101" /f /v "Service" /d "pciide"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#VEN_8086&CC_0101" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-08002
BE10318}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\PCI#VEN_8086&CC_0101" /f /v "Service" /d "intelide"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\*PNP0600" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-08002BE10318}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\*PNP0600" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\Primary_IDE_Channel" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-08002B
E10318}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\Primary_IDE_Channel" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\Secondary_IDE_Channel" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-0800
2BE10318}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\Secondary_IDE_Channel" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\*azt0502" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-08002BE10318}"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\CriticalDeviceDat
abase\*azt0502" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools>set Services=HKLM\loaded_SYSTEM\ControlSet002\Services

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbohci" /f /v "
Group" /d "Boot Bus Extender"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbohci" /f /t R
EG_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbohci" /f /t R
EG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbohci" /f /t R
EG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbohci" /f /t R
EG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbuhci" /f /v "
Group" /d "Boot Bus Extender"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbuhci" /f /t R
EG_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbuhci" /f /t R
EG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbuhci" /f /t R
EG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbuhci" /f /t R
EG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbehci" /f /v "
Group" /d "Boot Bus Extender"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbehci" /f /t R
EG_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbehci" /f /t R
EG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbehci" /f /t R
EG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbehci" /f /t R
EG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbhub" /f /v "G
roup" /d "System Bus Extender"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbhub" /f /t RE
G_DWORD /v "Tag" /d 2
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbhub" /f /t RE
G_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbhub" /f /t RE
G_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbhub" /f /t RE
G_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbstor" /f /v "
Group" /d "System Bus Extender"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbstor" /f /t R
EG_DWORD /v "Tag" /d 7
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbstor" /f /t R
EG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbstor" /f /t R
EG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\usbstor" /f /t R
EG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\Setup\AllowStart\UsbBootWatcher" /f
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\UsbBootWatcher"
/f /v "ImagePath" /d "UsbBootWatcher.exe"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\UsbBootWatcher"
/f /v "ObjectName" /d "LocalSystem"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\UsbBootWatcher"
/f /v "DisplayName" /d "Usb Boot Watcher Service"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\UsbBootWatcher"
/f /t REG_DWORD /v "ErrorControl" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\UsbBootWatcher"
/f /t REG_DWORD /v "Start" /d 2
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\UsbBootWatcher"
/f /t REG_DWORD /v "Type" /d 0x10
The operation completed successfully.

C:\Tools>rem add IDE and ATAPI

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\PCIIde" /f /v "G
roup" /d "System Bus Extender"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\PCIIde" /f /t RE
G_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\PCIIde" /f /t RE
G_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\PCIIde" /f /t RE
G_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\PCIIde" /f /t RE
G_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\IntelIde" /f /v
"Group" /d "System Bus Extender"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\IntelIde" /f /t
REG_DWORD /v "Tag" /d 4
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\IntelIde" /f /t
REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\IntelIde" /f /t
REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\IntelIde" /f /t
REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\atapi" /f /v "Gr
oup" /d "SCSI miniport"
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\atapi" /f /t REG
_DWORD /v "Tag" /d 0x19
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\atapi" /f /t REG
_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\atapi" /f /t REG
_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\atapi" /f /t REG
_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools>rem internal debug

C:\Tools>for %i in (*.reg) do reg.exe import "%i"

C:\Tools>reg.exe unload HKLM\loaded_SYSTEM
The operation completed successfully.

C:\Tools>goto :eof

C:\Tools>popd

C:\Tools>goto :eof

C:\Tools>

CODE
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>CD C:\

C:\>CD C:\Tools\UsbBootWatcher

C:\Tools\UsbBootWatcher>usb_xp_init.cmd U:\WINDOWS\system32
prepare offline XP files, set USB boot drivers
running windows XP or Windows 7

1 file(s) copied.
The operation completed successfully.
sp driver cab: U:\WINDOWS\Driver Cache\I386\sp3.cab
x86\UsbBootWatcher.conf
x86\UsbBootWatcher.exe
2 file(s) copied.

C:\Tools\UsbBootWatcher>rem detect Clone control CurrentControlSet

C:\Tools\UsbBootWatcher>for /F "tokens=3" %a in ('reg.exe query "HKLM\loaded_SYS
TEM\Select" /v "Default"') do set /a ControlSet=%a

C:\Tools\UsbBootWatcher>set /a ControlSet=0x2

C:\Tools\UsbBootWatcher>set ControlSet=000002

C:\Tools\UsbBootWatcher>set ControlSetNNN=ControlSet002

C:\Tools\UsbBootWatcher>echo. & echo ControlSet "ControlSet002" used.

ControlSet "ControlSet002" used.

C:\Tools\UsbBootWatcher>set CriticalDeviceDatabase=HKLM\loaded_SYSTEM\ControlSet
002\Control\CriticalDeviceDatabase

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0C0300" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-80
56-444553540000}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0C0300" /f /v "Service" /d "usbuhci"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0C0310" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-80
56-444553540000}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0C0310" /f /v "Service" /d "usbohci"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0C0320" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-80
56-444553540000}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0C0320" /f /v "Service" /d "usbehci"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#CLASS_08" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-805
6-444553540000}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#CLASS_08" /f /v "Service" /d "usbstor"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#CLASS_09" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-805
6-444553540000}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#CLASS_09" /f /v "Service" /d "usbhub"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#ROOT_HUB" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-805
6-444553540000}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#ROOT_HUB" /f /v "Service" /d "usbhub"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#ROOT_HUB20" /f /v "ClassGUID" /d "{36FC9E60-C465-11CF-8
056-444553540000}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\USB#ROOT_HUB20" /f /v "Service" /d "usbhub"
The operation completed successfully.

C:\Tools\UsbBootWatcher>rem add IDE and ATAPI

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0101" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1
-08002BE10318}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#CC_0101" /f /v "Service" /d "pciide"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#VEN_8086&CC_0101" /f /v "ClassGUID" /d "{4D36E96A-E325-
11CE-BFC1-08002BE10318}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\PCI#VEN_8086&CC_0101" /f /v "Service" /d "intelide"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\*PNP0600" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-08
002BE10318}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\*PNP0600" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\Primary_IDE_Channel" /f /v "ClassGUID" /d "{4D36E96A-E325-1
1CE-BFC1-08002BE10318}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\Primary_IDE_Channel" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\Secondary_IDE_Channel" /f /v "ClassGUID" /d "{4D36E96A-E325
-11CE-BFC1-08002BE10318}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\Secondary_IDE_Channel" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\*azt0502" /f /v "ClassGUID" /d "{4D36E96A-E325-11CE-BFC1-08
002BE10318}"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Control\Cr
iticalDeviceDatabase\*azt0502" /f /v "Service" /d "atapi"
The operation completed successfully.

C:\Tools\UsbBootWatcher>set Services=HKLM\loaded_SYSTEM\ControlSet002\Services

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbohci" /f /v "Group" /d "Boot Bus Extender"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbohci" /f /t REG_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbohci" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbohci" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbohci" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbuhci" /f /v "Group" /d "Boot Bus Extender"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbuhci" /f /t REG_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbuhci" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbuhci" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbuhci" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbehci" /f /v "Group" /d "Boot Bus Extender"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbehci" /f /t REG_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbehci" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbehci" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbehci" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbhub" /f /v "Group" /d "System Bus Extender"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbhub" /f /t REG_DWORD /v "Tag" /d 2
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbhub" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbhub" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbhub" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbstor" /f /v "Group" /d "System Bus Extender"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbstor" /f /t REG_DWORD /v "Tag" /d 7
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbstor" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbstor" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\u
sbstor" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\Setup\AllowStart\UsbBoot
Watcher" /f
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\U
sbBootWatcher" /f /v "ImagePath" /d "UsbBootWatcher.exe"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\U
sbBootWatcher" /f /v "ObjectName" /d "LocalSystem"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\U
sbBootWatcher" /f /v "DisplayName" /d "Usb Boot Watcher Service"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\U
sbBootWatcher" /f /t REG_DWORD /v "ErrorControl" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\U
sbBootWatcher" /f /t REG_DWORD /v "Start" /d 2
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\U
sbBootWatcher" /f /t REG_DWORD /v "Type" /d 0x10
The operation completed successfully.

C:\Tools\UsbBootWatcher>rem add IDE and ATAPI

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\P
CIIde" /f /v "Group" /d "System Bus Extender"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\P
CIIde" /f /t REG_DWORD /v "Tag" /d 3
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\P
CIIde" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\P
CIIde" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\P
CIIde" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\I
ntelIde" /f /v "Group" /d "System Bus Extender"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\I
ntelIde" /f /t REG_DWORD /v "Tag" /d 4
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\I
ntelIde" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\I
ntelIde" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\I
ntelIde" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\a
tapi" /f /v "Group" /d "SCSI miniport"
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\a
tapi" /f /t REG_DWORD /v "Tag" /d 0x19
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\a
tapi" /f /t REG_DWORD /v "ErrorControl" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\a
tapi" /f /t REG_DWORD /v "Start" /d 0
The operation completed successfully.

C:\Tools\UsbBootWatcher>reg.exe add "HKLM\loaded_SYSTEM\ControlSet002\Services\a
tapi" /f /t REG_DWORD /v "Type" /d 1
The operation completed successfully.

C:\Tools\UsbBootWatcher>rem internal debug

C:\Tools\UsbBootWatcher>for %i in (*.reg) do reg.exe import "%i"

C:\Tools\UsbBootWatcher>reg.exe unload HKLM\loaded_SYSTEM
The operation completed successfully.

C:\Tools\UsbBootWatcher>goto :eof

C:\Tools\UsbBootWatcher>popd

C:\Tools\UsbBootWatcher>goto :eof

C:\Tools\UsbBootWatcher>

Personally, I think these should be looking at "ControlSet001", but according to the data collected, only the "queryUSB.cmd" is right. The rest state, "ControlSet "ControlSet002" used". Maybe this is the only problem with the commands, I couldn't say, but I'm sorry I didn't post the stuff about XP before the post with "all the words and very little data". My bad....

SBernheart rolleyes.gif
cdob
Jul 31 2011, 09:18 AM
QUOTE (SBernheart @ Jul 31 2011, 10:30 AM) *
Personally, I think these should be looking at "ControlSet001",

Why do you expect ControlSet001 ?

QUOTE
only the "queryUSB.cmd" is right.
Sorry, actually "queryUSB.cmd" is broken.

Edit file "queryUSB.cmd", replace twice "HKLM\SYSTEM\Select" with "HKLM\loaded_SYSTEM\Select"

CODE
reg.exe query "HKLM\loaded_SYSTEM\Select" /v "Default" >nul 2>&1 && (
  for /f "skip=2 tokens=3" %%a in ('reg.exe query "HKLM\loaded_SYSTEM\Select" /v "Default"') do set /a ControlSet=%%a
jaclaz
Jul 31 2011, 09:47 AM
QUOTE (SBernheart @ Jul 31 2011, 12:30 PM) *
I get it even more now -- I think what you guys were trying to tell me (though I misunderstood previously) is that Ubuntu should occupy it's own EXTENDED PARTITION and within IT, I can have "x" number of logical drives. Then, for Puppy, it too should occupy it's own EXTENDED PARTITION and within IT, I can have "x" number of logical drives. So how many extended partitions can I have along side one Primary partition? Just asking....

Only 1 (ONE). frusty.gif
You can have a MAX number of 4 primary partitions or 3 Primary partitions + 1 extended one.
You CANNOT have more than one Extended partition.
You can have as many logical voumes inside the 1 and ONLY Extended partition.
One (or more) of these logical volumes can be "dedicated" to Linux Ubuntu, one to Puppy Linux, etc.
Installing TWO Linuxes on the SAME logical volume is STRONGLY NOT advised.

QUOTE (SBernheart @ Jul 31 2011, 12:30 PM) *
I'm just so used to you telling me "up to "boot.ini" choices..." that the statement is permanently engraved in my memory. Call it as you like, to me I simply meant "to the screen where I can choose between "GRUB4DOS" or "Win 7" and I always choose the latter...." and nothing more.

Look, it is not so difficult, if you have a NTLDR and BOOT.INI you get to BOOT.INI choices.
If you have a BOOTMGR and a BCD you get to BCD chioices.
This field as you should have learned by now revolves mostly about EXACTness of both reports and instructions.
EVERY single time you call a rose by any other name, you make other people either:
  1. FAIL to understand what you are saying w00t.gif
    OR:
  2. do an exceptional effort to GUESS what you are trying to say dubbio.gif unsure.gif

BOTH the above lead to a higher probability of getting back either incomplete/partial or plainly wrong advice/help.
So ultimately EVERY single time you use improperly a term or name something with an improper name you make things for yourself more difficult or longer/more probelmatic to solve.
Do yourself a favour, start calling things with their names. smile.gif


About the Registry:
Normally there are two ControlSet's in Windows NT/2K/XP.
The CurrentControlSet in use is selected by the contents of the Select key:
HKEY_LOCAL_MACHINE\SYSTEM\Select
Under certain circumstances (Registry corruption, boot failure, etc.) the Select key can be flipped to point to the "alternate" ControlSet (i.e. ControlSet002)
In some other circumstances a "brand new" ControlSet may be created, like ControlSet003, ControlSet004, etc., and the Select key value may change to make in use one of these latter.
Usually when there is a problem or a switch of the ControlSet, when booting you get a prompt for "Last Known Good Configuration" or something like it.

cheers.gif
jaclaz
SBernheart
Jul 31 2011, 04:02 PM
QUOTE (cdob @ Jul 31 2011, 10:18 AM) *
Why do you expect ControlSet001 ?

Only because the output of stated data previously used "ControlSet001" where here, everything stated used "ControlSet002" with the only exception of the "queryUSB.cmd" as IT used "ControlSet001". Shouldn't they ALL be working within the same set? Output appears the same to me.

CODE
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>CD C:\

C:\>CD C:\Tools

C:\Tools>queryUSB.cmd U:\windows\system32
The operation completed successfully.

ControlSet "ControlSet001" used.

usbehci Start REG_DWORD 0x0
usbehci Group REG_SZ System Reserved
usbuhci Start REG_DWORD 0x0
usbuhci Group REG_SZ System Reserved
usbohci Start REG_DWORD 0x0
usbohci Group REG_SZ System Reserved
usbhub Start REG_DWORD 0x3
usbhub Group REG_SZ Base
usbstor Start REG_DWORD 0x3
usbstor Group REG_SZ System Bus Extender
intelppm Start REG_DWORD 0x3
intelppm Group REG_SZ Extended Base

HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet001\Control\CrashControl
AutoReboot REG_DWORD 0x0


C:\Tools>

Command used as follows:

CODE
@echo off

rem Usage: queryUSB.cmd U:\windows\system32
rem
rem Environment: Windows 7

set XP_system32=%1

reg.exe load HKLM\loaded_SYSTEM "%XP_system32%\config\system"

rem detect CurrentControlSet clone
set ControlSet=001
reg.exe query "HKLM\loaded_SYSTEM\Select" /v "Default" >nul 2>&1 && (
  for /f "skip=2 tokens=3" %%a in ('reg.exe query "HKLM\loaded_SYSTEM\Select" /v "Default"') do set /a ControlSet=%%a
  set ControlSet=000%ControlSet%
)
set ControlSetNNN=ControlSet%ControlSet:~-3%
echo. &echo ControlSet "%ControlSetNNN%" used.

echo.
for %%a in (usbehci usbuhci usbohci usbhub usbstor intelppm) do for %%b in (Start Group) do (
reg.exe query HKLM\loaded_SYSTEM\%ControlSetNNN%\Services\%%a /V %%b >nul 2>&1 && (
   for /F "tokens=* skip=2" %%c in ('reg.exe query HKLM\loaded_SYSTEM\%ControlSetNNN%\Services\%%a /V %%b') do echo %%a %%c)
)

reg.exe query HKLM\loaded_SYSTEM\%ControlSetNNN%\Control\CrashControl /V AutoReboot

reg.exe unload HKLM\loaded_SYSTEM >nul 2>&1

SBernheart
SBernheart
Aug 1 2011, 07:07 AM
QUOTE (jaclaz @ Jul 24 2011, 02:16 PM) *
How the heck did you manage to have "BOOT.INI" choices on the Windows 7 disk? w00t.gif
You should have at the most "BCD" choices, and one of them should be Windows 7.

I believe this IS the first I recall your using this term "BCD", but I could be wrong. wink.gif I didn't know what you meant by this then, but I do now.

QUOTE (jaclaz @ Jul 30 2011, 10:37 AM) *
There are NO (and this is the nTH time I tell you this ranting2.gif ) "Win 7 BOOT.INI choices", there is actually NO file called BOOT.INI (or there SHOULD NOT be) on your internal disk, nor a NTLDR (which reads BOOT.INI and choices in it).

This, then, would be TWICE that "BCD" was implied or that Win 7 doesn't actually have "boot.ini choices". Maybe we could agree on simply "boot choices"? biggrin.gif

QUOTE (jaclaz @ Jul 31 2011, 10:47 AM) *
You CANNOT have more than one Extended partition.
You can have as many logical volumes inside the 1 and ONLY Extended partition.
One (or more) of these logical volumes can be "dedicated" to Linux Ubuntu, one to Puppy Linux, etc.
Installing TWO Linuxes on the SAME logical volume is STRONGLY NOT advised.

The difference between the screen pic of Disk Mgmt in Post #12 and the one I am posting here show clearly, primary partitions vs. logical ones AND neither of which having anything to do with XP (obviously XP is there in first, primary partition, but I'm referring to the Ubuntu install or Linux, in general).
This, as you state, IS exactly what I *thought* I understood from your previous "lessons", but then confusing my *extended* with my *Ext2/Ext3/Ext4* partition vs. file systems got me ALL tangled up. Just when I thought I understood my mistake and went back to my original understanding, you guys mixed me up all over again by pounding it into my head that I was NOT allowed to install Ubuntu AND Puppy on/in the same place. I don't know why anyone would want to install, say, Puppy, on the same "logical" drive, so I cannot say, but *I* certainly never proposed doing so. As if things weren't screwy enough, huh? So NOW noted:
  • XP -- 1st PRIMARY partition on new disk
  • ONE extended PARTITION created for Linux on new disk
  • Ubuntu -- 7th LOGICAL volume (in the ONE extended partition) on new disk (with it's added logical volumes 5th and 6th, i.e., "/boot" and "/linux-swap")
  • FUTURE Puppy -- nth LOGICAL volume (in the ONE extended partition) on new disk (with it's possible added logical volumes yet to be named)
OK -- I don't know why it started logical volume numbering at "5", but there are no other logical volumes (created by ME) other than what I just mapped out.

QUOTE (jaclaz @ Jul 31 2011, 10:47 AM) *
If you have a BOOTMGR and a BCD you get to BCD choices.
This field as you should have learned by now revolves mostly about EXACTness of both reports and instructions.

Speaking of "BCD" (now that I recall where I first heard of this) I had originally thought about EasyBCD for use with XP and Ubuntu (well before coming to this forum) until further reading lead me HERE and to the following about my version:

QUOTE
Due to a bug in Ubuntu 10.04+, the current steps are rather more convoluted than they used to be in previous versions, requiring the user to first give control of the MBR to GRUB2, and then use EasyBCD to put the Windows bootloader back in control. We have brought this issue to the attention of the Ubuntu developers, and hope to have it resolved soon.

If this can "clean up" the issue about letting Linux installer have it's way with XP's MBR, then maybe this is a different way to go? No, I am NOT trying to make things harder OR trying to cut corners , as you say, but rather just trying to get the job done with the best method available and/or with the best outcome.

QUOTE (jaclaz @ Jul 23 2011, 07:04 AM) *
....if the Ubuntu installer asks you:
  1. if it should install bootloader to the MBR, say NO. <<<*IT* never *asked* anything.
  2. if it should NOT install ANY bootloader say YES. <<<"Ditto" to #1.
  3. INSTEAD of the latter if it should install to the PBR or volume or bootsector or partition, say YES, it is good as well.

As stated in my "use LESS words and provide more DATA" Post #43, I ended up using the "lesser of two evils" by allowing the boot loader to install with XP on NEW DISK ONLY.

QUOTE (jaclaz @ Jul 30 2011, 10:37 AM) *
You don't mention WHAT/HOW/WHERE you installed UBUNTU, from what you write it seems like you installed it EXACTLY in the way that it was suggested you NOT to choose, i.e. installing GRUB2 to the MBR.

I can now expand on this topic and try to tell WHAT/HOW/WHERE I installed Ubuntu (although a peek at the screen pic may give you a hint happy62.gif). According to my notes, here's what I did as *exactly* as is "SB possible":
  • Loaded Ubuntu installer CD
  • Rebooted and CD executed "temporary" Ubuntu
  • Chose to "install" Ubuntu

    1. Language
    2. Time Zone
    3. Keyboard Layout
    4. WHAT/HOW/WHERE to install? Manually...
    5. Create extended partition/volumes
      • 1st ext2 volume -- 100MB "/boot"
      • 2nd swap volume -- 2000MB "linux-swap"
      • 3rd ext3 volume -- 15000MB "/" (or "/root")
      • 4th FAT32 volume -- 5000MB "/windows"
    6. Name, rank and serial number
    7. Review of data before actual installation begins <<<Location of an "Advanced" button, I clicked this and now "Install boot loader" ticked off with a drop-down list
    8. Installation begins
  • The final review is where I FINALLY found a reference to "boot loader" -- it was an "Advanced" button on the review screen. I tried to choose the Ubuntu volume(s), but IT wouldn't allow anything EXCEPT "/dev/sda" OR "/dev/sdb", so I chose "the lesser of two evils" and chose "/dev/sdb" even though I realized it would install on XP's MBR (or so I assumed), but I did NOT want it on Win 7's, so....see attached pic.
  • Hit "Install Now" and there you have it. Checked all the possible boot combinations (with new disk connected; without new disk connected; thus my "excess-LESS data" post) and was all right with everything EXCEPT not getting past that particular XP splash screen.

QUOTE (SBernheart @ Jul 30 2011, 09:33 AM) *
NOTE -- Included in the Ubuntu folders is one named "Windows" which was created as an afterthought as a 5GB FAT32 partition added after Ubuntu partitions were created. The installer didn't seem to appreciate my attempts at creating the Ubuntu partition as FAT32 stating, once again, "No root file system is defined. Correct from partitioning menu", so this was my *compromise* (for a lack of a better term). I can expand on this later. For now, my only concern is keeping the very "precious XP" as well as my Hub's Win 7 BOTH operational.
Rebooted to finally check on XP and from GRUB menu (yes, Ubuntu must have attached ALL disk choices HERE as seen in pic), I *quickly* chose "XP" and after initial XP splash screen, it continued to the next screen (blue screen with another XP logo on it). It's the screen you'd see before the logon screen (if you had one) and before you see your Desktop, but it doesn't go past this screen and instead, it appears to *hang* there. Had to power off....

At the risk of an even longer post, I'll end this now. Take your time -- I'll be out for a few. If you have any questions/doubts/gripes/etc all will be addressed in the order in which they are received....not. laugh.gif

SBernheart sleeping.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2013 Invision Power Services, Inc.