cluberti

According to a whois lookup, that block is maintained by Indosat M2...

In DHCP, disable the scope you need to change, and you should be able to modify the subnet and restart.

It could be a slow resource depletion issue, a filter driver issue, or a few other kernel-specific things that I can think of that would all clear up with a reboot. 1. Are you running realtime antivirus on this server? If so, uninstall the product and reboot to see if that changes the behavior. 2. Does your tape backup software use an Open File Agent component? If so, uninstall and reboot as per the previous suggestion. 3. Look in your system event logs for any 2012, 2019, 2020, 2021, or 2022 events - if so, some reg changes might need to be made to tune the box.

Take a quick look - this is usually a BIOS issue, and I'm interested to see what happens with x64 and a BIOS update.

This has been discussed before, with this being the most recent incarnation of this question: http://www.msfn.org/board/Expanding_Wirele...rk_t103467.html

If you're running an x64 version of Vista, I've seen 932596 fix issues like this. If you're running x86 32bit Vista, you need to make sure your network drivers for your NICs are installed properly and recognized and working properly in device manager before trying to set up a network connection - the error you're getting is "RPC Server Unavailable" on connect.dll, meaning it didn't get a response from the networking hooks. You need drivers installed and working, and if you're running x64, also make sure 932596 is installed as well.

Note that both Windows Update and BITS run inside an svchost.exe process, and if BITS keeps restarting it's at least possible that WU is doing the downloading. Disable Automatic Updates and see if the "problem" stops.

Sorry, but I feel like this has gone a little off-topic, and DL's script works just fine so question answered. Post closed.

Everyone, keep this conversation on point and take your tool comparisons and flamed rantings elsewhere, or I'll shut this down. Thank you.

You need the bootsect.exe binary from the WAIK to set it back to NT52 (XP/2003) before XP will see it, and you'll need to run it from a boot disc (like WinPE/BartPE or another ERD disc).

That error is either "STATUS_INVALID_IMAGE_FORMAT" or "ERROR_INVALID_NAME", and guessing from the sound of when it happens I'd say it's the former. Something didn't install properly, and if doing a repair install makes other apps break, it sounds like you need to do a clean install from the MCE disc you got from the vendor or the store.

Using 64bit Ultimate from the retail channel, and it's run great since RTM in November.

Technically, if we're testing a network connection with this, it would be wise to include the packet size: ping -l 1500 -n 1 google.com or ping -l 1492 -n 1 google.com

From the horse's mouth: In short, I would say this is one hotfix folder you should NOT delete.

Honestly, I couldn't say. It exists on a default install, so perhaps a game was installed onto the box that deleted it - I really couldn't say. As to x64, I wouldn't do it if you're running Creative hardware in your box, as they're notoriously bad with x64 drivers. As to the firewall and the svchost CPU issue, it's likely that the svchost.exe process was the network services svchost, which holds the server and workstation services (responsible for handling incoming and outgoing network traffic), and the firewall wasn't 100% vista compatible - I've seen that before with versions of ZoneAlarm (not the newest version, but some of the previous ones). Were you ever able to get dumps of wmp?

The problem with removing registry keys for another user when that user isn't doing the uninstall is that you don't necessarily have easy access to their registry (ntuser.dat). You could either write a script that loaded up everyone's ntuser.dat file, parsed the registry for the correct location to the reg keys you wanted to delete, and deleted them; or, you would have to parse all of the subkeys under HKEY_USERS to find the keys you are looking for. Note that neither approach is 100% foolproof, and that's why (in most cases) uninstallers only remove reg values from the HKCU hive for the user doing the uninstall, and everyone else's reg values (if they exist for the app) are untouched. http://support.citrix.com/forums/thread.js...4&tstart=30 http://groups.google.com/group/microsoft.p...=raot&fwc=1

Minimum score is 700, time should be about 2 hours.

That is bizzare, honestly. Have you tried it on Vista without any antivirus installed, or disabling the Windows Defender and/or Windows Search services?

I haven't touched your sig, and I can see it just fine here... As to your error, try this: Open Regedit and navigate to HKEY_CLASSES_ROOT\Lnkfile - click on this registry key to highlight it Once you're there, click Edit > New > String Value, and give it the name IsShortcut Click OK, then close regedit and reboot. That should fix it.

Not sure about specifics there, but I'd start here: http://msdn2.microsoft.com/en-us/library/ms190954.aspx http://msdn2.microsoft.com/en-us/library/a...60(SQL.80).aspx Also, running process monitor from sysinternals while the backup runs should give you an idea of what is being written to disk by whom, and how long the writes are taking. Perfmon SQL counters are a good tool as well.

This is no longer needed on Windows 2003 SP2 and higher (Server 2008), as it uses the pmtimer by default.

File names in DOS are 8.3, so the name likely has a tilde (~) and a number in it. If you run "dir /a" in the directory the file is in, it should show you the actual file name you can use to open or copy the file.

More than likely, yes, they're "checked" and are going through all kinds of assert routines that the RCs and release will not.

While he makes some good points (about content "protection" and encryption), he needs a tinfoil hat and to place the blame where it belongs - the US congress and the xxAA groups who mandate this nonsense or else companies cannot carry their "content". Most of what he complains of is regarding signed drivers (which, unlike his contention, I feel is GOOD for the industry as vendors are less able to let crappy drivers out into the wild, and are forced to fix them quickly when they do) and the behaviors of WGA/SPP. Again, some good points, but mostly just tinfoil hat.

"Gold" also refers to "RTM", or release-to-manufacturing, as this is the name of the actual build tree these binaries come from (you can see it on the advanced file properties of system files in the file version string, it is usually in a format something like "<some.file.version.number>_RTM_<some.date.here>".