danleff

No, this is really a Windows type of setting, but your PNP should work in Windows as well.

The first error, ignore, it is related to sync. with the hardware clock. It is harmless. In terms of the NIC card, look in the bios and see if PNP OS setting is set to "Yes" and change it to "no." See if this resolves the issue with the NIC card.

Probably the timeout was not set during the install, or you set it to ")" by picking Windows as the default option to boot. Get into the file manager as superuser and navigate to the /etc/lilo.conf file. Right click and choose kate to open the file. boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message lba32 default=linux image=/boot/vmlinuz-2.4.0-0.43.6 label=linux initrd=/boot/initrd-2.4.0-0.43.6.img read-only root=/dev/hda5 other=/dev/hda1 label=dos Change the timeout value to 50 or 100 (5 or 10 seconds). Then get into a terminal window, as superuser (or just get to the terminal window and type in su, then your root password). Once there, type in /sbin/lilo and wait for the command to alter the bootloader (until you get back to a prompt). On next boot, lilo should pause and allow you to choose Windows or RedHat.

You can actually run the install from the raw iso files that are on the hard disk with a Mandrake boot cd. They just have to be the actual iso files somewhere on your hard drive. I just did this about a month ago. The drawback is adding packages later on. If you would like, I can post how I did it over the weekend. The boot cd will ask where to install the files from. You pick the hard drive and point the boot disk to the location that the iso files are on. No need to uncompress the iso files. But, if you are making cd disks, you need to burn the iso images as that, images, not as data disks after uncompressing them. See my how-to here.

OK, it's all in the syntax and how grub is used in each distro. Try changing the entry from; title Fedora Core 3 rootnoverify (hd1,2) kernel /boot/vmlinuz-2.6.9-1.667 ro root=hdb3 initrd /boot/initrd-2.6.9-1.667.img to; title Fedora Core 3 root (hd1,2) kernel /boot/vmlinuz-2.6.9-1.667 ro root=hdb3 initrd /boot/initrd-2.6.9-1.667.img By the way, just check to make sure it is hdb3 is root in /etc/fstab in the Fedora install. It should be the first entry, such as; /dev/hdb3 / ext3 ................ If the first change does not work, we should change the entry for Fedora to directly hit the partition; title Fedora Core 3 kernel (hd1,2)/boot/vmlinuz-2.6.9-1.667 ro root=hdb3 initrd (hd1,2)/boot/initrd-2.6.9-1.667.img

Print Shop Deluxe DVD. Also, look here.

See if this link helps. But first, get to a terminal windolw as root user and type in; lsmod (as in the letter L) - hit the enter key. See if the module forcedeth is listed. If not then try loading the module by typing in modprobe forthdeth If you just get a cursor with no errors, then try to configure the network using the Yast2 Control Center. Post back what you find. If you need more direction, let us know.

OK, thanks. This explains a few things. Now we know that Fedora is probably on /dev/hdb3. I will have to look at my Fedora box to see what the default kernel and such is. You should be able to add this to the current Grub file. If you know what filesystem that you used, then you can mount the partition to see what the vmlinux and initrd is for Fedora and add them in the grub.conf file for RedHat. It should be something like; title Fedora Core 3 rootnoverify (hd1,2) kernel /boot/vmlinuz-2.6.9-1.667 ro root=hdb3 initrd /boot/initrd-2.6.9-1.667.img Of course, the kernel and initrd version should match what is the actual default Fedora kernel is and; rootnoverify (hd1,2) kernel /boot/vmlinuz-2.6.9-1.667 ro root=hdb3 initrd /boot/initrd-2.6.9-1.667.img indented from the title line (one tab space)and one line above the Windows title and lines. If anybody has the answer right off, please feel free to chime in so adamh does not have to wait. I'm going to be a little busy for the evening.

Ok, good. Now I have to think and look at my Fedora install (my box is apart at the moment). I may see some minor issues, maybe not. Let me ask, did you compile/install kernel 2.6.9 on the RedHat install? Notice this script in Grub.conf; title Red Hat Linux (2.6.9) . root (hd0,2) . kernel /boot/vmlinuz-2.6.9. ro root=LABEL=/ hdc=ide-scsi . initrd /boot/initrd-2.6.9.img You are defaulting to kernel 2.4.29, which is fine, the original RedHat install, as per; default=2 Let's look at this a little more before we go on. just to check, can you do the following when in RedHat? When in RedHat, get to a terminal window as root user. Type in fdisk -l The letter l, not the number one. Post the results here.

My memory of Redhat is not as good as it should be, but let's give it a go. If you know exactly what the linux name of the RedHat partition is, you can insert disk #1 of the Redhat cd disk into the cdrom drive and boot to the welcome install window. Once there type in; linux root=/dev/hdax. So say you know that RedHat is on partition hda5. Then you would type in; linux root=/dev/hda5 This shouold boot your RedHat system to the normal GUI. _________________________________________________________ If you don't know what the partition is, we go to plan B. Plan B You will be using the first RedHat cd (#1) to boot the system. 1) first boot the computer using the disc1. 2) type linux rescue on the setup prompt. 3) follow the instructions on the screen.(ur linux installation will be mounted on /mnt/sysimage) You should be prompted to enter the root password, which you should. 4) now at the prompt type chroot /mnt/sysimage This will mount the RedHat system, as if you booted directly into it, within a terminal window. 5. If you were able to get into RedHat via the linux root=/dev/xxx option, get to a terminal window as root user. If you used plan B. you are already at root user console. 6. Have a freshly formatted floppy ready. Put it into the floppy drive. Type in grub-install /dev/fd0. This is the number zero for /dev/fdx not the letter. This should write a boot floppy that you can boot the full system with, GUI and all. If you get this far, and got no error messages, for kicks, see if you can boot into X. Try typing in startx and see if KDE comes up. If you get an error message, type in login and follow the prompts to put in your normal user id and password. Again, try typing startx to see if the GUI comes up. What I would like to do is see what the Grub /boot/grub/menu.lst says. You should be able to boot into "normal" Redhat or Windows with the boot disk. Let us know if you get this far.

Take Dan's advice. I struggled some time ago with this (although things have improved with Linux support somewhat) until I got broadband. The Motorola SupraExpress external serial 56k works (the PC model, not the MAC model), as well, but they are hard to find. I would go with Dan's suggestion. If DSL becomes available in your area, consider this as an alternative. I know, but they have been working on DSL to make it a more viable option (switch station and booster ability), so you may see it come to your area in the near future.

Do you have the original cd disks for RedHat and the full install Windows XP disk? Do you remember if you installed Grub from the Fedora install? If so, did you tell Fedora to install Grub on the MBR or a boot partition? Did you do the partitioning using the Fedora Utility for the second hard drive (Fedora) install. If so, what option did you choose, expert partitioning or did you allow Fedora to use existing space on the second hard drive? If you have the original Redhat disks and did not update the RedHat kernel, we can try to recover the RedHat/Windows Grub boot. My guess is that you allowed Fedora to use it's grub for booting the system. It should have detected the prior RedHat and Windows installs, as well as Fedora, but something went amiss. If we can recover the RedHat install of Grub, we can move on from there. Thanks for responding with the master/slave designations, which look fine. Windows disk management can't properly see or detect the Linux installs, hence, the "unknown" designation of the Linux partitions. This is normal. Finally, I assume that you don't have a RedHat boot floppy disk?

What is the exact name of the package of amaroK that you have? Is it something like amarok-1.2.1.tar.bz2? Or does it have a .deb extension? Anyway, amaroK is included as an installable package in Mepis. Mepis has Synaptic, which is the easiest for some. However, I suggest the following; 1. Get to a terminal window and get to root user. (Once at a terminal window, type su hit the enter key, then put in your root password (hit the enter key). 2. Once there, type in apt-get update (hit the enter key). 3. Once the package list is updated and the prompt re-appears, type in apt-get install amaroK. Note the capital "K" not amarok! This may take a while. You will see a percent progress bar as it installs packages and dependencies. Apt-get is a package (program) installer that should take care of any other dependency needs that amoraK should have. amaroK should be installed. Find it under start-->Multimedia.

Did you do a hard drive install of BeatrIX on either machine? What bootloader are you using on YOUR box currently? From which distro?

Are you using the original grub from RedHat or from the recent install of Fedora? How id the second hard drive set up in the system? Primary slave, or secondary master? Is the second hard drive ide or sata? How are your cdrom(s)/cdrw drives set up, in terms of secondary master etc...?

I thought that you already had Xandros installed on your laptop? If you want to try out Mepis, just try it as a live cd and see what you think. Mepis does not come with Crossover Office pre-installed, but it is Crossover Office ready.

You need to have lilo or grub from another distro install, or boot from a floppy or CD. Lilo appears quirky with this, so I recommend grub. Puppy does not have grun or lilo included. However, if you want to boot from a cd, one Puppy user has developed a way to boot from a cd. Given the hard drive space on this system, why not make a boot cd and just leave it in the cdrom drive? See this post.

I'm not going to be much help here, but let me ask a few questions. Is this system meant to be set up as a web server? What exact distro and version are you using?

And what exact card make and model of wireless card, as well as revision number do you have? The revision number may be important for knowing what exact chipset is on the card.

Do you know what the partition designation is for the Linux (RedHat) install? If so, you can boot into the system with the install cd, or the rescue mode, then make a boot disk, if you are concerned about writing to the MBR. For example, if you know that RedHat is on hda5, then type at the command prompt when the boot disk goes to the install Menu; linux root=/dev/hda5 Using the rescue method, you only boot to rescue mode and root is not mounted yet. To get to root, and see your lilo file, once you are logged in, type; chroot /mnt/sysimage

I just have a little time to post this for now, have to pick up the little one at Daycare....but her it goes. When you do a hard drive install of Puppy, it will create a floppy disk to boot the distro from. The boot floppy is created relative to the designation of the hard drive. If you install from another system, you need to disconnect the hard drive in the system that you are doing the install from and make the hard drive (that you will use on the older box)the primary master in the installation box. For example, if the hard drive in the box is primary master, the boot floppy will point to the partition as the first drive in the box, in most cases hda (whatever). So, when you do the install to a primary master drive, when you put the hard drive back in the old box, it need to also be primary master. 1. disconnect the drive in thwe 128 mb ram box and install the drive from the older box. Do the install. 2. Remove the drive and place it back into the older box as primary master. 3. reconnect the drive in the 128 mb box, as it was, most likely primary master. Puppy should boot on the old box, the floppy pointing to Puppy on ther Primary master drive, at the correct partition, all relative to how the install was done and the designation of the hard drive. To clarify, if you put the hard drive from the old box as primary slave or other, the boot floppy would point to the primary slave, say hdb whatever. If you then put the drive back into the box as primary master, it will still look for the primary slave drive (hdb) not hda, which is likely where the drive is now in the old box. So you avoid re-jumpering drives and such when you disconnect the drive in the 128 mb box, keeping things relative to where the drive is set for the older box originally. Puppy has two hard drive installation options. One that will do an install point to an already present vfat partition, making a file called Puppy001, whch is really a compressed ext2 file, which Windows would see just as a file. Option #2 installs Puppy to a Linux partition, which it will be created for you during the install. You just point it to the space (partition) that you have on the system, that you want to install to. In your case, you would tell Puppy to takeover the hard drive (already existing partition) and convert the partiton to a linux ext2 partition. In either install, the boot floppy will be made to boot to the correct partition. A so called Network install has been talked about by some hardcore Puppy users, but this will not work, unless you really know what you are doing, if at all. Puppy looks for appropriate partitions locally, not on a network, or on two systems linked together.

This version of Mandrake is too old for this video card. If you have a TNT, TNT2, GeForce, GeForce2 or GeForce3 card, they should work. See this article.

From the Puppy Linux main page; Quote: Obviously, some objectives have qualifications, for example, to load totally into RAM the PC must have either 128M RAM or failing that a swap partition. You might be interested in what DSL users have to say about older systems and limited ram here.

I respectfully disagree with iamroot. I have used Linspire since the start. The claims of some hardcore Linux users about security issues has not shown to be true. Linspire is based on Debian and just is as secure as Debian. The issue is that the primary account is run as root user, which some cringe at. But. all accounts that you set up are as secure as you would like, just as with Debian. Take a look at this thread. Ease of use has been the claim of Linspire. It seems that the more you make a distro easy to use, the more people compare it to Windows. Unfortunately, then folks seem to claim that security is an issue. Since Windows has targeted Linspire in several lawsuits, with Windows trying to block the release of Linspire in several countries, tells you something about how viable the distro is. For the new user, Linspire, as well as other distros, can be a good start. Take a look at the Linspire forums and see what others are saying. I assure you, you will get varied opinions. Look at what the seasoned users are saying, as well as the new users. But, since you already bought Linspire, give it a try and see for yourself. Let us know what you think. I just did a review of the new beta version, which also has a link to an older article that I wrote. Yes, I have written several articles on various flavors of Linux, as well. My recent favorite is SimplyMEPIS 3.3, also based on Debian. Linspire Beta review. SimplyMEPIS review. Of course, you can look at the news page on this site to find other reviews, as well.

The problem is not in detecting the card, but in assigning an irq for video. So, if both PNP OS is set to no and an irq is set for vga in the bios, you need to look at what hardware is on the system. Can you post what your system specs. are? What motherboard and if all your pci/isa slots are filled. By any chance is this a Dell or Gateway?