danleff

Try the suggestions in this how-to. See if that helps at all.

Try this. I wonder if you are not in the audio group. I'm doing this on rote memory. As root user, try this in a console; adduser (your login name) audio So in my case it would be; adduser danleff audio Reboot and see what happens. Turn up the volume on the speakers a little.

Look at the "related threads" section below. There are quite a few posts on this subject. I don't use COD, so I can't be of much help. But there are others that do and can respond. It also mat be helpful if you be more specific. Post the distro and version of Linux that you are using and where you got it/what type of COD package that you installed.

You have a burned copy of Win 98? Don't tell Mr. Gates! In these old HP systems, the drives are often funky. Too many variables...the ability of the drive to read CDRW vs. cd-r disks, how they were burned (speed and specs. - joliet vs....) and the quality of the media they were burned on. In terms of cd's that come with a book or magazine...who knows what the issue is, damage (look on the underside of the cd disks), exposure to magnets, whatever. Try the disks in another system, if possible and see what you get. If the book included cd's work, you know it's the cdrom drive. If the others work also, that's the problem. Mel is right. I neglected to note the ram issue. Vector Linux may work. Puppy Linux may need 128 mg ram, as it runs totally in ram. Live cd versions are likely to be an issue, since they run completely in ram. Mel eluded to dial-up issues, which are a problem. often the downloads on dial-up are unreliable when downloading iso images. You need to check the md5sum of the donloaded images before burning them to assure that you got a good download. Maybe download them with an ftp manager like SmartFTP, that can resume interupted downloads. That reminds me, I need to update my article on burning iso images.

It sounds like you did an upgrade not an update. My guess is that you are booting to a new kernel? If so, alsa needs to be reinstalled for the new kernel. Are there any error messages on boot, when you get KDE that complain of dsp not being found? But, make sure that the sound is not really muted. At a console terminal, as root user, try typing in alsamixer and set the volumes up to almost the red.

I'm going to refer you to the DSL wiki page, that describes what to do. The link is here. But, let me make a few comments. 1. Did you burn the cd as an image, not a data file? 2. Did you burn the image at 8X or slower? 3. Is the bios set for the cdrom drive to be the first boot option? 4. Are you using a cdrw disk or cd-r disk of good quality? 5. Are you using the same cdrw drive to boot the cd, or an older cdrom drive? 6. Are you using dial-up to download the image and did you check the md5sum of the iso file after you downloaded it to make sure that the image was valid? DSL is a very small distro. The file structure seems fine, from what you described, so it looks like you burned the image correctly. Don't expect that you should see more files on the cd than you do. DSL is built on a small platform. Take a look at my how-to about burning iso images here

Try the following; apt-get update to update the apt database (assuming you have repositories already set-up) For X, do; apt-get install x-windows-system Or, you should be able to do; apt-get install kde or apt-get install kdelibs This should get you started. See this article to get some ideas. Once the GUI is up, then do; apt-get install synaptic This will give you the Synaptic package manager, which should be easier to use.

Try going to start-->multimedia-->volume control and see if the volume is turned up, or if the sound card is seen. Set the volume up to almost max, just as it goes from green to red for the first setting on the "master" setting. If the sound is not found or set up, let us know and we can go from here. The other way to do this is through the command line and alsamixer.

Commercially burned software disks are made to run on most older cdrom disks. This is why the Windows 98 disk works on the system. The older the cdrom, the less likely that home burned cd disks will boot correctly on the cdrom. Especially cdrw disks burned at too fast speed. CDRW disks do not work well on these older systems. I have tried several times on these old HP systems. CD-R disks may work, but they must be of good quality, rated for the speed of the cdrom drive and be burned very slow, say 2X or 4X. If you still have problems, you can either buy a newer cdrom disk drive, or a commercially burned cd of your favorite distro. They can be had fairly cheap, say at Linux Central or your favorite site.

I don't use raid arrays, but the concepts are not hard to figure out. Where did you tell FC4 to install grub? The MBR? When you did the install of FC4, what partition/drive did you install it to. what was the designation, hda, sda...? You can pop in the 1st FC4 disk and boot from it. Type in Linux rescue at the install screen and you should be able to get into Fedora, if changing the bios boot order does not work. Can you post the contents of the /boot/grub/menu.lst file? Also, type in terminal window (as root user), the command fdisk -l and post the results, if possible. That is the letter l in -l, not the number 1.

Do a Google search, but I don't think that Fritz 8 works in Wine. See this thread. At least not well. The link gives some other suggestions.

Go to the Winw HQ website documentation page at this location. What trouble are you having?

Did you check to make sure that the required libraries are installed for Firefox 1.07? Remember, Mandriva LE is just what it says, Limited Edition. You most likely don't have all the required packages installed to install from source packages. Also, is there a reason that you are not using Firefox from the Mandriva database through the software installer? See this link as well for further information.

Well, with the very limited information that you have given, I assume that you know how to compile a driver for this elusive webcam in the distro that you are using. The link to a driver, is found here.

Can you be a little more specific? Is it a problem with the resolution that you are getting? Theses cards should have good compatibility with Linux in general.

First, let's err on the side of caution, especially if this is your main system. If you are installing another flavor of Linux just to try it out, I suggest putting the third OS on a second hard drive. Your request is too long for a real post on this forum, but take a look at this thread. You did not post ant specs. on your system, which would be helpful for us to guide you more effectively. Assuming that you have enough disk space, you can resize your current partitions with a partition manager, like PartitionMagic or 7 Tools Partition Manager. Then install Mandriva, which will give you the option when it is finished to boot XP, SuSE and Mandriva. But, this requires a little knowledge on Linux, so that when you install Mandriva, you know what partition to use for Mandriva and not overtake one of your other OS installations. Make sure if you decide to do this, that you defrag your Windows partition first and back up your data files. This assures that you dont lose any files that may have strayed toward the end of your Windows partition and may get lost when you resize your partitions. But be aware, if you use only one hard drive, no guarantees. We have seen too many folks who try this and make a mistake, then post that they can't boot into Windows or their previous Linux OS anymore. The tools in Mandriva are good, but you need to keep track of your partitions and their linux assignment, just in case. And of course, when doing your most recent install, picking the correct partition for to install to. Having two hard disks reduces this error. I have no less than eight Linux distros on my current system, but not without some mistakes on my part!

Add one or the other command to grub at the kernel line. Depending on what distro you are using right now, at the grub screen, either you hit the esc key, or "e". Then make sure that the line highlighted is the kernel (hd0,)...line. Hit "e" again and you will be at the edit mode for that line. Use the forward/backward key to make sure that you are at the end of the line. Add the command, making sure that there is a space after the last entry and your command addition. Hit the enter key, then "b" for boot. Yes, it is only good for that boot. But if it works, you can add the command to the /boot/grub/menu.lst file, using your favorite text editor. It will then stick. The editor that you use needs to be as root user.

The Windows cd is not able to read Linux partitions, so it thinks that there is no usable hard drive on the system. If you installed Linux and allowed it to take over the hard drive, then this is the issue. Reformat your hard drive, making the hard drive either fat32 or NTFS and install XP. But, let's be clear on what you are doing. Was this a stock install of Windows XP, or are you using just Windows XP on this system. In other words, is the XP disk the one included from Dell, or your own full copy of Windows XP. If this system originally had the Dell install of XP, then the partition structure is a little different on your system. Dell often has a small hidden partition on the first part of the hard drive, that holds recovery data, along with some other information. In either case, if you no longer have XP on the system, either use the Dell recovery disks, or your full copy of XP to do a reinstall of XP. Then install Linux and follow the grub instructions provided by last post.

Is there a reason that You are using Fedora Core 1 rather than 4? If you have a newer system, then support for your hardware may not be in Core 1. This would be especially true if your video card is a newer model. Without knowing some of your system specs., it's hard to know what the issue is. Could you post some specs. so we can assist better? What system is this? Can you post the video card that you are using and the monitor make and model if this is a self-built system? Or, the system make and model if it is a stock system, say a Dell or Gateway system.

An ISA card, correct? If you are comfortable with adding commands, look at this link. In order to compile source packages, you must have some compiler packages installed. Did you do a standard installation (accept the Fedora default suggestions) or install "everything?" Is the card recognized in Fedora's Network configuration tool? Did you attempt to set up the card during the installation at the hardware configuration window? The compile may have failed as you don't have the kernel sopurce package installed, as well. The web page and/or readme/install file of the driver package should explain what is needed. Additionally, the web page that you got the drivers from may tell you this as well. Grub ius actually easier than lilo to add command actions to, if needed. But, you will need the irq of the card to know what to set. The link that I gave should assist with this. If the above link does not work, please post what system/motherboard that you have and possibly some links to web pages that you have referenced. If the above is too confusing, and you have a pci slot, the best solution would be to get a Realtek or Linksys NIC card and the problem will be solved. At about $10.00 USD this may save some headaches.

It depends on what you are now going to do with the system. If you are going to install Windows, the steps are a little more complicated, as the Windows cd will not see Linux partitions to start the installation, especially if you used the entire hard disk to install RedHat. Are you going to install Windows, or another flavor of Linux? If Linux, then just do an installation of the new distro and the partition will be written over by the new distro. If Windows, you need to format the hard drive. There are a number of ways to do this. Let us know what you plan to do and a little information about your system. This will help to guide us properly. Especially if this is a Dell or Gateway system. The rules are a little different.

ATI graphic cards have always been an issue. Linux support is limited, although getting better. ATI is getting the idea. Search Google on your card and Linux and you will see what I mean. I have never had any problems with NVIDIA cards in any of my systems. I know this is not an answer, but if you can wait for the final Mandriva release, support may be better in that release. I know they are actively working on it.

Do you have an internet connection in the system now? Did you set up the NIC card during the installation? Are you using dialup, DSL or broadband? Sometimes, the mirror that is doing the update fails. I have had this problem from time to time. You can try selecting a different mirrot for updates.

I had the same problem with one of my systems recently...never figured out why. It just went away. I found once that a faulty cdrom drive was at fault. When I looked at the log messages, it showed a problem. Does the freeze happen when accessing a cdrom disk? There should be no reason to disable USB. More likely, try diabling PNP OS in the bios. Look in the bios under PNP Configuration. If this does not solve the issue, which bootloader are you using, Grub or Lilo? You may need to add the noapic option to Grub or Lilo. Let us know what bootloader you are using and we can add this to the command options. Newer motherboards sometimes need this option added.

Apt-get works if you have sources in the /etc/apt/sources.lst file. If you did a network install from floppy, then the source list is via the net. You need a network connection to access the packages. If you installed from cdrom disks, then the apt sources include the cdrom disks. dpkg is local, so you need to have the package(s) that you want to install on the system locally. apt-get resolves any deprendent packages that may also be needed without you worrying about them and resolve any deprendent packages that may be needed. In your case, you were lucky that only the single package was needed, as pcmcia was working originally. You may want to try Synaptic to install new packages, which has a nice gui interface. Now that you have a working internet connection, just type as root user in a console; apt-get install synaptic and it should be installed. Using Synaptic, you can see what any dependency packages are and take control of the process much easier.