danleff

Glad that it worked out for you. Good work!

Does this diagram help? And the manual page.

Did you try the solution tree on Symantec's site located here?

Just deleting this file may not rid you of the spyware on the system. Do you have any spyware utilities, or antivirus software on this system?

On some rare cases, the motherboard ps/2 port goes bad. The USB keyboard will only work when you have that option available (enabled) in the bios. Usually you get an error message that the keyboard is not present when the ps/2 port is not working. Your system also seems to have a problem with the hard drives, as well. Can you enter the bios on start-up? How you do so usually depends on the motherboard in the system. As the system starts to boot, you should see a message on what key to push to get into the bios. Does the keyboard work when you try this? Was the system working recently, or has the system not been used in a while and the problem occured when you tried to boot the system after a long period of not being used?

What message do you get after typing in bootcfg /rebuild directly after entering the recovery mode? No other commands, as suggested. Do you get something like; "The windows installation was successful" "Total identified windows installed: (number)" or straight to the error message?

Did you try the troubleshooting tree at this Netgear page ?

Did you get into the chroot enviroment, using the Fedora 1st install disk before trying the fix? After booting to the command menu; linux rescue then when you get to a command line, after making sure you are root user; chroot /mnt/sysimage The syntax is also very important, so check it carefully. grub-install (space) --recheck (space) /dev/hda Quote: I have found if I press F8 while startup I get the boot option but with only the option for XP to choose from. Do you mean that you get the Windows safe mode by pushing f8 while the system is booting, or otherwise? Look at this thread for a detailed synopsis.

OK, I was just yrying to see exactly where you were at. Answering these quesrions helped me to understand what you really did and what the bootloaders were doing, based on what drives were on the system. What happens if you try these steps exactly as described in the article?

Question #1: Are all your hard drives sata drives? If not, then the boot order is dependent on what the bios is set for sata/ide... vs. IDE/sata... #2: Do you get the Grub boot menu with no way to boot any OS, or just the word Grub on the top of the screen with no options? #3: You told Ubuntu to install the grub bootloader on the MBR of the boot drive during the installation? #4: You told ubuntu to just install on the new drive? If Ubuntu was indeed installed on the second drive and the bootloader on the MBR of the original drive, then you can´t just remove the Ubuntu drive, as the reference files for Grub are on the drive that you removed. Grub then is unable to find these files that it needs to boot either OS.

Take a look at this article which should help.

Does this article help?

In theory, mixing RAM of different speeds, as long as they are supported by the motherboard, is not an issue. I have done this, but saw the lack of overall speed difference. The issue is with mixing different brands and speeds, as in your case. This can cause unpredictable results, since not all RAM is created equal between brands. I would try the best (faster) RAM first, then is that works fine, try adding the second stick. Your system will complain with bios beeps if there is a problem. Also, if you get unexpected crashes or errors, you have your answer. So the rule of thumb is; 1. If the RAM brand and type is supported by the motherboard. 2. RAM of the same brand and speed is preferred. 3. Take chances with RAM of differing speeds (ratings) and of differing manufacturers. I've seen RAM of specific brands cause problems in some systems. Your best guide is the manufacturer's web page and if they have a compatability database of supported brands and types on the support page. Of course, if it works...then....

As I suspected, Fedora treated the installation, as you did it, as if you had one hard drive in the system. So now you have Grub booting, but with an error, as both drives are not set up in the /boot/device.map file for Grub. Try getting back into rescue mode and chroot, then try; grub-install --recheck /dev/hda ...and see what happens when you reboot. All this assumes that the second hard drive is primary slave, as you said.

What probably happened is that the recovery process did not format the hard drive fully and left the MBR intact. Since you removed the Grub reference files from the old Linux partition, grub can't use these files to boot the system. Either the grub reference files are gone, or the location of the files has changed in the process (from the old Fedora partition). Do you just have the recovery disks, or a full install CD of Windows? Do you still have the Fedora install CD? If no to both, do you have access to a computer that you can download the hard drive utility (from the hard drive manufacturer) to properly format the drive? What system (make and model) is this?

Sounds like everyone is playing it safe, but i can understand this to some degree. If you know enough about systems to install a hard drive, then you would not need to ask the question. What did ASRock support say? Looking at the product support page for your system, any hard drive that has an IDE (ATA, NOT sata) interface, under 300 gigs, should work, to be safe. These motherboards can be tricky. Do you know how to install a hard drive? If not, do you have a computer savy friend that can assist you? Are you looking to just add storage space, or use another drive to be the main OS holder for the system?

At what point exactly does the system stop? Do you get any error messages at all? Do you just get a cursor with no message? Give as much information as you can, as the problem could be a multitude of things, depending on where the system stops. Do you hear any noises, beeps, grinding......? Were there any problems when the system was last used, which was when?

Are you trying to do a fresh install of Vista or an Upgrade installation? What version of PowerISO are you using? From what I read version 3.7 is compatible with Vista. What exact make and model Geoforce card is this? VGA...PCI-E? Did you run the upgrade advisor before the installation attempt?

You most likely installed the Linux bootloader on the secondary drive, not the MBR of your boot drive. See my article here. Quote: 2nd drive shows Slave as empty with RAW file type. What utility did you use to view the second drive? If from within Windows Computer Management, undersand that Windows does not see the partitions as you would expect. What type of filesystem did you select during the FC5 installation? The default? Are both your hard drivers IDE drives or one or both sata drives? Let us know if this helps.

Most Linux distros have taken great pains to get their systems to auto-detect Internet connections, as most users want to do this without the hassle of manually doing so. You can go to System-->Administration-->Networking and highlight your ethernet connection. Choose the edit button and uncheck the option of starting the connection on boot. Then save the changes. When you want to start the connection, go back to System-->Administration-->Networking and activate the connection.

Long time since I have done a modem setup, but can you be specific about what you tried so far? Did you try to set up the modem by going to Start-->Settings-->Networking?

Realize that you posted on a Linux thread. The previous folks also had a dual boot system with Linux...so that is why I asked, to make sure. See this Microsoft article for a descrpition of the issue. Has something changed in your system just before this occured, say a newly installed program, driver or hardware that required you to install a driver? Did you just try to install a service pack that failed? Did you do a recent backup of the system, or have a another problem that caused the system to reboot?

Can you be more specific? When you say that you did not split your hard drive, what do you mean? The previous posts refer to users with Windows XP and Linux installed on their systems, when they encountered the error. Is this the case for you? If so, what distro of Linux did you install...and do you have a dual boot situation right now?

Nice going!

When you set the VGA to Onboard, is there another option to disable it? According to the users manual, there should be. Auto enables the onboard totally. Kinda confusing.