RJARRRPCGP

I dunno, because I *never* had this problem.

Why would they give you that response? Windows 2000 isn't EOL'ed! It's not 2010!

I agree.

Seems to be related to the version of IPB or a recent mod to IPB. Because I never had to change anything before!

But, Windows XP will prohibit defragmenting directories with FAT32! Thus, there's still fragmented directories! Apparently, the defrag utility that comes with Windows XP will hide directories. Microsoft did this for the purpose of trying to force people to use NTFS.

At least, that was what I was warned about by the makers of 98 Lite. They claim Windows 95C has Internet Explorer integration.

nForce Windows 98 support sucks! Even with supported nForce chipsets, expect crashes regularly!

Windows 95C is more than Windows 95B with USB support, it's the first Windows with Internet Explorer integration included.

I have the same problem! This problem just started occurring today!

--Why is a post with such an old date showing up?-- I just posted to a thread with a majorly old date.

I dunno, because that problem appeared to have been fixed in 1.3.5. When I made a CD with 1.3.5 recently, it worked like a charm. Not even one little problem noticed during the installation process.

Sorry, I didn't see any error message.

I dunno, because that isn't like HFSLIP, for Setup refusing to copy random files.

I don't understand your grammar. Can you please edit your post?

Probably BS. Because it seems to be the same thing as Pro, because it ISN'T 2003 based.

Actually, I get rid of that by going to Control Panel> Administrative Tools> Services and select "Disabled" for the Error Reporting Service. (or similar)

If you forgot the CD tag, then you can forget about even being able to use Windows! Because it probably would repeatedly accuse you of not having the CD in the drive! Sounds more like that the source was previously modified. You are required to start over if you touched it with nLite! I'm wondering, because I'm close to making another Windows 2000 Pro CD! Long story. I decided to throw away my custom Windows 2000 Pro and Windows XP Pro CDs yesterday, because of malware possibly contaminating them!

Sounds like a corrupted download. Sorry.

It probably is corrupted. Please redownload and try again. When a file is corrupted, Windows XP may think that it's a DOS app and because it isn't, it fails! If the file isn't at least 2 MB, declare a download failure!

Here's my new DSL internet connection, with VTel, which is in Springfield:

Windows 2000 apparently is throwing a fit, because of iMesh depending on the Windows XP version of a DLL or you have a wrong version of a DLL! The version that was downloaded likely requires Windows XP!

Ummmm... Corruption of the OS can be caused by MANY other things; the same goes for BSODs. If one of the two sticks is faulty, then yes, there is a chance of getting a BSOD. However, even if you only have one stick of RAM in your computer, there is still a chance of getting a BSOD if the RAM is faulty. I have four sticks of RAM in my home server (each one being 128MB) and it has never crashed on me; not a single BSOD. Motherboard manufacturers put more than one RAM slot on their boards for a reason: to upgrade! Where are you getting this information from? Let me clarify. After I added another 256 MB DDR SDRAM modules with the FSB at 133 mhz and the RAM timings at 2.5-3-3-7, which is a standard setting, to my trusty Asus A7V8X-X motherboard, which I gave to someone. It seemed to be fine when I was configuring Windows XP Pro SP2 with it. But days later, the owner complained about it repeatedly rebooting at the Windows XP logo! Despite the above problem, Memtest 86 passed at least some loops. I didn't have the time to run Memtest86 for longer! I never gotten another complaint after removing that 256 MB RAM module then restored an image that I made. The issue is more likely to occur with newer motherboards. It seems that the memory controller gets strained or a VRM issue with newer motherboards. That's despite they are made to be able to run at 133 mhz. Thus, I'm puzzled, because I wasn't expecting Windows to throw a fit, because it wasn't even overclocked one little bit!

It can cause nLite to crash, with a file not found exception, even when you clicked on "Permit". A possible solution is to disable the application launch control function.

That apparently isn't nLite's fault. It appears that slipstreaming SP2 triggers the problem.

Windows 2000 don't even support WGA! That probably is why it failed. Microsoft apparently changed it so that Windows 2000 don't pass anymore!