Leaderboard

I speak only for myself, even if we leave aside your fears of Russian malicious activities inside the Kaspersky software, which do have some pretty solid base, with multiple warnings, like they say, "no smoke without fire". I'd still not use it. especially if we talk about the 19.0.0.1088 version, which is proven to have the infection CVE-2019-8286[62]. So not an option for any users, not only the XP ones. The source is solid, it's not like from a random internet guy. It's scientists. https://nvd.nist.gov/vuln/detail/CVE-2019-8286

I knew Process Explorer 16.22 had no hostile IP connections, that's why I suggested it to you, enjoy, I'm glad you liked it! I also think you won't miss anything important, if don't update further. Wow! It's even more nonsensical! So you just post spam, is this how you entertain yourself? At least you got a bit of bravery to confirm your malicious activities.

This thread was created by me for everyone who wants to use Windows XP as securely as possible. It doesn't matter whether novice, experienced or advanced user, or even expert. Therefore, antimalware programmes with real-time protection are particularly important. Unfortunately, they have become rare under Windows XP due to well-known reasons. One more reason to collect and preserve information about all available security programmes which still work under Windows XP in these days. If you are interested to create an own thread about browser security or whatever, just do it! But this thread is about all available security programmes targeting Windows XP only.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230708-3219d2d-uxp-9f1550fb5-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230708-3219d2d-uxp-9f1550fb5-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230708-3219d2d-uxp-9f1550fb5-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230708-d849524bd-uxp-9f1550fb5-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230708-d849524bd-uxp-9f1550fb5-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20230708-d849524bd-uxp-9f1550fb5-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20230708-d849524bd-uxp-9f1550fb5-xpmod.7z Official UXP changes picked since my last build: - Simplify incremental GC sweeping (95a1e4b7a) - Avoid TLS lookups when checking if zones need to be marked for GC. (24b1a0f16) - Fix debug builds (890e1eb84) - Issue #1969 Follow-Up: Error reporting arguments in RelativeTimeFormat/DateTimeFormat (5a531ea80) - Issue #2259 - Add missing IsAscii* helper functions in mozilla/TextUtils.h (7716602a2) - Issue #2259 - Add mozilla::Vector -> mozilla::Span implicit conversion (9914c0616) - Issue #2259 - Add mozilla::Result<V, E> and JS::Result<> for fallible return values (4c2e37861) - Issue #2259 - Add JS::StackGCVector and JS::RootedVector (f8f7aed52) - Issue #2259 - Adjust self-hosted Array.prototype.sort to ES2018 (a7d752def) - Issue #2259 - Introduce helper for self-hosted hasOwnProperty calls in intl (adffcb127) - Issue #2259 - Update Intl.* Object-ness to ECMA-402, 4th edition (30157344f) - Issue #2046 - Introduce mozIntl.DateTimeFormat with mozExtensions (85612accf) - Issue #2259 - Implement caseFirst option in Intl.Collator (949f69ef4) - Issue #2259 - Reimplement String.prototype.toLocale{Lower,Upper}Case per ECMAScript Intl specification (8d97bd437) - Issue #2259 - Support Unicode extensions with multiple value subtags in BCP47 language tags (e3dbf7c5e) - Issue #2259 - Improve ResolveLocale performance when initializing the default Intl objects (e923c48f4) - Issue #2195 - Add support for hourCycle to Intl.DateTimeFormat (cf7bd8232) - Issue #2259 - process Unicode langtags and locale identifiers according to BCP 47 (3ee2c9dcf) - Issue #1819 - Implement Intl.Locale proposal (c10a29d96) - Issue #2259 - Performance improvements in Locale (4ad4a82a1) - Issue #2259 - Performance improvements for LanguageTag parsing (0b3079d8e) - Issue #1819 - Further align Intl.Locale to spec (e01ff1c5f) - Issue #2046 - Implement Intl.DateTimeFormat's date-/timeStyle and hourCycle options (4400677af) - Issue #1656 - Follow-up: Re-nuke the vim lines introduced in #2265 (f9c39acaa) - [multiple] Update Intl tests. (81a3a92b0) - Issue #2255 & #1240 - Simplify and enhance Maybe and Some(). https://bugzilla.mozilla.org/show_bug.cgi?id=1325351 This is a prerequisite for our BigInt V8 fast forward and potential #2255 fix. (2c0384c4a) - [network] Prepare for requiring Authorization in CORS ACAH preflight (96d1e2766) - [DOM] Filter out symlinks for webkitdirectory. (a299eaa96) - [XPCOM] Win: Update executable extension list (c292f9ffd) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - webextensions: remove experiment related elements (7c4d0444b) Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Comodo Firewall was founded in in the United Kingdom by Melih Abdulhayoğlu in 1998. The company Xcitium, formerly known as Comodo Security Solutions, Inc., is a cybersecurity company, in the meanwhile headquartered in the USA, New Jersey, since 2004. It was a very good firewall in the past. A lot of settings could be done. I would say Comodo Firewall was rather targeting the more advanced user. Anyway! I used it in the past until I became aware of Windows Firewall Control from Sphinx. Users reported in the Comodo Forum that the last error-free working version under Windows XP has been Comodo Firewall 8.4.0.5165. More recent versions didn't seem to work properly under Windows XP although they were advertised to be compatible to this OS. That had annoyed many users. I personally never used it again after I had changed to Windows Firewall Control. But in that days, Comodo Firewall was one of the best. Unfortunately, its installation packages became bloated due to implementing an antivirus solution. These packages are called Comodo Internet Security. I don't like bloated software packages, though. Hope I could help you a bit.

archives updated

By "any" I mean the below, with the bold ones being the most ominous, meaning the drive will fail soon, and from my personal observations with many disks, it dies within days/weeks. (not months) Raw Read Error Rate (may live longer with it, in contrast to write error rate) Spin Up Time Start/Stop Count Reallocated Sectors Count Seek Error Rate (always huge in Seagate) Power On Time Count Spin Retry Count Drive Calibration Retry Count Drive Power Cycle Count Power off Retract Cycle Count Load/Unload Cycle Count Disk Temperature Reallocation Event Count Current Pending Sector Count Off-Line Uncorrectable Sector Count Ultra ATA CRC Error Count (some small chance it could be the cable one bought for cheap) Write Error Rate And I'm not sorry anymore, if you insist.

United Kingdom, one of my favourites! I learnt British English at school. I'm sorry I misspelt the Komodo name, I didn't even think it would be that humorous! I'll test older versions then, report back! Muchly appreciated! Ta muchly!

A real-time antimalware may be useful for novice users, but it makes little sense for users with a high level of mastery such as those who frequent this Windows XP section of the forum. After subjecting a system to on-demand scanning by multiple antimalware, online and offline, I can consider the system safe; rechecking every time I use components that have been in the system for many years and used countless times without problems is just a waste of time and computational resources. Since at least ten years I have been performing only periodic scans, and since the scans end regularly without reporting problems, gradually the period has automatically lengthened; and in any case, a possible infection would not create big problems and would be detected immediately. It is necessary instead carefully monitor new grafts, external elements entering into the system. To test new programs the procedures are well known to users of this forum: Virtual Machines, SandboxIE, other forms of sandboxes, etc. I typically test the installation of new programs under SandboxIE, and I use two scripts to derive a report of the changes that the installation would make to the system (new or changed files, changes to registry, etc.), reports that I archive along with the program. For incidentally, from this structural information I almost always build a portable instance of the program, which I keep off the system partition (20 GB, of which only 13.2 GB is occupied). If the program installs drivers in the system, SandboxIE is generally not usable and it is necessary to run the test in a virtual machine; even in this case I create and keep a report of the changes that the installation makes to the system. But today in reality the main source of infection is the Web, and the most dangerous vehicles are browsers; here the variables and defense mechanisms are virtually infinite, so I subscribe to the need posed by @UCyborg to create a new dedicated thread: Maybe we need a thread about surviving on the modern internet without an antivirus? Notes: 1. Similar considerations apply to Android, where the real usefulness of antimalware is even more doubtful, and many other defense tools exist. 2. I consider improper that in this technical forum are allowed expressions and positions of a decidedly racist nature, further confirmation of the well-known maxim that the first casualty of a war is truth (and common sense, I might add); but this too surely requires a dedicated thread. Greetings

KB943545: https://download.overrender.com/content/software/other/mysoft/wu/WindowsServer2003-KB943545-x86-ENU.exe KB946448: https://download.overrender.com/content/software/other/mysoft/wu/WindowsServer2003-KB946448-x86-ENU.exe Here you go

I explained that some weeks ago. I always try to write in British English but I often mixed up some words with American English. Starting some weeks ago, I now try my best not to do so anymore. But, I am not a native speaker and surely not perfect.

Hello @Saxon! Thank you very much for the kind words! I'll try to do my best. Researching and writing is unfortunately very time-consuming. Real life and physical health are two reasons my list of security programmes is increasing quite slowly. Comodo Varanus! That's very funny. I will do that with pleasure when I am back at my desktop computer.

An actors' social site IMDB is also paywalled since quite some time ago. They run a script to show their subscription window and then the site blocks the browser.

Wait. Reddit paywalled, too? It's not for me, Maybe it's country specific? Reddit is still free to watch in my EU country. Just a random topic I chose: https://www.reddit.com/r/MilitaryPorn/comments/1mludb/restored_german_88_aa_flak_cannon_firing_960x636/

After 10 years using Sandy Bridge, I have decided that the time has come to update my main hardware, I resisted updating, among other things, due to the stagnation of intel between 2012 and 2017 as well as the incompatibility of old Windows (already Kaby Lake was not even officially compatible with Windows 8.1). Then I found Alder Lake running on Windows 7 (with a dedicated graphics card): https://msfn.org/board/topic/183194-windows-7-on-the-intel-alder-lakez690-platform/, and I told myself it's time to upgrade! I have done several tests with different versions of Windows such as Windows 7, XP, and of course, Windows Vista. In this article I will summarize how I managed to install Windows Vista, although it is not the best option for such current hardware. Procedure to install Vista on an Alder Lake system: 1- Download USB 3.0 AMDXHCI drivers: Windows Vista, like Windows 7, are not compatible with USB 3 natively, so you have to proceed to unofficial universal drivers such as AMDXHCI, I leave a link to some specifically designed for Vista: here 2- Burn the Vista SP2 64-bit iso image on a USB stick: Do it with the Rufus program, if it's in GPT change it to MBR, change the file system to NTFS. After burning the ISO, copy the AMDXHCI folder to the root of your USB. 3- Enable CSM in BIOS 4- Time to install Vista!: Connect the USB memory in a USB 3.0 port, and use a PS2 mouse in this part since the whole USB will not work, when you click "Install Now" a dialog will appear asking for a driver, click on browse and locate the previously downloaded AMDXHCI. The installation is normal. 5- OOBE time: Before you get to the final Vista installation setup, press F8 as Vista starts and choose "Allow unsigned drivers" as USB 3.0 won't work. 6- Install essential drivers with SnappyDriverInstaller: When you get to the desktop you must install some drivers with SDI, select all the drivers that appear (except one for synaptics mouse) and install them without problems. Until here, ready, we already have Vista working in Alder Lake! Works: - HD Audio - USB 3.x It does not work: - Ethernet Without trying: - NVMe - Big-little Clarification: it is mandatory to use a dedicated graphics and disable the integrated graphics since with the latter the CSM will not work. You must have a dedicated network/wifi card since the ethernet provided by intel only works in Windows 10/11.

With all due respect to your personal experience, unless you are (and have been for a long time) an IT technician working on a very large organization (that actually monitors S.M.A.R.T. parameters on a large number of disks), I doubt that you can have enough data points to "cover" 17 different parameters and highlight as more common 8 of them (if you prefer your "many disks" may be too few to draw conclusions). Backblaze, monitoring some 70,000 disk drives found only 5 (maybe 6) parameters correlated with impending drive failure: https://www.backblaze.com/blog/what-smart-stats-indicate-hard-drive-failures/ and possibly: not fully overlapping with your list and with some caveats about the need of additionally interpreting the actual values depending on the timeframe they occurred/increased count. A known (cited in the article) BIG unknown is whether power up cycles (S.M.A.R.T. 12) has any correlation as the drives they monitored belong to server farms so they have very, very few power cycles, unlike the disk drives in use by many organizations and most final users that are usually powered on/off on a daily basis, it is reasonable to add it to the list, making it a total of 7 parameters to look for. jaclaz

You are very welcome to disagree, no need to be sorry. The point I am trying to make is that even if it (the S.M.A.R.T.) was a reliable predictor (and it isn't, at least in large numbers) it is a "vague" one, just like "Seagate", each model/series of a given brand like Seagate may present different failure modes, and while some of them may actually cause a change in S.M.A.R.T. parameters that can lead to a valid warning by the monitoring software many others won't. This and the lack of proper data (about the way some of the S.M.A.R.T. parameters are implemented by the manufacturer) lead to a situation that can be described as "when it works it works, when it doesn't, it doesn't" so that the reference I often make to flippism being equivalent (intentionally provocative) is not at all unjustified. The issue I have with your statement revolves about the "any" in "ahead of any failure", as what happens in practice is ahead of some failures where - additionally - the ahead could mean hours, days, weeks or even months ahead. Better than nothing, but still nothing to be trusted upon. jaclaz

Misspelling doesn't matter at all and was not the reason I had to laugh. It was the zoological classification of this firewall. Personally, I found it funny. And a bit of humour definitely can't hurt in this thread. In any case, thanks for your interest and support!

No, I mean you can use multi threaded WIM apply also with image.exe or DISM.exe on command prompt by just setting WIM_FileData_Number_Workers environment variable. WinNTSetup will load an existing WinNTSetup.ini on start. This .ini can be loaded or saved with Ctrl + L and CTRL + S hotkey and holds most GUI settings. WinNTSetup.ini.txt describes hidden feature than can be added to WinNTSetup.ini. like: [options] UseMultiCore=1

I'm sure you wanted to say evolves, right? Well, it depends on the social circle, and varies from one state to another.

... I don't even have Adobe Primetime CDM installed in my Serpent 55 profile - never needed it on Vista SP2, TBH ; but, I do have the Cisco Systems OpenH264 video codec v1.6 installed (and disabled), which correctly displays inside about:addons and about:plugins; widevine doesn't in either ; in my St55 profile, I have: media.eme.enabled;true media.gmp-widevinecdm.autoupdate;true media.gmp-widevinecdm.enabled;true media.gmp-widevinecdm.visible;true and the CDM correctly installed. When I downgrade St55 to a build before Apr 2019, in that same profile, then WV CDM is correctly recognised and additional prefs: user_pref("media.gmp-widevinecdm.abi", "x86-msvc-x86"); user_pref("media.gmp-widevinecdm.autoupdate", true); user_pref("media.gmp-widevinecdm.lastUpdate", 1549772952); user_pref("media.gmp-widevinecdm.version", "1.4.8.903"); appear inside my profile's pref.js file... Update St55 and these prefs are NOT read! Am afraid I've given all pertinent detail I found at the time; FWIW, I suppose you can troubleshoot DRM/Widevine issues in St55 on a Win7 OS too, probably no immediate need to install a Vista VM (a necessary step to troubleshoot the default St55 theme issue reported though, because under Win7 all looks fine); might be worth to inspect how St52 does it, as there both Adobe Primetime and Widevine can happily coexist... (Apologies, it's finally bed time here, so I'll be unavailable for quite a while ...) Edit: See further tests and discussion here ...

Not sure how much traction that would attract. The end-consumer is more interested in something like uBlock Origin and "downloaded lists" doing as much of the work as possible "for them", an ideology I myself do not subscribe to. And while I do applaud Astro's "intentions" in creating this thread, I do think that the most tech-savvy among us (the MAJORITY of MSFN Members?) do not run real-time antivirus "all the time". I don't even run manual scans, haven't in over 20 years! But again, I applaud the intentions of this thread. I see it more of as an EXPANSION to the MSFN USER BASE by bringing in a NEW AUDIENCE. I don't think it has (yet), but it has the potential to. I don't see the intended audience being the ACTIVE MEMBERS here at MSFN. But rather a NEW generation of active members.

... This is not accurate, though, because roytam1 did restore the bits of code that implement native Vista SP2 WMF support that Mozilla (and MCP) had originally removed... Yes, that's true, support for patented decoders aiming the XP OS (and Vista without PUS[Platform Update Supplement]) had been realised via modifying the ffvpx library, which uses ffmpeg code... Latest St55 (32-bit) comes with both media.wmf.enabled;true media.ffvpx.enabled;true and if I disable ffvpx, the app can still play back MP4 files via Vista's WMF ; the only major advantage of Vista's WMF over the ffvpx lib is that WMF allows for H/W decoding of h.264 video, provided your GFX card supports it; mine doesn't , so ffvpx stays turned ON... On the Vista side of things, however, two "things" at least remain broken ... a. The default St55 (complete) theme renders unsatisfactorily in the caption buttons (minimize/maximize-restore/close) area; it was all fine in the first St55 builds, below is a snapshot from a March 2018 St55 build: (which shows good rendering around the caption buttons area), but at some later point (I think it was one tenfourfox backport?) it broke in the same manner the default St52 theme renders under Vista: b. While St55 is still being built with "--enable-eme=widevine", its EME/WV implementation has been broken since many years ; by "broken" I don't mean that the WV CDM "can't properly decrypt DRM'ed content", this is to be expected if Widevine worked in the first place , because St55 inherited WV v1.4.8.903 from Mozilla, and that very old version has been deprecated by Google many years ago ... The actual problem/bug is that currently St55 doesn't even recognise the WV CDM when correctly installed and it doesn't display it at all inside the about:plugins list (provided "Play DRM content" has been enabled in preferences); this is a long standing issue I never bothered to report, because I normally use St52 to detect DRMed online media content ... Unlike the default theme issue above (a), I had kept records of the manifestation of this bug, here it goes: Last GOOD build: basilisk55-win32-git-20190330-09b851794-xpmod (buildID=20190329133942) First BAD build: basilisk55-win32-git-20190406-4d70836fa-xpmod (buildID=20190405065215) Regression window: https://github.com/roytam1/basilisk55/compare/09b851794...4d70836fa Probable culprit: ported change from iceweaselXP-53: Restored eme-adobe plugin support for Windows XP systems. So, in order to supply Windows XP users with an additional way to play-back MP4/m4a files in St55 (via the Adobe Primetime CDM, already familiar with in FxESR 52/St52), Widevine CDM became broken for Vista+ users ... Widevine CDM v1.4.8.903 for St55 (32-bit): https://www.mediafire.com/file/jrjkcqazh1xz6ce/gmp-widevinecdm.7z/file (The file should be extracted as a "gmp-widevinecdm\1.4.8.903\*" dir tree and placed inside your St55 profile directory); testing should be done on, e.g., https://bitmovin.com/demos/drm on fully updated Vista SP2 onwards, with up-to (and including) "basilisk55-win32-git-20190330-09b851794-xpmod": Later versions of St55 will just report:

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 http://o.rthost.win/basilisk/basilisk55-win32-git-20230708-fe0a96ad1-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20230708-fe0a96ad1-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Simplify incremental GC sweeping (95a1e4b7) (d2253a89a) - import from UXP: Avoid TLS lookups when checking if zones need to be marked for GC. (24b1a0f1) (e1689e78a) - import from UXP: Fix debug builds (890e1eb8) (f084c5f2a) - import from UXP: Issue #1969 Follow-Up: Error reporting arguments in RelativeTimeFormat/DateTimeFormat (5a531ea8) (69c57d4d0) - import from UXP: Issue #2259 - Add missing IsAscii* helper functions in mozilla/TextUtils.h (7716602a) (984ee494c) - import from UXP: Issue #2259 - Add mozilla::Vector -> mozilla::Span implicit conversion (9914c061) (ba968e34b) - ported from UXP: Issue #2259 - Add mozilla::Result<V, E> and JS::Result<> for fallible return values (4c2e3786) (c64ea42b8) - import from UXP: Issue #2259 - Add JS::StackGCVector and JS::RootedVector (f8f7aed5) (95477f4ad) - import from UXP: Issue #2259 - Adjust self-hosted Array.prototype.sort to ES2018 (a7d752de) (2ae545058) - import from UXP: Issue #2259 - Introduce helper for self-hosted hasOwnProperty calls in intl (adffcb12) (95626129f) - ported from UXP: Issue #2259 - Update Intl.* Object-ness to ECMA-402, 4th edition (30157344) (3c8e8054d) - ported from UXP: Issue #2046 - Introduce mozIntl.DateTimeFormat with mozExtensions (85612acc) (7954eab77) - import from UXP: Issue #2259 - Implement caseFirst option in Intl.Collator (949f69ef) (1f6a9788f) - ported from UXP: Issue #2259 - Reimplement String.prototype.toLocale{Lower,Upper}Case per ECMAScript Intl specification (8d97bd43) (974255cc9) - import from UXP: Issue #2259 - Support Unicode extensions with multiple value subtags in BCP47 language tags (e3dbf7c5) (a16d19623) - import from UXP: Issue #2259 - Improve ResolveLocale performance when initializing the default Intl objects (e923c48f) (71f8a0937) - import from UXP: Issue #2195 - Add support for hourCycle to Intl.DateTimeFormat (cf7bd823) (216d8574f) - ported from UXP: Issue #2259 - process Unicode langtags and locale identifiers according to BCP 47 (3ee2c9dc) (6e6363b76) - ported from UXP: Issue #1819 - Implement Intl.Locale proposal (c10a29d9) (a115fffe3) - ported from UXP: Issue #2259 - Performance improvements in Locale (4ad4a82a) (4e25a11d6) - ported from UXP: Issue #2259 - Performance improvements for LanguageTag parsing (0b3079d8) (46975f66d) - import from UXP: Issue #1819 - Further align Intl.Locale to spec (e01ff1c5) (b40437880) - import from UXP: Issue #2046 - Implement Intl.DateTimeFormat's date-/timeStyle and hourCycle options (4400677a) (df34fda78) - import from UXP: Issue #1656 - Follow-up: Re-nuke the vim lines introduced in #2265 (f9c39aca) (e2666e4ac) - import from UXP: [multiple] Update Intl tests. (81a3a92b) (22360cb99) - ported from UXP: [network] Prepare for requiring Authorization in CORS ACAH preflight (96d1e276) (c58b948b1) - ported from UXP: [DOM] Filter out symlinks for webkitdirectory. (a299eaa9) (64d75ced6) - import from UXP: [XPCOM] Win: Update executable extension list (c292f9ff) (fe0a96ad1)

Right! So what do you want to win? Agreed!

Present the point and let the reader decide. No "post scriptum" explanation required. Nobody wins if everybody strives to get the "last word". Just rambling... Carry on...

The reason I wrote this post is very simple. Cloning or imaging a hard disk which has errors will usually fail due to read errors. Good copy programmes report these unreadable or unsuccessfully copied files and skip them. In such a case, much better. Generally, I use special backup programmes to make complete images of only working, error-free system partitions. I never clone a drive completely. Other files outside of my system partitions will be backuped or synchronized by different tools depending on how I want to handle them.

@Monroe! Cloning or imaging a hard disk is the best method to get a backup including the file system structure if the drive is error-free. But if your hard disk has already errors, it will be better to copy all files using a copy programme such as TeraCopy (or similars) which reports all unsuccessfully copied files and skips them. You can set TeraCopy to check the hash of each copied file. It will backup all files that are readable, and you'll definitely know which files are problematic and to be restored.

That's the thread count used by wimgapi. See WinNTSetup.ini.txt, by default if uses half of CPU physical cores. You can uses this with imagex.exe or DISM.exe, too. set WIM_FileData_Number_Workers=8 Imagex /apply ...

What I always do is to monitor the S.M.A.R.T. values. You can do that with tools like Hard Disk Sentinel or CrystalDiskInfo. I have a license for Hard Disk Sentinel. Therefore, it is always running in the background to notify me if the S.M.A.R.T. values have changed.

Hello @Monroe! Thanks for sharing! Most of the programmes in that article are already part of my private archive. On Lifewire, one can find a lot of articles with software presentations in terms of different topics. In any case, good find!

It is hard to say which is the fork-point since they squashed merging few time of whole repo: they started with 52.0.3: https://github.com/roytam1/moebius-archive/blob/ee321f0b4a7739e8ff23d08c933a24b3c79f8d72/config/milestone.txt in 1st time of squashed merge, it becomes 53.0.3: https://github.com/roytam1/moebius-archive/blob/18f9942ea70f66ffa26b81ac393542751b9df407/config/milestone.txt and changed it to 54 after a while: https://github.com/roytam1/moebius-archive/blob/563aca227cebddb69b9c1fdf6136329e5a214ee4/config/milestone.txt and changed it to Goanna 4 after somewhile: https://github.com/roytam1/moebius-archive/blob/d4fd245a62b255a10618c3cdabe897d194a44a6f/config/milestone.txt the problem is what mozilla hg rev is moebius rev 18f9942ea70f66ffa26b81ac393542751b9df407 based on?

Dear guru AstroSkipper, hello! Would you be so kind to tell your opinion about Comodo Varanus FW, I don't see it in either of you lists (good-bad). Would it be polite to trouble you for such a personal advice, just a couple of words really, use-not use, thank you! PS. As always, can't get enough of your amazing software compilation! I can't even imagine how much hard work is in it!

Your link is outdated and doesn't work, please check and do aproper research before posting. Here is 16.22, perhaps you would want to try? https://www.filepuma.com/download/process_explorer_16.22-20946/

No, more European companies will emerge on the market, good.

It was simple, yet ok and clever for that times, Nero indeed had several legit services running, if you installed the full package, like with the search bot for winXP. Called "Nero scout". So seemed fine, even for the crappy NOD32 or AVAST, they both completely ignored it. I'm sure you can find similar stories, many people had the combination of AVAST+NERO during that era.

On topic > I don't know if either of you heard these sad news, Twitter is now fully blocking Nitter! Twitter has become absolutely isolated, no way to read it for free!

Thanks for your information! My processor is an Intel Pentium 4 32-Bit single core in my Windows XP Professional computer. This CPU is vulnerable to Spectre and Meltdown, of course. But as I am aware of, don't we need to distinguish between a CPU and. a browser in terms of vulnerability? I think so! Especially after what I have read. At least, that's presumably the reason there is a CPU test and a seperate browser test.

The only one who is desperate here seems to be you. Again and again the same. The topic has been over for a long time. Everything has been said. And your permanent, personal attacks then don't help any more, either. As always, the following applies: Reading and understanding is an art in itself.

Criticizing? Far from it. As far as I'm concerned, everyone can do whatever they want with their computer. Whether it makes sense or not. I couldn't care less! And if you read my first post properly, you would have noticed that I appreciate your project from a technical point of view. Here is my statement again: And having a different opinion and expressing it does never harm. Quite the opposite! It might make you think. At least that's how it works here in Germany and in many other European countries. And if someone has a problem with that, it doesn't bother me at all. For my part, I am neither interested in gaming nor in retro computing. I have been a genuine Windows XP user for over 20 years and am therefore not interested in retro, but in original. All my doing here on MSFN is to support real Windows XP users who need this operation system or want to use it for whatever reason. And by that I don't mean playing around with Windows XP today and Windows 98 in a VM tomorrow and so on. Yep, the beauty of XP is in the sum of its part and has fully developed in my computer over more than two decades. And it doesn't seem to want to stop. Cheers, AstroSkipper

TBH, how many seconds more or less are needed for a cold or warm start of a computer is completely irrelevant to me and not an important criterion. Then I'll go have a smoke. The actual point I was making is different. Brevity is the spice: modern computer, modern operating system. It's as simple as that. IMHO, Windows XP belongs on older hardware, which is fully utilised by this operating system. Otherwise, a computer would not be used in all its capabilities.