HarryTri

Yes, but this omission can be the sheer truth and the other stuff "political" nonesense. Anyway, I don't know... The only thing that I know by common sense is that there isn't and won't ever be virus-proof OS and noone can persuade me for the opposite.

Oh, I don't know. It just seemed logical to me that an antivirus for Linux would check for linux viruses (there must be some of them too I suppose). From the reffered page: It doesn't say something like that for AVG.

Yes, but it will scan for threats that affect Linux.

Hello compatriot! AVG Free for Linux is detecting Linux viruses, not the Windows ones, you must use AVG Free for Windows to check your Windows partitions (by the way I also use AVG Free and I think it is a really good antivirus program).

Maybe Andromeda43 wanted to type "Windows-98" and the "9" was missed?

NX or DEP is from preventing the execution of malicious code that can seize the whole memory. It renders a part of the memory for data storage only and if a program tries to execute code in it it just crushes. The only problem that I am aware of is with programs that doesn't respect the DEP restrictions (usually old ones).

No, it doesn't (I know it from personal experience).

I mean that if you do a repair install it must restore the basic keys of the registry in order to repair it.

And what happens if you delete almost everything? Some things will have to be restored, won't they?

The %errorlevel% is of the previews "set pwd=Admin" command? Which is supposed to be the default password? Maybe the correct syntax would be "if "%adminpwd%"=="" set %adminpwd%=Admin"? I think that as it is writen if %adminpwd% is null it remains so and pwd becomes null also.

Windows XP CD has the option for a repair install. I did it once and it is the same with the Windows 7 thing as Charlotte describes it. It restores the default Windows files and registry entries (which means that you loose any service packs or updates installed) without affecting other files and registry entries as those of the several installed programs.

I run Windows XP SP3 on my 512 MB Pentium M laptop and my 256 MB Pentium III desktop with no problem. As for the NTVDM problem, it is probably the one that has to do with the later NT OS kernel patches, there is a solution for this, have a look here: http://www.msfn.org/board/topic/163182-solution-for-the-ntvdm-crashing-problem/

I still have and use my Pentium III 1 GHz desktop (once in a while). I mostly use my Pentium M laptop, it still does the job. I have Windows XP on both.

By the way Recovery Console is supposed to be contained in the Windows XP installation CD, isn't it? I think you can even install it on your HD.

@technoid It's the answer to your last question: The problem probably has to do with "system" since the windows inicialization stops there and you don't get into safe mode (as far as I understand correctly), yet a disc check will surely not harm. Edit: RC is the recovery console, I thought you were talking about Windows, sorry.

1. The system boots so there is no reason to mess with the MBR. 2. There is no usuall size, it differs from system to system (some MBs anyway). 3. I suppose it's about the same thing. 4.If it worked untill now the origin doesn't make any difference.

It seems that the "system" file of the registry is corrupted (in the C:\WINDOWS\system32\config folder). You can use Recovery Console to replace it with the "system" file in C:\WINDOWS\repair folder or (preferably because the mentioned file will be a bit outdated if you haven't recently made any system backups with NTBackup or other program) with the corresponding file that can be found into the "snapshot" folder of any restore point (if there are any). In the second case you must rename the file from blahblahblahsystemblahblahblah (I don't remember the naming exactly) to just "system" after copying it to the C:\WINDOWS\system32\config folder- you must delete the existing "system" file in order to do so.

Advanced SystemCare Free also cleans and defrags the registry. I use it to clean the registry to have it, let's say, more tidy, the truth is that after the first time there are no many things to be cleaned, as for defraging it hardly makes any difference in size under normal conditions. The process is rather safe anyway if the application used isn't a crapy one, at least that's my experience- of course always something can go wrong, whatever you do in this world has an unavoidable risk, doesn't it?

Command prompt doesn't recognizes systeminfo as a valid command but here is the "ntldr" modification date: Wednesday, 17th October 2012. I installed from an OEM XP Home SP2 CD and I installed SP3 afterwards. Then I updated my OS with Windows Update and I kept on updating it when new updates were available.

I checked and I have the log (Windows XP SP3 fully updated). Maybe there is something wrong with Remote Desktop itself in your system? By the way I have never used it, maybe the problem has to do with it (changed settings or whatever)? You were faster than me.

Why not MusicMatch Jukebox version 10 (not the Yahoo one of course)?

Good news! I found the solution for the NTVDM problem here: KB2724197 causing ntvdm.exe to crash. Cannot run 16bit applications Here it is presented as a .reg file: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NTVDM] "BiosRomMappingOption"=dword:ffffffff It works with the latest NTOS files update KB2813170. Caution: It needs a reboot in order to work.

Good news! I found the solution for the NTVDM problem here: KB2724197 causing ntvdm.exe to crash. Cannot run 16bit applications Here it is presented as a .reg file: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NTVDM] "BiosRomMappingOption"=dword:ffffffff It works with the latest NTOS files update KB2813170. Caution: It needs a reboot in order to work.

I eventually installed .NET Framework 3.5 and run the Fix it. It says that the location that Windows Update saves files changed (not at all in fact), it supposedly fixes the problem and verifies the fix but if I run it again it reports exactly the same problem. I guess we must wait for a new version of Windows Update as I have already said.

The FixIt requires NET .Framework 2 which I haven't installed at the moment and I don't think it worths the fuss to install it. The KB is for Windows XP SP2, the update package refuses to run on Windows XP SP3 because the SP3 is newer. I searched the Microsoft's site for something else relevant to the problem and I found nothing. I suppose we must wait for a new version of Windows Update. @snuz2 Did you tried x's solution? Did it help?