Myke

You could try to pop the battery out of the motherboard. Let it sit for about 30-45 seconds before placing it back in the motherboard. This should reset the BIOS/CMOS. I belive that might reset the password default to not prompt.

While in the command prompt, try releasing and renewing your IP. 1. type IPCONFIG /RELEASE 2. type IPCONFIG /RENEW 3. type EXIT If your issue still ocurrs, then it might be a router configuration problem. Try unplugging everything from your router, including the power cable. After 30 seconds, plug in your router's power cable and wait for the self-test to complete. Then plug your computer's ethernet cable into the router. Afterwards, repeat steps 1-3 above.

Hi jasont21. If changing your sound settings to basic acc worked, then that is most likely where to being resolving the issue. In order for anyone to help, though, we need the hexidecimal code that the blue screen gives you (e.g., 0xC000001E); there should be one outside of the parenthases and four inside. This will help determine what specifically is wrong and how to correct it.

I have a Windows 2000 SP4 server with Microsoft ISA Server 2004 installed on it. I've had to manually install the SAV client on the machine, but the server is not receiving the virus definition updates from the server which manages it. We are using Symantec AntiVirus Corporate Edition v10.1. I've tried toying with the exclusions setting by opening up the ports which Symantec states are necessary for the application to work, but this has not resulted in success. Currently, I have had to download the XDB file from Symantec's support site and manually update the files, which gets rather annoying. All other servers/clients are receiving the updates. Does anyone have suggestions or experience in dealing with this? I've searched both Microsoft's and Symantec's support sites, but have not found any resolution to the issue. Thanks in advance.

Here's an upate: I called Symantec and waited on hold for a good 45 minutes. Unfortunately, I was forced to listen to Yani-type central american music that made me feel like I should be engaging in a halucenatory sun god ritual. When I finally go through, Symantec firmly stated that they could not help me because the issue was only with the ISA 2004 software and not theirs. TCP port 2967 is the only port that needs to be open for communication between the parent server and managed client. I have it open for bidirectional communication at that port, but still nothing happens. So this issue only deals with configuring the ISA policies. Since I'm a bit inexperienced with ISA configuration, I need some help here. Any ideas?

This has been an ongoing problem that is getting very annoying. My goal is very simple: Print the first page of a letter from Tray 3 (coversheet) and print all other pages from Tray 2. This is something that I could pay a monkey with a diaper to do. If only printing one letter, then there is not too much of a problem. When performing a mail merge, only the first page of the first letter prints from Tray 3. All other pages of all the letters (including the first page) print from Tray 2. It is completely unpractical to have users print out each letter individually when they have to do 100+ letters. Network Information: Printer setup via direct IP (no print server) PCL 6 or PCL 5e drivers installed (some PCs have PCL 5e due to other issues) All clients use Windows XP Pro SP2

You should be able to run it without any problems. It's worked just fine for me when I installed it on an XP machine. Try uninstalling it, reboot, then disable any antivirus or anti-spyware applications before isntalling. If that doesn't help, go into your event viewer and see if there are any messages which could tell you more about the error.

Try hooking you SATA HDD up as a slave. If the machine can then recognize it, then you know it isn't the HDD itself. It might (and I stress "might") be due to RAM. Try migrating any files you want to save over to the HDD that works, then format the SATA HDD. Afterwards, switch the SATA to be the master HDD and try reinstalling Windows from there.

Yes, the cloning application works as long as the new HDD is of equal to or larger than the original HDD's size. Just make sure you know what you are doing when you take your tablet apart and with setting your jumpers right. Other than that, it's rather straight forward.

I forgot to address your last question about cloning the HDD: The best program that I have used to clone a HDD was Acronis MigrateEasy. It's a very simple and easy to use tool which operates outside of the Windows environment and does not take too long to perform. When I cloned a laptop's HDD, I had to purchase 2 IDE converters (one for each HDD) and place the HDDs in a tower. It worked like a charm and is now the only program I use to clone HDDs. I highly suggest NOT using Norton Ghost, as it did nothing but cause problems.

I actually just attended a Microsoft seminar yesterday where Vista was 1/3 of the 5-hour conference. The guy was running it on laptop that didn't really have too much power in it, and it ran just fine. Microsoft actually has a few tools you can run to check both your hardware and software to see if they are compatible with Vista. Another cool thing to note is that if you buy the business version of Vista, it comes with 4 licenses for VM (yes, I'm aware that VM is a free download), which you can install certain OS's on if a needed program cannot run on Vista. This next comment does not apply too much to you, seeing as you just ordered 2 GB of RAM, but it's mad cool. Windows Vista has a new function which other versions of Windows did not have. It's called ReadyBoost. Basically, it allows you to use a USB Key as RAM; so if you have a 1GB USB key, you can use up to 850 MB of it to function as RAM, provided that it has enough free space on it, obviously. I hope that this somewhat helped answer your question. I have been very hesitant about trying Vista, but after yesterday's presentation, I can't wait to try it out.

Yeah, uh... you don't want to do that. SVCHOST is kind of necessary for your OS to function normally. In fact, you should expect to see mutliple instances of it running at a time. If you do a search for it, you'll find that it is a rather important process with helps you system handle DLLs. You might want to allow SVCHOST to run.

Honestly, the Google Toolbar is mad annoying. For those sites which require the pop-up blocker to be disabled in IE, you not only have to do that but also have to turn off the Google Toolbar. There are some other annoying feature that go along with it and it eats up more resources than necessary. My advice: don't install it. Unless you really don't know what you're doing on a computer or on the Internet, then you don't need it.

Just before you computer restarts, do you hear a strange clicking noise? If so, then you have a physical error on the HDD, which is pretty much unrepairable. If not, try booting up from a boot disk.

If you want to clone your IDE to your SATA, then you should make the SATA the slave drive first. Boot into the IDE drive and then clone the IDE to the SATA. After the cloning is complete, switch the SATA to be the master drive and the IDE being the slave. Boot up your system and you'll have everything loaded onto the SATA drive. I have not used Maxblast for disk cloning/imaging, but have used Arconis MigrateEasy serveral times and it works like a charm. MigrateEasy performs the cloning process outside of Windows, so the job goes much faster and without being interrupted by warnings and services and the likes. Be warned though: the program didn't run well with 98 machines for some reason.

I am trying to create a Windows Server 2003 version of Emergency Repair Disk (ERD), which must be run through the Automated System Recover (ASR) wizard. The server I need this created for is also our Exchange server. The main OS runs on the C:\ drive, while Exchange is stored on the D:\ drive (an additional E:\ drive is also present). Becaus there is not too much free space on the C:\ drive and plenty of space on the D:\ drive, the destination backup file is set to the D:\ drive. I have even tried pointing it to the E:\ drive, but to no avail. When I run the ASR wizard, I continuously get an error with a log reading: Backup Status Operation: BAckup Active backup destination: File Meda nam: "Backup.bkf created *date* at *time*" Vlume shadow copy creation: Attempt 1. "NTDS" has reported an error 0x800423f0. This is part of System State. The backup cannot continue. Error returned while creating the volume shadow copy:800423f0 Aborting Backup. I have run the ASR on a seperate Windows Server 2003 machine without a problem: I stored the backup on the D:\ drive. This machine is simply a web server and it ran rather smoothly. I've done some research into this and have found that it relates to VSS WRITEERROR, which I know very little about. What I have read mainly deals with SQL databases and I am very apprehensive to do anything too drastic to the Exchange server. Does anyone have an tips that they can throw at me? I just need to create the Windows Server 2003 version of an ERD.

Well, I have still gotten no where with this. The VSS service is started and the same error is still popping up. I selected only the System State, as all I want to do is create an ASR disk, but this does not help. I tried all three drives as the destination for the backup, but still nothing works. I've read other posts in different forums about creating dummy files and changing the AD log file location to be on the same drive as the System State, which they are, but that still doesn't help. Does anyone have any further ideas about this? All I need to do is create an ASR disk, similar to the ERDs for previous OSs. Thanks.

Check the jumper settings to make sure that the DVD drive is set to be the slave. When the computer starts up, go into the BIOS and check to make sure that it can properly identify the drive. If you notice that both the HDD and the DVD drive are shown as "Unknown," then the jumper settings on one of the two are off.

Workgroup is the default domain/network that Windows selects upon initial setup of the OS. You might want to see if any of the machines are currently part of Workgroup. I've seen 98 (all versions) machines continue to show the Workgroup domain despite the fact that no machines are connected to it. As for the other mystery networks, it might be possible that a machine was setup to be on a different network before joining your network. A few questions: What operating systems are you running on your machines? How many machines are on your network? Were each of them fresh installs of Windows when they were hooked up to your network? What operating systems are you running? What networking equipment are you using?

Can you boot into safe mode? If so, run MSCONFIG from the Run command. You can select different types of boot sequences which can help you determine what exactly is causing the problem. If you are unsure how to use MSCONFIG, I'd suggest reading up on it first.

You should be able to format the C: drive without any interference with to the E: drive. Even if both drives were physically on the same disc, you should be able to format just the C: drive. The only way to get rid of partitions on a single disk is to completely format the entire disk. I have a 120 GB HDD with two logical drives (20 and 60 GB). I originally had ME on the 20 GB and made it the bootable drive. Because it was ME, I had to reformat the C: drive multiple times and it never touched anything on the D: drive (60 GB).

A client on the network has been continuously experiencing an error with Outlook. This usually happens when she opens an e-mail (sometimes when closing). Outlook freezes and then eventually just illegally closes, which yields an error message. The message claims that there is an issue between Outlook and Symantec's WinFax Pro. I am 100% sure that WinFax is not installed on the PC. I've searched the entire hard drive and even the registry for any possible existance of the program, but have not found anything. Through my research, this problem is not all that rare. Apparently, Microsoft is aware of the issue, but has not provided any additional information. I've gone through almost everything I can think of and no workaround has succeeded. I am at the point of just uninstalling Office and then reinstalling it. This should hopefully take care of the problem, but I'd like to know if anyone else has experienced this and found a workaround, in case this scenario should arrise again. Here are some of the details: OS: Windows XP SP2 App: Office XP Pro SP3 (Outlook 2002) Occurrance: only one PC experiences this error Security Risks: no malware/viruses detected Any help would be greatly appreciated.

The entire agency uses Exchange and this only happens on her PC. I ended up just uninstalling and then reinstalling Office, and the problem went away. Microsoft has still not released anything on this, but they claim that they are aware of the problem.

This is more of a curiosity question. I've noticed that when an e-mail with attachments arrives from an external source, the e-mail's total size will be significantly larger than the combined total of the attachments. For instance, an employee received an e-mail with a size of 10 MB. It contained 3 attachments, each being only 1 MB (total of 3 MB). There is little or no text, but the message is coded in HTML format. When the user forwarded the e-mail to me (internally), the e-mail's size was only 4 MB, which makes much more sense. I had originally thought that perhaps this was due to encryption, which doesn't make a whole lot of sense, but was the only thing I could think of. The originally message was also sent to 3 other people, besides our user. Does anyone have any clue to why this is the case and what is causing it?

Thanks for the input. I ended up finding another reason for this. Apparently, e-mail formats can sometimes skew the file size of an attachment, mainly HTML and MIME formats. They have to potential to bloat the attachment's size from 2/3 to 2 times the original size. This is what was causing this to happen on the network. We've had to advise certain persons to the reasoning why some e-mails are getting bounced.