Hi Folks,
Installation CDs and pre-installed O/S plus recovery disks.
I have always installed from a full O/S disk. My daughter and several of the outlaws have bought systems with pre-installed O/S and recovery disks (Tiny and Acer). Initially, these boxes had Win95. Recovery on these machines was in fact a reformat and copying of a 'mirror' image and not a full version. I upgraded my sys to Win 98 and eventually 98SE (do you think I'd admit to upgrading the outlaws?) Currently, because Photoshop CS demanded it W2K (which is absolutely with no exceptions they flakiest O/S I've used - and I started with CP/M! Fond memory says W3.11 was the best.
I now have two towers and two USB externals. The 'twin towers' each have two HDD. The reason for this is that initially a refusal to boot up and even acknowledge the presence of emergency repair disk in floppy drive or the installation CD in CD drive caused my local guru to pronounce the HDD dead. I bought and fitted new drive, reinstalled every thing and fitted (after setting jumpers) 'dead' drive as slave in the hopes of being able to recover data including a large number of scanned images. Lo and behold, the 'dead' drive was seen and all the data was there and could be accessed. So verily the dead drive was resurrected! The next time the 'C:' drive 'died' on me, it was another trip to PC World for another HDD and again installing and loading O/S. This time 'dead' drive went into one of those new fangled (at the time) external USB drive boxes where it remains. As I said - two boxes and now six HDDs later have lead me to believe that it is software (namely windoze) that is at fault, not the hardware! Possibly a viral infection could have caused it but who knows? Next failure will see a smaller drive installed as 'C:' as it will in fact only contain O/S and those programs that won't install anywhere else but C: Why smaller? It takes an age to scan for Virii or defrag big drives! Incidentally, the latest reformatting because windoze wouldn't boot resurrected a dormant Linux partition which the system labelled C: and windoze took itself off into a second partition it named F: I wonder how long before I have to repeat the exercise? Now come the question; with multiple hard drives installed, can Linux install and boot from a second hard drive D:? Having windoze and Linux in separate partitions on the same hard drive made me give up on Linux.
Reading these mails - your comments re operating/installing Linux is absolutely frightening. A 'simple' installation CD that injects Linux onto a hard drive and which comes up with a desktop 'just like windoze' (or Mac O/S) is all 99% of PC owners want. We don't want to know about command lines - just icons on the desktop just like the original Digital Research GUI that all other O/S desktops have copied!
Cheers,
BD.
On Wed, Nov 09, 2005 at 10:27:54AM -0000, Bob Dove wrote:
upgrading the outlaws?) Currently, because Photoshop CS demanded it W2K (which is absolutely with no exceptions they flakiest O/S I've used - and I started with CP/M! Fond memory says W3.11 was the best.
Weird, my experience was that Win2k was by far the best OS Microsoft every released. It had all the benefits of plug & pray (but matured so it actually worked) and none of the teletubby add-ons of Windows XP and had the welcome addition of a security model.
it named F: I wonder how long before I have to repeat the exercise? Now come the question; with multiple hard drives installed, can Linux install and boot from a second hard drive D:? Having windoze and Linux in separate partitions on the same hard drive made me give up on Linux.
In answer to your question, Linux can boot quite happily off a 2nd Hard disk (or 3rd or 4th etc.) as long as it can find the bootloader. Your description of the other problems (it confused me a bit) sounds like you have a hardware problem or that the Bios setup is perhaps somehow wrong. I'd perhaps stop taking the machine to PC World (or whichever store you are taking it too) and try a local independant shop to get it sorted as it shouldn't take very long for someone who knows what they are doing to sort it out. (or bring the machine to an Alug kitmeet)
Reading these mails - your comments re operating/installing Linux is absolutely frightening. A 'simple' installation CD that injects Linux onto a hard drive and which comes up with a desktop 'just like windoze' (or Mac O/S) is all 99% of PC owners want. We don't want to know about command lines - just icons on the desktop just like the original Digital Research GUI that all other O/S desktops have copied!
Installing Linux isn't difficult tbh, and doesn't /really/ involve any command lines. What tends to make installing Linux "difficult" is the prescence of Windows on the computer already.... and of course have you ever tried installing Windows onto a computer which has Linux already installed without Windows killing Linux? The only bit that people get trouble is with the partitioning of disks, and of course the Windows disk partitioner isn't any better than any command line Linux tool (like cfdisk) to be entirely fair it is far far worse! To install Ubuntu you can just point it at a computer and say "use the entire disk" (same with Debian Sarge iirc) and you get a few other questions (like, which country are you in, what is your keyboard layout etc.) and it installs in far less time than Windows will (without the added "fun" of downloading all your Windows drivers+updates+software you essentially need).
Thanks Adam
The message 20051109105854.GF11826@thebowery.co.uk from Adam Bower adam@thebowery.co.uk contains these words:
/snip/
Installing Linux isn't difficult tbh, and doesn't /really/ involve any command lines.
I'd dispute your first statement, vigorously - I've had problems not installing S.u.S.E., installing Mandrake, which went on, but consistently froze when the logo appeared, Mini Linux which did sweet FA, and now Debian Woody. I can't get Python's fdisk to play nicely either.
What tends to make installing Linux "difficult" is the prescence of Windows on the computer already.... and of course have you ever tried installing Windows onto a computer which has Linux already installed without Windows killing Linux? The only bit that people get trouble is with the partitioning of disks, and of course the Windows disk partitioner isn't any better than any command line Linux tool (like cfdisk) to be entirely fair it is far far worse!
Now I've sussed cfdisk, it's easy, but some of the commands along the way were a bit abstruse.
To install Ubuntu you can just point it at a computer and say "use the entire disk" (same with Debian Sarge iirc) and you get a few other questions (like, which country are you in, what is your keyboard layout etc.) and it installs in far less time than Windows will (without the added "fun" of downloading all your Windows drivers+updates+software you essentially need).
Hum. I could download Sarge from one of Zetnet's Debian mirrors (http://debian.zetnet.co.uk/ - ftp://debian.zetnet.co.uk/ - rsync://debian.zetnet.co.uk/) but...
On Wed, Nov 09, 2005 at 02:31:59PM +0000, Anthony Anson wrote:
The message 20051109105854.GF11826@thebowery.co.uk from Adam Bower adam@thebowery.co.uk contains these words:
/snip/
Installing Linux isn't difficult tbh, and doesn't /really/ involve any command lines.
I'd dispute your first statement, vigorously - I've had problems not installing S.u.S.E., installing Mandrake, which went on, but consistently froze when the logo appeared, Mini Linux which did sweet FA, and now Debian Woody. I can't get Python's fdisk to play nicely either.
From the sounds of it you aren't having much luck installing Windows
either ;) tbh if you are having that many problems with so many distributions I'd suspect something is seriously wrong with your hardware or similar.
Thanks Adam
The message 20051109153344.GI11826@thebowery.co.uk from Adam Bower adam@thebowery.co.uk contains these words:
I'd dispute your first statement, vigorously - I've had problems not installing S.u.S.E., installing Mandrake, which went on, but consistently froze when the logo appeared, Mini Linux which did sweet FA, and now Debian Woody. I can't get Python's fdisk to play nicely either.
From the sounds of it you aren't having much luck installing Windows
either ;) tbh if you are having that many problems with so many distributions I'd suspect something is seriously wrong with your hardware or similar.
Two - well, three different machines.
The first was a PIII-450 which *DID* have problems, and there was no way Win 2000 would go on - it started from the (SCSI) CD-ROM, but when it needed to refer to CD again, it refused to find it.
The same CD installed like a dream on a 233MMX.
The box I've been trying to put Woody on (AMD-900) seems OK, and when I changed to it, Win 2000 went on like clockwork. However, now you come to mention it, the board in the box I'm trying to put Win 98 on has the same PIII-450 and board as the box which wouldn't install Win 2000, so it may well be faulty in some way.
However, it did have Woody on it before I rebuilt the box with the AMD-900 and its board.
I think I might reinstate the default settings in the BIOS, and if that doesn't work, reinstall them. Thanks for reminding me.
On Wed, 2005-11-09 at 16:51 +0000, Anthony Anson wrote:
The first was a PIII-450 which *DID* have problems, and there was no way Win 2000 would go on - it started from the (SCSI) CD-ROM, but when it needed to refer to CD again, it refused to find it
That is a very common thing with Windows 2000/NT and some SCSI controllers. There is some keypress (F6 ? I can't remember) that has to be made at an exact point during the install phase (at least 2000 prompts for it *I think*) at that point you pop your SCSI drivers on a floppy and point it at them.
The reason it boots from the CD and then refuses to find it is that before the installation kernel loads everything is being done in legacy emulation...at the point the installation kernel loads if it hasn't got the correct SCSI drivers it is a bit stuck.
Funnily enough some people installing WinXP on modern SATA or on board RAID machines have to play the same game even today.
The message 1131570239.3072.435.camel@localhost.localdomain from Wayne Stallwood ALUGlist@digimatic.plus.com contains these words:
On Wed, 2005-11-09 at 16:51 +0000, Anthony Anson wrote:
The first was a PIII-450 which *DID* have problems, and there was no way Win 2000 would go on - it started from the (SCSI) CD-ROM, but when it needed to refer to CD again, it refused to find it
That is a very common thing with Windows 2000/NT and some SCSI controllers. There is some keypress (F6 ? I can't remember) that has to be made at an exact point during the install phase (at least 2000 prompts for it *I think*) at that point you pop your SCSI drivers on a floppy and point it at them.
Yes, that's the one (I can't remember which keystroke either), but it didn't help to install the driver. (I have it on CD and floppy.)
The reason it boots from the CD and then refuses to find it is that before the installation kernel loads everything is being done in legacy emulation...at the point the installation kernel loads if it hasn't got the correct SCSI drivers it is a bit stuck.
Funnily enough some people installing WinXP on modern SATA or on board RAID machines have to play the same game even today.
Why am I not surprised?
On Wed, Nov 09, 2005 at 09:03:58PM +0000, Wayne Stallwood wrote:
On Wed, 2005-11-09 at 16:51 +0000, Anthony Anson wrote:
The first was a PIII-450 which *DID* have problems, and there was no way Win 2000 would go on - it started from the (SCSI) CD-ROM, but when it needed to refer to CD again, it refused to find it
That is a very common thing with Windows 2000/NT and some SCSI controllers. There is some keypress (F6 ? I can't remember) that has to be made at an exact point during the install phase (at least 2000 prompts for it *I think*) at that point you pop your SCSI drivers on a floppy and point it at them.
Yup, F6 is the magic key. Windows XP does this also, of course i'm not quite sure what happens if the machine doesn't have a floppy drive... and/or you don't have the drivers on a floppy. Then, Windows is supposed to be easy to install ;)
Adam
On Wed, 2005-11-09 at 21:59 +0000, Adam Bower wrote:
Yup, F6 is the magic key. Windows XP does this also, of course i'm not quite sure what happens if the machine doesn't have a floppy drive... and/or you don't have the drivers on a floppy. Then, Windows is supposed to be easy to install ;)
There is actually a process where you can slipstream the correct SCSI drivers into the installation media. Of course in most cases it is easier to just (even just for the purposes of the installation) plug in a floppy. Although I have in the past encountered SCSI drivers that wouldn't fit on a floppy.
Actually slipstreaming installation disks has always fascinated me, on one hand they tell you not to make copies of the installation media, on the other they endorse (and provide the tools) to make your own slipstream installation disks.
But yes you are right it's always something I bring up when somebody complains about how hard Linux is to install
On 11/9/05, Wayne Stallwood ALUGlist@digimatic.plus.com wrote:
Actually slipstreaming installation disks has always fascinated me, on one hand they tell you not to make copies of the installation media, on the other they endorse (and provide the tools) to make your own slipstream installation disks.
"Do not lend or make illegal copies of this software"
You can make legal copies :-)
Tim.
The message 1131579705.3072.452.camel@localhost.localdomain from Wayne Stallwood ALUGlist@digimatic.plus.com contains these words:
On Wed, 2005-11-09 at 21:59 +0000, Adam Bower wrote:
Yup, F6 is the magic key. Windows XP does this also, of course i'm not quite sure what happens if the machine doesn't have a floppy drive... and/or you don't have the drivers on a floppy. Then, Windows is supposed to be easy to install ;)
There is actually a process where you can slipstream the correct SCSI drivers into the installation media. Of course in most cases it is easier to just (even just for the purposes of the installation) plug in a floppy. Although I have in the past encountered SCSI drivers that wouldn't fit on a floppy.
I rather think that some ATI graphics cards wouldn't, maybe even Linux drivers for them.
Actually slipstreaming installation disks has always fascinated me, on one hand they tell you not to make copies of the installation media, on the other they endorse (and provide the tools) to make your own slipstream installation disks.
They (even M$) sanction your making one for backup purposes.
But yes you are right it's always something I bring up when somebody complains about how hard Linux is to install
Minds work in different ways. I'm sure you'd pick up and retain pootery stuff much better than I. My short-term memory alway has been atrocious, possibly due to lead poisoning when I was an anklebiter.
Because I've installed versions of Windows many times over, I find that easy. (Until something goes wrong, and I have to unforget something very pootery...)
Give me a set of bench tools though, and I could devise ways of making really complicated items out of a variety of materials, and carry out the task, down to hardening and tempering steels without the use of an oven.
On Wednesday 09 November 2005 10:27, Bob Dove wrote:
Hi Folks,
Installation CDs and pre-installed O/S plus recovery disks.
I have always installed from a full O/S disk. My daughter and several of the outlaws have bought systems with pre-installed O/S and recovery disks (Tiny and Acer). Initially, these boxes had Win95. Recovery on these machines was in fact a reformat and copying of a 'mirror' image and not a full version. I upgraded my sys to Win 98 and eventually 98SE (do you think I'd admit to upgrading the outlaws?) Currently, because Photoshop CS demanded it W2K (which is absolutely with no exceptions they flakiest O/S I've used - and I started with CP/M! Fond memory says W3.11 was the best.
Well I remember the downturn that was windows 95 also. I worked with Win3.11/NetWare networks and I can honestly say that (whilst 3.11 problems could be a *real* nightmare) 95 struck me as them introducing a CD full of nasty problems then scrabbling to turn it into a viable software product for years afterwards.
Preferred dos myself, but hey.
To me, Microsoft were once a half decent outfit, whatever people might say.
That's part of why I now use a superior environment for work and play.
I now have two towers and two USB externals. The 'twin towers' each have two HDD. The reason for this is that initially a refusal to boot up and even acknowledge the presence of emergency repair disk in floppy drive or the installation CD in CD drive caused my local guru to pronounce the HDD dead. I bought and fitted new drive, reinstalled every thing and fitted (after setting jumpers) 'dead' drive as slave in the hopes of being able to recover data including a large number of scanned images. Lo and behold, the 'dead' drive was seen and all the data was there and could be accessed. So verily the dead drive was resurrected! The next time the 'C:' drive 'died' on me, it was another trip to PC World for another HDD and again installing and loading O/S. This time 'dead' drive went into one of those new fangled (at the time) external USB drive boxes where it remains. As I said - two boxes and now six HDDs later have lead me to believe that it is software (namely windoze) that is at fault, not the hardware! Possibly a viral infection could have caused it but who knows? Next failure will see a smaller drive installed as 'C:' as it will in fact only contain O/S and those programs that won't install anywhere else but C: Why smaller? It takes an age to scan for Virii or defrag big drives! Incidentally, the latest reformatting because windoze wouldn't boot resurrected a dormant Linux partition which the system labelled C: and windoze took itself off into a second partition it named F: I wonder how long before I have to repeat the exercise? Now come the question; with multiple hard drives installed, can Linux install and boot from a second hard drive D:?
Certainly, most modern installers will help you out by allowing you to choose where to put / and swap.
Having windoze and Linux in separate partitions on the same hard drive made me give up on Linux.
It's like this - if you want to partition your drive up amongst different operating systems, then once you're comfortable with partitioning it's easy.
It kind of works the same whichever OSes you're installing together, it's not just a linux thing :)
If you are interested in getting more comfy with partitioning, in my experience the best way to teach people about partitioning is to give them VirtualPC (Although less so recently) or an equivalent, one or more OS installation disks, hammer home the difference between a virtual hdd and their real hdd and leave them to it. They soon come back ready to partition stuff and understanding how not to wipe everything off the disk!
Reading these mails - your comments re operating/installing Linux is absolutely frightening.
To be honest, there's been a lot of guff posted around here lately about that if you ask me.
Pretty much any major distribution is now a piece of pie to install.
Debian Woody can't be taken as a fair example of a current Linux installation, if you're into "end user installations" it's probably more representative of 5 years ago than anything else.
A 'simple' installation CD that injects Linux onto a hard drive and which comes up with a desktop 'just like windoze' (or Mac O/S) is all 99% of PC owners want.
Then fear not, all you have to do is target your requirements at this specific area. The Mandrakes, Ubuntus and SuSEs of this world all provide varying degrees of this.
There will (hopefully) never be a single, homogenous standard of usability in the GNU/Linux world, because everyone wants different things, so some distros will not be putting 100% focus on, say, usability.
This is ideal, because everyone can get what they want, and the different motivating factors (Militantly Free Software, commercial Usability, etc.) produce different types of advances that can benefit us all.
We don't want to know about command lines - just icons on the desktop just like the original Digital Research GUI that all other O/S desktops have copied!
I think, and this is just me, that in order to really get an advantage from upgrading to a GNU/Linux, you're going to be best not shying away from the console anyway.
There really is nothing inherently bad or unusable about consoles.
As an aside, there's *got* to be some way to remove the fear of the console for the average user. Whether it's consoles in funky anti-aliased truetype fonts with images/music/css theming/whatever in a gnome/kde app, or even turing-type rubber-fork "find me the mp3s I saved in july last year" type stuff, if we could just crack this heinous culture that's built up against using fast, expressive, intuitive typed commands, then people would REALLY be moving to linux.
Whether that's 1. Important or 2. Ever going to happen or even 3. a Good Thing, is another matter, I suppose :)
Thank you for reading my largely subjective opinions,
--
Ten
The message 200511091344.37544.runlevelten@gmail.com from Ten runlevelten@gmail.com contains these words:
Sorry - so full of = 20 &C formatting that it's undecipherable in some places.
On 09-Nov-05 Ten wrote:
I think, and this is just me, that in order to really get an advantage from upgrading to a GNU/Linux, you're going to be best not shying away from the console anyway.
There really is nothing inherently bad or unusable about consoles.
As an aside, there's *got* to be some way to remove the fear of the console for the average user. Whether it's consoles in funky anti-aliased truetype fonts with images/music/css theming/whatever in a gnome/kde app, or even turing-type rubber-fork "find me the mp3s I saved in july last year" type stuff, if we could just crack this heinous culture that's built up against using fast, expressive, intuitive typed commands, then people would REALLY be moving to linux.
I (personally) think a key to selling the console/command line would be to demonstrate what you can do with it, which you can't do, or only with difficulty, using point&click.
People can see the theoretical argument that with a GUI you can only get what has been planted in the menus, and anything else is unavailable, but will not feel moved by this if they don't see that they might need things not in the GUI.
At this point I think one can divide "People" into two camps (with some overlap).
There are those who have come to see using a computer as being like a trip to a brightly lit superstore. Anything that's there that you might like to have is easily visible and ready to grab. Their needs for what they'd like to have, have been formed by repeat visits to the superstore.
And there are those whose needs are formed by how life impinges on them, and they look for a way to turn their computer to fulfilling these needs. They are like the folks who will go out and hunt in all sorts of places for the precise unusual thing they've set their minds on.
Then there are little practical details, like the fact that most simple things are more wuivkly anf easily done via the command line -- conpare typing "ls" with pulling down a menu, clicking on drive letter to open a menu of files and subdirs, and so on.
On the other hand, is can be easier to use a menu system for certain programs (xcdroast comes to mind) where the everday options are can be encapsulated in a few easily accessible menus, as compared with the rather hairy and long command lines you would need to do the same job via a console.
So in that sort of respect it's horses for courses, and you'll be building a fence against yourself if you reject one or the other.
I think the GUI/console divide is a relatively recent development, in my estimation since 1995 or later, probably nearer 2000.
Prior to that, most users still had a memory of DOS, and command lines were in everyday use even in that world.
And of course the Unix tribe of that era (or any other) needed no persuasion of the value of the command line.
Best wishes, Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 09-Nov-05 Time: 14:41:03 ------------------------------ XFMail ------------------------------
The message bdfoto%40tiscali.co.uk$80.47.174.218$.001701c5e518$887c9910$daae2f50@bdf2 from "Bob Dove" bdfoto@tiscali.co.uk contains these words:
/snip/
Re what might have been above if I hadn't snipped it, I agree that 3.11 was the best Windows version, but preferred CP/M
Reading these mails - your comments re operating/installing Linux is absolutely frightening. A 'simple' installation CD that injects Linux onto a hard drive and which comes up with a desktop 'just like windoze' (or Mac O/S) is all 99% of PC owners want. We don't want to know about command lines - just icons on the desktop just like the original Digital Research GUI that all other O/S desktops have copied!
Ah. Yes. Well, I *DO* want command line as well as GUI, but I'd settle for either to begin with. But I'd agree with you: I read some of the steps in setting-up Woody and mutter expletives to myself. How the hell do I know if I want which of a list of locales, whatever they are. I checked them all, just in case. (I have a suspicion they might relate to languages/text sets supported, but...)
Do I know what Privilege separation is? Do I ****! And it interacts badly with PAM - whoever *SHE* is...
And it fails to find my (hardware PCI modem.
(Knoppix 3.1 (which I know is elderly) won't run on this machine because it can't cope with the ATI Rage 128 graphics card.)
<hair mode="tear">