danleff

OK, try this. Add the following to your device.map file, using your favorite editor. (hd1) /dev/hdc This adds the Secondary master drive to grub. Then to the menu.lst file; title Windows XP chainloader (hd1,0)+1 Make sure that there is an extra space after this entry. Save the file and see if you get a valid Windows boot on your next boot, by choosing the Windows XP entry at the grub boot prompt. Realize, that grub does not know about the extra drive that you added, until you tell it so.

Most likely related to the age of the cdrom drives in these systems and their ability, or inability, to boot off of cdrom disks burned with newer cdrw drives (home burned). In addition to that, the type of media used. These old cdrom drives have particular problems with cdrw media versus cd-r media. If using cd-r media, they work best with slow rated disks. I recently had this problem working on an older HP system trying to use my rescue disks that were rated at 52X. I actually switched to 4X rewritable media and that worked.

kyrnel; Please post the content of your /boot/grub/device.map file. The best way to do this is to add Windows to your grub file. To accomplish this, we need to know what the drive designation layout is for grub, as it seems that you have your system setup in an unusual fashion.

Quote: In the meantime, should I just use something like partition magic to wipe my MBR on IDE0 and set the boot order in my bios to work around it? PartitionMagic, I don't think, will just erase the MBR, but in fact the whole partition. You don't want to do that, as then you lose Windows. Well, maybe that's not such a bad idea! Your MBR has been written over by grub. I'm not sure what you mean about switching the boot order in the bios, unless you mean that that is how you have been booting SuSE to begin with. But the same rule applies. Your Windows installation is on hda1, or your primary master drive. Grub has overwritten the MBR, so your ability to boot into windows sans the removable drive attached the system is gone. You can fix the MBR via the Windows recovery utility, but this will erase the grub references in the MBR and being able to boot into SuSE is lost. You can make a boot floppy in Yast before recovering the MBR in Windows, so windows will boot. Then you can use the floppy to boot into SuSE when the removable drive is attched to the system. You can just always make sure that the removable drive is always attached. Finally, you can do a minimal installation of Suse on soe free space on your hard drive. I just did this when my system crashed. This way, all the grub files are always there and you can dual boot with or without the removable drive on the system. You would just have to add the relevent additions to the menu.lst files on the minimal hard drive installation to have the option to boot from the removable drive. In terms of Twinview, in SuSE, from what I have been reading, you need to add the appropriate additions to the xorg file manually. See; this appendix of the NVIDIA readme file. Also read the second link I gave before from the SuSE forums, where a reader comments on this. But, please, heed the warnings about backing up your original xorg.conf file. This will save you possible headaches.

No problem! I'm glad you got it sorted out. This thread was a bit difficult, as the boot order was switched somewhere in the process. I note to readers, there is no need to do this. Resist the urge to change the boot order when installing Linux. Then have fun! Remember (read my signature)...

If your booting straight into sata drives, there is no hda, but only sda (unless you also have ide drives on the system). grub-install --recheck /dev/sda rechecks the disk order and assigns designations in that order, installing grub on sda. If your Windows installation is on the first sata drive, and you have the bios set to boot sata first, then this is good. grub-install --recheck /dev/hda installes grub on the primary master ide drive. If Windows is on the primary master, in an ide only system, then this is fine. Where folks get into trouble, is thinking that they need to switch out the boot order in the bios. You should not change the boot order in the bios before or after installing Linux. There is no need to do this. Doing so only complicates matters, confuses grub and your windows boot.ini is also pointing to the wrong drive and partition as well.

Even though you installed Grub to the MBR (Master Boot Record) the actual stage files reside on the hard drive in the Suse install /boot directory. Only the part of grub that catches the MBR resides on the MBR that directs things to the actual location of the grub stage files, menu.lst and device.map files. This design if by default, as it is expected that you would have a hard drive installation. Doing otherwise, you need to get fancy. Thinking more about this, I think that I will try it on my test system. Unless you installed grub totally on a small boot partition on your hard drive, you are missing critical files that tell grub what to do. I have never done it this way, but given recent events where I trashed my Suse install (which resulted in no grub boot amymore). In terms of dual monitor setups, I don't have one, but doing a google search on suse dual monitors or suse twinview should give you some good hits. For example; this hit. Also, check the same search on the Suse forums. Here is one example.

Quote: Then i copied the first 256 bytes of hd6 using dd command in a file fedora.bin and copied this file into the windows partition . sachin, the first 256 or 512 bytes? dd if=/dev/hdb6 of=bootsect.lnx size=512 count=1. kyrnel; Quote: have a fc3 installed last year 2005 in 40gb Secondary Slave. i've got the cd rom in Primary master. then this time i install a windows xp in a 40gb Secondary Master. My problem is that i don't know the command line to put in the windows xp dual boot menu - boot.ini file. the to OS is running if i used the bios boot sequence. Please be a little more clear. You currently have grub or lilo as your bootloader and it is working for Fedora? Where is it installed? You noted that "this time" you installed XP on the secondary master. Did you have it installed elsewhere before? If so, did you upgrade the installation (just choose to reinstall to a specific drive), or start from scratch? What is on the primary slave, if anything? Generally, it is not advised to install Windows XP after linux. The reason? The boot.ini file is specific to where you installed XP. So, when you use grub or lilo, you need to know where grub or lilo is installed. If you are using grub, and can boot into Fedora, can you post the menu.lst file? Then we can go from there.

Never have tried VMWare, but someday.... But a couple of things caught my attention. The host system is RedHat 9. Does this mean that it uses that bootloader? Device sda, is this a sata drive, or is this how the resources are allocated in VMWare 4.5? Did you find any installation instructions on Fedora? It looks like Fedora is not supported with this version? I don't know if we have any VMWare experts here, but I would also try specific forums for the product. This may yield you some more helpful information, if nobody here has an answer.

We need more information. Quote: Hi, I just installed FC2 on a dual boot environment. I have connectivity through wire, but I'd like to configure my wireless. I'm entirely new to Linux. Does anyone one how I can configure it and where I could get drivers? Itz a proxim 802.11a/b/g card. OK, what exact model of Proxim is this? They made several and from what I read, there are at least three different chipsets that they used in their cards. Knowing which exact model and revision card that you have will help us determine what driver you actually need. I am just curious, any reason why you installed Fedora Core 2 and not Core 4, which has better wireless support? Quote: I checked manufacturer's website. They dont have it. And I thought I d/l ed the driver from one of the Linux websites. Did you actually download a driver or not? Is it in your home folder? I understand that you are new to Linux, so bear with me. Also, I have no idea what driver you downloaded or from where. Could you supply a link to the site that you downloaded it from? Or at least a file name of the driver? Quote: But I dont know how to compile it. Does anyone know how to do this? Any help is greatly appreciated Again, we need to know what the driver is and where you got it. This will determine if you downloaded the correct one and what is needed to install the driver. Often, there are several different wireless driver projects, so we need to know what you downloaded.

...and there looks like your problem, the boot.ini file, which is pointing to the first drive on the system, as it was when you had sata as your first boot device. You have a couple of choices. 1. If you feel comfortable doing this, and have admin rights to your Windows installation, you can try editing the boot.ini, changing it to; boot loader] timeout=30 default=multi(0)disk(0)rdisk(2)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /NoExecute=OptIn Then use the reverse mapping scheme that you originally had, or my modified one without the norootverify etc... 2. Reinstall grub on sda, not sda1 and make sure that you change back the boot oder to sata first. 3. Reinstall Linux and install the grub bootloader to sda. What you choose to do depends on your level of comfort and the critical nature of your system, whether Windows is a critical mission system or not (you can afford to mess things up on the system). The last option being the easiest and probably the least risky.

OK, let's back up a little. Did you re-install grub after changing the boot designatio to ide first? If so, how did you reinstall Grub...via the command line? If so, what commands did you use? Also, there is a typo, I think, on my part. Try; title Windows XP chainloader (hd2,0)+1 (no space between chainloader (hd2,0) and +1) If that does not work, try; title Windows XP chainloader (hd0,0)+1 Let us know if you get any errors. if still nogo, try; title Windows XP map (hd0) (hd2) map (hd2) (hd0) chainloader (hd2,0)+1 Remember, changing the boot order also confuses the boot.ini file, which is set to look for the Windows start-up files on a specific drive. Changing the boot order in the bios can affect this as well.

Take a look at this article which should help.

Are you using KDE or Gnome as your desktop GUI? Look at this article. Look at the section - Launching PPP from the Gnome desktop

I'm iooking hard and deep at this thread. I myself just trashed my grub install, trying to open more disk space for my multiple OS' and deleted my grub, having to start from scratch. Your problem seems to be connected to switching your boot order. One must have a solid plan of attack to make sure that grub is configured properly. Your boot.ini file is located at sda1, which grub needs to reference. But then you switched the boot order from sata to ide. Grub, for sure is installed on the first ide hard drive at the MBR? If I am reading this correctly, your grub file is mismatched for the drive. I assume that you are editing grub at the boot menu, not the grub.conf or menu.lst file itself? This way you can easily try some commands and see how they work, before making them permenant. Try the following for Windows; title Windows XP chainloader (hd2,0) +1 No reverse mapping, makeactive or rootnoverify lines. I don't have grub installed via Fedora, which probably has different syntax...but let's see. Let me know what error messages that you get, if any.

15,225 reads on this thread???? Someone should do a how-to article.

fd0 is the floppy drive. Where did you install grub? On the MBR (of sda) or on a boot partition created by Fedora? If on a boot partition, then that partition needs to be set active before grub is found. Otherwise, you are booting from the MBR, where grub is not located. This step is often missed or misplaced during an installation by the user.

Wildcard26, look at your original thread that you started. You are using Redhat 9, not Fedora. Try moving to Fedora Core 4 for your system, which should have better hardware detection for your system.

Try Fedora Core 4 for this system. Dell systems can be problematic, due to the legacy hardware on their systems. I'm sure that Redhat 9 is having trouble with some of the hardware.

Three questions. 1. Where do you have grub installed? 2. Where is the installation if XP? 3. What was the original boot order that you had? If you change the boot order from sata to ide or the other way around, you change the drive designations, hence grub gets confused if it was installed when your original boot order was active.

Did you click on the Install button on the "Bootloader Installation"-screen to install a bootloader, or just click on "Next >" to continue without installing a bootloader?

Take a look at my article on how to burn iso images, located here.

Take a look at the PCLinuxOS wiki page which should help. What specific problem are you having? Can you also give us the exact model of motherboard that you have?

What you should be doing, is connecting to DSL via the NIC card. During the Yast setup; Start-->System-->Yast-->Network Devices-->DSL ...is setting up DSL using the NIC card. Note that you have a button to configure the NIC card. If you have dynamic DHCP, then configure the card as such, then proceed to add your DSL settings, such as username and password to login. Once you are finished, try the following. At a console window as root user, type in the following (assuming that your NIC is configured at eth0); dhclient eth0 (hit the enter key) then type in; ifup dsl0 (hit the enter key) See if that works.

Just look at the Asus site, choose to search by motherboard, pick your processor and go shopping! Asus CPU support site Eoin, go to the Suse hardware compatability site.