RJARRRPCGP

Really? Just like eMachines. eMachines uses MSI too.

If Windows never finds the HDD, then it probably is because the BIOS failed to detect the HDD.

It needs to be h4x0r3d! Of course it failed under Windows 2000, because Microsoft wants to screw Windows 2000 users!

There's also the following issue: If you use more than one stick of RAM, the OS may get corrupted. There's a chance of a BSOD. Also, Windows may silently get corrupted, it's fine, then when you turn on the PC the next day, you get a crash and can't use Windows! The symptom may be a BSOD or it reboots over and over again at the Windows logo.

You need to OC that Barton some more! 2.2 Ghz is wimpy for today's standards.

You will only ever have this issue if you do not keep your windows up to date. I dunno, because there seems to be often occurring zero-day exploits! After Blaster in 2003, came Sasser in 2004. That's the reason SP2 comes with a firewall!

LOP? LOL. The only time I gotten LOP was when I went to a pr0n-related website back in 2003 or late 2002.

Have you ever noticed musical chords having a color? Or letters and/or numbers having a color in the mind's eye? Examples of synaesthesia: http://www.jwannerton.pwp.blueyonder.co.uk/itow.htm

I said that because the service pack wasn't reinstalled. The repair function downgraded the files to SP0!

Discarded. I have an DMA/100 HD but is used in DMA/33 mode (i have a 440BX based board). Well, i will change my awe 64 to a SB 128 pci in two weeks(and my riva tnt will made more heat). Thanks for help . It only occurs with motherboard chipsets that support UDMA 100 or higher. If the BIOS reports UDMA 100 or higher, then Windows 2000 without service packs at all will think that the HDD don't support DMA.

That probably was because the HDD was in PIO mode! Windows 2000 without service packs is incompatible with HDDs higher than UDMA66! Without service packs at all, Windows 2000 will think that the HDD don't support DMA at all! What in the world does that have to do with anything? I won't even get into the that your facts are wrong. On some motherboards, it will go right to PIO mode without a service pack. This is a known issue. Also, I confirmed it. I saw the HDD in PIO mode after installing Windows 2000 Pro without any service packs at all on a Via KT133 motherboard. After I installed service pack 4, it was back in UDMA mode. But there was a hotfix for Windows 2000 without service packs. Information about that here at: http://www.hgst.com/hdd/support/w2kata100.htm

That probably was because the HDD was in PIO mode! Windows 2000 without service packs is incompatible with HDDs higher than UDMA66! Without service packs at all, Windows 2000 may think that the HDD don't support DMA at all!

That's exactly how I've always perceived time......as a pictograph. (or picture, fading into the distance, getting dimmer and dimmer as the years pass) I've always perceived a year as a circle, well lighted by the sun during the summer and in the shade in the winter. But why did you ask about "Synesthesia" ??? It's definitely not something normally discussed. Andromeda43 B) Because I had feelings of things having a color or a color feels like it fits. I seem to have that with music! I also may with letters!

The nag about not having USB 2.0? That's a feature that was introduced in Windows XP SP2 (or SP1). If you plug in a newer USB device into a USB port in USB 1.1 mode, Windows will nag you about plugging it into a USB port that's in USB 2.0 mode.

Don't jump the gun. It could be nothing. Try unplugging your HDD connector (IDE or SATA/2) and reconnecting it. My in-law had that issue with NTFS.SYS and doing that fixed it for her. Otherwise, boot to your XPCD and do a repair install. If that doesn't work, plug the HDD into another system, backup your data and reformat. If that doesn't rectify the issue, it's likely a faulty HDD, which you can determine by downloading and burning the Ultimate Boot CD 4.0 and testing it with the appropriate tool. The same error can occur if your processor is overclocked too much or not enough Vcore.

Maybe if you don't know what you're doing. I'm serious, port 135 and 445 are open by default! That was very smart, Microsoft! Unless the ISP is blocking those ports, you're probably gonna get attacked! Expect to eventually get this from Windows, "The system is shutting down, because the RPC service terminated unexpectedly." and etc. or similar. And likely Windows file corruption. It's likely that you're gonna get often occurring DOSes.

That defragmenter needs major work! It crashed on me, apparently, because of Windows denying access to a file, because of it being open. Apparently, it crashes instead of just skipping the file! Thus I have to say this, DefragNT definitely don't hold a candle to JKDefrag. JKDefrag has a GUI while being just one file!

An easy way to crash FF.... Start downloading anyfile through FF's Built in downloader Close any instances of FF except the download status window. Reload FF Should crash FF. If it dont work, try again... No such problems with IE7 or Opera9.xx And yeah ...What a memory hogger! just tried that, downloading ie7 (oh the irony) closed ff and reopened - nothing! ff didnt even flinch, but lets not argue, each to their own I'm with you. Firefox never crashed when I opened another Firefox with one Firefox downloading a file. Sorry, Lightbringer, I can't reproduce the problem.

Kingston? My memory supplier tells me that about 80% of Kingston memory is refurbished RAM, made up from chips that failed final inspection at the original mfg. plant. There will NEVER be any kingston ram in any PC of mine. RAM is the very Heart of any system,,,,,not a very good place to pinch pennies! Good Luck, Andromeda43 B) That sounds like BS! Otherwise, it wouldn't overclock for Jack! I had good luck with Kingston. My PC2700 overclocks good for PC2700.

That error sounds like likely a Windows error, because of missing DLLs. Did Windows give an error such as "The application failed to initialize properly. (0x00000135) Click "OK" to close the application."

Because of the first error, likely a hardware malfunction. Please check the caps on the motherboard. A while ago, badcaps.net has been reporting a rash of bad caps in Dell PCs.

That motherboard likely has bad caps.

I agree. My Asus A7N8X-X has a long POST sequence. It may seem that it's gonna fail to boot, but it always booted.

I dunno. But I have good news, with Avast, the entire program is smaller than 15 MB! Also, the defs are no bigger than 1 MB, AFAIK and likely at only 512 KB or around there! Avast is available at: http://www.avast.com

Probably a RAM malfunction. This is because your RAM is overclocked too much, overheating or incompatible with the motherboard (or processor, if it's an Athlon 64). I gotten that before when defragging, because of my RAM overclock when I was overclocking some PC2100 DDR SDRAM. If you're overclocking the RAM, increasing the VDIMM may solve the problem.