danleff

Yes, but Puppy runs all in ram, unless you do a hard drive install, but you need 129 mb of ram to run the install script from within Puppy. You can also add swap space now in a hard drive install of Puppy, which uses Fvwm95 and Xvesa is by default. This is where the problem lies in Live cd disks.

Yes, you are right, it is new. Take a look at this article. No linux drivers yet?

Try this. Add nvidia to the /etc/modprobe.preload file, then reboot. Or you can try testing it by changing to root user at the terminal window (since you are not in X) and type in modprobe nvidia (hit the enter key), then type in startx. If you get a message that you are unable to open a screen, then type in login, sign in as normal user and type the startx command.

Actually, Puppy needs at least 64 mb of ram to run. The reason is that the complete system runs on ram off the Live CD. Your best option is to upgrade the ram. Even the less memory intensive distros want more ram than what is on your machine. Even Vector Linux has this 64 mb ram requirement. You can run Puppy on this system, if you used the cd on another box with 128 mb ram to do a hard drive install, then put that hard drive back on the older box. Take a look at the Puppy forums and you will get the idea.

I have the exact same video ard in my system and just did an install of the 6629 version in Mandrake 10.1. Let me ask a few questions. Did you do the install of the drivers after exiting X? Are the kernel sources installed? Did you make sure that load "glx' was not commented out in the xorg file? Did you install the Linux IA32 drivers?

Can you be specific by "driver software" or do you mean a formatting utility? What version and distro of Linux are you using now? Some, like Mandrake, will automatically place an icon on the desktop when the card is plugged in. Some do not, but should be able to mount the card. they just don't do it automatically. In terms of the printer, if you only have one card type, and the card reader on the printer is working fine, there is no use for a multi card format reader, unless you plan on using more types of flash cards (say in different cameras that use another type of card). I can say that I have a multi card reader and it works fine in Linux.

I dfon't have grub installed in my Fedora install, but just look for the following; get into the file manager in superuser mode. Navigate to the /boot/grub directory. Open the menu.lst file (right click on the file...open with kate) Add the command at the end of the kernel line, so you have something like; kernel (hd0,0)/boot/vmlinuz root=/dev/hd0... acpi=off Your menu.lst file may look somewhat different. Just make sure the command is last and that there is a space between the last entry on that line and the added acpi=off command. Save the file and try it out.

It will be interesting to see what Smartlink says. I did find this page which seems to indicate that there are complications using the driver, without a modification. Of course, this is for Windows. It is apparently an HSF modem, which may work with the Linuxant drivers.

Originally posted by tripitaka: Quote: you need to change "nv" to "nvidia" in /etc/X11/XF86Config then add nvidia to /etc/modprobe.preload before installing the driver. I just installed the drivers easily on my Mandrake 10.1 system. I edited my /etc/X11/xorg file to make sure Load glx was not commented out. Added nvidia to the /etc/modprobe.preload file as suggested by triptaka using mc (Midnight Commander). Rebooted and the driver came up with the quick NVIDIA splash screen, then KDE came up. /etc/XF86Config is automatically altered on reboot, so there was no need to change this file. See if this works, then we will look at the resolution problem.

Have you tried to install xemacs via the Mandrake Control Center? This should solve any dependency problems that you have. Start-->system-->configure-->configure your computer-->software management-->install I assume that you have Mandrake 10.1 installed on your system?

This is really a question for the netodragon folks. If they made the Linux package for 32 bit systems, then they need to guide you through this, or develop a package for 64 bit systems.

What version of Mandrake are you using? I ask, as some folks download older versions which may not be compatible with newer program packages. Each distro has it's own installation type packages. Mandrake and Fedora use files with rpm extensions. Most of the software is already located on the cd disks that you downloaded. In the case of Firefox, it uses a generic install script that installs the program (package). Look at the directions located here. First, you must uncompress the package. This is like a zip file in Windows, but done from the terminal window. If you downloaded the package to your home directory, then open the terminal window, which should default to your home directory. Type ls and hit the enter key. You should see the file in the list. Then type; tar -xzvf firefox-1.0.1.installer.tar.gz NOTE: you must use the exact name of the file that you downloaded. I assume you have firefox-1.0.1.installer.tar.gz as the package name. This will expand the package into a directory called firefox-installer. Get into that directory by typing; cd firefox-installer (hit the enter key) Then run the install script; ./firefox-installer You should then get a graphic installer that will guide you through the install and bring up Firefox. Once you get this far, then we can add an icon to the desktop to run Firefox.

Witht he internal modem, the problem is more likely the kernel in Fedora and it's use of acpi via the bios. What bootloader are you using? Try passing the acpi=off command in the bootloader to see if this corrects the issue. See the linuxant HCF FAQ page, item #12 located on this page. If you don't know how to do this, let us know what bootloader that you are using and we will try guiding you though this.

Did you get this sorted out yet? If not post the following; 1. What tool you are using to format your hard drives. 2. What make of hard drive is the 40 gig drive. 3. Currently, what hard drive is the primary master? You need to format the larger drive first properly for NTFS, if that is what you are using. Most hard drive manufacturers have a utility to format the drive properly for this. Then install Win XP on that drive. If grub is on that drive in the MBR, then the install of XP will over-write the MBR. If you changed the drive designations, or erased RedHat from the slave drive, then grub has no reference file to direct the boot. I also assume that the bios is set to boot the first hard drive in the system? Do not install RedHat 7,2, or 7.3. You should use (as suggested) RedHat 9, or Fedora Core 3, not Core 1 or 2. The older RedHat versions have trouble with NTFS and Core 1 and 2 have trouble with NTFS. I realize that you installed RedHat on the second drive, but the drive designations in grub need to match what order the drives are set up as. Make sure that the Primary master is set as NTFS (the first partition). What utility that you are using to format the drive will make a difference, so knowing what you are using will help sort out the issue. It sounds like the 40 gig drive is not formatted correctly for Windows to find it. Windows always wants to be first (primary master) so check this out and post back.

OK, now I'm getting confused. 10g4n, is this the system with Windows ME on it or one with just Fedora installed? If just Fedora is on the hard drive and the entire hard disk is formatted with only Linux partition(s), then the Windows install disk will not see any hard drive space and spit out an error message or fail. Windows is unable to see Linux partitions (sees no hard drive space at all to install to). It will see this as no hard drive installed in the system at all. If this is the case, you need to re-format the drive with a Windows filesystem, then install Windows. Let us know why the system is not Win XP compatible. Is it that there is not enough memory, or it does not meet the processor requirements for XP?

Just to get you started, look at this article. Since you are not using the modem, which would be an issue, this is good. The other question is do you have a full Windows XP install disk as a backup, or is Windows pre-installed with no XP disk provided to you? For general links to Linux on laptops, see this link. Is the DSL modem hooked up via USB? If so, we need the make and model.

Quote: resize? is it ok? I mean, will it not confuse the FC3? I remembered once i do a resize on my old pc's linux partition (a Pentium2 pc), and the linux (mandrake, i think) won't boot.. got many error. It's good that you are thinking of a back-up plan. Especially since you had trouble before. You can resize partitions, as long as you don't move them around, or add new partitions. I will assume that you added a partition before in the free space that you made? Of course, this would change the partition designations. The second thing is, with the current partitions that you have, what are primary vs. logical partitions? This would make a difference, as well. Now let me ask, you have 60 gigs of space on the ide drive and 80 gigs of space on the sata drive, all being available to Windows? Will adding 10 gig of space make that much difference (assuming that you keep FC3 installed and just reclaim space from that partition - resize the partition so FC3 stays on the drive with less space)? In terms of the fdisk /mbr command. This is really for Windows 98 or ME. Some claim to have done this for Windows XP, but it is not totally reliable. The fixboot and fixmbr commands are specific for XP. I will guess that when you did this before, did you really have the MBR pointing to the right drive when you applied these commands? Sata is another issue. I recently got one of these drives and discovered a few things. Make sure that you do not have an MBR written to the sata drive. I bet the fixboot and fixmbr have to be specified when using the fixboot and fixmbr commands. I will try and find the Windows article on this for you. In terms of backing up grub, try this. Get into FC3 and a terminal window as root user. See if you can make a grub floppy disk by issuing the command in the terminal; grub-install /dev/fd0. Make sure that there is a freshly formatted disk in the floppy drive. If this works, then at least you have a floppy grub disk. I'm going on vacation tomorrow until March 4th, so if I don't get back to you, there are fine folks on these boards that can follow-up with this. P.S. In terms of a boot floppy, look at this thread. Also, for XP boot rescue using fixboot and fixmbr, see this Microsoft atricle.

Try this. Use <ctrl> <alt> <F1> to get to a terminal window. Login as root user... root (enter key) enter your root password (enter key) See if Midnight Commander is installed... Type mc (hit the enter key. navigate to /etc/hosts Open it by hitting F4 to edit the file. CAREFULLY take out the entry that you put in and make sure that the hosts file looks exactly the way it did before you edited it. Hit F2 to save the changes. Hit F10 and follow the prompts to getout of MC. <ctrl> <alt> <del> to reboot. See what happens on next boot. When you get the same error, post exactly what it says, if possible. If it srolls past to the GUI right away, let us know.

OK, then two possible issues. The cdrom is not compliant with home made bootable cdrw or cdr disks. Or, the bios is not compliant with booting the same. I would replace the cdrom, as it is probably the culprit. They are inexpensive enough. Good luck!

Quote: I kept all the original suggested automatic partitioning hoping that I wouldn't have problems like this. Is the drive just failing (which I doubt cause just had fedora 3 installed on it) First, stop making all these changes to your system it's no wonder that you are having problems. You updated the bios...got the 3 beep codes, but the system is booting normally now? If so, let's move on with your install. You tried Mandrake. Did this install at all, or fail at the partitioning section? You had Fedora Core 3 installed. Did you attempt to install Core 1 over the Core 3 installation, or wipe the drive and start the install of Core 1 and just tell it to accept default partitioning? Do you have Windows on this system at all, or just Linux? If Windows, is the Windows install XP using the NTFS filesystem? Do you have a sata drive on this system, or ide; or a combination of the two? Grub is failing because it can't read the disk partition. If you had failed prior or successful installs and tried to over-write the partition each time (did not re-format) this can be a problem. Grub may not be reading stage 1.5 or 2 correctly because of the partition confusion on each install, how did you set up the bootloader? Did you tell the Fedora Core 1 install to over-write the MBR?

You can't just remove the Fedora partition, as it has references to Grub. Grub must be removed first. This is why the system would not boot when you just removed the Fedora partition. Since you already tried to use fixmbr and fixboot, I wonder what your system layout is. What system is this and what are the partition designations as PartitionMagic sees them? You can also resize (shrink)the Fedora partition if you don't have much on it and enlarge the XP one to gain more space. Another simple fix would be to add another hard drive for your data files, if this will work for you.

First of all, I would not attempt to install Linux on a computer that is not yours. It belons to an organization? If you install Linux (not a live cd version) then it will want to over-write the bootloader. If you are the only one using the system and don't care if you accidently trash something, then i guess it's OK, if you have permission to do so. Otherwise, you will confuse other users when they boot the system. The question is, does the cdrom read disks fine? If so, you probably did not burn the iso as an image. Open at the cd that you burned in Windows. Do you see just one iso file, or a bunch of directories and files? Finally, are you sure the bios is set to boot from cdrom? Some organizations have their systems set up so this is not so, just for the reason of preventing people from installing another OS in the system.

The easiest solution? Grab a copy of Mepis and burn it on a cd. Boot Mepis via the cd and there is a package called qtparted that will do the job for you. Once in Mepis, get to a terminal window as root user and type in qtparted. This will allow you to resize the original partition and create another ext2 or ext3 partition for Core 2. Make a note of the partition name, say hda3, or whatever it is so you know the correct partition to install to. Or, you can just leave the space blank and tell the install to take the free space. If you choose to make a partition, when you install Fedora Core 2, tell it to use the already existing partition that you made by using the custom partition option. The only other issue is the bootloader. Fedora Core 2 will want to install a bootloader. You can choose to install the bootloader to a floppy, or not install one at all. This depends on how comfortable you are with editing grub or lilo. You can always change your existing bootloader to include Core 2 if you wish. I'm not sure if Fedora Core 2 will set up the bootloader correctly, as you are going backwards in installing versions (Fedora Core 3 to 2). Perhaps somone else has done this and can comment further. But I guess the issue is, before you do all this, what are the package incompatabilities that you are experiencing? Fedora Core 3 should handle everything that 2 did, and more.

Also look at the balance settings. Someimes they are a bit off. After turning the volume settings up, if this does not work, play with the balance, while a cd is playing. I'm glad we were able to isolate the issue. You should have this cleared up soon.

Before you get too involved into a hardware issue (which is possible), suspect the media as at fault. Take a look at my draft ISO burning guide. The critical thing is the speed that you burned the cd disks at. Also, the A7V600-X has a feature that reboots the system (clears the system) when a power failure or interruption occurs, say when the system crashes due to a system problem. If the disks are bad or the iso faulty, causing the system to crash, this can happen. What media are you using? Did you burn the iso images at a slow speed?