LLXX

If all your ports are closed then you're going to be unable to connect to the Internet at all! You must have at least one port open...

What Antivirus are you using? I don't think it's an effective one.

DDR should work at any speed below or equal to its rating (and a little above too ). I used to have PC3200 in an old mobo that ran at 266MHz (PC2100).

Feel how much air is being moved through the opening. If the airflow is noticeable on the back of the hand, there shouldn't be any problem.

ASPI has nothing to do with large hard disk support. When you mentioned that you installed the new ASPI layer and it worked, that was probably a secondary consequence that it installed a new driver for the HDD that handles 48-bit LBA correctly. The Maxtor article you linked applies to "1394 ext. Storage Device" - I assume you're not booting from and installing Windows on an external IEEE1394 drive!? The large disk problem is due to ESDI_506.PDR only.

Reversing the air flow isn't good, since the PSU fans always blow outward from the rear. If the air is made to enter from the rear, it'll just exit again out the PSU and "short-circuit" the circulation.If the output fan blows less than the input, the case will be pressurised.

It'll work if you set the "115/230 V selector switch" to the right position.

Remove its CLSID from the HKEY_CLASSES_ROOT\CLSID. On my system it's named 20D04FE0-3AEA-1069-A2D8-08002B30309D. Better to export that key first before deleting it, so that it's possible to restore if it doesn't work as intended.

I've seen that too. It the search assistant thing. It attempts to connect to a Microsoft-owned IP (sa.windows.com, 207.46.248.249) and most likely send them information regarding your search queries etc.

You can also check the digital signature that Microsoft puts on all of its downloads.

Those would be your Windows installation files. Don't delete them unless your HDD is low on space and you have them on CD already! It's very common for OEMs to not even supply a recovery disk with the Windows files on it, but to just put them on the HDD.

Click "To see what data this error report contains, click here" message in the error report window, then choose "To view technical information about the error report click here" and you should see the machine state dump... drwtsn32 shouldn't need to be used for this...

You must be running XP. Disable unneeded services and background programs that load on startup. 50MB free out of 256M is extremely low for an idling system.

That would be the one that took the most damage. Completely killed the USB controller and probably blew the fuse on the "port that the mouse was plugged into".

It might be Ghost, but the symptoms mentioned with the Ghost are a shutdown or reboot, but not "The machine simply powers off and will not come back online unless you unplug and replug the machine". I still say this is a hardware problem.

It might be the Starforce. Look here: http://www.star-force.com/protection.phtml?c=261&id=707

Another DRM attempt by Microsoft... now they're trying to maintain control over what code gets to run in kernelmode. Now I'm even more reluctant to use Vista

Have you tried MSCONFIG in safemode? It certainly sounds like you have a virus.

Have you optimised it to remove redundant files? That can significantly decrease the space required. http://www.msfn.org/board/index.php?showtopic=64996

I'm not familiar with this. Could you please direct me to information on how to decompress this type of file, as well as an example compressed file that I could test with? Assuming there are no technical limitations involved, I'd be happy to add support. Here's a *very* simple implementation that allows the decompression and compression of Zlib files: http://www.dogma.net/markn/articles/zlibtool/zlibtool.htmI've been using that demo program above to manually unpack installers that use Flate/Zlib, and can say that it works quite well for the purpose. I'd love to add support for NSIS installers. If you'll check out my ToDo file, you'll see that it's one of the two specific formats that I'd still like to add. However, to my knowledge there's currently no possible way to extract files from NSIS installers. If you know of a way, please let me know! Can you write a decompressor for it? It's open-source, so most of the decompression code is freely available and ready for use. Basically just the installer without the "installation" portion.

What do you call 'resource intensive"? I often run apps that make my resource meter display a 100% usage of everything, and 0% free, and almost no ram left... the OS still doing fine. Please, concretely tell me what you were doing so intensively? As of today, I still don't know how many apps, running processes and/or windows I can open before it crashes my w98PC. It would be nice to make a test.After 3 weeks of uptime on my main machine I decided to take the test and see how many IEs I could open simultaneously. After opening 43 instances of IE it gave me an "Insufficient memory to run program" error. I managed to open another 7 notepads before it wouldn't let me go any further. At this point, the OS is surprisingly still usable - I could still browse through files in an Explorer window (of which I could open 5 before it complained) and everything appears to be functioning fine. Take a look at the system properties - 0% resources free: After I closed all the running processes leaving explorer and systray, resources free immediately went back up to 83%. Everything is still working perfectly, and in fact this post I'm writing is on the machine that I tested with. So, the claim that Windows 98se cannot handle large resource usages has been disproved. I might try this out with the XP on this same machine.

ROM shadowing may be causing a conflict with the card. Look in the BIOS setup for "ROM shadowing" option... disable it for segment c800.

If you think that will solve the problem go ahead... I disclaim all responsibility. Are you sure it's not overvolted? Look at the voltages in the BIOS setup. DDR should normally be at 2.5 volts. I have the feeling that the RAM you have is being run at 3.3v...

Another possibility: corrupted BIOS? Do a BIOS upgrade if possible.

The importance is that your Operating System must not attempt to write or read files from the disk during startup, as that can make it harder on an already failing drive. It is for this reason that I recommend it be done in DOS. Windows all versions will attempt to write or read certain files from the attached disks when it starts.