Myke

Well, if you want to do it completely from scratch, then delete the partition(s), create a new partition, format that partition and reinstall the OS. The easiest way to do this is to use the installation disc that came with your machine. Insert it and boot up your machine. Watch for the lights on the keyboard; after they blink, hit F12 a few times until you hear a beep. This will bring you to the boot select menu. Here, you'll select to boot from the CD drive. Once done, you should receive a message asking you to hit any key to boot to the CD. Do that and then follow the on-screen instructions. Make sure you format the partition in NTFS, not FAT32.

You don't want to the system scan the Internet for updates because you will always receive the same message. Try downloading the drivers from the manufacturer's website for the specific model. Then you will be able to force the install by selecting the location Windows will look for updates.

Even if they say they are up to date, force a manual install because you might have corrupt drivers. I doubt the ISP tech. support will be of any service (they only frustrate me), but if you've run out of options, it might be worth a shot.

Go to the modem's manufacturer's website and then the support section. There should be a link in there for downloading drivers. Then search for your model of modem, download and install it. If the file you download doesn't automatically install, you go manually do so by right-clicking My Computer and selecting Properties. Go to the hardware tab and click Device Manager. Look through the categories for the modem and double-click it. There, you'll be able to manually install the driver.

It couldn't hurt to take a look. Have you tried reinstalling the drivers I mentioned. Worst case scenario, you still have these problem, but we can at least say we tried it.

As from what I've read, the BAD_POOL_CALLER 2c, 00000007 errors are pretty trickey to troubleshoot. Does your event viewer show anything with more detail? When you are playing this game while using the ethernet port, do you experience this problem? I know that you said there is a latency issue, but this will help narrow down the choices. I'd suggest working on the drivers for the modem and USB ports. If that doesn't work, then all that's really left is horrid debugging.

When performing an install of Windows XP with an installation disc that didn't come with the entire system, the most common driver issues are the ones you are speaking of: network adapter, VGA, and sound. I suggest going to the retailer's (of the motherboard), download the specific drivers, and install them manually. I'm making the assumption that they are all integrated, as that's what it looks like. As for formatting and then a clean install, the installation disc is the easiest way to do this. When your system first boots up and you see your keyboard flash, hit F12 a couple of times until you hear a beep. This will bring you to the system boot menu, where you will select booting to the CD drive. Make sure you watch the screen, because it will most likely tell you to "Press any key" to boot using the CD; otherwise it will just continue on as normal. Follow the instructions on the screen and delete the partition with the OS installed on it. Use NTFS as the format options, performing a long format. You will still run into the same driver problems you are having with a clean format. NOTE: Formatting will erase all data on your HDD, which won't be recoverable. I'm sure you already know this, but I just have to make mention of this to ensure that I'm not responsible for any lost data.

When you get the blue screen of death (BSOD), what are the hexidecimal values (e.g., 0x0000001a). There will be one initial value, followed by four more parameters in parenthases. This will help us determine more specifically what is wrong.

As per this article (http://www.practicallynetworked.com/sharing/xp_filesharing/), Windows XP Home only supports simple file sharing, while XP Pro can make use of ACL lists, although simple file sharing is on by default. This may be the reason why Pro can access Home's shared documents, but not vice versa. You might be better off removing all of the shares and starting over, unless you find something in the related link of the above mentioned site which can help you. The link may seem silly or possibly insulting, but I have a feeling that this is something very simple that we're overlooking.

Regardless of the name of the user, if the user has admin rights, then it won't make a difference. As for the sharing issues, check the Pro's firewall and ensure that File and Print Sharing is enabled as an exception. See if that helps.

Macs are good machines, there is no doubt about that. The thing about Macs is that you're paying for a social symbol more than anything else. If you're doing anything artistic (music, art, etc.), then Macs are the way to go. If you're doing anything business related, then Macs are horrible and should be avoided; stick with PCs. If you're a gamer, then Macs are crap, as developers don't usually program games for Macs. If you're just wanting a machine for internet access and music organization, then it's completely your choice with the money you want to spend. Macs are a huge trend right now, thanks mostly to their amazing marketing campaign (despite that it's not completely true, but not lying).

If you still have the diagnostics disc(s) that came with the computer, I recommend using it(them). The discs contain other useful tools to help you figure out what is wrong with your system. Also, when your system first boots up (the keyboard lights should flash and then come on), hit F12 to bring you to the boot select menu. There you go boot to the utility partition or perform an IDE drive diagnostics. Run all of the tests (which could take a while) and see if they find any errors with your system.

Let me think of a few things, but I had to respond to the last question. The flux capacitor comment is my signature; it is put at the end of my postings and has nothing to do with the posting. My apologies if this led you astray. The flux capacitor is actually the Y-shaped gadget used for time-travel in the Back to the Future movies. I put it as my signature because someone I know actually responded to a tech. call with this so that he didn't have to explain to the user that it was was a very very stupid fault on the user's part. Again, sorry to mislead you with the signature. I just think that the quote is priceless and in no way reflects anything about questions or users on this site.

Components were melted? That's not good at all. You may have more issues than just a power supply. The fact that there were burn marks on the unit and melted components might mean that your motherboard is in serious condition and might need to be replaced. Also, double check all of the connections. Sometimes, when installing new hardware, the connections aren't in secure enough. Unplug all of them and them plug them back in. Hopefully the former is not the case. Best of luck.

When you say that it crashed, what specifically happened? Did you get a blue screen of death (BSOD)? Did the system just power off or reboot? Did you hear any strange noises from inside the system before the crash? When you are in safe mode, which version are you using (e.g., Safe Mode with Networking)? Have you run the diagnostics tests outside of Windows? Also, when you reinstalled Windows, did you perform a full format or a quick format? Any new hardware recently installed before the crashing started to happen?

I'd suggest performing a repair of the OS. You can do this with the installation disk. Boot to the CD and run the program. When prompted, perform a repair. This is your best bet before having to take drastic measures.

Thanks for the link, Cincinnerdi. I had not seen it until now. The symptoms described in that article were extremely similar to the ones I am experiencing, so I decided to run the script. Unfortunately, the script did not work and I am continuing to receive this message, althouhg I am receiving all updates and the system continues to function normally. Again, I appreciate the link you provided.

If you happen to remember an older password that was used, you can restore the server's system state to a point where it had the old password. Here's an article that talks about a few different methods for recoving administrative passwords: http://www.petri.co.il/forgot_administrator_password.htm

I believe that, by deafult, no web sites are running when IIS is installed. You have to set those up manually.

You should try installing the patches that Blizzard released: http://us.blizzard.com/support/article.x...p;pageNumber=1. They help out with multiple problems. In addition, their support site tends to be decent.

You have to have a previous verion in order to install the upgradable version of 2007. I wish it weren't the case, as it would make building new clients much easier for me. From the way you worded the question, it sounds like the version of Office is already installed on your system. Are you saying that your machine came with a validated version on it originally but it currently is not installed on it?

mrfac, thanks for bringing that link up again. I, too, visited that site quite some time ago and there was little then. Now, it's almost overbearing with how much is there. I've tried a few of the tips suggested there, but none of them have worked for me. Specifically, I tried the above suggestion that Uberstein posted, but the correct port was already displayed; does it need the SSL port or regular one? I also changed the "Default Web Site" port to an un-used one (82), then started and stopped it, but that didn't help either. Part of why it is a little tricky for me is that I have 5 web sites running on one machine, all of which are internal.

zepper, theoretically it is possible for a desktop to use laptop RAM, but I honestly have never seen nor heard of a motherboard which supports both. That's what it comes down to: the motherboard.

To be honest, you're right about "Windows being stupid" with the last part. I occasionally get that on machines. My workaround has been to leave the USB cable plugged into the same port all the time. It's not a permanent solution, but it may be less frustrating for you.

It looks like migisukhoi named the 192.168.1.10 machine MiG and the 192.168.0.1.11 machine Sukhoi. The network was renamed from WORKGROUP to Munja. Since you are using the Windows Firewall, check the machine in question's setting to make sure that File and Print Sharing is enabled. If not, that'll be your culprit. If it is enabled, then you probably have permission issues. The fact that one machine can connect to the other, but not vice versa, rules out connectivity issues.