schloss

If they have no password, NO remote access to Windows will work, neither shutdown, nor psshutdown.

That link is broken. Try this for now: http://www.msfn.org/board/topic/142961-new-win7-reg-entries-related-to-folder-views/

I can confirm that AnaDisk completely bypasses the BIOS and accesses the FDC hardware directly. So if AnaDisk "sees" the drive, your drive and cable are good, but this won't detect misaligned or worn heads. If an AnaDisk "scan" of the floppy reads all the sectors, your drive heads and floppy are good too. In Europe, we had three types of 5 1/4" double-sided drive: 360k, 720k and 1.2M.

No, it isn't browsing history, for sure. Like Maxfutur, referrer (referer) is http://mimo.zxq.net/. I agree The domain squatter for all the links is hitfarm. The ad server has determined that "slip" is an item of female underwear and is serving ads and multiple links according to this definition. @Mim0 Please remove the link to hfslip.org on your home page from the sentence: "... because the original web-site www.hfslip.org is down..." Thanks.

Fedora 10 (not listed) CentOS (also not listed)

The two sets of numbers are not the same thing. Windows allocates space in blocks, not in single bytes: each block is usually (but not always) 4096 bytes. On a flash drive, or external drive with FAT/FAT32 formatting it may be much bigger (4096, 8192, 16384...). So the "allocated" size for a 1-byte file will be actually 4,096 bytes or more. The first three sizes are "allocated" sizes. The second pair of sizes are the actual file sizes added together.

"early turn of the century" just about sums it up for me, in this cautionary tale. Looking back, it is clear that it was a compromise solution at a time when disk prices were way above what we have now.

I didn't make it clear that this applies to both Windows 2000 and Windows XP. Not sure whether you know this, because only the Windows 2000 list has been changed.

Regular users will know that from time to time Microsoft serves garbage instead of windowsmedia11-kb946665-x86-intl.exe It's happening again -- I have multiple reports from all round the world that the windowsmedia11-kb946665-x86-intl.exe download is corrupt. It's not just me and it's not just one or two countries. Anyone know how to get Microsoft to fix this?

I can confirm what Tomalak has said. KB956391 replaces KB953839 which replaced KB950760. To verify this you need to see the Security Advisories, not the KB articles. (Source: http://www.microsoft.com/technet/security/...ory/956391.mspx) (Source: http://www.microsoft.com/technet/security/...ory/953839.mspx)MS08-032 is KB950760. Thanks for compiling and maintaining these new lists. .

That's because they are the exact same links as are listed in the KB article I posted. KB949104. Except, that by now they are beginning to propagate. Two of them now work. The third still doesn't. Come on Microsoft. Get you act together. When the KB article says: that's wishful thinking, not a version of reality that's actually recognised in Europe..

There's a newer version of the Windows Update Agent (WindowsUupdateAgent30-x86.exe) announced -- version 7.2.6001.788. See KB949104 "How to obtain the latest version of the Windows Update Agent to help manage updates on a computer" Don't bother trying to download it just yet, because Microsoft have managed to give three broken links to it. --

Answering just the question in your topic title, no this is not a SP3/AMD problem. That affected only HP computers and then only if an HP install or recovery disk had been used. The problem (short version) was that HP installed an Intel driver file on the CD sent out with all computers, including those with AMD processors. If you really need to know, it is not too difficult to determine when SP3 was installed, by looking in the registry and/or in WindowsUpdate.log or (simplest of all) by using Nir Sofer's WinUpdatesList (wul.exe). I would not like to see SP3 installed or uninstalled whilst both AVG and Comodo are running, but then I am naturally cautious when installing Service Packs!

As these are all functions from the standard C library, have you tried asking this question in the Programming section of these forums? You might need to provide more precise information, including what language(s) are being used on the affected systems. Link: Programming (C++, Delphi, VB, etc.)

I would include HFSLIP as well as nLite, especially if the option to remove Security Catalog (.CAT) files is used. At least one person in this topic is using HFSLIP. If anyone really wants to know how to fix this, you must first carry out the steps outlined by cluberti. This includes manually checking the files present. Have you checked your system32 and dllcache folders against the following list? Advpack.dll, Dxtmsft.dll, Dxtrans.dll, Extmgr.dll, Icardie.dll, Ie4uinit.exe, Ieakeng.dll, Ieaksie.dll, Ieakui.dll, Ieapfltr.dat, Ieapfltr.dll, Iedkcs32.dll, Ieframe.dll, Ieframe.dll.mui, Iernonce.dll, Iertutil.dll, Ieudinit.exe, Iexplore.exe, Inetcpl.cpl, Jsproxy.dll, Msfeeds.dll, Msfeedsbs.dll, Mshtml.dll, Mshtmled.dll, Msrating.dll, Mstime.dll, Occache.dll, Pngfilt.dll, Url.dll, Urlmon.dll, Webcheck.dll, Wininet.dll Have you also made the registry change to enable verbose logging? Have you made a copy of WindowsUpdate.log available? There is no point in speculating about the cause, if none of these steps are carried out.

The Windows Product Key Update Tool was designed for exactly these situations. It was recently updated to include Service Pack 3. If necessary, it can replace the validation and product key handling files (i.e. .dll files) present on the disk with genuine Microsoft versions to enable your genuine OEM key to be accepted. Without this step, pirated (corporate) versions will not accept genuine OEM keys.

From what you have posted, both the remaining accounts are disabled and locked, preventing you from logging in. This can be fixed. The CD you now have can clear all this, and reset the flags in the Registry to (re-)enable normal login. Again, since a script with prompts is running, you are guided through the procedure. Also you can now take the plunge and reset the password. By far the safest option is to choose a blank password, rather than attempt to set it to a particular name/word/phrase. You can always set/reset the password in the normal way, once you are logged-in. Even if the password is already blank, it is best to ask the script to reset the disabled/locked status for Administrator, and also ask it to blank the password again. In my experience re-enabling the locked account and blanking the Administrator password is very safe on Windows 2000. I have never yet lost a client's data. BUT it is always best not to be over-confident and to recover user data first. When you reboot, you will find that Windows first runs a chkdsk and checks the file system before the login screen appears. This is not a sign of a corrupted disk. The chntpw program has requested this, as a precautionary measure. If all this fails, or you choose not to do it, you still have the option of a repair install of Windows, using the original Windows CD, without having to reformat the disk. The disadvantage of this is that you will lose all updates to Windows that have been issued since the date of the CD. Updating Windows to the present day is not a trivial matter but it is still better than reformatting the disk.

Even after many years of dealing with computers I am still amazed at the numbers of ways that users find to destroy them! From the information you have given so far, assuming a typical installation, there were three accounts on this computer: 1) The Administrator account (RID=500) 2) The Guest account (RID=501) normally disabled and locked 2) The "user account" (whatever it was called) (RID=1000 or greater) Do not be swayed by the "user account" still being displayed on the login screen. All that tells you is the name of the last person to login, nothing more. It does not change, even if the account is destroyed, because it is only showing a value copied from the registry. I know you have said that password recovery is not the issue here, but the password utility I have in mind will establish what user accounts still exist. You will need access to another computer with a CD-RW drive, then access to the broken computer. Download and burn to CD, Petter Nordahl-Hagen's chntpw from his website. Read the instructions on his site thoroughly, then boot from the CD you have made. Follow the script that scrolls on-screen right through to editing users and passwords. At this point, a list will be shown, something like the following: RID 0x1f4 Administrator RID 0x1f5 Guest RID 0x3e8 "user account" You may see one, two, or all three of these depending upon what has been destroyed. It is not important to understand exactly what an RID is: just think of it as a user number. RID=500 (my top list) is the same as RID=0x1f4 (on-screen list) because 500 in base 10 = 0x1f4 in base-16 arithmetic. By carefully following the on-screen prompts you can see this list and then exit without causing any damage. All you are doing is reading the disk. Depending on what you see, you could try logging in as the Administrator, or you could post your findings or further questions in this forum.

No, this absolutely is not true. IASTOR.SYS is in the Intel® Matrix Storage Manager. You can download iata57_enu.exe or iata57_cd.exe and extract IASTOR.SYS or you can download f6flpy32_57.zip if you want the floppy image. These are all version 5.7.0.1011 for Windows 2000. Step-by Step instructions are given by Intel here: How to do unattended install of AHCI/RAID driver on Windows 2000 Click on the Intel® Matrix Storage Manager link at the bottom of that page. On the next page: Click Get the latest driver On the next page, select: Windows* 2000 and click Go! On the next page download the files you need.

It depends what you do on the internet. It also depends on which browser you use. A starting point for understanding what a Root Certificate is might be: WikipediA: Root Certificate Microsoft KB931125 However, the WikipediA article is too technical and uses too many unfamilar abbreviations. The Microsoft article is even less helpful. It is also badly maintained and badly out-of-date. (Please note: these are personal opinions, from the perspective of an end user trying to learn what a Root certificate is. I have nothing against Wikipedia or against Microsoft.) There are also two much longer (and much better) technical articles published by Microsoft: Microsoft Root Certificate Program Certificate Support and the Update Root Certificates Component You don't need to read all of these articles. I suggest you read How Root Certificate Distribution Works from the first article and Benefits and Purposes of Certificate Functionality from the second article. Most computer users will use a Root Certificate without even knowing it, when they attempt to pay online using a credit card. Then the address in your browser will start with https:// not http:// If you rarely do this, or you just use local companies, then you probably don't need the very latest update. On the other hand, if you transact globally in emerging markets, you probably do.

@jcarle Yes, I am aware of that. I agree! The vast majority of the OP is also about Windows 2000. However, I am also aware that this topic has since branched to other OS as well. That's why I was careful in choosing my quote. @cluberti Noted -- thanks.

So, why are there two different files for ENU? Which do I use? The one posted by definicjaCEPA, or the one posted by Anderton? And what the reason for your choice?

It is determined by TXTSETUP.SIF. See: KB216573 How Windows Determines ACPI Compatibility KB237556 How to Troubleshoot Windows 2000 Hardware Abstraction Layer Issues KB246236 How to Upgrade Windows 2000 to Use an ACPI HAL

According to Microsoft, the OP is right: [quote]IoPageLockLimit This registry key isn't used in Windows 2000 Datacenter Server and is no longer used in Windows 2000 starting with Windows 2000 Service Pack 1[/quote][i]Source: Inside Windows, Third Edition, chapter 7: Memory Management[/i] The authors of that book are David A Solomon and Mark E Russinovich. David Solomon was given access to the source code of Windows by Dave Cutler at Microsoft and Mark Russinovich needs no introduction. If anyone is going to contradict these two guys you need a lot more evidence than personal opinions! One tiny piece of that evidence might be that the Microsoft link in the OP (contradicting him) has been pulled. There's also a Microsoft written PowerShell script that references IoPageLockLimit, but when you trace the reference link back, it goes nowhere too, because the one thing Microsoft then [i]don't[/i] do is mention IoPageLockLimit.

I think not to do that .... Last update of list for Windows 2000 = 2008-04-14 Last update of list for Windows XP SP3 = 2008-06-11