danleff

According to the Canon Australian site, this printer is not compatible with Windows XP or Vista. I saw quite a few posts on other forums that suggest that it does not work in XP, so you may have an issue with it. See the cannon support page here. However, I also found a link to XP drivers here. You may want to give it a try. On another note, the NT compatability database suggests that it does work, but gives no details. See here.

cvr has a double post. Let's see if we can stick with this thread, which has already received a response. I will delete the other one, since it gives even less information. The other post refers to Windows server 2003. Quote: how to remove grub prompt on windows 2003 server It was on a thread for RedHat 9, which I am not sure that he has. cvr, please stick to one thread, so answers to your questions can be answered with all the information in one place. This way, you will get a more concise answer.

Is your card a Radeon Club 3D R9800, as per the compatability list? Have you installed the vga drivers, from the Asrock download page?

Well, should be and is are two different things. What make and model video card is it? Did you attempt to uninstall the onboard drivers, as suggested by American Zombie, via Windows safe mode, before installing the new card? When the computer starts to boot, does it show the information for the onboard adapter, or the ATI card?

What model headset is it and what exact operating system do you have?

First, let's clarify what you have. I assume that this is the version 5.0 motherboard model, since you have AGI. Did you assure that the video card is supported by the motherboard? From the users manual; Quote: The AGI [ASRock Graphics Interface] slot is a special design that only supports compatible AGP VGA cards. For the information of the compatible AGP VGA cards, please refer to the “Supported AGP VGA Cards List” on page 8. The list of supported cards is here. If so, then did you change the bios to turn off the onboard graphics chip and make AGI the primary video interface?

Before you look at the bios, did you update to the latest NVIDIA NFORCE4 Chipset drivers for this board?

This drive was mentioned in a previous post. The user sent it back. I went to the Newegg site (who sells an OEM version) and looked at the reader comments and rankings.They either loved the drive or hated it. Two things seem important to get this drive working; 1. Update the firmware on the drive. 2. It seems to work ok when not using Windows Vista beta (which you do bot have). But, the catch is to have this drive as the only one on a given SATA port. So, you have 4 sata connectors on your motherboard, with 2 groups of 2 side by side. In your description, I was not clear. If you try to connect the drive on a SATA port by itself? On otherwords, say your SATA hard drive on one port with this drive connected on the secondary port? So, if the hard drive is on SATA 1 (of SATA 1 or 2) then the SATA DVD drive on a secondary port (3 or 4) by itself?

Yes, you can try Memtest, or if you have 2 sticks of RAM, take one out and see if the problem persists. If so, try the other stick. I assume that you have used good quality memory sticks in the system? If they are two sticks, then they are the exact brand and model sticks? But let's look at what we have so far. I have always needed a floppy driver disk for a sata installation of Windows XP to a sata system. Windows XP just does not have the drivers for sata in most cases. This is an OEM version of XP. I don't know why ASRock says that it will work. Flashing the bios may be the issue, but ASRock does not say this on their faq page. You can flash the mobo with a floppy, according to their web page. If you install Windows XP on another machine, you have the same problem with sata drivers. Installing on another machine, especially a pata only system results in no sata drivers for the new system when you switch the drives. You also need to make sure that the drive is booted and jumpered exactly as in the other system. Win XP may complain about the process, as you changed hardware, which you know it does not like. If you are adventerous, you can try a Live CD version of Linux, running ot off the CDROM/DVD and see how the motherboard behaves. This may give you a clue on what is going on. And, you are sure that your hardware is installed correctly, that the video card and memory are fully seated? Also check the sata cables for good connections and seating? A once also found that I had a bad sata cable, but this does not seem to be the case for you, given what you have already tried. Finally, try setting the bios setting to the default level and see what happens. There may be a setting that is off that you don't know about. Have you contacted ASRock and files a trouble report? They may have a quick answer, before you dump the motherboard.

In the bios, under Advanced-->IDE Configuration, is the mode set to non-raid?

How is the drive jumpered AND cabled on the system now? Does this article seem to apply to you? Did you try Wilhelmus' linked fix?

Linpus is a little lacking on information on their website, but it is based on Fedora, so... If the partition that you can't delete is at the begining of the drive, with the MBR previously occupied by a ext3 partition to boot, then this is likely the issue. What hard drive make and model do you have? You can use the manufacturer's utility to zero write the drive and make one single fat32 partition, then install Windows. The issue is that generally you can't just try and delete the partition(s) easily with a utility that doesn't recognize all Linux partition types then try to install Windows on the drive, leaving the errant partition is on the drive. Many folks make the mistake to think that this will work, just deleting the apparent Linux partition, then installing Windows. But, humbll is correct, what utilities do you have available to erase the apparent Linux partition and make one fat 32 partition. I suggest posting your information here so that users can respond and walk you through a solution.

According to the ASRock support page, if you are not using raid, you do not need to make the driver floppy. Quote: SATA RAID Driver is for users who plan to install Windows OS on SATA / SATAII HDDs with RAID functions. To use RAID functions, you need to make a SATA RAID Driver floppy diskette before you install the operation system, such as Windows XP. If you do not plan to use RAID functions, it is not necessary to make a SATA RAID Driver floppy diskette . Did you try it without the floppy disk driver?

Try looking at this post and booting with the apm=off command.

Providing more information would help troubleshoot the problem. Could you specify what Linux distro and exact version that you are using? Also, what system/motherboard is this? The sound module also looks like it is not loaded. Did you specify what soundcard you have during the installation? Specifying what exact distro and version would help assisting you in detecting the soundcard and configuring it. There may be some other issues, but starting here would help.

Take a look at this article which should help.

What happens when you add the command acpi=force to the command line when you get to the installation main menu?

If you are not getting a post on attempted boot with the DVD drive connected, then this is not an XP problem. Well at least not at first. What exact model of the motherboard is this? There are four models. I wonder if the bios is set for RAID rather than IDE for the sata interface in the bios. get into the bios (delete key on boot) and choose Integrated Peripherals-->SouthOnChip PCI Device--> and see if the onchip SATA Type is set to IDE Controller. Once that is set (save the changes), then try to boot into XP.

The Windows CD does not boot. as I assume that you allowed Fedora to take over the entire hard drive during the installation. Windows can't read Linux partitions, so the Windows CD dies, as it can't find any fat32 or NTFS partition on your hard drive. The easiest way to do this now, without knowing what you already tried, is to grab the utility from the hard drive manufacturer for your hard drive and reformat the drive with one large NTFS or fat32 partition, then install Windows. For example, if you have a Maxtor hard drive, use it's Maxblast utility to do the job. Of course, this assumes that you have another PC that you can download the software with and burn a cd. The other method is to use the first Fedora boot cd and progress through the installation steps to the partitioning section. Choose custom partitioning and tell Fedora to format the drive to fat32. Allow the partitioning to occur, then stop the installation process once the drive is partitioned. Then install XP. Finally, you could also download a Live cd of Knoppix or Mepis, then use the included partitioning utility (gparted) to format the drive to fat32. This assumes that you did not allow Fedora to use LVM partitions on the drive. I'm not sure if gparted can alter LVM partitions, but you could give it a try.

What version of Ubuntu are you using? Is it an AMD64 version and are you running an Athlon 64 processor?

Grub error 17 appears when Grub recognizes the partition that you are trying to boot, but the file system type does not match the OS that you are trying to boot. So, we need more information. Do you have Slackware dual booting with Windows? If so, when does the error occur, when booting Windows or Slackware? Very often this happens when you have a system with hidden partitions, say an HP or Compaq system that has a hidden recovery partition. Is this the case with your system? Did you partition the hard drive space before installing Slackware, or allow Slackware to do it for you? What did you choose during the process? Did you change the boot order of the hard drives (if you installed slackware on it's own hard drive) in the bios at any time during the process? No I am not recommending you do this!

Take a look at the FAQ page that will answer several questions like this that you may have.

Do you have the users manual? Looks like there are some real issues with some Vaio laptops. Look at this article on Fedora. Additionally this one speaks to your actual video driver.

Is this the same system in your other post? Make and model of the system, please?

With each post comes some useful information. Just to note, your version of xpress recovery supports sata drives, according to the motherboard manual. Quote: and it has 3 pci slots with 2 purple ram slots and 2 orange ones with no built in video card and the thin that throws me off is that the heatsink is diagonal not flat like the fan on top of the CPU hope I'm making sence here lol The Gigabyte website states on the picture for the board, that it is for representative purposes only and may not match your board exactly. Was this system purchased from a vendor, or built by someone? What do you mean that the heatsink is diagonal? Is it not resting directly on top of the processor? If not, most likely a clip has popped off the the processor socket. This could explain the boot issue. Do you get any bios beeps on boot? How many, and short, long, or a combination of both? This can help narrow down the possible problem. If this is a system that was purchased from a vendor and has a warranty, take it back to be repaired. If someone built it for you, consult with them and have them look at the motherboard and processor to see if this is the issue, noted above.