Mr Snrub

That's not Vista, that appears to be a skin for Windows XP.Start button & menu are wrong, and it is running IE6. I don't think this is an "official" Microsoft product at all, and a 3rd party extension to add alpha blending of Windows to the desktop must have a huge performance hit on XP...

Try these commands: w32tm /config /manualpeerlist:192.43.244.18,0x8 /syncfromflags:MANUAL net stop w32time & net start w32time w32tm /resync If that does't work, try time.windows.com to see if you get a different result: 207.46.130.100 If it continues to have a problem, I would take a network trace on the DC and capture the traffic while it tries a resync and see what requests & responses are on the wire. Edit: Checked this last night - set up a Windows 2003 R2 Server, configured as a DC in a new forest, saw the complaints about w32tm not being configured and ran the 3 commands above - w32tm is now happily getting time from time.nist.gov.

Are you trying to upgrade or dual boot?I have seen this behaviour on laptops which have bluetooth and/or wifi cards enabled - the setup screen is very slow to respond and never gets past that point. The second the bluetooth adapter was turned off the installation continued almost immediately. I would guess that something similar is occurring to you - one of yoru pieces of hardware is making the setup "stick" at the hardware detection stage. Try starting at the bare minimum hardware, disabling unecessary onboard functions in the BIOS. Or wait for the February CTP.

If the broadcasts come from the clients and stop if they are rebuilt, then something is lingering in the client with a reference to the NetBIOS names of the old NT4 boxes. I would take a look in the C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS file first. If they are broadcasting for the names of the servers then it's probably not configured with those as WINS servers as you would have those listed by IP address, but it's worth double-checking the client network config. Rather than rebuild the workstations, does it help if you remove them from the domain and re-add them instead?

Process Explorer seems unable to determine the paged and nonpaged pool limits when configured to use (only) the public symbol server, I've never had any success with it. _NT_SYMBOL_PATH = http://msdl.microsoft.com/download/symbols - pool limits read "no symbols" When I use a local downstream cache point for the symbols (with the debugger installed and Process Explorer set to point to the debughlp.hlp that comes with the debugger) it works just fine though: _NT_SYMBOL_PATH = SRV*C:\symbols*http://msdl.microsoft.com/download/symbols I ran into this problem trying to help a customer find out his nonpaged pool limit on a bunch of Windows 2000 Servers and reproduced this locally on XP x64 too, so I don't trust Process Explorer to be able to talk to the public symbol server by itself.

Does the event log record anything to indicate a system resource shortage? You could try using the debugger to check out the state of the system when it's under load: Download and install the Debugging Tools for Windows Download and install the symbols for Windows XP Launch WinDbg (as an Administrator) Click File / Symbol File Path In the box, enter SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols Click OK Click File / Save Workspace Click File / Kernel Debug Select Local tab, click OK At the prompt at the bottom, type !vm and press enter This should list a summary of virtual memory usage and the processes running - see if any of the "usage" values are close to their correspoding "limit" values, or any "free" values are very low.

It will not work, why you are putting file name?The command is: copy c:\explorer.exe c:\windows\ Pawan The result would be exactly the same - the first copies explorer.exe over the file c:\windows\explorer.exe and the second copies it into the folder c:\windows (The only possible difference would have been if there was a folder called explorer.exe in c:\windows, in which case it would have been copied to c:\windows\explorer.exe\explorer.exe.) However, as explorer.exe is your shell it is locked as soon as you logon so you can't overwrite it from within a Windows session. You would need to boot into a recovery console from your CD and do the copy operation from there. (The guy recommending deleting c:\windows\explorer.exe as the first instruction in a list is also very bad advice - it could have left the system unusable if the other operations had failed.)

Try here for information on the "IRPStackSize" registry value: KB177078 Some 3rd party products are known to change this value and make it too low, it would be worth checking out what you have set.

Correct - when optimising code you look at shaving a small amount off a section which is used frequently, there is no real gain it shaving even 5 seconds off a process used just once. Once the kernel (and possibly SCSI driver) is loaded the boot loader's job is over, and that entire process takes a very short amount of time. W2K3 SP1 kernel is in XP x64

I believe you need to have more than one input language or keyboard defined for the language bar to be available, after all it is meant for switching between the options so it doesn't make sense to have it present if there is only one language & keyboard defined. I just verified this in XP SP2 in a virtual machine: Originally had Swedish input language and Swedish keyboard. Added UK language and UK keyboard, clicked Apply - "Language Bar" button becomes active. Removed Swedish settings and applied - "Language Bar" button disable again. Added the Swedish keyboard layout and clicked Apply - "Language Bar" button becomes active once more. (i.e. one language and 2 keyboard setting options) Also verified the "Language bar" option appears under Toolbars when right-clicking on the task bar.

Launch the process you want to monitor Launch Perfmon Left-hand pane, expand Performance Logs and Alerts, select Counter Logs Right-click in right-hand pane, select New Log Settings & give it a name Click Add Counters Select Performance object: Process Make your select of counter(s) & instance(s) - your process should be listed as an instance Hint: Even if I want information on a specific process, I tend to select All counters and All instances, then just filter when I come to review the information Click Add, then Close Set your sample interval to suit (default is 1 per 15 seconds) Click OK (and again if you get prompted that the folder you specified for the log does not exist) When you want to start monitoring the process, right-click on the counter log and select Start (and later repeat but select Stop when you are ready to stop logging). When you come to review the data, launch Perfmon and right-click on the graph then select Properties Go to the Source tab and select Log files, then click Add Browse to your .BLG file and add it, then click Apply Select the Data tab and click Add - now you should only see all the processes that were running when you logged the data - find the instance(s) and counter(s) that are interesting and click Add for each, then Close Click OK and you should see the logged information about the counter(s) selected - the default Y-axis is 0-100 so should work perfectly for percentage counters (for others you can manually the scale of the counter to make it fit, or the scale of the graph itself). Hint: If you have multiple counters visible, use CTRL-H to highlight the selected one

Dual booting Windows is for simple (read: non-RAID, possibly non-SATA) configurations straightfoward for the most part. The reason installing Windows 2000 after XP screwed up the XP system was most likely because you regressed the boot loader. Same thing happens if you install XP after 2003, for example - the boot loader on the active system disk has to be the later one as the older boot loaders won't understand how to load NTOSKRNL.EXE for later versions of Windows. The repair option on the XP disk would have sorted you out before - or manually restoring NTLDR and NTDETECT.COM at the root of C:

What is the reason for wanting to reduce the working set of all processes? The working set manager thread is called by the balance set manager once per second as well as when the free memory falls below a certain threshold, and this handles the overall memory management policies such as working set trimming, aging and modified page writing. There are "RAM optimizing" programs which have the same effect as your batch file but achieve it by trying to consume all available memory which forces agressive trimming of all process working sets, and then it relases it all. The upshot is that they show "available memory" increases. To quote Windows Internals:

I would agree, that you modified the partition table on that disk with XP RTM means that it probably fixed up the table to what it thought was the maximum. BOOT.INI is only for marking bootable partitions, it doesn't actually define anything. NTLDR reads the partition tables in a chain from the disks themselves - this information is now corrupted and needs fixing. There may be a tool which can analyse disks to present what it thinks might be the start and end of partitions, but it's more reliable as a manual process (using something like DskProbe), and if certain sectors have been overwritten then it's virtually impossible. Unfortunately most of the "partition repair tools" cost money and don't have guarantees. I hope you have that data backed up.

If Word prints fine, it is not a problem with Windows - the problem is with the 3rd party word processor. You don't mention what version of Word you are using, and as this is an application (not XP) problem this should have gone into a different forum.This would be the appropriate place to ask, give your version of Word and describe your problem: http://www.msfn.org/board/index.php?showforum=121 I have Office 2003 and it sounds like you are describing "AutoFormat", the settigs for automatically formatting text, smart tags and spell checking, etc. are in the menu option Tools / AutoCorrect Options - could be in a different place if you are using an older version. Microsoft are quite correct in pointing you to the OEM for support - if you buy a retail copy of Windows you are entitled to Professional support and can contact Microsoft directly. The OEMs get massive discounts on every copy of Windows they preinstall because they take the responsibility for supporting the end users - so yes, you do have to contact Acer/Dell/HP/whoever if you have a problem with the OS that came with the machine. You have paid the OEM for support, not Microsoft. If the OEM cannot help you with your problem then they should have a support contract with Microsoft to be able to get your problem resolved.

Looks like Steve Gibson's ploy worked - lots of attention for him and lots of hits for his site. To the security community he is considered a joke, and his website reads like a gaudy flyer for a low-class burger joint, stuffed with pseudo-technical jargon, fantastical tin-foil hat claims and portents of doom (still yet to materialize). The US government does not have worldwide jurisdiction and Microsoft would not be so short-sighted as to deliberately put in a "backdoor" which could be exploited by just anyone - "reasonable conclusion" is not the description I would use. Not a very good "backdoor" either as it requires user interaction. Steve's use of CAPITAL LETTERS in his text in a bid to reinforce his POINT is also very IRRITATING. He has zero credibility in my book, unless I'm after a good laugh.

Experience. If you have a need, such as you did, then it pays to be inquisitive - and back when I started playing with PCs you only had DOS. Some things are just so much easier with a simple batch file than relying on tools, GUIs or scripting engines.

Okay got it, your file must have had a space in the name - sorry my fault. Copy & paste this into the batch file instead: @echo off set SRCDIR=f:\test1 set DSTDIR=f:\test2 for /f "delims=" %%a in ('dir /b "%SRCDIR%"') do ( if not exist "%DSTDIR%\%%a" echo Copying %%a if not exist "%DSTDIR%\%%a" copy "%SRCDIR%\%%a" "%DSTDIR%" > nul ) This stops a space being a valid token delimiter and screwing up filenames.

Copy/paste the contents of the last code window into Notepad, then save as "test.bat" (make sure you put quotes around the filename when saving, or change the filetype to "All Files", otherwise ".txt" gets appended to the end). Double-click on the test.bat icon and it should do its job. If you need to edit the batch file, right-click on it and click Edit to open it in Notepad again.

Looks like you hit ENTER a couple of times in the middle of a line. Check back at my example, there should just be 2 lines between the brackets, both starting with "if". @echo off set SRCDIR=f:\test1 set DSTDIR=f:\test2 for /f %%a in ('dir /b "%SRCDIR%"') do ( if not exist "%DSTDIR%\%%a" echo Copying %%a if not exist "%DSTDIR%\%%a" copy "%SRCDIR%\%%a" "%DSTDIR%" > nul )That should be what you have in a batch file.

No quotes in the SET statements, and no spaces either side of the equals sign.

@echo off set SRCDIR=C:\Example Source Folder set DSTDIR=E:\Folder Where I Want To Copy Stuff To for /f %%a in ('dir /b "%SRCDIR%"') do ( if not exist "%DSTDIR%\%%a" echo Copying %%a if not exist "%DSTDIR%\%%a" copy "%SRCDIR%\%%a" "%DSTDIR%" > nul ) That should do you, and report each file it copies from SRCDIR to DSTDIR, you just need to set the variables accordingly. If you want to get really advanced with error checking you could ensure that SRCDIR and DSTDIR actually exist before starting the FOR loop.

You didn't try to click the link in the details you expanded?http://go.microsoft.com/fwlink/?LinkId=55919 Wrong, that was MS06-001 and was an out-of-cycle update released on 5/1:http://support.microsoft.com/kb/912919/en-us

Don't forget to use quotes to make sure paths or filenames with spaces are handled okay, e.g.: @if exist "C:\Documents and Settings\MyUser\Desktop\blah.lnk" copy "C:\Some Folder\A file.exe" "C:\Some other folder\" or with the other example: ...if exist "%file%" goto YESFILE...

I don't know how you got it to this state- if you were starting from the full OS and removing components then it would be obvious whatever you did to break it. If you are starting from "nothing" and only adding in what you think is required then it's a lot more of a challenge. One thing to note is that this appears as "Local Area Connection 2", which often implies another entry is in the registry using this driver but the system does not see it connected at present (badly coded PnP drivers can cause this, or moving a USB device to another port after configuring it). DHCP Client is only a service, a working and connected NIC, with TCP/IP bound and functional are prerequisites for this do be able to do anything at all. You'd need to look at event log entries and maybe take a network trace when the machine boots up or "ipconfig /renew" is executed to see what is failing or if anything is actually hitting the wire.