 
Starting Over
A tale of woe with many changes. When you screw up royally ... and then screw up the recoveries ...
you are allowed to change your mind as much as you want to. Some of this will help and some of it will just be,
I hope, interesting to read. Fascinating if nothing else. You can always get something out of something.
Another thought is, this might be a good time to try out Linux, if you haven't already. There is a lot you can do and learn with a dual boot system. IT is NOT as hard as you think. Even though I highly recommend SuSE, it might be best if you got the same one your friends have, if they do. That way you can discuss ideas and problems. If your friends do not have Linux yet, then IF you have access to a high speed Internet connection, I would like to suggest that you download a copy of the latest 'Stable' openSuSE and install it. Or even better, purchase a boxed copy with DVD's and Manuals. That way you can support the effort. After a Screw Up!! Well, it happened. I was trying to create enough room to have more OS's on my system. Presently I have, inside VMware, two versions of Win2K, Win Vista and Windows 7. This is all inside SuSE 11.1, which I use as my main system. During the setup of this mess I made a wrong choice during the "Resize/Recovery" of my Win XP Media Center. I had not crashed the WinXP side of this machine, my HP 7480, since I have had it...Jan 27, 2009... welll... not so that I had to reload it. Now then, I was trying to reduce the size of the WinXP C: drive, increase the size of the Extended Partition with Linux in it, and then install the latest SuSE 11.2 inside VMware. Through the use of PartitionMagic(WinXP), chkdsk(WinXP) and Partition Manager(Linux) at first I could not do it. Grub didn't like changes in the Extended Partition. At first I tried just reducing the Win C: drive by 20MB and extending the Extended Partition that much. This would have been the rear end of Drive C: and the front end of the Extended Partition. I believe that is why Grub didn't like it. I'll swear that I was able to do this before, but I do believe that I was enlarging the extended partition on the rear end, like I did the C: drive. Anyway, I could not change the Linux portion. As things progressed, I decided to just make a partition between the two, but larger. Now is where the
problems started to intensify. PartitionMagic would not make it bigger. The problem was: Well, now the windows side was back to the way it came from the factory, or close to it anyway. The Linux side was still intact but I couldn't boot to it. Fortunately, my two data sections were also safe. Contrary to previous "Windows Full Recovery", this one only formatted the C: Partition and NOT the whole drive. It also DID NOT mess with my second drive, which also had been a problem with previous systems. However, the portion of the C: drive that I had stolen, it... the Recovery... grabbed back. Now the problem was... I could no longer dual boot. Thanks to a program called SuperGrub, and lots of Internet searching, I was able to boot back into my Linux. Like the author(s) said, this will teach you something about the booting process. I still have a lot to learn but, by guess and by golly, I got it to dual boot again... without re-loading my Linux stuff. Now then, the worst part of all this is ... you guessed it ... I didn't have everything on my C: drive backed up!!
The really, really worst part was I lost my Video's that I had captured from the TV. I was going to burn them out to DVD's but just hadn't
done it yet. Now I have to figure all that out again. Think I have something concerning the TV ops somewhere here in these Web Pages. I had
the new PC for quite some time before I even used the TV part cause it wasn't that important to me. Then after learning about it, and trying,
I saved some important things. Guess they weren't all that important... What Now???... Some of this will be repeated in one or more of the Web Pages referenced on the side. That is cause those were the three things I was working on, playing with, at the time of this incident. (openSuSE 11.1, openSuSE 11.2, Windows 7) The thought Now Then ... Just What Are We Trying To Do?? Things would be easier IF this was a new system with essentially nothing on it, except the original OS. But, that is not the case. One of my problems with the old layout was VMware data inside my home dir. The only reason that became a problem was, because I wanted to build more virtual systems. My "original" plans were to put the OS's on the first HD and the Data on the second HD, which is essentially what I did. Reason?? So that I could keep the Data safe. At this point it looks like I was successful, for the data anyway. The other reason was to get the Max HD space available. At that time, NTFS was going to give me the most and best use of HD space. The cluster/sector size was smaller, which would mean less HD waste. See: HP 7480 - Two HDs for the full story.
Well, as usual, whenever I get into something interesting I get interrupted. I have a customer with an Access problem
that I am going to have to switch over to and hope I can remember what in the heck I was doing here when I get back.
Let's see: Triple Booting, Multiple Partitions, SuSE 11.1 and 11.2, Windows XP - Vista - and 7. Drive organization. .... annndd ... probably re-loading everything. 
...And today is: 05 Jun 09
Top 18 Jun 09 This is going to be a long continuous process. As in the past, as I need things they will get loaded and/or
modified to fit my needs. I am in the Linux side more than the WinXP side so this "Re-Install" of WinXP Media Center will be
slow. Just today I got Flash back in and this app, Homesite back in. I use Homesite in Linux via VMware Win2k and Win Vista.
I re-installed Homesite here on WinXP so I could take some notes and now ...?.?.. I forgot what they were!!!
A further Push to re-do Everything!! - 8 Jul 09 Well, the latest fiasco was caused by "updating" openSuSE 11.2. During the long break in this document, I was messing with my system AND I finally created a partition between WinXP and openSuSE 11.1. This is where I loaded openSuSE 11.2 Milestone 2. Now comes the problem. I did an Install/Update to 11.2 Milestone 3. This actually went very well. One of the cleanest installs I have had. However, it wasn't as clean as I thought!! After loading SuSE 11.2 M3, I could not boot into my SuSE 11.1. You can look into my openSuSE 11.2 document for the dirty details, but suffice it to say, durning this "update", my home dir in SuSE 11.1 was wiped. I was blaming the 11.2 installation process -BUT- I found out it was an operator error!! After embarrassing myself to the world and reporting a bug to the Developers, and then analyzing some more, I realized that I got my sda's mixed up and I let the update use the WRONG one. I really thought it strange that this excellent install process could screw up like that. Well, it didn't. So, since I have almost totally destroyed my system -- in this learning process -- I guess I can just take the time to re-evaluate my drive layout and start ove. Right now I can not dual boot. I'm not gona go through all the gyrations to get it back as I did before cause the important parts, the home dir, is gone anyway. So, we will treat this almost as a new machine. Hmmmmm... that means I have to re-load PartitionMagic(and everything else for that matter). This gets frustrating at times. TopSystem Layout - The way it was:
Initial Drive Layout System Layout - The way it is now(or will be): Now we try to avoid another disaster. Starting as if this was a new machine. This time I am gona try to remember to record -ALL- the programs I load up. I had numerous little utilities that I had forgotten what I had got them for. So, we will create a log and make notes, WhatsLoaded, as to what in the heck we are doing. Also try to be more -religious- on the backups. First we need to figure out what we need, keeping past experiences in mind. Since we had success
in maintaining the data by having it on a separate drive, we will keep that concept. No changes...except for possibly
the Drive Letters. Because it will, in effect, be a new and different system.(However, through Windows Administrative
Management -> Computer Management -> Disk Management we got the Drive Letters back the same, or close to it.)
Ok. Now we need to tackle the First Main Drive. It already is divided up into some partitions. The first part is for the C: Drive and the last part is for the Recovery. Since the Drives are so large now-a-days, HP and others are placing the "Recovery Discs" in a special FAT Partition at the end of the main drive. IF you want physical DVDs you can order them -OR- you can create them yourself with a program provided by HP. At any rate we are not gona bother that last partition on the first drive. There is a 7.8MB unused portion between them. Don't know why unless the numbers wouldn't work
right. It will be used in our new machine cause we are gona change the numbers. I do believe that we only need about
80GB (If you are old enough to remember, that or less was all that you got when you purchased a New PC.) for drive C:
and even that may be to much. Previously we had 146.8GB and most of that went unused. So making the
adjustments in PartitionMagic and we get:
This has left a BIG Hole in the First drive. It will be filled with two Linux Partitions. I
still want the "Newest" Linux to have a Partition of its own. A lot of my troubles in the past were because
of VMware.( Now then, I still may want to "initially" load up the new Linux inside VMware to do the initial checks and testing. Then after I am satisfied, move it over to the "extra" partition to test VMware. So, how much room do we need?? We just need enough for the OS's. I do believe that each of the Win2K setups needed 8GB each. Then the Win Vista needed 16GB and Windows 7 expanded to 24GB. Not sure it really needed that much. But if we add those up we get 8x2 + 16 + 24 = 56GB just for the OS's inside VMware. On top of that we need 3GB for Linux. Then we need room for all the programs and the minor data storage. In the previous setup I only had 69 or 71GB (depending on how you count) for my home dir. In order to "play" with the other OS's I needed at least 24GB more. So, we take the space available 198.6GB - (122.1GB + 26GB = 148.1GB) = 50.5GB. So for the main Linux system we will have 148.1GB and for the new Linux test area we will have 50.5GB. Should work. Now the question is: Do I put the extra Partition at the end or in the middle?? There is, or was, a starting position boot requirement. I think that has been eliminated with these newer systems. BUT we will do our usual and search the Web for an answer. Well, I couldn't find anything. How-some-ever, as I recall, the MBR (Master Boot Record) is what is important. The normal Windows MBR gets modified to point to the menu.list in grub and then to make the decisions on which system to boot. A little Blurb I got from the SuSE people at: openSuSE Situation You want to remove GRUB from the MBR (Master Boot Record) of the hard disk. Procedure from SUSE LINUX 9.0 on As of SUSE Linux version 9.0, YaST creates a backup of the MBR during the installation. Thus, the MBR can be easily restored in case you want to remove the boot loader GRUB from the MBR. For this purpose, start YaST and select the dialog:
Then select "Restore MBR of Hard Disk" to overwrite the boot loader GRUB. Which proves my point. It changes the Windows MBR. Now we still have to decide on the positioning and "Who's on First?" Because ... in the experience I just flopped on, when I had the triple boot, it would start in the Bios, jump to the MBR and then list the Grub selections for the "last" Linux loaded. In those selections, you must have the other Linux as one of them. Now then, once again going on experience, I do believe that I want the Main Linux System loaded first and then the extra Linux section at the end. Why?? Cause I do believe that, IF I have to change the partition with PartitionMagic, it will work IF the changes are at the END of the Partition. I have no proof of that ... yet... but previous memories haunt me that I was able to change all Partitions as long as they were at the end. Course I could have been making the changes before a re-load. We'll see. For now I going on the hunch. I am NOT going to allocate the Partitions for the two Linux systems. I am going to let them do
it themselves. I am just going to use PartitionMagic to calculate the values that I will have to supply to the Linux installation
process. I will then just have to make note of the sizes I have chosen and after all is done I will get another
picture of the Drive with PartitionMagic. The possible values are:
Nope. Ran into trouble right off the bat. Linux, at least this version, will NOT let you change the size of an Extended Partition. So, I am going to have to create them here in PartitionMagic and then move over to Linux. With all that space it was going to allocate 20GB for root and 172GB for home. It would NOT let me make home bigger but I could reduce home. So, we'll try the 20GB root and a 110GB home dir. Well, here we go again. Created the Partition in PartitionMagic -BUT- it did not finish properly. A CTL-ALT-DEL was needed. Then a re-look with PartitionMagic showed that it "looked" OK. It just got so far and then did nothing more. Ran a Partition check and it checked OK. Try the Linux install again. Later again: I am trying to keep the Partition notes/info here together
even though they may have been encountered at another spot. Anyway, I got an Error 116 when I went back to Windows
and looked at the disc with PartitionMagic. Quote:
Disk Access Errors (40-56) Errors in the 40-56 number range indicate that accessing your disk is not possible, and often result from hardware problems. Some problems may have simple solutions; for others, the only solution may be replacing the hard disk. When possible, PartitionMagic detects major errors before any changes have been made so you can back up your data before replacing the hard disk. Check Errors (500-599) Check errors occur when PartitionMagic checks the integrity of a partition. #510 The version of the file system is not supported An updated version of PartitionMagic is required to operate on this new version of the file system. Visit www.symantec.com for information about updated versions of PartitionMagic. Which brings up a point. Sometimes ... an Error ... is not an Error. 
Top
ARRRGGHH!!!!!!!! Sometimes I hate computers!! I had "Updated" my Linux Systems
from 10.3 to 11.1 and not really
installed them. With the new magical installers I thought that it would be a snap to load up openSuSE 11.1.
It wasn't!! I am tired of fighting with the problems created since going into the 11 series. I am going back to 10.3.
I need to keep it for serious work and
use that extra partition to play with the newer systems. Maybe I can get my database back into operation. I do believe that 10.3
was the last version that it worked in. I like the new graphics in the newer versions BUT I do not like the way they are operating.
Top Back to Re-Installing Once again I will be bouncing back and forth between Quanta and Homesite. This time it is because I am dual booting into Windows -OR- Linux. Haven't loaded up VMware yet. Taking my time and trying to think and reason this out so that everything fits. Also have to get used to the "new" nomenclatures. Most of the drive letters have changed. Can't believe that the "same" system can be so different. Oh the horros of it all. I have had this PC running since Feb of 2007. Now I have to re-load
EVERYTHING!! I also have to remember how to do it. The Networking gets a little tricky. That's where I am now... trying
to get my local Network back in operation. I will admit it right here and now ... Windows is easier to set up.
The Networking answers can be found in NewSuSE-10-3.html
Network / Samba. Read down to the part about
mod_userdir.conf. Don't totally remember why, but I had an httpd.conf that I had saved and placed back in the apache2 dir. It caused a problem. Couldn't read my WebPages locally. Thought that was why I had changed it before BUT I put back the one that came with 10.3 and my local stuff worked properly. So, at this point, only the moduserdir.conf change was neccessary. Not true! Had to make this change in httpd.conf:
# forbid access to the entire filesystem by default
## http://httpd.apache.org/docs/1.3/mod/mod_access.html
<Directory />
Options Indexes FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Allow from dusty-tr.TRComputing
</Directory>
Annndd... had to add index.php to the DirectoryIndex inside http.conf.With the changes above I was able to access my WebPages locally. What I have to change, changes with the wind, or so it seems. It's all part of the changes they are making to make the system better and more secure. Just gets rather annoying having to fix the same things -only differently- over and over again. BUT then on the other hand ... I learn more by having to dig for the answers. Two way street??? Reference: Network / Samba Top Whats Loaded Oooopss Using KDiskFree I found the following: Allllrighty now ... the 11.2 load. First thing I am gona do AFTER making these comments is to make sure I have the items that I need backed up (including this documentation) and then ... use the technique described above to get back my Windows MBR and then completely wipe the Linux Partition and start over ... again. Rut Roh!!
Shouldn't have done that. The technique for restoring the MBR DID NOT WORK. After
performing the steps listed, I re-booted the machine. Horror of Horrors ... I got the following messages: Ok. Let's try loading and using openSuSE 11.2 Milestone 3 My greatest problem with the newest openSuSE Is KDE4. It looks promising and will probably be great ... BUT ... it is a big change. The real answer will be VMware. I like using it and playing will other OS's inside the system that I happen to be using. IF I can not get VMware to work inside this newest Linux ... BAM ... it's back to the old one, 11.1. The next words will be from inside Linux. Ok I lied. I took a look with PartitionMagic. In the previous attempt, using openSuSE 10.3, I had to set the Partition BEFORE installing Linux -OR- it would use the whole unused space and NOT let me adjust it. (or was that 11.1??) Anyway I am going to TRY to install 11.2 without setting up the Partition beforehand with PartitionMagic. No can do!! I tried everyway that was available and it would not let me set the sizes
that I wanted for root, swap and home. I think version 7.x or 8.x were the last ones that I remember being
able to set. Actually, I don't remember, when I started do Updates instead of FULL installs. Anyway I am going
to try to use a partition setup via PartitionMagic and see if it will let me. Nope! It didn't use my sizes and made things even smaller. Besides that it is using ext4. Hmmmmm... they sneaked a new on in on me. Probably a long time ago, since I don't pay enough attention to some of these details. TopMention these good tools somewhere...I did. Better later. img burn prog - Gparted - TV card - communications - Display offsets - xvidtuneSysRescueCD ImgBurn xvidtune  And after adjustment:  xvidtune How-to use: Using xvidtune Top Another Try Well things are going all to hell!! Bouncing around I lost some more notes AND my AC (air conditioner) went on the frits!! Oh well... it's only 115 today here in Phoenix. I did another install of SuSE 10.3. This time, in addition to that I fixed my display. As I mentioned above, it was always shifted to the Right and I had to use the monitor's buttons to manually fix it. Well, I found xvidtune and used it. Unfortunately, in order to get the settings to save, I had to do a FULL blown update(YOU) of 10.3. This contained the proper nvidia drivers, so all helped. However, (that word again) all is NOT well. AFTER the Full update my Quanta was missing, konqueror was missing and who knows what else was missing.!.! Such a disaster. Then I tried to find the konqueror in the Repositories to replace it AND it was NOT there. At least NOT the KDE 3 version. All that was there was the KDE4 stuff. So now I am going to try to re-load the SuSE 11.1 version again. IF I run into any problems I think I am just gona call it quits on Linux and stick with Windows. TopHopefully, the last SuSE Linux 11.1 re-load...(but I doubt it) Already have SuSE 10.3 loaded. Because it detects hardware that 11.1 didn't on the
install of it, I am going to Update 10.3 to 11.1. Well, we have a problem. The screen is shifted to the Right again. Have to see if I can fix it like the last time, with xvidtune. Nope. Once again, I can move it over with 4 clicks but it doesn't save annnnddd... even if I modify xorg.conf it doesn't fix it. Now, kupdateapplet came up and has 61 updates for me. In 10.3 when I got a lot of "updates" I lost some functionality. So I'm leary on a large amount of updates. BUT we will do it AND make sure I have the latest nvidia stuff. Arrrgghh!! During this massive update I got a Allllrighty Now!! Got the updates ANNDD... the display stayed fixed!! no more offset to the Right. AND konqueror is working AND Quanta is still there. Looking Good. Hmmmmmm... display didn't last through a Re-Start. Checked out the nvidia drivers and updated them. Did an End Session and the display stayed. Now need to do a re-Start and see if it stays. Ok. Looking Good again. It appears that we finally have the display fixed. I just re-booted into Windows and it looks ok also. Now we need to get VMware loaded up in Linux. TopI found this little Gem on the Web, once again looking for something else, BUT I wanted to share it cause it expresses my feelings almost exactly. The site can be found at: CompuClues Forum Bitzenbytes.com With openSUSE, there's an easier way. ...and here's where I get on my soapbox. 
To anyone reading this, I don't care what OS you use. Really. Use Windows. Use openSUSE. Use one of the *buntus. S'ok, really. Some folks seem to care. I'm not one of them. That said, I recommend openSUSE to everyone. Why? When you get down to it, all Linux distros (distributions) are essentially the same. They've got the Linux kernel. They've got the GNU utilities. They've got the same userland software, more or less (and if they don't, you can grab the source and compile it). Yup...all the same, except for a couple-three things:
There are other minor differences (and when you've gotten the hang of this stuff, a little, I'd urge you to poke around the /etc folder of a few different distro installs. Kinda like kicking the tires and peeking under the hood)...but there are more similarities than differences. I like openSUSE the most because of YaST, pure and simple. YaST stands for 'Yet another Setup Tool' and is essentially just that...the tool SuSE has given you to install and manage its distro. YaST also gives you a nice interface for its package manager, so installing software is easy too. So, we've got YaST. Let's use it. Open YaST. Give it the root password when prompted. Top Got VMware loaded Looked like it was gona be good until ... I tried to access other dirs. After lots of head scratchin' cussin' and moanin' I found that, once again, even though you load something during the install it doesn't neccessarily get started. Like apache2 that's what happened on the Sambo Server. I had to start it. Now that it is started I need to get my user name and password registered in the password file... or something like that. Ah, ha.... smbpasswd -a ctaylor then enter the password. Which must, or
should(can't remember which), be the same username and password as your user in Linux. If you have the same username
and password on everything it makes it easier on the system, yourself and the crooks.
Sound Not everything gets setup automatically in Linux ... yet. We have the differences between, [Simple, Fast and Easy trying to become Secure] vs [Complex, Hard to use and Secure trying to become Easy]. Back in the Early Days of Home PC's, with DOS and Windows 1.0, things were not all that easy either. But as time went on and sales increased, enterprising individuals on their own and through major companies all got together and created a Windows World. Mater of fact there was a time period when the PC's were very, very Windows Specific. If not the whole thing at least parts of it. Thats where the money was... and still is. BUT the manufacturers have slackened up on the Windows specific elements and have even been providing drivers for Linux. So, we Linux users are making some headway. Still have a long way to go, though. Which brings us to Sound and some forgetfulness. In my newest system, they detected the sound
system but forgot to enable it. I did but got choppy sound. The original setup and fixes are described in: Don't forget K3b, lame, k3b-codecs, libmad0 And it ain't over yet!! Whilst operatiing my Firefox browser I noticed that I wasn't getting any sound in Flash and YouTube. AFTER dumping pulseaudio completely, I was able to get the sounds in both ... again. Another item released a little to soon. Well this is the end... For the most part my PC machine has been restored. I know, and you do too, that there will be things that I will want to do ... and can't ... because of something that I forgot. If and when that happens I will try to remember to make a note of it in my WhatsLoaded doc. I still need to re-load Vista, Windows 7 and the latest openSuSE 11.2 but those will be covered in their own WebPages... cause that is what I happened to be doing when I caused this rucus!! TopTriple Boot Well, it appears that my notations and experiences on setting up the triple boot are going to
be contained in this file. This note is actually after the following scenarios. -But- another screw up. I just "updated"
my SuSE 11.1 and then re-booted. as required, cause the kernel was changed. Oooops... the grub being used for boot is actually in
the last linux loaded, which was 11.2, and it doesn't know about the changes in 11.1!! I didn't pay proper attention to this
fact and now it can not find my 11.1 partition and I don't know the new name of the kernel. From fragmented memories and Web
searches I believe that I have to change the numeric portion to 2.6.27.29-0.1.1. I am allowed to edit the boot line so we will
try that. Can't hurt anymore than now. (By the way, I am creating this particular paragraph/note in Windows.)(now in Linux) I was
almost correct. Had to remove the last dot 1(.1). The actual name(s) were/are:
title openSUSE 11.1 - 2.6.27.29-0.1 (pae)
root (hd0,5)
kernel /boot/vmlinuz-2.6.27.29-0.1-pae root=/dev/disk/by-id/ata-WDC_WD3000JS-60PDB0_WD-WCAPD1266636-part6 resume=/dev/disk/by-id/ata-WDC_WD3000JS-60PDB0_WD-WCAPD1266636-part5 splash=silent showopts vga=0x31a
initrd /boot/initrd-2.6.27.29-0.1-pae
Thanks to the Lord for opening my eyes to see this.Now the above lines were taken from the Grub inside 11.1 -but- it isn't used in the boot. Multi-boot can get tricky. Those lines, however, need to be in the SuSE 11.2 grub and they are ... now. Will have to try to remember this in the future. New attempt at "fixing" the Partitions. The sda8 partition in the list below is my latest attempt at correcting the Partitions on my first drive. sda5, sda6 and sda7 are used for my current Linux SuSE 11.1. I wanted the sda8 to be an "Unallocated" portion of the drive. However, in the calculations by the systems, I had an unused portion of 462MB at the end of the Extended Partition. I tried to reduce the Extended Partition and add the unused portion to the Unallocated part. Let it suffice to say that the only way I could get back the unused portion was to create/reduce/expand a partition at the end of the Extended Partition. Whew... a tounge twister. Now then, in order to do what I want to do, I need to create a root, home and swap inside sda8... which should recreate it and make an sda9 and sda10. We'll see. dusty-tr2:/home/ctaylor # fdisk -l Disk /dev/sda: 300.0 GB, 300069052416 bytes 255 heads, 63 sectors/track, 36481 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x70987098 Device Boot Start End Blocks Id System /dev/sda1 1 10199 81923436 7 HPFS/NTFS /dev/sda2 35529 36481 7654941 c W95 FAT32 (LBA) /dev/sda3 * 10200 29319 153581400 f W95 Ext'd (LBA) /dev/sda5 10200 10461 2104483+ 82 Linux swap / Solaris /dev/sda6 10462 15934 43961841 83 Linux /dev/sda7 15935 29260 107041063+ 83 Linux /dev/sda8 29261 35528 50347678+ 83 Linux Partition table entries are not in disk order Disk /dev/sdb: 300.0 GB, 300069052416 bytes 255 heads, 63 sectors/track, 36481 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x03ce34a8 Device Boot Start End Blocks Id System /dev/sdb1 1 34443 276663366 7 HPFS/NTFS /dev/sdb2 34444 36481 16370235 f W95 Ext'd (LBA) /dev/sdb5 34444 36481 16370203+ b W95 FAT32 dusty-tr2:/home/ctaylor # Allllrighty now ... I could not deallocate sda8 via Partition Magic. The previous partitions are ext3 and it doesn't understand them. Kept getting unrecognized system error everytime I tried to delete the sda8 partition to make it empty. My first attempt at installing SuSE 11.2 in this manner was NOT successful. It wanted to use my SuSE 11.1 partitions. I used gparted to make it empty but I do believe that was futil. You can only have 4 physical partitions on a disc. For a linux system you need three. A swap, root, and home. So, I must extend the Extened partition and then try the install. -BUT- we need a plan. I don't believe that it is going to let me have two swaps, two roots and two homes. Ok, with Partition Magic I created an Unformatted partition of the Unallocated space. Let's see what the installer thinks of that. Bumber!!! It keeps wanting to use the partitions from my SuSE 11.1. Now then, in doing my usual, searching the Web, I found this from Oldcpu in the openSuSE Forums. Notice: he's got the WinXP portion as a Primary AND the roots of both the Linux versions ALSO are Primary. This takes the first three of the 4 allowed physical partitions. The fourth Partition is an Extended one in which you can create others.(logical ones) Looks like that is the only way I am going to get a Dual Linux on the same HD. (Well, possibly not true...see below)
Well, I posed the question to the indiviuals on the openSuSE Forum and the answers I got back
tell me I should have been able to accomplish this, the triple boot, earlier if I had just kept my sda's straight. So,
we will try again. Using Gparted with a SystemRescueCD I exetened the Extended Partition and created Partitions for
another swap, root and home to be used by openSuSE 11.2 Disk /dev/sda: 300.0 GB, 300069052416 bytes 255 heads, 63 sectors/track, 36481 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x70987098 Device Boot Start End Blocks Id System /dev/sda1 1 10199 81923436 7 HPFS/NTFS WinDrv C: /dev/sda2 35529 36481 7654941 c W95 FAT32 (LBA) WinDrv Recovery /dev/sda3 * 10200 35528 203455192+ f W95 Ext'd (LBA) Extended Partition /dev/sda5 10200 10461 2104483+ 82 Linux swap / Solaris openSuSE 11.1 /dev/sda6 10462 15934 43961841 83 Linux / openSuSE 11.1 /dev/sda7 15935 29260 107041063+ 83 Linux /home openSuSE 11.1 /dev/sda8 29261 29526 2136613+ 82 Linux swap / Solaris openSuSE 11.2 /dev/sda9 29527 32251 21888531 83 Linux / openSuSE 11.2 /dev/sda10 32252 35528 26322471 83 Linux /home openSuSE 11.2Top Printer Server & Printer PS110: This is a Netgear Printer Server. It naturally comes with
a disc providing software and drivers that will be needed. cp1700: This is a fine HP Printer. It also comes with a disc containing software and drivers. Refs: PS110 - cp1700 and My 7480 TopRouter & Switcher RT311: Netgear Router. This came with a disc -but- so far on this Re-Install and Re-Setup of my system I haven't had to load any of it. Both the Windows and Linux Systems have been working fine. So for now... we will not load the software. (if it ain't broke ... don't fix it) FS108: Netgear Switch. Sorta same here, 'cept I can't find a disc for it. Don't know right now if it came with one or not. So far nothing is needed anyway, on either Operating System. Top All Done
Top
|
But ... it might have made
things worse. I had been thinking of redoing my System anyway ... but in a more controlled manner.
...hmmmmmm...
occurred
to me that now would be the time to do an analyzation of my System Setup and HD usage. I had done this when I first got my
new 
Now then, I'm surprised that it looks like this. The Disc by ID is possibly leftover from the 11.1 attempt,
since they are empty. BUT I thought that the area was to be wiped and formatted when this 10.3 was loaded.
Final results according to PartitionMagic:
Doesn't matter. My database didn't work here in 10.3 either. Think I am just gona re-load up the 11.1 and be
done with it. In fact ... I may do openSuSE 11.2. Why?? Cause it understands my Sony Monitor. SuSE 11.2 is the
first Linux OS that I have loaded that got the positioning of my display correct. On all the previous Linux
loads, I had to manually adjust the positioning of the display. So what, you say? Well, the problem was... the
textual display was to far to the left and the graphic was to far to the right. Naturally, since I was in
X-Windows all the time I had the display shifted to the left. I like to watch the boot sequence and it was always
one and a half characters off screen to the left because to this adjustment. The displays in SuSE 11.2 do not
have this problem. They look correct... so far.
