danleff

What RPM are you looking to install? Can you give a link or name for the RPM so we can tell what you are doing? Do you have the kernel source installed?

What NIC card is this? Onboard? Chipset? You should not need an RPM to install on most boards.

Assuming that you are using a dynamic IP address assignment via your provider, go to the network configuration (control panel) and re-initialize your NIC card. Look and see if the connection is active and activate it if it is not. What is the output of kudsu -p? Does it show your NIC card loaded as a module? Does ifconfig show an ip connection, say 192.168.2.100? I assume this is a cable internet connection?

Quote: You originally re-installed XP on the primary master drive as the first OS on the system, or hda1, correct? Which is why I asked the question. Perhaps I should have been more clear and said drive "C". But, i am used to speaking in linuxease. Glad you got it sorted out. What packages are you looking for? You should have all you need on the cd disks or through the package installer, if you configured a download site. The process if quite automatic. I highly suggest using the package manager, but if you have specific packages that you want to install, let us know.

Mandriva 10.1 requires a Pentium class system andf at least 256 mb of ram. So, you don't meet the basic system requirements for Mandriva 10.1. You can easily add more memory to your system and this may help. You could also try enlarging your swap space. OpenOfficer is also a memory intensive program and I am not surprised that you are having trouble with it. There are less memory intensive office packages out there, like Koffice. Other flavors of linux are less memory intensive. You may want to look at Vector Linux, which can run easily on 64 mb of ram. See this link for an overview of system requirements for Vector. In terms of making a "mini-network" this is quite possible. Since you have a router, you don't need to connect through the old box to access the internet, rather you would connect through you router. This is the easiest method to use, unless you plan on making the old system a server. If you don't need the latest and greatest (not always the case), Mandrake 9 may work much better on your system. It has less memory needs and should run better on your system. Take a look at the DistroWatch site, which will give you a good idea of what flavors of Linux that are out there that may meet your needs.

Try the following. Edit the menu.lst file, or add another grub entry that has these values; title Windows rootnoverify (hd0,0) chainloader +1 makeactive boot If you know how to edit Grub manually at boot time, you can add these values at the command prompt, one by one and see if it works. Then, if it does, you can make the changes stick by editing the /boot/grub/menu.lst file. See the how-to located here Look at section 4.1.2.

It Looks like the kernel is not loading the usb drivers for the drive. Apparently this has been a problem in the new release. See the Ubuntu thread located here. I don't have a solution, but you may want to post the problem on the Ubuntu forum.

So, these were all sata drives? Nice! I think I get it. Good find padmoz!

OK, bear with me. You now have Fedora Core 2 installed... You originally re-installed XP on the primary master drive as the first OS on the system, or hda1, correct? Grub is set up to boot on the master boot record. Could you post your /boot/grub/menu.lst? This will tell me what grub is set to for booting XP. Different versions of Linux and grub do this a little differently. If all the above are correct, then I am interested in seeing where grub is trying to boot XP and if the entry matches where your boot.ini is for XP. You should have an entry like the following; title windows root (hd0,0) chainloader +1 The key here, of course, is where XP is installed and where the boot.ini file is located. You have a complicated partitioning scheme and I want to make sure Windows is installed first as hda1 before we fix it.

Ahh..just another winmodem problem? I have not used modems for a while, but the solution is there. The simple solution? Buy an external serial modem and save a lot of headaches. Make sure that the modem is not a controllerless modem. in other words, a true hardware modem. Ask a sales rep. at any good computer store. If he/she is knowledgable, he/she should know. If you buy it there, you can always return it if they were wrong. DapperDan had a link to one a while back that works. I have a Diamond SupraExpress external modem that works, but they are hard to come by. I think that Dan's was an Actiontek modem, I will try to find a link. P.S. The modem link is here Of course, you can buy it anywhere, Just do a google search.

Your post got me thinking about this, as I am just waiting for a new second sata drive for my system. You need to remember that physically switching drives changes their designations. You need to have the XP drive set up as it was originally for XP to work. The boot.ini file has code that points to the drive where it was when XP was originally installed. The same thing with Grub. Libranet looks for the drive where it was originally installed and it's designation in the /etc/fstab and /boot/grub/menu.lst files. Physically switching the drives confuses the boot files, as they look for things where they were when that OS was originally installed. Can you post the contents of Libranet's menu.lst and device.map files? Actually someone else posted a solution in another thread that should work. But, I would like to see how your system was originally set up when you installed Libranet. You had XP installed before you did Libranet installation, right? What motherboard is this? Does it support both IDE and sata drives? The XP recovery console probably does not load sata drivers before starting, which is why you get the no drives found message.

Simple solution...any reason why you are using RedHat 8 and not Fedora? Life is much easier with Fedora, which has many enhancements.

We need more information. Why do you keep reinstalling XP? Redhat 9 is old and does not sometimes play well with NTFS partitions, if that is what you have for XP. What system is this? is It an HP or Compaq box by any chance? Where did you tell grub to install the bootloader, the MBR, or a boot partition? XP should always be installed first, then linux. You will get different opinions on this, but it makes life easier. Did you allow RedHat to take space from the XP partition, or set up a Linux partition for RedHat ahead of time? Any reason why you are using RedHat and not Fedora? When in RedHat, get into a terminal window, as root user and type in; fdisk -l (hit the enter key) That's the small letter l, not the number 1. Also, a space between fdisk and -l. Can you post the output that results?

Well, the symptoms that you are experiencing to bad disks. Just because you think they should be OK doesn't mean they are. Given the age of the system, the cdrom drive could be at fault also. Can you try the disks on another system? If they work there, you have your answer, the cdom drive. If not, then you know the disks are at fault. Another trick you might try is to boot from disk #2. When you get a message that this is not the first installation disk, switch out to disk #1. See if you get any further with the installation. My guess, cheap disks that your drive can't read. Trying another box or cdrom drive will give you the answer.

In terms of the sound card, I don't know. I should have tried this before, but i have not. What makes you think that you need the kernel sources? It would be helpful if you could post the version of Fedora that you are using, as well as what sound. Onboard? If so, what chipset. This would save us looking it up, since you have the users manual. What NIC card? Onboard? What chipset? It should work out of the box. Did you set up the card during the installation? Broadband or DSL?

Are you using DSL? Try looking at my guide for my wireless card, located here. Also, here. On each page, note the references, as well.

It looks like you know how to partition your drive, so we will proceed as such... Quote: - Is blank space REALLY required in installing linux (say FC4) Any installation requires a game plan. You need to have some space available on the hard drive, whether it be space that you borrow from your Windows drives, or unformatted space. You need to have the space available by either making some empty space available, or allowing Fedora to borrow it from the hard drive. It usually takes space from the last partition, if you allow an automatic partitioning scheme with the Fedora installation. You can also pick the "expert mode" when you reach the partitioning section of the installation and resize to make room. You probably want at least 5 gig of space, depending on what you want to do. About 2.5 for the OS and as much as you want for storage. Quote: - does the partitions names affect anything? No..this is only a Windows issue. Fedora will see the fat32 partitions, no matter what designation they are in Windows. Quote: - Is there chance of missing data from corrupted installing? Yes, this is why you need to defrag your Windows volumes before attempting an install. Of course, this is a good idea if you resize your partitions yourself, to make sure that data is moved away from the end of each Windows fat32 partition and the data is not lost during the resize. Quote: - btw will my "ADMtek AN983 10/100 PCI Adapter" be recognized ok? (i cant go online w/out it) Thank you all. It should. There is little data on this card on the web, but some have reported no problems with this card. If it does not, you can easily buy an inexpensive card for about $10-15 USD that will work fine, either a Linksys or Realtek card. Remember, when you do the installation, make sure that when you get to the hardware configuration screen to set up the network. You need to know if your ISP uses static or dynamic proticol. If you are using cable (broadband) then make sure that you assign auto DHCP at this stage.

Bad signature errors usually mean that you have bad disks. Who knows? Are there any scratches on the cd disks? They could have been exposed to a number of environmental problems, static, magnetic discharge... Do they look like commercially made disks, or homemade? The other possibility is an old cdrom drive. What system (make and model) are you attempting to do the installation on. Older cdrom drives sometimes are not able to read some disks properly. If it is a newer system, consider a newer version of Mandrake, as yours is an older version and may not have the hardware support that you need. The GUI errors are a result of some of the core packages not being installed properly, a sign of bad disk(s).

Try adding this to the menu.lst file; title Windows at sda1 rootnoverify (hd1,0) map (hd1) (hd0) map (hd0) (hd1) makeactive chainloader +1

SLES9 is based on SuSE, owned by Novell now. It is a commercial product. I don't believe it is open source and widely available, Did you do a web search on it? Try a search using "index SLES9." A while ago, I got a free dvd pack from Novell. I'll have to look and see if it was included. Nope, I just looked. You may also want to contact Novell to see if they will extend the trial period, based on your need for it.

You need to be more specific. What distro and version of Linux are you using? ..and are you attempting to run COD using Wine? What version? If Wine, did you install the distro's version of Wine or from source?

Isn't the MadDog a cdrom or writer, not a hard drive?

Do the Linux cdrom disks that you are having trouble with boot in the Vectra? If so, you know that it is the fault of the cdrom drive in the older machine. In terms of the Mad Dog 4 in 1 Dominator, my guess that the bios on the Pavilion is the problem, if you are sure that you jumpered and set the cable to the cdrom drive correctly. Try setting the Dominator to master slave and the cable connection accordingly. Sometimes a bios update will fix such issues, but be aware, that on these older Pavilions, some of the bios information is resident on the hard drive. There is a small hidden partition on the drive that holds some bios data, as well as the recovery data. Make sure that if you try any bios updates, that the original drive is in the Pavilion. HP often uses legacy hardware, so this could be the source of your problem with the Dominator not being recognized in the bios. But hopefully installing Ubuntu on the newer machine and putting it back in the Pavilion will work. Also be aware, that grub or lilo will point to where the Ubuntu installation was on the Vector, relative to how you jumpered it on that system. Since this drive is probably Primary master on the Pavilion, you will need to edit grub, if you jumpered it differently on the Vectra to do the installation. To explain, if you put the drive in the Vectra as master slave, grub will look for the kernel at hdb, or (hd0,1). When you place it back into the pavilion as primary master, grub will need to be editied to hda, or (hd0,0). Of course, if you put the pavilion's drive in as primary master in the Vectra to do the install, the above does not apply.

Please do not post multiple threads. Try to stick with the original thread that you started, so folks can follow what the issue is and what has been tried to fix it. Could you post on the other thread what distro of Linux that you are using and some content of the error messages that you are getting. This would help us see what the issue might be. Did you looke at the other posts under "related threads" to see if your issue is under one of these threads? Your original post is located here

The extra entries are left in Grub, in case the new kernel does not boot for some reason. You can edit the /boot/grub/menu.lst file to either comment out the entries that you do not want, or delete them. I would comment out the lines, in case you make an error editing. I would leave the failsafe entries intact, in case you ned to recover or troubleshoot any issues later on. When you have FC4 up, make sure that you know what the current kernel is that you are running. Type in uname -r and make note of the current kernel. Comment out the lines in the menu.lst file for the grub entries that you want out, starting with the "title" line, like such; #title..... #kernel (hd0,0)/boot/vmlinux (the kernel version to comment out) #initrd (hd0,0).... On your next grub boot, these lines will be ignored.