Pzatch

Have you tried setting the connection to DHCP in the MCC?

What kind of switch?

What exactly is the error your getting. There are several problems a drive could have with linux that have nothing to do with linux specificly. If all installs failed then its more than likely you have the computer set up wrong for linux. We need the specifics in order to help better.

Great because my local moron said he had no idea. The guy has a hundred used laptops for sale a doesn't know his but from a hole in the ground. Its a small shop though.

I'm limited to only english and quite limited at that. So sorry I just can't help you. You could be proud though thats the first I've ever heard of a problem like that. Though I'm pretty sure it has probably happened before.

Learn love english. :D PC by PC we're taking over the world!!!!

I'll have a talk with my local hardware guy. He does a lot of laptop work and should know just what to do.

Linux can't use just one partition. It needs at least 2 one for / (root) and one for /swap (the swap partition) I use 10 The first for windows. So small now I can't load any games into it. Mandrake 9.1 / I use 2.5 gig for that. Its a little big but hey I got the room. /user 3 gig. /var 1 gig Hey I got the room. /home 20 gig WAY more than I need but hey.... /tmp 1 gig The Gimp needed a bigger temp file area than normal for some REALY big files. /swap 1 gig And the second drive Mandrake 9.2 with 2 basic partitions. / (root) /home the swap for 9.2 and 9.1 are shared. And the last 10 gig is a big empty FAT32 partition.

What did the button say next to it? No manufacturer even puts a button on something with out labling it. Did you try pushing the button. WOW

You might be better off putting lilo on the computers hard drive and having it point to the USB device just like the other post said. The real problem is USB drives need software to run and if your not loading it first then your not running the drive. Untill the drivers are fully placed into the BIOS then its going to take some jumping though hoops to get them running other wise.

Basicly your right. On the back of any hard drive or cdrom are a set of jumper pins. On new hard drives they are labled so you won't have to flail around blind like I did at first. One could say master/single - This is used for the first drive or primary. Normaly its used if you have only one drive or this is the first drive in the pair that can go on an IDE ribbon cable. The second should be slave - obviously this meens that its slave to the first drive or the second on the ribbon cable. The third is for cable select - This option was brought about by the fact that people got too confused between the first two choices. you use this one if you can't figure out which drive to make first or second. A forth pin set might be for used just holding the jumper pin untill you need them. Basicly just a blank. Does nothing. As with anything though your pin set is probably a little different only because the manufacturer wanted to be different and origional. The pin layouts are now written on the top of the drive normally. The same is used for DVD and CD roms. Oh yes and USUALLY the drive on the end of the cable should be designated the master but sometimes it works the other way around. I too started doing this hardware stuff when MFM drives were common. I hated hand editing the bios settings for each drive.

Check the VIA website. they have a lot of support for Linux. Though the list of chipsets and all possible combinations is a little long and confusing.

I'm not on a MAC but i just had a similar problem installing 9.2 on my system. Got almost all the way though the install then just a total stop and after about 3 minutes of just letting it sit my keyboard lights started doing the same as yours. I switched to a different screen and found out it was a bad burn of a bad download. So I redownloaded the ISO that was bad and reburned at the slowest spead. Try that and post back.

Just wait until the court day gets closer. You'll see SCO trying anything including the totaly ridiculous just in hopes of getting a little more good press before everything in court comes out in public and they look like fools. I wouldn't be suprised if just before court time they "find" evidence of actual physical breakins into their offices and theft of their code. Or even supposed intimidation threats from linux advocates. I bet SCO puts off the court day until all the executives get their cut of the inflated stock sold. Then the exec's will resign, retire, get fired by a buddy, move to a different division or just basically skip out and leave the next patsy to take the heat. Like rats on a sinking ship. We can write the letter but the judge has in all probability already heard the same arguments from the people already involved. We can write a 'friend of the court' letter giving our opinions and ideas but it would have to be truly sincere and have well reasoned arguments. Whats the record of the judge who's hearing the case? He might not take kindly to letters and think its an insult to his intelligence. He is just a person after all. He also might not know that SCO is owned in part by microsoft. Something over 15% from what I hear. It could be enough that M$ could be brought in as a witness. Do we have a local legal beagle to help out on this one?

Thanks Steve after you said it I now remember hearing about the scsi writing thing. your probably right about his DVD-R problem also.

I'm talking off the top of my head here since I don't have a dvd drive yet but shouldn't the drive be listed as a scsi device instead of a hard drive? /dev/hdb6 /home ext3 defaults 1 2 /dev/hdc /mnt/cdrom auto codepage=850,noauto,iocharset=iso8859-15,nosuid,ro,umask=0,user,nodev 0 0 /dev/scd0 /mnt/cdrom2 auto codepage=850,noauto,iocharset=iso8859-15,nosuid,ro,umask=0,user,nodev 0 0 shouldn't it say something like: /dev/scd1 /mnt/cdrom auto codepage=850,noauto,iocharset=iso8859-15,nosuid,ro,umask=0,user,nodev 0 0 or something like that. Someone correct me I'm sure I'm wrong.

Windows doesn't really care if the drives are set master/slave or cable select. So go ahead and set the first for master and the second for slave. You might have to reinstall the boot manager from the first mandrake disk in rescue mode, but that should clear up your problems with running windows and linux. Just don't change and partitions and definately don't reformat any of them.

As a fall back any lawyer I believe could argue that since the GPL was written years ago and subsequently followed and accepted by the majority then it should stand as a legal document. Sco shot any argument against this down when it released a copy of the GPL and followed it as though it was a legal and binding document. Thats also the part they are saying that they didn't understand fully when they did it. Unless the GPL could be shown to be against any other longer accepted law then the states judges will find it very hard to shoot down. Now that most every other company has accepted it as a binding contract then it will probably be upheld.

Roland scary. I've never been sued so I don't know: what could happen if when sued you write a letter to the court saying that you have no time nor money to wast with your aggressors stupidities and don't care at all ? Well here in the states they just kindly send you another letter ordering you to make it to court then if you miss the second time a nice sherif comes to your house and escorts you to court. If you loose the case and can't pay then you stand a good chance of having a new home with a few new overly affectionate room mates. :o

The posters to that offer really look undiased.

Make sure the jumper pins on the back of all drives are set for master/slave and not cable select. Microshaft handles cable select by software i guess and linux doesn't as of yet. Try to just reinstall your boot loader if it's in the MBR. It should then find the right place for everything and get you going again.

Its always the simple things. Once you figure out the problem. Congrats.

I haven't bought a monitor in 4 years but most used to put their refresh rates and some other details on the back in real small writing. Post back any trouble or error messages.

If you made the boot disk from the 8.2 files then that could be you're problem. Use the boot disk file from the 9.1 disk. Or just have the computer boot to the cdrom.

Try the normal cable for a hoot. Linux might not be using the card for all its capable of. Try using the genaric VESA driver just to see if you can get any kind of color screen. The VESA driver is an old old standard that 95% of cards still use to give a basic screen. Instead of reinstalling try running as root...... xf86config from the command line. This will help setup the hardware and vidio.