Sampson

It is pretty late, and I didn't really have a chance to study the new sysinfo that well, but one quick discrepancy is the Parallel port. In your Bios setting you assign it an IRQ 7. This is not reflected in the Sysinfo. In your hardware device manager the parallel port can be assigned 3 different ways of communicating. I look at it more closely tomorrow.

You've nailed it before, and your probably right. Time to move on.

First PC - 1986 Zenith Heathkit. Began with CP/M system 1984

It was in looking at a previous Sysinfo.txt, that the dicrepancy was found. All I am asking is that you run the System Information program. It refreshes its reading of your system each time it runs. Click on Start/Programs/Accessories/System Tools/System Information. Then, click on the plus next to Components and the plus next to MultiMedia, then CDRom. What does it say? Do the same for Storage and Drives. What does this say? Consider this a fishing expedition.

To enable an interface so that you can use this technology for your programs after you apply Windows 2000 SP2: 1. Log on as Administrator. 2. Click Start , and then click Run . 3. In the Open box, type the following command, and then click OK , where %SystemRoot% is the drive and folder in which Windows is installed: regsvr32 %systemroot%\apppatch\slayerui.dll Administrators can use a program shortcut to set the compatibility mode for a target program. This requires that the Compatibility-mode properties be correctly installed and registered on the computer by using the previous steps. To enable Compatibility mode by using a program shortcut: 1. Log on as Administrator. 2. Right-click the shortcut, and then click Properties . 3. Click the Compatibility tab. This tab appears only if the Compatibility-mode interface has been properly enabled on the computer. 4. Click to select the Run in Compatibility Mode check box to enable Compatibility-mode support for the program. 5. Click either Windows 95 or Windows NT 4.0 compatibility mode in the drop-down box. 6. Click OK to save the changes. 7. Double-click the shortcut to run the program.

Since you have not posted back, I am presuming that you are still having issues. H-P software used to install a SCSI device driver with their CD burners. Look in your Hardware manager and see if it is there. This would interfere with some DVD players making them unplayable. Removing this device from within the hardware manager allowed the DVD to be seen and did nothing to impede the burner.

I don't know of any program that would tell you why the system is indicating usage from a variance of 0-20%. If your computer is on a network, cpu usage may be involved. Depending on the speed of the computer and the amount of memory, the disk cache usage (virtual memory)can kick in system usage. Copying large files between disks will have this effect. Some programs create and maintain log files that itermittantly may be written to disk and this will involve system time.

Since you're resisting Harry's methodical but very sound approach, if you wouldn't mind - Bring up your System Information program. Click on the plus next to Components and the plus next to MultiMedia, then CDRom. What does it say? Do the same for Storage and Drives. What does this say?

While this is a piece of software, it is really a Hardware install. Open up Control Panel -> Add/Remove Hardware -> Choose From List -> Other Device -> Have Disk. At this stage, point it to the .inf file that you've extracted earlier. At least that is how it used to be done, for example, as in creating a ramdisk.

Congratulations!!! I would do a couple of more things. Keep some word processing document running in the background, and cut and paste all of the things you did, the content of the documents you referenced on the web, and the status of your Bios settings. I have made so many bonehead mistakes that I have a notebook the size of a telephone directory. Web pages change and an article you read may not be available anymore and yet you might remember that there was something that fixed an issue if only you could find it again. The other thing is backup your registry. W2k does have a backup for a recent boot but it does not work like XP's that successively backs up. You may never use it, but it is there nonetheless.

Most dual (or multiple) displays are meant to just expand the "surface" of your application over a larger area. I have never tried to do what you're doing so, I most certainly could be wrong in saying that I don't believe that you can run a program in one monitor while seeing your desktop in another under W2k alone. Even with dual processors because most software is not written to take advantage of them won't do it. But, as I said, I've never tried it, so I could easily be wrong. On the other hand, I am a little more certain that your Voodoo Rush might not be able to handle things. The "older" PCI cards most often mentioned are Matrox, ATI, some 3dfx, and certain STB cards. (I know some STB's can because I have one that does.) A lot of these had TV out features and some slow but passable 3D processing capabilities. Running dual displays with two different cards does gobble up memory resources so things can get flakey depending on what you are doing.

Sorry Ron Jeremy, I really need to work on my communication skills. I didn't mean for you to reinstall windows, just uninstall and then reinstall Media Player and Winamp. What I think may be happening with your Retail CD's is that Media Player and Winamp are attempting to go out on the internet to the Database that contains the Name and Title of the CD that you've just inserted into your CD Rom so that they can display the Titles of the songs on the various tracks. So, my guess is that there is nothing wrong with the programs they're just timing out trying to connect to the internet. Bring up Media Player. Click on the Tool Menu item, then Options, then click on the Performance Tab. Depending on how you connect to the internet (cable,dsl,modem) pick the button. For a dialup modem, it is the second choice and give it the speed of the modem. While you are at this screen, Under Internet Settings UNCHECK the selection "Allow Internet Sites to Uniquely Identify You Player" (This has nothing to do with your problem, but you can give yourself a much bigger one since a hacker can aquire your IP and go looking for you). Next, Click on the Network tab. Under protocols put a check in them all. Under Proxy settings will vary. Most often you should set HTTP (double click on it and Use browser settings. On MMS normally you set it: Not to use proxy server. (But if you have to use a proxy server for either of the above, these will vary) If you've changed the way you go onto the Web recently - let's say you used to dialup but now you are using DSL, Winamp or Media Player, may not have been updated and are holding the old settings. You can go into them and basically change the settings to reflect what your settings are in your browser. Or you can uninstall Winamp and Media Player and then reinstall them. (Be sure you download an installing setup of these respective programs from the web first) If you have a firewall, this too may be impeding these programs. Hope this gives you some new avenues to explore.

This is what Microsoft support reports: Code41 Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41) A driver was loaded but Windows cannot find the device. This happens when Windows does not detect a non-Plug and Play device. If the device was removed, uninstall the driver, install the device, and then click Scan for hardware changes to reinstall the driver. If the hardware was not removed, obtain a new or updated driver for the device. If the device is a non-Plug and Play device, a newer version of the driver might be needed. To install non-Plug and Play devices, use the Add Hardware wizard. Click Performance and Maintenance on Control Panel, click System, and on the Hardware tab, click Add Hardware Wizard. On the General Properties tab of the device, click Troubleshoot to start the troubleshooting wizard.

Some who use the VIA chipset advise that you disable ACPI in the BIOS which "forces" Windows to use the IRQ's set by the Bios and then in the middle of installation they choose Standard PC. For some this works better with the 4in1 drivers. For others the regular Windows install using ACPI to handle the devices works fine. Working through the install methodically as you are doing is an excellent (but sometimes frustrating) way to track down the problem. This is just an option that you can keep in the back of your mind.

Good card selection. Reinstall as Sapiens says and you should be good to go. But, since you like to play games, and if you've grown fond of your p3 mobo (and don't want to get a new mobo), you might also consider stuffing it with as much memory as it can hold, and if the budget will allow, making a CPU upgrade with something like a PowerLeap product to go from 450 to 850 or 1GH. These products are a little pricey and probably not as cost effective as a new mobo, etc., but for the little time it takes to install them and the results that you get, you will be able to tap a little more of the power of your new video card since some things are still CPU intensive. It's just a thought since you've taken the plunge in upgrading your machine.

Before you go ripping into things, try these first. This is just to eliminate some possibilities. 1st experiment: Rather than use Winamp or Windows Media Player go to Programs/Accessories/Entertainment/CD Player - if it plays your CD's, you know that the problem is not with the CD and your the Codecs have not been changed.(the error message you get from Winamp can mean that it is trying to look some CD ip on the net and cannot make a connection). If it doesn't play if may mean the codecs were changed or the drivers for the CD's are corrupt. 2nd Experiment: Copy an mp3 from the CD to the Hard Drive. Again try to play the CD using the CD player supplied by XP. If it plays, your codecs are fine. If not the Codecs have been corrupted or substituted. Run your anti-virus software to see if you have some beast lurking on your machine that may have caused the damage. If you can play the CD with the CD player on the CD, reinstalling Winamp and Media Player should alleviate the problem. If you can play the CD with the CD player on the Hard Disk but not on your CD devices it means there is a difficulty with those devices. These things can happen for no reason because they can be hardware related. They can also happen inadvertantly because we have installed some new software or game that puts dll's and drivers in the system that optimizes that software but breaks something else. Have you made any such installations?

shassouneh, Glad you are looking at the heat issue. The factors you want to consider with the heatsink/fan are the volume of air that it pumps and the noise it makes to do it. Installation of the device is the devil in the details. There isn't a lot of room on some of these mobos so clearance is one problem. How it attaches is a big problem especially with AMD processors. Some heatsinks like the AlphaPal practically require you to tear the whole machine apart to attach it. Humor me once more if you would. Bring up your System Information program. Click on the plus next to Components and the plus next to MultiMedia, then CDRom. What does it say? Do the same for Storage and Drives. What does this say? This process will actively query what you have in there. Harry is urging you to consider that one or more physical devices may be the culprit, which may have been harmed by a possible heat issue or an electrical surge, and a methodical bare bones installation of XP is a good first step to eliminating those as a problem. Only then should you move on to something else. I am still puzzled by the number of CDroms reported, the SCSI devices, etc. Don't worry about an A drive when you don't have one installed, all Windows versions reserve an IRQ and memory map for one whether one is truly there or not. It's a database entry. You won't go wrong in addressing heat management, but you might consider eliminating the possibility that other devices need to be tested before introducing new hardware into the equation.

Also in your sysinfo.txt it shows your hard disk to have six partitions. They are not accounted for in the portion I pasted in above. If they do exist and overlap with all of these "CD roms" this is where your STOP 0x00000023 error comes into play. The system is identifying a partition as a CD rom or viceversa. Maybe it is time to look at a new controller card.

Consult this list to see what Hardware is compatible with W2k: http://www.activewin.com/win2000/win2000hcl.txt Though it is a pain, clean intall W2k. I would also pay attention to how your drives are configured in Bios: Master/slave Primary/secondary. If you are installing from a CD using your Plextor, it probably requires DMA support. W2K and XP have a bad habit of initially installing CD's with PIO, which the Plextor will choke on. Have no idea about the 3Com or the Samsung DVD, but if they are not in the list above, disconnect them on your initial install and try to add them with their own drivers afterwards. W2k will install its generic Nvidia drivers, so you may wish to install the drivers and support software for the Asus after W2k is up and running smoothly.

shassouneh, Cute name - Crashproof Drive C: Description Local Fixed Disk Compressed No File System FAT32 Size 14.64 GB (15,719,546,880 bytes) Free Space 5.12 GB (5,494,857,728 bytes) Volume Name WINDOWS Volume Serial Number 103E17E9 Drive D: Description Local Fixed Disk Compressed No File System FAT32 Size 23.64 GB (25,387,204,608 bytes) Free Space 23.61 GB (25,347,031,040 bytes) Volume Name STORAGE Volume Serial Number 086717F4 Drive E: Description Local Fixed Disk Compressed No File System FAT32 Size 2.93 GB (3,144,085,504 bytes) Free Space 2.93 GB (3,143,942,144 bytes) Volume Name CRASHPROOF Volume Serial Number 065A17F6 Drive F: Description CD-ROM Disc Drive G: Description CD-ROM Disc Drive H: Description Removable Disk Drive I: Description CD-ROM Disc Drive M: Description Network Connection Provider Name \\linuxsux\mp3z This is how your system sees your configuration. It counts 3 partitions on your hard drive and 3 CD Roms. Does that compute?

Just to answer your last question, the 850 supported Rambus ram, which, for a while, was Intel's preferred memory solution. Some feel that in the future Rambus will not be supported by Intel. This remains to be seen. The P4 can utilize SDram and DDR ram also. The .18 micron chip and SDram are soon to become relics. What I am saying is that in addition to the "Flavors" of the P4 are the species of motherboards which support the P4 in different ways and with different memory solutions: 850 (rambus), Intel-DDR, SIS, and VIA.

These three articles might help since you're using a Scsi hard drive: http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q242518 which deals with boot.ini http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q157910 deals with disabling synchronous negotiation in your Bios and http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q316243 which will allow you to see verbose messages as to what all those pregnant pauses mean that you are having to waiting for. Finally, your registry can get fragmented like a hard disk. Especially, if you've added a lot of software or patches, the hives should be defragged. There is a freeware program called Pagedefrg.exe that will do this. You didn't mention if this machine is networked. There are ways of speeding up domain accesses.

shassouneh, Obviously you've done something to be able to get it to boot at 1.4GHz when last night it would only run stable at a 100FSB. It would be helpful to know how you accomplished that. Issue 1 Heat: This is what I could find out on the web that others have encountered with this mobo and their advice: "Check your CPU heatsink and make sure it is spec. up to support your processor. Certain older coolers can support up to TB 1.2G. This sort of heatsink will not be good enough for your athlonXP or 1.33G and above processors." "The other possibility is due to the chipset's heatsink. If you remove the heatsink, you will notice that a double sided tape is used instead of thermal paste. The double sided tape is a bad conductor of heat and it will trap the heat of the chipset (that is why when you touch the heatsink, it feels cool). Remove the tape and apply thermal paste onto the surface of the heatsink and attach the heatsink by using two droplets of super glue on two diagnoal corners of the chipset (it might be difficult for you to remove the heatsink, so do it carefully)." ----------------- You said you don't have a floppy. I counted at least two CD's and one DVD device on your sysinfo.txt One CD seems to be to be a scii. On the net there seemed to be an issue about DMA support for these devices for your mobo. Apparently for no reason a device that had DMA support reverts to PIO. A device like a CD-RW which expects DMA support and only has PIO can randomly crash a computer. So, we'll make this Issue 2 DMA support There were two sets of opinions about how to enable DMA support. Both groups seem to think that simply enabling it through XP didn't resolve the DMA support. One group said, "you do need to run SISIDE.EXE to make sure that all of the drives are in the correct DMA mode. Siside.exe does not produce any output when executed. Be aware that It's not enough to set 'DMA if Available' in the device manager, you need to use the utility." The other group did not like using SISIDE.EXE and had this solution, "1st you have to set everything to PIO mode under device manager 'IDE ATA/ATAPI Controllers'. Now After you have set both channels to PIO mode, reboot.When the system boots backup, change everything back to UltraDMA mode just like you did before. Reboot,and presto!" Issue 3 XP shutdown Some experienced problems in that shutdown proceded so hastily that some settings were not saved or became corrupted. This was given as a suggestion: "Some people suggest that modifying the HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Session Manager\Memory management\ClearPageFileAtShutdown to a value of 1 could help because one is giving a 1-2 secs delay for Windows to properly write HDD cache to disk." There were issues with the USB ports. Some had them configured properly, they just didn't work, yet XP reported them as just fine. There were issues with IRQ sharing especially with SB soundcards. Too many to go into now. There were several reports of those who had run their setup for months and then added a new device like a CD who started to have issues like the one's you've been having. Then, again, one fellow replaced his battery and took care of things. When the machine was running at 100FSB did it ever give you a stop message? When the machine freezes after 15-20 minutes does it give a stop message? Would you have a screensaver coming up about that time? Is the stop message different when you try to play something as opposed to letting it fail by itself? I know this is a nightmare for you, maybe something will pan out.

Didn't use ntbackup under NT because of its limitations. We used a different backup program, so this may be totally irrelevant. Two things I remember kept the backup from occuring. Built into a file is a date/time stamp. Our program only backed up files when it found a more recent date/time stamp. It ran but did nothing. Since the offices were closed on the weekends, nothing was backed up since nothing changed. The other thing was that one particular individual at times would not log out of the database at the end of the day locking those files. The backup would refuse to back up. It came on and stopped. Something built into the program would stop it but leave no error message.

The error messages you have been receiving are timing related as well as driver related. Your peripherals are not being recognized correctly at 133FSB. You see this on some systems that have been overclocked and some one component be it a controller, memory stick, a pci card or the AGP, or even the processor can't reckon with the higher FSB. Some component cannot keep up with the higher instruction rate. This could be as simple as the DVD drive not having DMA support or it could be what both Harry and Alien have astutely indicated as possible heat problems Harry and Alien suspect overheating. While you have made it abundantly clear that system is not overclocked, you are running the FSB higher which is going to produce more heat. As you have pointed out this system has run fine for six months without a hitch and it is rated for the speed you have been running it at. But, if there are heat problems, even if very slight, it is known that certain components degrade and cannot tolerate a higher FSB after a period of time, even though they ran flawlessly previously. Let us know how your tests come out.