Linux, anyone?

[Bob in a quantum-state-of-faith]

Okay, that's all very well.

I'm planning on dedicating a specific hard disk to Linux.  During the entire install, I'll be removing all my windoze drives (temporarily) so as not to confuse anything-- a long-learned lesson from the past.

Once Linux is up and running as it should, I'll re-connect the other drives one at a time.

As for booting, I'm planning on using my BIOS build-in drive selection menu-- obscure, true, but Just Works.  And a nice label takes care of the obscurity issues (the seemingly random mix of numbers and characters that 'identifies' the disks appears to be arcane magic.  )

Anyone see an issue with the above plan?

Or will Linux futz with my Windoze drives once it gets a chance to see them?  That would be a deal-breaker...

[Sibling Zono (anon1mat0)]

ubuntu (I can't tell about other flavors because the last time I played with mandriva was long ago) won't harm your win disks.

In theory your bios solution seems workable but I had some headaches with a similar config because the boot part is usually in only one disk on the system. In theory once you tell it to boot from certain disk it should do it, in practice can be tricky. If each disk has the installation completely isolated it should work.

[Bob in a quantum-state-of-faith]

ubuntu (I can't tell about other flavors because the last time I played with mandriva was long ago) won't harm your win disks.

In theory your bios solution seems workable but I had some headaches with a similar config because the boot part is usually in only one disk on the system. In theory once you tell it to boot from certain disk it should do it, in practice can be tricky. If each disk has the installation completely isolated it should work.

I'm only too familiar with the MBR issue.  That's why I always disconnect the data wire from other working disks.  I learned that problem, back during an upgrade from Windows NT to Windows 2000.... I mistakenly left the WinNT drive in place when I cold-installed Win2K.   I had heck fixing that one.... eventually, the creation of a MBR repair disk solved it, but it was touch-and-go for a bit.

The fact is, as far as I can tell, the BIOS really does not care if there are multiple, primary, active drives in it-- that convention was likely invented by some basement dweller back at IBM in 1963 or something.  And nobody's bothered to fix it since.   

But the only way I've found to create multiple, primary, active drives, is by creating the partition with just that drive in place. 

Hence, the disconnect all the others, every time I'm doing a system install.

I usually always do it this way, regardless:  drives are cheap (relatively).  If I want a fresh install of Windoze (a recommended practice-- I used to say bi-annually (win95/98 days) but now, things have improved, and once every coupla years seems enough) I would buy a new, larger drive, and bare-metal install Windoze on it-- with nothing else in the system.  Then, I could re-connect the old drive and fish for files.   But, in a pinch, I could re-connect it and boot from it, if I needed.  Once in a great while, a fresh out-of-the-box drive is bad, but only after a week of burn-in.... having the previous install still intact has saved my butt a time or two.

I find I like the idea of using the BIOS, even with it's arcane language    There's nothing else burdening my system that way, and it's a literal key-press away.

That way, if I decide in the future, I could remove 2 of the 3 OS disks, and I'd still have a working PC... 

I'll post my results when I get around to making the Linux disk.

[Lindorm]

A bit late to the party, but I can only add to the choir of praise. Installing Ubuntu did wonders for my blood pressure and productivity. It just works, period. And it talks to most peripheral devices without any hiccups, even some Windows-based stuff that is supposedly only useable with proprietary programmes ( i e certain MP3 players, our notoriously diva-tastic HP printer etc.)

A caveat, though: Since Ubuntu is distributed as free, Free and Open Source, some media formats and programmes (DVD player among them) may require a bit of tweaking in order for them to play all your media properly. This is mostly just a matter of writing a few lines of text in the command-line editor and very well documented on various forums, How-tos etc, and really just a minor inconvenience.

[Bob in a quantum-state-of-faith]

Thanks, all for the info.

I've burned a nice bootable CD of the latest stable Ubunto.  I did locate a nice website with a questionare about which linux to choose, here:  http://lifehacker.com/146963/which-linux-distro-is-right-for-you

I took the quiz, looked carefully at the results, then checked out the various websites the results produced.

Ubunto was one of the 100% "compatible", according to how I answered the quiz, and the site confirmed it.

I already sent them 2 feedback comments, as two of the supposedly 100% compatible offerings were not, in fact, all that compatible when looking closely at their sites-- mainly a lack of 64bit support.   Since I have 8gigs of ram, I want to make full use of it, and the 4 processors-- which means 64 bit as far as I can tell.  Sure, the 32 bit will run-- heck, I'm on XP at the moment (due to that's how I'd left my machine from last night, and I'm too lazy to re-boot into 7).  But XP is 32 bit, and it sees only 2gig of my memory-- ignoring the rest, I presume.*

In any case, this weekend, I'm planning on cracking the case open, installing that last SATA hard drive, disabling the other two active, primary drives, and seeing what happens.  With any luck?  It'll just work.

Hmmm.   I probabily ought to pre-load some Linux drivers onto somewhere or other, in case the network card won't network...   In fact, I may go back to MSI's website, and choose "Linux" and see what sort of drivers they offer, first. 

I could stash these onto my storage volume drive, I suppose-- there's nothing there that's propriety to microsuck, and it's neither a primary, active, nor bootable anyway-- strictly a storage disc (500gig).




))))))))))))))))))

_{* I'm going to look for a crack/patch for XP to see more RAM, but I've not got around to it}

[Sibling Zono (anon1mat0)]

They have an x86-32 and a x86-64/AMD64 version, you can download both .iso files from this link:

http://www.ubuntu.com/getubuntu/download

Note the alternative download options to change to the 64 bit version.

[Bob in a quantum-state-of-faith]

They have an x86-32 and a x86-64/AMD64 version, you can download both .iso files from this link:

http://www.ubuntu.com/getubuntu/download

Note the alternative download options to change to the 64 bit version.

Thank you-- but I already discovered that setting.

I should have posted a link myself, I suppose.

That's the version (64bit, complete) that I burned into the CD.

[Bob in a quantum-state-of-faith]

A bit of thread necromancy, and a bit of a serious complaint.

I had twiddled with Linux awhile back-- and I see nearly 3 years back (I knew it was awhile).

I tried and tried to beat Linux into submission, both with the printing issues and the multiple-monitor thing.

Never did get either one to work-- at all.   Eventually gave it up as a waste of time and energy, beating one's head senselessly against an immovable object.

But the other day, I realized that one (or more) of my hard drives was failing, gradual slow-downs, longer and longer waking from sleep, etc. 

I presumed it was my oldest drive, a 320gig that I had been using for my programs' installs, as I noticed the hesitation anytime I accessed programs installed on that drive.  I was wrong, but didn't figure that out at first.  So, I'd been in the market for a new(er) drive, and Best Buy the other day, had some pretty good specs on one for less than $100.  64meg cache, SATA 6, etc.  So I got it.

Here comes the Linux thing-- I reconnected my external Linux drive, and told BIOS to boot from it, so I could use Linux to clone the 320gig onto the new 1000gig.  I'd extend the partition to fill the whole drive in Windoze (very easy to do, if the space is unallocated).

And there began my Tale Of Linux Arrogance:  Linux wouldn't let me do much of anything, until I upgraded to a later version.  (And I'd forgotten my password.. meh)  Fine.  Upgradealready.  Sheesh, arrogant $*^(#^%& software...

... and THAT was a horrible, horrible mistake.  At least with the old Linux, I could actually read what was on the duplicated-desktop (the 3rd screen remained 100% unused... stupid OS).  But post- "upgrade" the video was all hash.  Meh.  Finally, looking on the Web, using my Android tablet, I found a way to both recover my password & boot into a "low graphics safe mode" (whatever that is).  At least I could see the words, now. 

I wasted another 45 minutes in a futile attempt to find a reasonable way to make the graphic card work (that did not involve arcane Linux spellcasting that only SuperUsers understood fully... arrogant is what I would describe the majority of the Linux [no]Help forums.  Gave up.  Will keep booting into "low level graphics safe mode" in the future.   

Anyway, I did manage to recover (or more properly, reset) my admin Linux password--that was relatively painless, and not a little bit concerning-- it' really was too easy to do, I could have walked my mom through the process over the phone... not really a good thing, security-wise.  And also makes me quite irritated that I have to key in the damn password for nearly everything I wanted to do!  Why bother?  Since it's so very simple to change with just a few steps.... !!

meh.  But I did manage to duplicate my (what I thought was) ailing P: drive (programs) onto the 1000gig one, using a terminal command (diskrecover, I think.. was going to use DD, but it doesn't continue after an error, so I used the recover one instead-- had to install it, which was actually explained quite well in the one thread, to my astonishment...)

Power off, no problem.  Remove the old P: disk, and the now unneeded Linux disk, and power on.

Fail.  Epic-epic fail.   My original Windows disk would no longer boot!  It put up a 100% useless message having something to do with a Grue or a Grep some nonsensical crap from ... it could only be ... that massively--^)#^*()#$ Linux update!  How.  Utterly. Completely. ARROGANT-- to write over my MBR without so much as a "by your leave".... !!!!   To say I was mad, would be to say the Sun in Florida is middling bright.   Now, I had no computer at all!  Aaaaaaagh!

So.  Power off.  Reconnect the stupid Linux disk, and try again-- booted directly to Linux, with the garbled & unreadable graphics.  Reboot, only hold down the shift key (I remembered the 2nd time) so I could get into the low-graphics "safe" mode again.   Search the webs for what had happened-- Linux obviously trashed the MBR on my main Windows drive... and the only way to fix it, was to boot into Windoze, and create a recovery CD.  Catch-22.   But some fiddling about, and I managed to engage the GREP or GRUE or whatever it's stupidly called boot menu from Linux-- WHICH I DID NOT WANT.  (did I mention arrogant?  I did?  Well--it was.)

Reboot.  There's the boot menu, finally-- choose Windoze 7-- wait & finally, I'm back in Windoze land.  Dig out of the junk parts bin an unused CD.  Create the "recovery disk".  Reboot--use BIOS to boot to the CD, and let Windoze repair the MBR.   That was actually pretty easy, both to find, and to do once I had the MBR disk-- there's a little utility .EXE file that Just Works.  Command line simple.   I didn't even have to print the instructions, they were so easy (for me).

Remove CD.  Reboot with hands-off.  *sigh*  Windoze started automatically.  *sigh*-*sigh*.   Back, baby! 

Only, my halts, hesitations & slowdowns were not fixed... I'd replaced the wrong drive... !  It was my el-cheapo Windows drive, it was only 160gig when the norm was 500gig & higher.  I deliberately wanted a small system drive, so it wouldn't get burdened with extra files I needed to keep... turns out that was a bad decision, as it also meant el-cheapo, bottom-of-the-barrel quality & electronics.

During the Linux disk cloning process, it had a rather nice display of the bits-per-second during the copy process, including both instant & average.  I had noted that cloning the new drive, the average speed was in excess of 5000, and sometimes peaked at 6000+.    I didn't think anything of it at the time....

... I was now really concerned about that ailing 160gig system disk.  Hmmm... I now had an unused, but apparently still reliable 320gig I wasn't using anymore... so.... Back to Linux-- using BIOS to choose which disk to boot from-- remember to hold the SHIFT key, to get into the "emergency" low-level graphics mode....

.. and this time, I would be cloning the 160gig onto the 320gig (wiping it out in the process-- no problem).   I invoked the same spells as before, only with new targets.  And during the cloning process, I noticed the bits per second dropped to 3000 and occasionally lower.  That right there told me the 160gig was sub-par, as the target in this one had been the source in the previous test.

About an hour later--ironically about the same time as for the 320-- I had me a clone of my Window's drive.  Power down.  Disconnect the 160.  Reconnect the 320, mount it in an empty slot (I have lots in this case), connect the cables that formerly fed the 160, to the 320 now. 

Boot up and see what's what:  during BIOS POST, there's no more halt at the disk-detection phase.  Yaaay!   And Windoze was many times faster too.   Let it come all the way up-- it has to trundle a bit, to "reinstall" a few things, as Windoze knows I've changed the drive (serial number), but is happily trundling away.  When that was done, I went in to Disk Manager, and extended the Windoze partition to fill up the rest of the unused space (why not?).  Then rebooted to let everything settle in. 

This final reboot, things just flew by-- like it was new, in fact-- and I believe I've isolated & repaired my hesitation issues.  I'm so delighted, I think I'll go ahead and order a high performance WD Velocitiraptor drive, who runs at 10,000RPM, and has about 500gig or so space.  About $100US (or so).  A nice 64meg cache, SATA 6mb interface, a nice drive.  Reviews were positive for the most part.  It apparently runs a wee bit hot, so I'll likely move things around in my trays, to put this one up-top, in front of a fan.  But that's for another day... (and I'll have to deal with the Linux-beast too... maybe I ought to download & create a new, fresh install-- that one was only 10.xx something, and I think they are all the way up to 12.xx now.... meh.  As bad as Windoze 98 days, with daily updates... )



So.  Why did I bother with Linux at all, if I only wanted to change disks in Windoze?  Because Windoze does not play well with hardware changes, if you make them within Windoze' full attention-- it insists on doing nefarious things to a brand-new drive first, and can get it's registry really befuddled if you do it that way.

By doing these hardware swaps outside of Windoze, it pretty much remains ignorant of the new hardware, and you don't need to modify the registry pointers to the new stuff-- the clone process makes the new disk exactly like the old one, as far as Windoze & it's funky registry is concerned.  Not a trivial concern.   

Back in the day, I would've done all this in DOS.  But, alas, DOS does not understand NTFS, the preferred format for drives larger than 2 gig in size.  I'd go into it, but this is long enough as it is.  So my choice was use XP or Linux.  Unfortunately, my XP install is completely hosed--I had done something bad to it, and it's now in an endless boot-loop.  I haven't bothered to fix that, as I don't use it anymore anyhow....  I had foolishly thought that Linux would be a painless way of cloning the disk...

... silly me.

[Griffin NoName]

I always buy WD. At least, if I buy them seperately and am not constrained to the choice the actual computer manufacturer provides.

Sounds like you had fun !

[Bob in a quantum-state-of-faith]

Actually? I did--once I had beaten out all the knots in the system. 

There is a great deal of satisfaction in finishing such projects. 

[Sibling Zono (anon1mat0)]

Were you using a CD boot version of linux? That is the way to do such things BTW.
--
Also, you can do partition cloning from Win using Partition Magic without major complaints (at least in my experience).
--
And as for the graphics/3rd monitor, etc, that isn't the OS fault but the manufacturer of the hardware not making a fully working driver (and admittedly both AMD and nVidia make some half-a$$3d jobs on their linux drivers, hopefully that should get better now that Steam is in linux).

[Griffin NoName]

I always buy WD.

Actually?

Yes, actually.  Oh, wait a minute, that's a film   oh no, that's Love Actually. Must stop rambling//......................

[Bob in a quantum-state-of-faith]

I always buy WD.

Actually?

Yes, actually.  Oh, wait a minute, that's a film   oh no, that's Love Actually. Must stop rambling//......................

[Bob in a quantum-state-of-faith]

Were you using a CD boot version of linux? That is the way to do such things BTW.
--
Also, you can do partition cloning from Win using Partition Magic without major complaints (at least in my experience).
--
And as for the graphics/3rd monitor, etc, that isn't the OS fault but the manufacturer of the hardware not making a fully working driver (and admittedly both AMD and nVidia make some half-a$$3d jobs on their linux drivers, hopefully that should get better now that Steam is in linux).

Frankly, I can't be bothered to go to all the trouble to create a boot version of Linux.  Yes, I know I know it's supposedly pretty easy.  But I really had wanted to like Linux, and I had this extra 120gig drive lying around, and a nice, quality external case....

I am well aware that many of the drive duplication software runs on a custom version of Linux-- my past-favorite Acronis did exactly that, and came with a nice utility that would create a bootable CD/DVD to do the duplication.  But I have not kept up with them, and the copy of Aronis I have does not speak SATA.   Too cheap to upgrade.  Besides, I had a nice pure-install of Linux on a 120gig drive... right?  Right?  meh.

As for the graphics thing?  I could not even figure out how to get it, let alone figure out where the damn thing was installed (or not) or what the unnecessarily-opaque Linux was using instead of what it ought to have been using.  The no-help forums were very little help to anyone who wasn't deep into Linux culture and understood the subtle nuances of Terminal-speak. 

There was once a time, when I had the energy to dig into that-- I still remember 90% of my DOS commands for example.  But that was due to 17 years of doing DOS on a daily basis, and very complicated DOS it was, too.  Tweaking, by hand (and trial and error) the memory, the interrupts, the PORT settings?  Yeah, I did that.

And I do not miss it even a little bit.   Windoze, for all it's piggyness?  It just does that carp for me, good enough, too.  Is it perfect?  Nope-- so what?  It Just Works.

I cannot say the same for Linux--not even superficially does it work-- forget the 3 monitor fiasco.  Forget that I cannot print in Linux--ever.   It can't even be smart enough, to automatically put my graphic card into a mode where I can read the damn screen!   And the fix?  The fix requires a PhD in Linux.

So do I blame the OS?  You damn betcha I blame the OS.  At a bare minimum, it should be able to be--easily-- put into a simple, low-level graphic mode and stay there.  Can I beat on it to do that?  No-- I can get it into the low level mode temporarily, by jumping through some very silly hoops first.  Each. and. every. time.

Fail.  Epically so.

[Sibling Zono (anon1mat0)]

Creating a boot is a matter of just burning the ISO you download, and that will run in almost anything precisely because it's configured for compatibility. Running 3 screens though, being something that only a tiny portion of users do, that requires 3rd party drivers, that are underdeveloped by the videocard manufacturers, will not happen out of the box.

Forgive me but it would seem to me that you expect Linux (and you didn't even specified which flavor) is supposed to magically do everything easier that windows itself, and at this point that isn't a logical expectation (because not even windows is able to do so).