danleff

As soon as the Dell splash screen appears, have him/her try; Dell: - F1 or Del. Other possibilitites can be; Dell: - Some require pressing reset twice Dell: - Ctrl + Alt + Enter But I bet it is the F1 or del key on his/her system.

So, you get a black window with no command prompt? I have read by some users, that Mandrake has a bug with these installs from a hard drive. Since you are back in Windows, I would burn some cd's from proper iso images and try an install. I would also avoid using Mandrake's partitioning utility and re-format the current ext3 partition and start from scratch with a partitioning utility like PartitionMagic, before installing again. Most distro's do not like being installed over a prior installation.

It has been reported as a problem. However, I did an upgrade install on my system (allowed FC II to upgrade over a FC I install) and did not allow my lilo to be overwritten. I added FC II's information to my current lilo file. No problem. There is somethng with kernel 2.6 and parted causing the issue. So...I recommend avoiding using FC II's partitioning utility. I would recommend using PartitionMagic on a fresh install to set up the partition, then do the install.

How about Suse's hardware support database here. You can also let us know what you have in terms of specs. and we will try to help.

You need a router to get internet access to work from both boxes. From my experience, a crossover cable will not work. So, as a result, you have a local network connection only.

Are you using a router and are the two systems connected to the router, with the Win 2000 box to the main router connection and the RedHat to a secondary? Wired connection or wireless? In RedHat, when you type in ifconfig in a console, what do you get? Just an lo entry or two entries? Is DHCP set to connect at boot in the RedHat system?

DapperDan, your as bad as me with the kernel entries! I don't have my Fedora box open right now for reference, but you can add Fedora Core 2 to the grub file. Since you are using Kernel 2.6 you can forget the ide-scsi driver, which should not be needed. 1. Mount the Fedora Core 2 partition. 2.Copy the vmlinuz and initrd to your boot directory of the original Fedora install that has grub installed on it. I like to make a directory in the boot drive for other versions and distros. In your case, the boot is hda1. If you elect to just put the files in the boot directory directly, then you don't have to point to the Fedora Core 2 directory. So, cp the files to the boot directory. 3. Add/copy one of the old fedora entries in the grub menu file as the second to last entry, or wherever you wish, then edit it. The syntax should like like; title Fedora Core_2 root (hd0,5) kernel /vmlinuz-(version of kernel) ro root=LABEL=/ (omit ide-scsi) initrd /initrd-(version of initrd) I believe that in Grub, the partitons begin with "0" so, the partition 6 on hda1 should be (hd0,5). If you get a kernel panic error on boot, try changing it to (hd0,6). I think that you should be able to edit Grub at the boot menu, when it first comes up, if memory serves me right. So, if all the entries are right (except the partition) then you can edit the entry at the boot menu. When the menu comes up at boot, highlight the entry you want to edit, hit "e" and see if it brings you into edit mode, if you need to edit the entries. Esc backs you out of edit mode, "b" tells it to boot the edited entry, in your case Fedora Core 2.

Did you try disabling the onboard video in the bios? Then try the agp card.

This has come up a few times. The issue is also noted in Fedora installations, where the XP partition is affected. Something to do with parted and kernel 2.6, from what I have gathered. Of course, back up any important data on the XP partition. Use a partitioning utility like PartitionMagic to reformat the Redhat partitions to ext3. Since you are not worried about the data on these partitions, this is fine. DO NOT use the Mandrake partitoning utlity to format the partitions. Do an expert install of Mandrake. After booting with the first Mandrake cd, type in expert at the command prompt. This allows you to have the most flexability in choosing options. When you get to the partitioning section, choose custom partitioning. Assign the partitions as you wish to root, home and whatever. DO NOT choose to format the partitions, but to assign designations the already existing partitions only. Allow the install to complete and choose grub as the bootloader. You should not have any problem with Mandrake picking up the XP boot, unless you have Windows assigned to anything but the first partition on your drive. If everthing was functional before you began, there is no need to reformat XP, if grub does not give you an XP option. You can add xp to the grub.menu file if it is not there, but this should not be necessary.

Thanks Mel. I also have problems with that word proprietary! I would assume that you are correct. I have one of those HP external drives lying around and will try it also. The HP driver for this model series is available in the 2.4 kernel, at least in the 2.4 series - I wonder if it is enabled in most basic stock kernels, or a re-compile is needed in most cases (íf it is not generally enabled by default). I going to check on of my installs and see what´s up. P.S. Yep, it is in the stock Mandrake 10 CE kernel, listed as ¨hp cd-writer 82XX support (experimental)¨ under USB support. Looks like the usb-storage module needs to be loaded, as well as the HP support. Not enabled by default!

My opinion...leave well enough alone. Unless you own the computer at work, you chance trashing the Windows install. There are too many variables here. If the system is just a desktop, that is one thing. If the system is connected to a network at your work site, this is a risk. Obviously, you do not want to format the drive. Is there something that you need in the official release? If not, enjoy what you have. I am a lan admin at my job and just re-imaged my boss´ system because he tried to install his palm software on his system too many times trying to get it to work. There were so many install tries with different versions that it was impossible to sort it out.

The simple answer is yes. I am surprised that you are not connected to the system via a nic card ay your university, which would work. I believe this is a Rockwell HCP modem, which is designed for windows use, a so called "winmodem." If you do not get a better answer here, I would seach google and see if you can find a modem driver, although my simple search failed on google. If you can find a hardware modem, this would be the way to go. It will save a lot of headaches.

Disk two, if it works, will boot the system, then prompt you for an install disk (claim disk 2 is not an install disk). Before clicking to continue, place disk 1 in the drom and continue.

I just did the worst possible install senario of Fedora Core 2, an upgrade install. Mind you, I have played and upgraded FC1 on my system at will. The install took about one hour on my AMD 1800+ processor, a bit of time. Turned off by the reports of corrupted XP partitions, I elected not to install the bootloader, since I have several distros on this system. So, I can't report on this problem. But, from what i read, it may be due to the use of kernel 2.6 and parted, which is upgraded in FC2. So, no partitioning of my drive (used the existing partition to upgrade) and I did not allow a bootloader to be installed. I edited ny current lilo and gave it a go. What a difference in speed and functionality! Very nice indeed! FC2 left all my settings and favorites intact. However, k3b failed with permission erors that were not able to be corrected by using the k3b setup feature, which has been removed in FC2, according to the release notes! The use of ide-scsi in lilo is no longer needed in kernel 2.6.5 to recognize the cdwriter. I upgraded to k3b 0.11 using the yum repositories found at the k3b website and all is fine. Redhat-config-whatever has been replaced by system-config, so that you can type system-config-network in a command line to configure your nic card within a gui interface, but this was not necessary, as the upgrade found all my hardware, including my nForce chipset. Other system options are for packages (system-config-packages) and more for configuring samba, sound and display, among others (read the release notes). I added some other packages using yum with ease, including gnucash and manually installed flphoto and Nvu, no problem. Again, I caution you about the reported XP partition corruption issue on new installs, but if you get it up and going, what a nice change in functionality! Testing continues... Read a not so flattering review of FC2, posted by linuxcompatible from linux.com here.

I'll take a stab in the dark. It looks like cdrecord does not like the media. What exact media and size (72 min vs. 80 min.) are you using? It looks like cdr media, but rated at 2X for this writer? It also looks like the media write has been writing to the cdr with an error. The media is fixated and can't be written to again... So, you run the risk of wasting cdr media? If the dummy write does not work, then don't remove this option, until cdrecord finishes without errors. Make sure that you use a fresh cdr media that has not been used before and that it is rated for this writer.

Nice Mel! Hopefully this will help those users asking questions more clearly, by clarifying what will help us help them...rather than "Please help, it doesn't work!"

Where did you get notepad from? Did it install with wine, or are you using notepad from an XP installation? Is your windows installation an XP one? It looks like maybe you do not have a wine.conf file (I'm guessing, since i use codeweavers and have not used stock wine for a while). It looks like it, but do you have a .wine directory in your home directory and did you use winesetup to set the fake wine directory and it's components?

Since no one has responded yet, I will give this a try. What Linux distro and version do you have? Kernel versions less than 2.4.20 apparently had a conflict with ide-scsi, so this may be an issue. Do you have sane installed on the system? I assume that you tried modprobe sg and have no output for the scanner when looking at dmesg? What does lsmod show?

It has been reported by a user on Slashdot that Fedora Core has an apparent problem setting up dual boot systems with windows XP. Others have posted on this forum problems with Mandrake 10 installs and partition issues, myself included. For know, take care installing a new distro and always read up on the distro that you plan to use before taking the plunge! Always make sure that your hardware is supported before installing and save yourself the headaches that can occur later on. And..it goes without saying, always take care when installing a cutting edge distro version on your production system. The newest is not always better! [Edited by danleff on 2004-05-25 20:27:26]

In Mandrake, if I used the Mandrake partitioning utility to create the partition, then PartitionMagic saw the drive as bad. Sector reading problems. I wonder if Fedora has the same issue. I'm going to try Fedora Core 2 on my secondary system and see what happens. However, since I already have a partition set up, this will be an upgrade install. Since I do have some space available, I may try a fresh install on the secondary system and see what happens. Don't want to do this on my main system, which has 6 distros on it. Good thought about kernel 2.6, which seems to be the issue with Mandrake. My Mandrake test version install was fine, but I believe this still was using the 2.4 kernel. I experienced the partitioning problem with the final release of Mandrake CE.

Of course there is! Nvu Bluefish Quanta Plus And under Crossover Office, Macromedia MX... Just to name a few.

What kind of networking? Does the knoppix networking faq help?

Looking futher into it, this appears to be an xfree86 and ati issue, as noted in this article. I assume this is the patch that you were referring to? The issue is further outlined in this one. To quote; "Q: I have a working, hardware accelerated OpenGL setup, but when I try to run the game, I get a message on the console and in my logs that says something like "OpenGL renderer relies on DXTC/S3TC support". A: Your drivers do not support the "GL_EXT_texture_compression_s3tc" extension. This is needed to play the game. THIS IS NOT A UT2003 BUG. Currently, the only working drivers we are aware of that support this extension on Linux are the official Nvidia binary-only drivers. We are currently exploring options with other driver vendors, and we are willing to cooperate with any driver vendor that wants to support ut2003. The bottom line, however, is this: if you want to play the game right now, you should pop an Nvidia card into your machine." But there has to be a solution by now! Like you said, you can't just pop in a nvidia card into the laptop.

Sure, How about giving some system specs. on the boards. 1. CPU 2. amount of memory installed 3. video card 4. The issues that you have been having trying the installs. 5. What you want to be able to do with the Linux installs. Desktop, networking...? The problem is that these boards are quite old and probably the newer distros will not run on them well, if at all. You may need to try a less system intensive distro, like Libranet to run on any of them, depending on the specs. See the system specs. requirements on the Libranet site here. Have you tried Knoppix or Mepis live cd to see if it will run off a cdrom, provided they have enough memory?

Finally DapperDan! 8) Got my wireless D-Link DWL-g650 running under Linspire on my laptop, using the Linuxant package with Windows XP drivers. Linspire has a nice GUI for network configuration that allowed me to play around with the settings. WEP and all! The Linspire forums had a nice how-to on getting it to work. I am going to try Knoppix next and see if the Linuxant package will work there, as well. The Linuxant package is free trial for only 30 days, but for $19.99 it's good for me! Saves the headaches! I will try open source next(ndswrapper) or madwifi. You do need to have a compatible card for the Linuxant package, which the D-Link atheros chipset is, on this card.