RJARRRPCGP

Sounds more like an occasional message about explorer.exe not responding. When logging off.

In my experience it didn't make a perceptible difference in system performance moving from a single 7200rpm SATA disk to 2x 10000rpm Raptor SATA disks in RAID0.Again, this is my experience from my style of using Windows and applications, so other people may have different experiences. I had XP x64 and Vista x64 on the same RAID set during Vista's beta period and it was clear after a while that Vista's Superfetch out-performs XP's prefetch once it has had chance to build a history on your commonly-used apps. Reading the data from disk before you need it is so much more useful than being able to read it on demand a fraction of a fraction quicker. High RPM disks are useful for sustained, contiguous disk operations - if your data is fragmented then the disk will spend a lot of time seeking inside of reading.If applications read a lot of small files then high speed doesn't help so much. For me, the cost of 10k over 7.2k rpm disks is not worth it, plus the Raptors are noisy beasts. Actually, vice versa. With many small files, it's better to have a lower random seek latency. That's the benefit of a Raptor.

How did you get a 25,000 MB partition?

It probably is a virus. Probably the dreaded Blaster virus. Probably because ports are open. You probably don't have a NAT router. A firewall is required! Windows XP, starting with service pack 2, has a firewall by default. Windows Vista includes a firewall already. *If you slipstreamed service pack 2 or later, make sure Windows Firewall is running!*

In that screenshot, I saw 48 percent for "NMIndexStoreSvr" which seems a little high.

I checked the cable and it was fine. Appears to possibly be that the ID'ing of Samsung HDDs cause Windows to think there's an IO error. Samsung was NOT a common brand, thus may have ID compatibility problems. Or compatibility problems with southbridges. Because that cable was fine afterwards and Windows didn't give an atapi error in the event log. (usual sign of a damaged IDE cable) Also, it passed a scanning test with MHDD, AFAIK.

The links are bad!

You must disconnect all other drives other than the CD drive and try again. If Windows Setup sees more than one physical HDD, you will have this problem.

When I installed Service Pack 2 (before Service Pack 3 was official) on an MSI 845 E Max motherboard and Samsung SpinPoint SP0802N HDD, when the Service Pack 2 installer was ready to reboot, then after I rebooted, I then saw a flash of blue and then it rebooted AGAIN after the Windows XP logo and that would repeat. Service Pack 2 (and possibly later) seemingly gotten confused when it encountered the fact that the HDD is a Samsung. POSSIBLE CAUSE: Windows XP installed the wrong disk driver when it noticed the Samsung SpinPoint SP0802N. -------------------- I NEVER saw this occur with a Maxtor nor a Seagate nor a Western Digital. Has anyone with a Samsung SpinPoint HDD gotten stuck in a reboot loop after rebooting to complete the service pack 2 installation from Windows XP without a service pack?

But, it's fine with a T-Bird 1.4 and Asus A7N266-VM/AA. I installed service pack 3 for the first time yesterday, on July 2, 2008. (A test bed) I would like to know if the generation of AMD has something to do with it. It will suck if Windows XP gives that BSOD with a Barton. Thus, reminding me of a buggy motherboard. LOL.

I saw a web site with someone claiming Windows XP keeps rebooting after installing Service Pack 3 with an AMD processor. (I assume, because I didn't see the person talk about the chipset) And the person claimed there's a patch for that problem from Microsoft, but not official. Now, I may not be able to use Service Pack 3 with my Asus A7N8X-X and Athlon XP 3000+.

This may be because Microsoft decided to block anything other than XP Home Edition from using the upgrade mode. Or Windows 2000. The installer likely disables the upgrade mode when the installer sees XP Professional. It likely ignored the settings, because it wasn't ran from XP Home Edition.

Did you burn with Infra Recorder? If you did, it's a known issue. Sorry.

Looks like motherboard issue or a PSU issue.

It may mean that you have a corrupted burn.

The ONLY child proof way is to NEVER allow to be logged in as an administrator!

I have model SB0100, which is a SoundBlaster Live! 5.1. Anyone else gotten the drivers installed and installed properly with the SB0100?

That's a message from the bootloader on the HDD, wipe the HDD, repartition, reformat and try again.

Could be the power supply or processor. (less common)

Sounds like Windows 98 may be giving an error about a file, because of the DDE file associations. Messed up registry updates done by Opera is possible.

But, the Windows 2000 CD gives me "NTDETECT failed" . Are other people having this problem with Infra Recorder? That's despite I gotten the boot image with BBIE and selected the settings equivalent to Nero: The segment at 0x7c0 and the size at 0x4 and "None" for emulation. This is OK with Nero. It's looking like I'm forced to use Nero.

The second error usually is caused by disabling the swapfile (also known as pagefile) with limited RAM capacity.

Actually, the same can be said for XP. Windows 2000 is my backup OS. You don't have to worry about Windows Product Activation and Windows Genuine Advantage with Windows 2000.

Your symptoms sound like a corrupted Windows XP installation. Sorry.

Sorry, that's not correct, if the place you're at isn't in the list, you can't get it!