Oh, and try using the test26.s stock kernel with 10.2.

What are bonecrusher's sata iso disc and shilo's website? Do not get yourself confused. I managed to install Slackware and Lilo on my AMD64 without any problems. After installing the packages, did you select to use the default kernel or a kernel from Slackware CD?

I have my SATA HD identified as /dev/sda as well under Slackware. However, yesterday I installed the 64-bit version of SuSE 9.1 and it identified my SATA HD as /dev/hde. Since then my SATA HD started to make some noise which I am not comfortable with.

Nothing wrong w/ that. It's actually a technique of dual-booting with hostile versions of Windows that won't let lilo own the MBR. It also allows you to install and reinstall Windows as many times as you want and it will never disturb your other operating systems. From my own experience, my SATA drives will not boot from the linux superblock, so either I use the MBR or a floppy to dual boot. MBR is out of the question from XP's perspective, so a floppy is my only choice. It also allows other users to use your station without knowing that there is another OS installed. It will be completely transparent to them; which is handy because my wife is a total Microsoft junkie.

Just so you know with 10.2 there is a sata kernel provided. No need to use anyone else's modified CD's. I know the one you used and had to use it once before sata support came default, but if you're using the one I think you are, it's old as hell. You can just use the regular 10.2 install cd's(or dvd) and at boot prompt choose sata.i as your kernel.

My experience was with a Nforce 3 250 and slack 10. i was not able to get anything to happen. it was as if lilo never existed the only thing i have left to try is physically removing all drives but the one i want. and see if that works. i will likely try again the next time i have a chance to yank drives from my system getting inside is somewhat of a issue. but you are the first person to say they were able to use lilo with an amd64.

Lilo has worked perfectly for me on my AMD64 3200+. I've *never* seen a problem with it. The problem could more be the nforce board you're using. I know there has always been slow linux support for those things and have avoided them like the plague. I have a Shuttle SK83G with a VIA K8M800 chipset and it has been supported since I bought it over a year ago. Everything from sound and ethernet to SATA. What more people need to do if they are going to be spending alot, or any amount for that matter, of money is research research research.

I spent 2 months making sure all the hardware I was buying was linux compatible. Surprises suck sometimes. Not only look for what problems linux users have had with mobo's and chipsets but also windows users. If a board has some fault where it won't detect cpu clock speed right that's going to affect you no matter what os you use. Websites like amdmb.com are a good place to look in the forums and see what people that have the hardware for more then a week are saying about their hardware 6 months after purchasing it.

If a mobo dies a slow death over a few months I wouldn't want to find that out after purchasing $1,000 in computer equipment. Computer hardware can be a crap shoot but you can put the odds in your favor if you research for common or unusual problems prior to purchasing. Newegg.com has user posted comments. Those can be useful as well as *actual* tech site reviews. Not those crappy ones from cnet. Again the best place is forums on tech sites. Life can be easy or it can be hard. I like putting together a desktop or server and just installing and using it. I have had to go through hardware hell before and vowed never again. Besides, it's your money and you should use it on things that work.

Just my 2 cents...