Because there recently has been a rash of bad cap reports with Dell PCs, it's likely that your Dell PC has bad caps!!! Please go to the following web site below for more information: http://badcaps.net
Actually, if the RAM is stable, you probably can leave the turbo setting on and disabling the assign IRQ for VGA option isn't a good idea, because video cards require an IRQ and thus doing that can cause the video card driver installation to fail.
First off, Windows 9x isn't "emulating" 32-bit code, it has real 32-bit code, but it's hybrided with 16-bit code, thus causes confusions. Also, it's not just a "GUI shell" on DOS! Otherwise, many games wouldn't run on that OS!
LOL. I doubt that a PC made in 1999 would outperform a Celeron 850 mhz, because they weren't even such thing as anything faster than 600 mhz back in 1999.
LOL. How can it physically damage a hard disk drive? Are you literally saying that an EMM386 conflict can cause a hard disk drive to get damaged so that you can't even reformat it anymore?
If fdv is around, I wonder if the sound card drivers are guaranteed to be Internet Explorer dependency free? I want to make sure that a driver package don't sneak Internet Explorer back on to a Windows 2000 installation with Internet Explorer removed.
This switch is said not to be working in post SP1 XP....? jaclaz <{POST_SNAPBACK}> Actually it's invalid with Windows 2000 SP2 and later, thus, all versions of Windows XP!
There's a known issue with Western Digital HDDs that cause this. Because of being required to change the jumper setting not only to change from master to slave (or vice-versa) but also required to change the jumper based on how many HDDs are on the IDE channel! With Maxtor HDDs and probably the same with Seagate, only required to change the jumper setting on the HDD if you want to change it from master to slave or vice-versa. With Western Digital HDDs, you're required to change the jumper setting if you add or remove a HDD that's on the same IDE channel.
Believe it or not, that message isn't generated by the BIOS. It's generated by the boot sector! Unless a disk a explicitly made to be bootable, that message text is written to the boot sector and thus is displayed when attempting to boot off of such disk. Thus that message means that the boot sector isn't bootable! The fix is simple: With Windows 9x: Use a DOS boot floppy that was made under the exact version of Windows you want to install then type sys c:
The HP OEM one sucks anyways, thus if you don't require access to a camera that you have, you can try Linux. As long as you don't have a software modem, you shall be fine!
If there isn't a fix for HDDs larger than 128 GB, (I hope there is!!! Can you please give a link to free fixes found?) look for a jumper setting to limit the HDD capacity to 128 GB or less, but that option (varies with HDD manufacturer)may jump down to a limit of 32 GB. (If you don't mind getting brand new HDDs then setting them to 32 GB with a jumper setting sometimes known as the cylinder limiter jumper. (or CLJ in the HDD manual) (read the HDD documentation for jumper setting information)
No, it won't unless there's a bug in the defragmentation process that causes files to get misplaced when moving them to certain areas of the HDD. There are smaller cases where Windows may flip out with a system is low on virtual memory error, page file too small error message or a system has no page file error message. Also there was a case where some files of an application got corrupted. I would try to make a bug report if ***ANY*** of the above mentioned symptoms occur after defragmenting the HDD.
Were you installing a newer version for Internet Explorer? If the Internet Explorer installation process fails, you're probably are going to get the above symptoms.