cluberti

Does this issue happen from a reboot in safe mode, or just regular boot? If it doesn't happen in safe mode, you can be sure it's a driver or startup application/service causing the issue. However, if it happens in safe mode too, it could be that the machine is crashing - could be an issue with the software, but it could also be hardware. Make sure you've configured your PC to create a COMPLETE memory dump, that your page file is on C: and is at least RAM+50MB in size, and then try to make the problem occur. If the machine is crashing (not from hardware errors), it should now bluescreen rather than just reboot. If the machine still just reboots, I would consider checking the hardware (especially the RAM) for errors.

Normally, when we see these sorts of errors during setup, it indicates a hardware failure. I am sure you've been told to check the RAM and the CPU for errors, but consider the hard disk another area where faulty sectors or the start of a failed disk servo could be causing this as well. I would contact the vendor of the disk to see if they have a low-level format utility you can run on the drive to make sure it is indeed formatted and clean before installing, and you may also want to check the disk for physical errors or sector errors as well before continuing. If the stop errors you are seeing are always stop 50, it could very well just be a bad sector (or worse, a faulty disk).

You would have to do this from a boot disk outside of XP, either a floppy or CD, that makes the first partition unhidden and active. I'm not sure this can be done from within Windows XP itself (perhaps it can be done with partition magic or another 3rd party software like it, but Windows itself won't have a way to see the hidden partition).

Is this happening in Windows XP, or XP MCE? If so, there are some known issues with ATI drivers. Since you haven't provided any data other than an error message, this is as much as I've got right now.

It depends - most files can be unregistered, replaced, and then re-registered using the regsvr32 command, but there are some system files that are memory-mapped, and thus require a reboot to replace (the file loads into memory and is read from there, rather than disk, and only a reboot can unload it for replacement).

I'd say that unless you've done a typo on the domain, that is the issue - there's no tld at the end, and thus Exchange DNS lookups on the FQDN are failing. For reference, it's even telling you which RFC it's failing on, RFC 822. http://www.faqs.org/rfcs/rfc822.html

Perhaps check the vcore settings of the motherboard to the processor, make sure your BIOS and motherboard are compatible with the processor, and lastly run the system through some sort of hardware diagnostics checker. Not sure what else to tell you - you already know what a machine check error is, so perhaps AMD or your motherboard manufacturer (or again, the vendor of your machine) could give you some insight as to why this keeps occurring?

http://www.windowsnetworking.com/articles_...l-Networks.html http://www.windowsnetworking.com/articles_...-Directory.html http://www.windowsnetworking.com/articles_...s/wxpjoind.html Those should get you started.

No, but I would update your antivirus and antispyware software to the latest definition updates, then boot into safe mode and use both to scan your PC for viruses and spyware.

If you can configure the RAID in the BIOS of each controller, that would be much more recoverable that doing it in software in Windows - if Windows dies and you can't restore it, the software RAID is gone too. If it's on the controller, and you lose Windows for some reason, the data goes nowhere and everything is (relatively) kosher. I would go with your first idea - RAID1 for the OS and RAID5 for the data volume.

Something simple - try removing the network cable and booting to see if it makes a difference...

Create a host in dns called www, using the IP address of the website. This is expected behavior.

MsnMsgr.Exe is the main executable for MSN Messenger. However, this file has also been known to be seen with issues like this after being infected with he Mytob and SDBot worms. Since this happens on a schedule, check and see if you have MSN Messenger installed on your computer. If not, I'd say booting in safe mode and doing a full system scan using the latest version of your antivirus software's definitions is in order, ASAP.

http://www.winguides.com/registry/display.php/790/

You can make a boot volume a RAID1, but not a RAID0. http://support.microsoft.com/default.aspx?...;302969&sd=tech

To each his or her own. B)

You can add autologon settings to your sysprep answer file - it's in the help file.

A RAID controller would be a hardware device, not software (although NON boot volumes in Windows can be configured as such within Windows). You would go about doing the following, if you really want to do this: 1. Purchase a PCI IDE RAID controller, either at your local retailer or online 2. Back up your personal files to another PC, a CD-R or CD-RW, or an external hard drive or USB key 3. Format both hard drives using a DOS boot disk (www.bootdisk.com) 4. Power down your PC 5. Insert the new PCI IDE RAID controller card into your PC 6. Attach both hard drive data cables to the new IDE RAID controller 7. Power up your PC 8. Follow the instructions that came with the IDE RAID controller to enter the BIOS 9. Follow the instructions that came with the IDE RAID controller to create a RAID0 array 10. Reboot your PC, and install Windows XP

Prime95 is a system test/stress test tool. http://www.mersenne.org/freesoft.htm

Windows will try to correct soft errors whenever it can - however, if you're getting this message, the processor is at fault whether the box BSOD's or not. Also, make sure you're running the 64bit version of Prime95, because the 32bit version only stresses the 32bit subsystem and does not touch the extra registers and such that are 64bit only.

replmon and netmon would be two good tools to monitor replication.

Tell us how you really feel .

That kind of replication is not unheard of, but at those data sizes you would need to have a relatively fast network (1GB or better), good chunks of memory (the file cache on those things will be huge, and you'll need at least 4GB of RAM to keep it fed), and at least a cadre of 10K SCSI disks (15K if you can swing it, and RAID10 if you are able, to really keep I/O bottlenecks from occurring). I would also recommend NOT running antivirus software in realtime scanning mode on either node as well, as this adds at least double the processing time per I/O request. You would also do well to upgrade to R2 on those machines to get the DFS and FRS improvements in large file replication (copying only updated files and updated portions of files, faster replication, etc). FRS and DFS in R2 see huge improvements over their SP1 counterparts in heavy use scenarios.

Except the things borrowed from the 9x line that we take for granted in 2000/XP/2003/Vista, like plug and play and laptop battery support, for starters . I'll agree NT-based OSes are more stable and ultimately more viable as a desktop OS than Win9x ever was, but to say 9x was awful does it a bit of injustice.

If you've got Windows Server 2003, install SP1 and you will have one built-in (same as XP SP2's firewall). As long as you steer clear of McAfee, you should be fine with whatever you choose. http://news.zdnet.com/2100-1009_22-6048709.html