Leaderboard

Fact: There's a handful of accounts that can't properly behave themselves with women. My opinion: I'm not sure if the downvote button will make them behave. There's got to be another form of punishment. I'm giving out a couple of examples. Their posts are quoted with my replies, they are known to edit posts out. https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=1259796 https://msfn.org/board/topic/184249-chrome-110-based-opera-i-ported-it-to-vista/?do=findComment&comment=1260409 What do other users think, will "not like" help? I don't think so. I'm open to suggestions, opinions.

The Death of Security: Hackers Can Extract Your Fingerprints from Sound of Swiping Touchscreen https://www.breitbart.com/tech/2024/02/21/the-death-of-security-hackers-can-extract-your-fingerprints-from-sound-of-swiping-touchscreen/ Lucas Nolan / 21 Feb 2024 Researchers have reportedly discovered a new side-channel attack that can extract a person’s fingerprints from the sounds made when a finger swipes across a touchscreen. Toms Hardware reports that researchers from institutions in China and the United States have outlined an innovative attack targeting biometric security in a paper entitled “PrintListener: Uncovering the Vulnerability of Fingerprint Authentication via the Finger Friction Sound.” This attack utilizes the audio characteristics of a finger gliding across a touchscreen to infer attributes of the fingerprint pattern. more ...

You may be surprised, I used to think the same thing. I'm running 10 on a 15yr old eMachines T3656 with only 3GB RAM without any issues whatsoever. WinReducer EX-100 - Learn it, Use it! :) NO! I'm not being <insert negative adjective of choice> and trying to load up 10, 20, or 30 tabs in a web browser! Some times we bring upon our own misery and cannot blame others for that misery.

The paper is here: https://www.ndss-symposium.org/wp-content/uploads/2024-618-paper.pdf Of course everyone will start swiping with knuckles, scared by the possibility (actually extremely remote) that something like what is described in the paper actually works in the real world. A much more dangerous attack, with almost 100% success : https://www.dailymail.co.uk/news/article-4069090/Mommy-shopping-Six-year-old-Arkansas-girl-used-sleeping-mom-s-fingerprints-unlock-iPhone-buy-13-Pokemon-gifts-Amazon-total-250.html jaclaz

I see, if my HW could be faster, I'll use Win7,because lots of software doesn't support XP

Big tech builds the AI so the old machines go for scrap. That is why the internet change the form to IoT. Welcome to New World Order...

Thank you, very interesting, enjoyed the reading! Keep adding more of these, please.

3.7.4 has been taken down, please stand by Meanwhile, please test http://startisback.com/StartAllBack_setup.exe

OK, here's what i got when I went back to XP. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Users\Dave>chkdsk t: The type of the file system is NTFS. Volume label is BACKUP. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed. Windows has checked the file system and found no problems. 2861586 MB total disk space. 1617508832 KB in 85507 files. 27348 KB in 1716 indexes. 0 KB in bad sectors. 265220 KB in use by the system. 65536 KB occupied by the log file. 1312463684 KB available on disk. 4096 bytes in each allocation unit. 732566271 total allocation units on disk. 328115921 allocation units available on disk. D:\Users\Dave> And here's what I got back in 10. Microsoft Windows [Version 10.0.19045.4046] (c) Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>chkdsk t: The type of the file system is NTFS. Volume label is BACKUP. WARNING! /F parameter not specified. Running CHKDSK in read-only mode. Stage 1: Examining basic file system structure ... Attribute record (80, "") from file record segment 14E0C is corrupt. Attribute record (80, "") from file record segment 14E11 is corrupt. Attribute record (80, "") from file record segment 14E13 is corrupt. Attribute record (80, "") from file record segment 14E18 is corrupt. Attribute record (80, "") from file record segment 14E19 is corrupt. Attribute record (80, "") from file record segment 14E1A is corrupt. Attribute record (80, "") from file record segment 14E1B is corrupt. Attribute record (80, "") from file record segment 14E6B is corrupt. Attribute record (80, "") from file record segment 14E6C is corrupt. Attribute record (80, "") from file record segment 14E70 is corrupt. Attribute record (80, "") from file record segment 14E76 is corrupt. Attribute record (80, "") from file record segment 14E78 is corrupt. Attribute record (80, "") from file record segment 14E7D is corrupt. Attribute record (A0, $I30) from file record segment 14E9E is corrupt. Attribute record (A0, $I30) from file record segment 14EFD is corrupt. Attribute record (A0, $I30) from file record segment 14EFE is corrupt. Attribute record (A0, $I30) from file record segment 14F05 is corrupt. Attribute record (A0, $I30) from file record segment 14F12 is corrupt. Attribute record (A0, $I30) from file record segment 14F21 is corrupt. Attribute record (A0, $I30) from file record segment 14F2E is corrupt. Attribute record (A0, $I30) from file record segment 14F48 is corrupt. Attribute record (A0, $I30) from file record segment 14F4B is corrupt. Attribute record (A0, $I30) from file record segment 15037 is corrupt. Attribute record (A0, $I30) from file record segment 15042 is corrupt. Attribute record (A0, $I30) from file record segment 15048 is corrupt. Attribute record (A0, $I30) from file record segment 1504F is corrupt. Attribute record (A0, $I30) from file record segment 15073 is corrupt. Attribute record (A0, $I30) from file record segment 15074 is corrupt. Attribute record (A0, $I30) from file record segment 15091 is corrupt. Attribute record (A0, $I30) from file record segment 150A8 is corrupt. Attribute record (A0, $I30) from file record segment 150C5 is corrupt. Attribute record (A0, $I30) from file record segment 150CF is corrupt. Attribute record (A0, $I30) from file record segment 150ED is corrupt. Attribute record (A0, $I30) from file record segment 150F5 is corrupt. Attribute record (A0, $I30) from file record segment 15107 is corrupt. Attribute record (A0, $I30) from file record segment 15108 is corrupt. Attribute record (A0, $I30) from file record segment 15134 is corrupt. Attribute record (A0, $I30) from file record segment 15142 is corrupt. Attribute record (A0, $I30) from file record segment 15168 is corrupt. Attribute record (A0, $I30) from file record segment 15199 is corrupt. Attribute record (A0, $I30) from file record segment 151D2 is corrupt. Attribute record (A0, $I30) from file record segment 151D3 is corrupt. Attribute record (A0, $I30) from file record segment 151EC is corrupt. Attribute record (A0, $I30) from file record segment 1521D is corrupt. Attribute record (A0, $I30) from file record segment 15272 is corrupt. Attribute record (A0, $I30) from file record segment 1A3BB is corrupt. Attribute record (A0, $I30) from file record segment 1A407 is corrupt. Attribute record (A0, $I30) from file record segment 1A429 is corrupt. Attribute record (A0, $I30) from file record segment 1A434 is corrupt. Attribute record (A0, $I30) from file record segment 1A435 is corrupt. Attribute record (A0, $I30) from file record segment 1A76D is corrupt. Attribute record (A0, $I30) from file record segment 1A77B is corrupt. Attribute record (80, "") from file record segment 1A781 is corrupt. Attribute record (A0, $I30) from file record segment 1A790 is corrupt. Attribute record (80, "") from file record segment 1A791 is corrupt. Attribute record (A0, $I30) from file record segment 1A7B8 is corrupt. Attribute record (80, "") from file record segment 1A7DD is corrupt. Attribute record (80, "") from file record segment 1A844 is corrupt. Attribute record (80, "") from file record segment 1A855 is corrupt. Attribute record (80, "") from file record segment 1A85F is corrupt. Attribute record (80, "") from file record segment 1A863 is corrupt. Attribute record (80, "") from file record segment 1A864 is corrupt. Attribute record (80, "") from file record segment 1A867 is corrupt. Attribute record (80, "") from file record segment 1A869 is corrupt. Attribute record (80, "") from file record segment 1A870 is corrupt. Attribute record (80, "") from file record segment 1A877 is corrupt. Attribute record (80, "") from file record segment 1A879 is corrupt. Attribute record (80, "") from file record segment 1A87B is corrupt. Attribute record (80, "") from file record segment 1A87E is corrupt. Attribute record (80, "") from file record segment 1A882 is corrupt. Attribute record (80, "") from file record segment 1A889 is corrupt. Attribute record (80, "") from file record segment 1A88A is corrupt. Attribute record (80, "") from file record segment 1A88B is corrupt. Attribute record (80, "") from file record segment 1A88D is corrupt. Attribute record (80, "") from file record segment 1A896 is corrupt. Attribute record (80, "") from file record segment 1A8A4 is corrupt. Attribute record (80, "") from file record segment 1A8A6 is corrupt. Attribute record (80, "") from file record segment 1A8B0 is corrupt. Attribute record (A0, $I30) from file record segment 1AA4C is corrupt. Attribute record (A0, $I30) from file record segment 1AA4D is corrupt. Attribute record (80, "") from file record segment 1AA5E is corrupt. Attribute record (80, "") from file record segment 1AA63 is corrupt. Attribute record (80, "") from file record segment 1AA81 is corrupt. Attribute record (80, "") from file record segment 1AA82 is corrupt. Attribute record (80, "") from file record segment 1AA83 is corrupt. Attribute record (80, "") from file record segment 1AA85 is corrupt. Attribute record (80, "") from file record segment 1AA86 is corrupt. Attribute record (80, "") from file record segment 1AA87 is corrupt. Attribute record (80, "") from file record segment 1AA88 is corrupt. Attribute record (80, "") from file record segment 1AA8A is corrupt. Attribute record (80, "") from file record segment 1AA8B is corrupt. Attribute record (80, "") from file record segment 1AA8C is corrupt. Attribute record (80, "") from file record segment 1AA8D is corrupt. Attribute record (80, "") from file record segment 1AA8E is corrupt. Attribute record (80, "") from file record segment 1AA8F is corrupt. Attribute record (80, "") from file record segment 1AA90 is corrupt. Attribute record (80, "") from file record segment 1AA91 is corrupt. Attribute record (80, "") from file record segment 1AA92 is corrupt. Attribute record (80, "") from file record segment 1AA93 is corrupt. Attribute record (80, "") from file record segment 1AA95 is corrupt. Attribute record (80, "") from file record segment 1AABA is corrupt. Attribute record (80, "") from file record segment 1AABC is corrupt. Attribute record (80, "") from file record segment 1AABE is corrupt. Attribute record (80, "") from file record segment 1AABF is corrupt. Attribute record (80, "") from file record segment 1AAC0 is corrupt. Attribute record (80, "") from file record segment 1AAC1 is corrupt. Attribute record (80, "") from file record segment 1AAC3 is corrupt. Attribute record (80, "") from file record segment 1AAC4 is corrupt. Attribute record (80, "") from file record segment 1AAC5 is corrupt. Attribute record (80, "") from file record segment 1AAC6 is corrupt. Attribute record (80, "") from file record segment 1AAC7 is corrupt. Attribute record (80, "") from file record segment 1AAC8 is corrupt. Attribute record (80, "") from file record segment 1AAC9 is corrupt. Attribute record (80, "") from file record segment 1AACA is corrupt. Attribute record (80, "") from file record segment 1AACB is corrupt. Attribute record (80, "") from file record segment 1AACC is corrupt. Attribute record (80, "") from file record segment 1AACD is corrupt. Attribute record (80, "") from file record segment 1AAD0 is corrupt. Attribute record (80, "") from file record segment 1AAD1 is corrupt. Attribute record (80, "") from file record segment 1AAD2 is corrupt. Attribute record (80, "") from file record segment 1AAD3 is corrupt. Attribute record (80, "") from file record segment 1AAD4 is corrupt. Attribute record (80, "") from file record segment 1AAD5 is corrupt. Attribute record (80, "") from file record segment 1AAD7 is corrupt. Attribute record (80, "") from file record segment 1AAD8 is corrupt. Attribute record (80, "") from file record segment 1AAD9 is corrupt. Attribute record (80, "") from file record segment 1AADA is corrupt. Attribute record (80, "") from file record segment 1AADB is corrupt. Attribute record (80, "") from file record segment 1AADC is corrupt. Attribute record (80, "") from file record segment 1AADD is corrupt. Attribute record (80, "") from file record segment 1AADE is corrupt. Attribute record (80, "") from file record segment 1AAE0 is corrupt. Attribute record (80, "") from file record segment 1AAE1 is corrupt. Attribute record (80, "") from file record segment 1AAE2 is corrupt. Attribute record (80, "") from file record segment 1AAE3 is corrupt. Attribute record (80, "") from file record segment 1AAE4 is corrupt. Attribute record (80, "") from file record segment 1AAE5 is corrupt. Attribute record (80, "") from file record segment 1AAE6 is corrupt. Attribute record (80, "") from file record segment 1AAE7 is corrupt. Attribute record (80, "") from file record segment 1AAE8 is corrupt. Attribute record (80, "") from file record segment 1AAE9 is corrupt. Attribute record (80, "") from file record segment 1AAEA is corrupt. Attribute record (80, "") from file record segment 1AAEB is corrupt. Attribute record (80, "") from file record segment 1AAEC is corrupt. Attribute record (80, "") from file record segment 1AAED is corrupt. Attribute record (80, "") from file record segment 1AAEE is corrupt. Attribute record (80, "") from file record segment 1AAEF is corrupt. Attribute record (80, "") from file record segment 1AAF0 is corrupt. Attribute record (80, "") from file record segment 1AAF1 is corrupt. Attribute record (80, "") from file record segment 1AAF2 is corrupt. Attribute record (80, "") from file record segment 1AAF3 is corrupt. Attribute record (80, "") from file record segment 1AAF4 is corrupt. Attribute record (80, "") from file record segment 1AAF5 is corrupt. Attribute record (80, "") from file record segment 1AAF6 is corrupt. Attribute record (80, "") from file record segment 1AAF7 is corrupt. Attribute record (80, "") from file record segment 1AAF8 is corrupt. Attribute record (80, "") from file record segment 1AAF9 is corrupt. Attribute record (80, "") from file record segment 1AAFA is corrupt. Attribute record (80, "") from file record segment 1AAFB is corrupt. Attribute record (80, "") from file record segment 1AAFC is corrupt. Attribute record (80, "") from file record segment 1AAFD is corrupt. Attribute record (80, "") from file record segment 1AAFE is corrupt. Attribute record (80, "") from file record segment 1AAFF is corrupt. Attribute record (80, "") from file record segment 1AB00 is corrupt. Attribute record (80, "") from file record segment 1AB01 is corrupt. Attribute record (80, "") from file record segment 1AB02 is corrupt. Attribute record (80, "") from file record segment 1AB03 is corrupt. Attribute record (80, "") from file record segment 1AB04 is corrupt. Attribute record (80, "") from file record segment 1AB05 is corrupt. Attribute record (80, "") from file record segment 1AB06 is corrupt. Attribute record (80, "") from file record segment 1AB07 is corrupt. Attribute record (80, "") from file record segment 1AB08 is corrupt. Attribute record (80, "") from file record segment 1AB09 is corrupt. Attribute record (80, "") from file record segment 1AB0A is corrupt. Attribute record (80, "") from file record segment 1AB0B is corrupt. Attribute record (80, "") from file record segment 1AB0C is corrupt. Attribute record (80, "") from file record segment 1AB0D is corrupt. Attribute record (80, "") from file record segment 1AB0E is corrupt. Attribute record (80, "") from file record segment 1AB0F is corrupt. Attribute record (80, "") from file record segment 1AB10 is corrupt. Attribute record (80, "") from file record segment 1AB11 is corrupt. Attribute record (80, "") from file record segment 1AB12 is corrupt. Attribute record (80, "") from file record segment 1AB13 is corrupt. Attribute record (80, "") from file record segment 1AB14 is corrupt. Attribute record (80, "") from file record segment 1AB15 is corrupt. Attribute record (80, "") from file record segment 1AB16 is corrupt. Attribute record (80, "") from file record segment 1AB17 is corrupt. Attribute record (80, "") from file record segment 1AB18 is corrupt. Attribute record (80, "") from file record segment 1AB19 is corrupt. Attribute record (80, "") from file record segment 1AB1A is corrupt. Attribute record (80, "") from file record segment 1AB1B is corrupt. Attribute record (80, "") from file record segment 1AB1C is corrupt. Attribute record (80, "") from file record segment 1AB1D is corrupt. Attribute record (80, "") from file record segment 1AB1E is corrupt. Attribute record (80, "") from file record segment 1AB1F is corrupt. Attribute record (80, "") from file record segment 1AB20 is corrupt. Attribute record (80, "") from file record segment 1AB21 is corrupt. Attribute record (80, "") from file record segment 1AB22 is corrupt. Attribute record (80, "") from file record segment 1AB23 is corrupt. Attribute record (80, "") from file record segment 1AB24 is corrupt. Attribute record (80, "") from file record segment 1AB25 is corrupt. Attribute record (80, "") from file record segment 1AB26 is corrupt. Attribute record (80, "") from file record segment 1AB40 is corrupt. Attribute record (80, "") from file record segment 1AB41 is corrupt. Attribute record (80, "") from file record segment 1AB42 is corrupt. Attribute record (80, "") from file record segment 1AB49 is corrupt. Attribute record (80, "") from file record segment 1AB64 is corrupt. Attribute record (80, "") from file record segment 1AB90 is corrupt. Attribute record (80, "") from file record segment 1AB9D is corrupt. Attribute record (80, "") from file record segment 1ABCB is corrupt. Attribute record (80, "") from file record segment 1ABCD is corrupt. Attribute record (80, "") from file record segment 1ABD2 is corrupt. Attribute record (80, "") from file record segment 1AC15 is corrupt. Attribute record (80, "") from file record segment 1ACAD is corrupt. Attribute record (80, "") from file record segment 1ACAF is corrupt. Attribute record (80, "") from file record segment 1ACBA is corrupt. 109824 file records processed. File verification completed. Phase duration (File record verification): 7.90 seconds. 2 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. Errors found. CHKDSK cannot continue in read-only mode. C:\WINDOWS\system32> Looking at the Chkdsk logs it does strike me that the folders with the errors always seem to be the same ones. They are part of my mobile phone backup, mainly image files in folders at at - T:\Phone Backup\Backup\SM-G935F\SM-G935F_07762200581\SM-G935F_20240201191121\Photo\_EXTERNAL_\Archive Whether this is signifiant I don't know, perhaps the path length? Sorry I have to leave this for a few hours now. I'll be back!

@jaclaz Do we now think that this file system corruption when going between operating systems is an intrinsic problem? What I could do is to try temporarily connecting the disk in the enclosure directly to the motherboard, and make sue it's powered all the time that the system is on, so it will be just like it was a fixed internal drive. If I use it like that and see if the corruption still occurs, that should at least prove whether the problem is being caused by the connection via the card or not.

I've been trying other drivers on XP, with no success I'm afraid. The version 1.1.7.110 driver wouldn't install at all. If I run the setup, it runs briefly and then just closes, with no messages on screen. This might have been because there was already a later version of the driver installed. Version 3.2.0 was even worse, it apparently installed, but then there was a BSOD, MACHINE_CHECK_EXCEPTION. On reboot, the machine started OK, but nothing seemed to have changed. In Device Manager, the Asmedia card now showed driver version 3.2.0.0, but on inspecting the driver files it was still using asahci32.sys version 2.0.3.0001 as it was before. Trying another update from the INF file just produced a system freeze. I then tried reinstalling the original 2.0.4 driver. That said another stalled installation needed to be rolled back, which it did and the system froze again! It rebooted OK, and I then manually cleaned the registry of the previous driver installations and started from scratch again with the 2.0.4 driver, which then installed fine. I don't think I'll be trying that again! There was no evidence at all that version 1.1.7.110 was 98 compatible, in fact the INF file specifically says that it isn't, so I'm not even going to try!

This is what I have in my BIOS. The ROM Scan Ordering is set to 'Onboard First' as you can see. The other option is 'Addon First'. There doesn't seem to be an 'Option ROM Scan' option in my BIOS, but the BIOS options can change of course depending on the configuration of the machine, type of processor etc. I haven't tried changing the option. I did try as an experiment connecting the Blu-ray drive to the eSATA port on the other Silicon Image card in the machine, the one I used to connect the external disk enclosure to. To my surprise, it wasn't recognised at all, it was like it didn't exist! No sign of it in the BIOS still, and not in the XP Explorer or Disk Management. I didn't try in Windows 10, but I guess the result would have been the same. I tried updating the driver in XP using the one on the disk which came with the card. It went through the motions and then said 'Windows cannot open this program because it has been prevented by a software restriction policy.' I don't know what to do about that.

I own GTX 780 Ti, more than enough for me, but 3GB of memory seems on the low end, so better go with at least Titan 6GB.

Ok! I totally forgot that. Same happened to me with the most recent New Moon some days ago but only once. Therefore, I did not pay any further attention to it.

@roytam1Any site where it happens to report? Or under what circumstances happen that crashes? So far i do not experience any crashes here at all. Yep, I would be interested in more details, too. AFAICS, the most recent version of New Moon doesn't crash in my Windows XP system, either.

Linguistically a little curious, but if the function "define" is simply not defined, it still makes sense.

For installing unsigned web extensions in Serpent 52 and 55 (moebius! ) they have first to be compatible with these browsers. Deleting any files from the folder META-INF of a xpi file does not do anything, and is therefore no solution. Furthermore, only setting the preference xpinstall.signatures.required to false, which is already the default setting in Serpent, is no solution, either. To install such an unsigned web extension permanently (there is no META-INF folder in its archive, or it has been removed) in Serpent, the file manifest.json has to be modified to assign a unique ID to this extension. For testing purpose, I did that in the case of the web extension save-as-ebook 1.4.2 loaded from https://github.com/alexadam/save-as-ebook/tree/master/web-extension which lacks of such an ID in its file manifest.json. After assigning a unique ID to it, I packed the complete extension into a zip file and renamed it to save-as-ebook-1.4.2.xpi. If done, it can be installed then as usual, works as it should and also survives the next browser restart. Without enabling add-on debugging which would only result in a temporary loading of the web extension anyway! As a unique ID, I chose user-save-as-ebook@email.com. Here is a screenshot as a proof: Cheers, AstroSkipper

Glad you like my suggestion! The tools from Nirsoft are simply great, and this has been the case for many years. I used the tool MZCacheView in the past, and the path to the cache folder of the browser profile directory has to be adjusted there, too. Nirsoft offers such tools for all major browsers like Firefox, Chrome, Opera and the old IE.

And that has been the case since the very beginning!

That was me also. And I had to TEACH MYSELF how to trim XP to the basics. Therefore, yeah, you can also teach yourself to trim 10 to the basics.

Thank you very much for your advice @NotHereToPlayGames I very much appreciate that you care to help me.

Seems the "NoDarkTooltips" reg option is ignored by this new version.

Thanks for pointing out the errors. Line 56 was thus: Reg.exe add "HKLM\SOFTWARE\Classes\Python.File\Shell\editwithidle\shell\edit38-32\command" /ve /t REG_SZ /d "\"%ProgramFilest%\Python38\pythonw.exe\" -m idlelib \"%%L\" %%*" /f When it should have been: Reg.exe add "HKLM\SOFTWARE\Classes\Python.File\Shell\editwithidle\shell\edit38-32\command" /ve /t REG_SZ /d "\"%SystemDrive%\Python38\pythonw.exe\" -m idlelib \"%%L\" %%*" /f I shall re-upload Python 3.8.1350.7z with these corrections. I made the batch file by monitoring the changes made to the system by installing an official Python 3.8 distribution and saving the changes to the registry as a reg file which was then converted into a batch file using RegConvert. In the registry paths were not written as variables, so I had to convert them to variables in the batch file.

We surely need to work against that; any way we can.

Thanks to @Andalu I can now hopefully dispense with the Paragon GPT driver. I will do that and see if it makes any difference to the filesystem corruption issue.

Greetings ; what do you mean by "still" ? Was it working in UXP-based browsers and then stopped? How long ago was that? Have you already reported that breakage in the past and you now feel disgruntled the issue remains unresolved? Please be aware that UXP, as a platform, is not very good at supporting these so-called web (in-browser) editions of popular chat/messaging applications, which are usually optimised for recent Chromium-based browsers (or just for the browsers on your mobile device ) ... Such web-compat issues are usually for "upstream" (MCP) to address, but if one asks "there", the standard answer from "them" is: "Use the dedicated Windows application"; this is, of course, no consolation for XP/Vista users, because most of these apps now require at minimum Win7 (soon to be Win10 ?) ... Searching in the PMForums, someone there suggested using a "legacy" URI of the form: https://web.telegram.org/?legacy=1#/login , does it still work on you for log-in purposes? ... In my "dirty" St52 profile, all I get is a white/empty page inside a thin-lined black frame , much like what @mina7601 has already posted... It would appear the most important clue inside the Web Console simply eluded you ; the page deploys a script which performs browser-feature checks: https://web.telegram.org/a/compatTest.js UXP then fails those tests , because it doesn't, yet, support "Intl.DisplayNames", a JS feature which was first implemented in Fx-86/Ch-81: It just so happened that "upstream" (MCP) have opened a UXP issue for that just 6 days ago, but so far it hasn't received any activity ... A polyfill for that missing function already exists ; my JS-coding skills are non-existent , but I tried to make a userscript out of it (and inject it through Violentmonkey), problem being the script gets quite large when you add all the needed "locale.data" ... Another issue is that, during my tests, I discovered that for the userscript to work on "telegram.org", one has to globally disable CSP protection in the browser, which. in itself, is a security risk ... FWIW, with my basic "polyfill-as-userscript" and CSP (temporarily) disabled (security.csp.enable;false), the offending web page finally loads: I don't own a mobile device (yet anyway , by my government has other "plans" for its subordinates ), nor do I have an account with Telegram, so my experiments ended just there ... Kind regards.

So sorry, I hadn't picked up that, or if I did, I had forgotten about it! If it's likely to be the cause of the issue, I will certainly uninstall the Paragon driver. Where can I get the Win2003 files from? He may have been right, but I'm not quite ready to condemn the disk itself yet! Of course if this proves to be unresolvable, the disk would certainly be a prime suspect as the culprit.

OK, this is the result with chkdsk in read-only mode. Microsoft Windows [Version 10.0.19045.4046] (c) Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>chkdsk t: The type of the file system is NTFS. Volume label is BACKUP. WARNING! /F parameter not specified. Running CHKDSK in read-only mode. Stage 1: Examining basic file system structure ... Attribute record (80, "") from file record segment 14E0C is corrupt. Attribute record (80, "") from file record segment 14E11 is corrupt. Attribute record (80, "") from file record segment 14E13 is corrupt. Attribute record (80, "") from file record segment 14E18 is corrupt. Attribute record (80, "") from file record segment 14E19 is corrupt. Attribute record (80, "") from file record segment 14E1A is corrupt. Attribute record (80, "") from file record segment 14E1B is corrupt. Attribute record (80, "") from file record segment 14E6C is corrupt. Attribute record (80, "") from file record segment 14E70 is corrupt. Attribute record (80, "") from file record segment 14E76 is corrupt. Attribute record (80, "") from file record segment 14E78 is corrupt. Attribute record (80, "") from file record segment 14E7D is corrupt. Attribute record (A0, $I30) from file record segment 14E9E is corrupt. Attribute record (A0, $I30) from file record segment 14EFD is corrupt. Attribute record (A0, $I30) from file record segment 14EFE is corrupt. Attribute record (A0, $I30) from file record segment 14F05 is corrupt. Attribute record (A0, $I30) from file record segment 14F12 is corrupt. Attribute record (A0, $I30) from file record segment 14F21 is corrupt. Attribute record (A0, $I30) from file record segment 14F2E is corrupt. Attribute record (A0, $I30) from file record segment 14F48 is corrupt. Attribute record (A0, $I30) from file record segment 14F4B is corrupt. Attribute record (A0, $I30) from file record segment 15037 is corrupt. Attribute record (A0, $I30) from file record segment 15042 is corrupt. Attribute record (A0, $I30) from file record segment 15048 is corrupt. Attribute record (A0, $I30) from file record segment 1504F is corrupt. Attribute record (A0, $I30) from file record segment 15073 is corrupt. Attribute record (A0, $I30) from file record segment 15074 is corrupt. Attribute record (A0, $I30) from file record segment 15091 is corrupt. Attribute record (A0, $I30) from file record segment 150A8 is corrupt. Attribute record (A0, $I30) from file record segment 150C5 is corrupt. Attribute record (A0, $I30) from file record segment 150CF is corrupt. Attribute record (A0, $I30) from file record segment 150ED is corrupt. Attribute record (A0, $I30) from file record segment 150F5 is corrupt. Attribute record (A0, $I30) from file record segment 15107 is corrupt. Attribute record (A0, $I30) from file record segment 15108 is corrupt. Attribute record (A0, $I30) from file record segment 15134 is corrupt. Attribute record (A0, $I30) from file record segment 15142 is corrupt. Attribute record (A0, $I30) from file record segment 15168 is corrupt. Attribute record (A0, $I30) from file record segment 15199 is corrupt. Attribute record (A0, $I30) from file record segment 151D2 is corrupt. Attribute record (A0, $I30) from file record segment 151D3 is corrupt. Attribute record (A0, $I30) from file record segment 151EC is corrupt. Attribute record (A0, $I30) from file record segment 1521D is corrupt. Attribute record (A0, $I30) from file record segment 15272 is corrupt. Attribute record (A0, $I30) from file record segment 1A3BB is corrupt. Attribute record (A0, $I30) from file record segment 1A407 is corrupt. Attribute record (A0, $I30) from file record segment 1A429 is corrupt. Attribute record (A0, $I30) from file record segment 1A434 is corrupt. Attribute record (A0, $I30) from file record segment 1A435 is corrupt. Attribute record (80, "") from file record segment 1A781 is corrupt. Attribute record (80, "") from file record segment 1A791 is corrupt. Attribute record (80, "") from file record segment 1A7DD is corrupt. Attribute record (80, "") from file record segment 1A844 is corrupt. Attribute record (80, "") from file record segment 1A855 is corrupt. Attribute record (80, "") from file record segment 1A85F is corrupt. Attribute record (80, "") from file record segment 1A863 is corrupt. Attribute record (80, "") from file record segment 1A864 is corrupt. Attribute record (80, "") from file record segment 1A867 is corrupt. Attribute record (80, "") from file record segment 1A869 is corrupt. Attribute record (80, "") from file record segment 1A870 is corrupt. Attribute record (80, "") from file record segment 1A877 is corrupt. Attribute record (80, "") from file record segment 1A879 is corrupt. Attribute record (80, "") from file record segment 1A87B is corrupt. Attribute record (80, "") from file record segment 1A87E is corrupt. Attribute record (80, "") from file record segment 1A882 is corrupt. Attribute record (80, "") from file record segment 1A889 is corrupt. Attribute record (80, "") from file record segment 1A88A is corrupt. Attribute record (80, "") from file record segment 1A88B is corrupt. Attribute record (80, "") from file record segment 1A88D is corrupt. Attribute record (80, "") from file record segment 1A896 is corrupt. Attribute record (80, "") from file record segment 1A8A4 is corrupt. Attribute record (80, "") from file record segment 1A8A6 is corrupt. Attribute record (80, "") from file record segment 1A8B0 is corrupt. Attribute record (A0, $I30) from file record segment 1AA4D is corrupt. Attribute record (80, "") from file record segment 1AA5E is corrupt. Attribute record (80, "") from file record segment 1AA63 is corrupt. Attribute record (80, "") from file record segment 1AA81 is corrupt. Attribute record (80, "") from file record segment 1AA82 is corrupt. Attribute record (80, "") from file record segment 1AA83 is corrupt. Attribute record (80, "") from file record segment 1AA85 is corrupt. Attribute record (80, "") from file record segment 1AA86 is corrupt. Attribute record (80, "") from file record segment 1AA87 is corrupt. Attribute record (80, "") from file record segment 1AA88 is corrupt. Attribute record (80, "") from file record segment 1AA8A is corrupt. Attribute record (80, "") from file record segment 1AA8B is corrupt. Attribute record (80, "") from file record segment 1AA8C is corrupt. Attribute record (80, "") from file record segment 1AA8D is corrupt. Attribute record (80, "") from file record segment 1AA8E is corrupt. Attribute record (80, "") from file record segment 1AA8F is corrupt. Attribute record (80, "") from file record segment 1AA90 is corrupt. Attribute record (80, "") from file record segment 1AA91 is corrupt. Attribute record (80, "") from file record segment 1AA92 is corrupt. Attribute record (80, "") from file record segment 1AA93 is corrupt. Attribute record (80, "") from file record segment 1AA95 is corrupt. Attribute record (80, "") from file record segment 1AABA is corrupt. Attribute record (80, "") from file record segment 1AABC is corrupt. Attribute record (80, "") from file record segment 1AABE is corrupt. Attribute record (80, "") from file record segment 1AABF is corrupt. Attribute record (80, "") from file record segment 1AAC0 is corrupt. Attribute record (80, "") from file record segment 1AAC1 is corrupt. Attribute record (80, "") from file record segment 1AAC3 is corrupt. Attribute record (80, "") from file record segment 1AAC4 is corrupt. Attribute record (80, "") from file record segment 1AAC5 is corrupt. Attribute record (80, "") from file record segment 1AAC6 is corrupt. Attribute record (80, "") from file record segment 1AAC7 is corrupt. Attribute record (80, "") from file record segment 1AAC8 is corrupt. Attribute record (80, "") from file record segment 1AAC9 is corrupt. Attribute record (80, "") from file record segment 1AACA is corrupt. Attribute record (80, "") from file record segment 1AACB is corrupt. Attribute record (80, "") from file record segment 1AACC is corrupt. Attribute record (80, "") from file record segment 1AACD is corrupt. Attribute record (80, "") from file record segment 1AAD0 is corrupt. Attribute record (80, "") from file record segment 1AAD1 is corrupt. Attribute record (80, "") from file record segment 1AAD2 is corrupt. Attribute record (80, "") from file record segment 1AAD3 is corrupt. Attribute record (80, "") from file record segment 1AAD4 is corrupt. Attribute record (80, "") from file record segment 1AAD5 is corrupt. Attribute record (80, "") from file record segment 1AAD7 is corrupt. Attribute record (80, "") from file record segment 1AAD8 is corrupt. Attribute record (80, "") from file record segment 1AAD9 is corrupt. Attribute record (80, "") from file record segment 1AADA is corrupt. Attribute record (80, "") from file record segment 1AADB is corrupt. Attribute record (80, "") from file record segment 1AADC is corrupt. Attribute record (80, "") from file record segment 1AADD is corrupt. Attribute record (80, "") from file record segment 1AADE is corrupt. Attribute record (80, "") from file record segment 1AAE0 is corrupt. Attribute record (80, "") from file record segment 1AAE1 is corrupt. Attribute record (80, "") from file record segment 1AAE2 is corrupt. Attribute record (80, "") from file record segment 1AAE3 is corrupt. Attribute record (80, "") from file record segment 1AAE4 is corrupt. Attribute record (80, "") from file record segment 1AAE5 is corrupt. Attribute record (80, "") from file record segment 1AAE6 is corrupt. Attribute record (80, "") from file record segment 1AAE7 is corrupt. Attribute record (80, "") from file record segment 1AAE8 is corrupt. Attribute record (80, "") from file record segment 1AAE9 is corrupt. Attribute record (80, "") from file record segment 1AAEA is corrupt. Attribute record (80, "") from file record segment 1AAEB is corrupt. Attribute record (80, "") from file record segment 1AAEC is corrupt. Attribute record (80, "") from file record segment 1AAED is corrupt. Attribute record (80, "") from file record segment 1AAEE is corrupt. Attribute record (80, "") from file record segment 1AAEF is corrupt. Attribute record (80, "") from file record segment 1AAF0 is corrupt. Attribute record (80, "") from file record segment 1AAF1 is corrupt. Attribute record (80, "") from file record segment 1AAF2 is corrupt. Attribute record (80, "") from file record segment 1AAF3 is corrupt. Attribute record (80, "") from file record segment 1AAF4 is corrupt. Attribute record (80, "") from file record segment 1AAF5 is corrupt. Attribute record (80, "") from file record segment 1AAF6 is corrupt. Attribute record (80, "") from file record segment 1AAF7 is corrupt. Attribute record (80, "") from file record segment 1AAF8 is corrupt. Attribute record (80, "") from file record segment 1AAF9 is corrupt. Attribute record (80, "") from file record segment 1AAFA is corrupt. Attribute record (80, "") from file record segment 1AAFB is corrupt. Attribute record (80, "") from file record segment 1AAFC is corrupt. Attribute record (80, "") from file record segment 1AAFD is corrupt. Attribute record (80, "") from file record segment 1AAFE is corrupt. Attribute record (80, "") from file record segment 1AAFF is corrupt. Attribute record (80, "") from file record segment 1AB00 is corrupt. Attribute record (80, "") from file record segment 1AB01 is corrupt. Attribute record (80, "") from file record segment 1AB02 is corrupt. Attribute record (80, "") from file record segment 1AB03 is corrupt. Attribute record (80, "") from file record segment 1AB04 is corrupt. Attribute record (80, "") from file record segment 1AB05 is corrupt. Attribute record (80, "") from file record segment 1AB06 is corrupt. Attribute record (80, "") from file record segment 1AB07 is corrupt. Attribute record (80, "") from file record segment 1AB08 is corrupt. Attribute record (80, "") from file record segment 1AB09 is corrupt. Attribute record (80, "") from file record segment 1AB0A is corrupt. Attribute record (80, "") from file record segment 1AB0B is corrupt. Attribute record (80, "") from file record segment 1AB0C is corrupt. Attribute record (80, "") from file record segment 1AB0D is corrupt. Attribute record (80, "") from file record segment 1AB0E is corrupt. Attribute record (80, "") from file record segment 1AB0F is corrupt. Attribute record (80, "") from file record segment 1AB10 is corrupt. Attribute record (80, "") from file record segment 1AB11 is corrupt. Attribute record (80, "") from file record segment 1AB12 is corrupt. Attribute record (80, "") from file record segment 1AB13 is corrupt. Attribute record (80, "") from file record segment 1AB14 is corrupt. Attribute record (80, "") from file record segment 1AB15 is corrupt. Attribute record (80, "") from file record segment 1AB16 is corrupt. Attribute record (80, "") from file record segment 1AB17 is corrupt. Attribute record (80, "") from file record segment 1AB18 is corrupt. Attribute record (80, "") from file record segment 1AB19 is corrupt. Attribute record (80, "") from file record segment 1AB1A is corrupt. Attribute record (80, "") from file record segment 1AB1B is corrupt. Attribute record (80, "") from file record segment 1AB1C is corrupt. Attribute record (80, "") from file record segment 1AB1D is corrupt. Attribute record (80, "") from file record segment 1AB1E is corrupt. Attribute record (80, "") from file record segment 1AB1F is corrupt. Attribute record (80, "") from file record segment 1AB20 is corrupt. Attribute record (80, "") from file record segment 1AB21 is corrupt. Attribute record (80, "") from file record segment 1AB22 is corrupt. Attribute record (80, "") from file record segment 1AB23 is corrupt. Attribute record (80, "") from file record segment 1AB24 is corrupt. Attribute record (80, "") from file record segment 1AB25 is corrupt. Attribute record (80, "") from file record segment 1AB26 is corrupt. Attribute record (80, "") from file record segment 1AB40 is corrupt. Attribute record (80, "") from file record segment 1AB41 is corrupt. Attribute record (80, "") from file record segment 1AB42 is corrupt. Attribute record (80, "") from file record segment 1AB49 is corrupt. Attribute record (80, "") from file record segment 1AB64 is corrupt. Attribute record (80, "") from file record segment 1AB90 is corrupt. Attribute record (80, "") from file record segment 1AB9D is corrupt. Attribute record (80, "") from file record segment 1ABCB is corrupt. Attribute record (80, "") from file record segment 1ABCD is corrupt. Attribute record (80, "") from file record segment 1ABD2 is corrupt. Attribute record (80, "") from file record segment 1AC15 is corrupt. Attribute record (80, "") from file record segment 1ACAD is corrupt. 109824 file records processed. File verification completed. Phase duration (File record verification): 6.55 seconds. 2 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. Errors found. CHKDSK cannot continue in read-only mode. C:\WINDOWS\system32>

Oww, comeon, I was joking, as you well know it is the approach used on italian television to vote at (say) Ballando con le stelle or (still say) the Festival di Sanremo, but also at the Primarie del PD, Possible? Yes. Probable? No. jaclaz

@jaclaz @Andalu OK, I've now connected the 3TB drive directly to my motherboard. All seemed well in XP, the drive was there in Explorer, with the correct drive letter.. I did a backup to it, which apparently went fine. I then ran chkdsk on it, and all was fine. No sign of the drive being in use when I ran chkdsk this time BTW. I then booted into Windows 10, the drive was there, fine. Without doing anything, I ran chkdsk on the drive, and to my horror got this! CHKDSK.txt So I think that proves that the problem is nothing to do with the connection method! It appears that Window XP, with the Paragon GPT driver, is writing to the drive in such a way that it appears badly corrupted to Windows 10. Once again, chkdsk did not run automatically when I booted into Windows 10, which is in itself very strange as one of the fixed drives was obviously badly corrupted! The only reason I can think of to explain that is that the corruption only occurred after the system had finished booting, which surely isn't likely to be the case. If this can't be resolved, it's useless. I will now try the same thing the other way around!

Please don't blame yourself! It was a perfectly reasonable thing to do, to try other drivers to see if they made any difference to the issues. I'm really not at all sure why trying to install the 3.2.0 driver caused so much problem, it says quite specifically that it's XP compatible, and the installer certainly didn't say otherwise. What I should have probably done is completely uninstall the existing driver and clean the system of it before installing 3.2.0, rather than trying to install 3.2.0 over the top of it. I still don't understand why the driver on the disk that came with the card won't install because of a 'software restriction policy'. That is very puzzling. I did try changing that BIOS option BTW, but it seemed to make no difference to anything. I do think that the important thing now is to track down the cause of this file system corruption that I'm seeing when going between XP and 10. If that can't be explained, the whole thing is useless anyway, so there's no point in playing with different drivers and cards.

Hi again ; I can't see myself how that could've helped , because Fx-120.0 is incapable of running under NT 5.2 (Windows Server 2003 x86 ?); with the above UA, you're just "sticking out like a sore thumb" ; still, stranger things have happened in the world of IT... Also, if elektroda are adamant on supporting only the latest Mozilla Firefox version, pretty soon you'll have to spoof Fx-123.0 ... ... And you're most welcome ...

Thanks for the advice! No need (at least as of now), I live off my military pension, but it's quite enough (we have them high in France), I also have private contracts, but in that case it would be easier to just move to github then. Like win32 already did. Easy to add payment options, etc.

Yes, this is a new bug, sure this is to be fixed I have found and appllied several things to make browser faster, as i usually do examine newer firefox code.

Politics is forbidden of this website. I'm rather interested to read about Opera. Stop derailing.

Did you see this? https://www.techmesto.com/download-official-nokia-usb-drivers-for-windows-adb-fastboot-others/

Try you luck here! Type in your model, or better the device ID. https://driverscollection.com/

Am I safe on Brave 1.50.xx? It runs on Chromium 110.

Dakar Desert Rally v1.11.0 (Racing, Simulation) requires Windows 10/11

I's start with trying to set the full RGB mode. Perhaps something had messed up this setting when you reinstalled the driver.

I fail to understand why do they all patch only the standard chrome, not ungoogled.

Has anyone tried to open a RapidGator link in New Moon 28 the last months? The final captcha doesn't work anymore in the last releases. Doesn't matter which link is selected.

Never used it in an UXP browser! If I wanted to use such Google services, I would open them in a browser on my Android tablet. Google and Android is an endless love.

Maybe so, but it makes a good point! Since we're making "useless" posts today, I've noticed another, similar kind of post almost as much as those switch to Linux posts, and even had a CS instructor* go on about it: "throw out your old PC and buy a new one with Windows 10!" I do NOT see any point in throwing out a perfectly fine PC just because it's 4 years old, just to get a new one which that may not have the features I like, and probably won't run the software I want because Windows 10 won't run them (this, I admit, is rare-ish, but it happens). c *I went out of my way to run a Latitude D630 (from 2008) with Windows 2000 to make the point that one need not upgrade to the newest hardware and software to get things done (I did eventually upgrade it to XP, but the point was still valid because XP was only released one year later than 2000; because XP had such a long service life, it has become extremely mature and as a result, supports an unusually wide range of hardware (everything from the earliest Pentium Pros to at least Haswell, or Skylake and up with some ACPI patching and creative workarounds for some hardware that lacks XP drivers), and has at least some support for a lot of modern conveniences).

well peoples think "what you gonna do about it" and pay more to them instead of actually doing something like boycott companies until they change their way. Last Windows I paid was Windows 7 that I needed to have full paid retail version to my use or would not pass auditing. I currently got personal ban on Windows 8, 10 and 11 on my network and only use them work. If Microsoft changes their way of doing operating system I will be more than happy lift the ban but I doubt it . And before someone says Windows before it had issues too I am aware of them but at end they were solid and reliable products (Windows 3.x and 98FE as expections ) that made powerusing much easier. I am using linux if need new os which sadly seems to be going same path. System D as good example . Luckily Systemd free distros exist. Also cannot go linux full time on personal system since Windows games wont work, mix of package managers is hell etc so. no perfect soluction

well from my narrow perspective, as it is all business why make good OS/product when you can make crap, then sell it, then make it fancier and maybe tweak thing here and there, then sell as "better version" and then slowly introduce something that is in fact old but for their ecosystem is new (example with native PDF reading, MKV files, mounting virtual iso's) and again sell it as something revolutionary... etc... to me MS will only update drivers and hw support, but as OS itself it is waaay behind... but at the end its all money that counts... they stopped giving two bit s*** what ppl want/need long ago they get some exclusive right sales from US goverment most likely coz they bent over for free trojan insertions it just bleeds money money money

Thanks for the advice. My problem isn't really that there isn't a firewall solution for each of the many, many network-integrated applications I need to be able to run; it's that trying to keep up with the level of complexity has become practically impossible. With the level of constant change required to the firewall configuration to make things work, I can't really practically spend all day every day fooling with the config, I'm expected to get some work done. The base problem is that everything is just much more complex. Here's the thing: If I was actually able to get MORE work done than I did, say, back in 2013 or so, then I'd be able to more easily accept the additional complexity as a necessary evil. As it is, it's just more complex but doesn't really do more useful stuff. In fact, trying to do things "the new way" like edit a shared document in Word and dealing with practical problems like failure to save or loss of changes has proven again and again to become more error prone and ultimately costs more effort than just keeping one person in charge of the document and receiving submissions from others. Telesconferencing in the modern era seems to involve a lot of "we're not seeing your screen" or "we can't hear your video", even beyond the obvious issues like networking failure during meetings, etc. Even just that the tech has gotten more complex is problematic - I have to monitor 3 different chat features, have multiple calendars, am expected to keep up with eMail from 6 different inboxes, track my work in an online service, track expenses in a different online service, deal with health care, investments, payroll, etc. all online, many via browser, many not... Each of these functions embody essential communications, but they're not integrated nearly as well as they ought to be, and trying to figure out what servers to allow to get each to work is just not practical. -Noel

Following up on an earlier bit of conversation about what's improved... I actually HAVE found a few things - and they're not huge - that I do like better about Windows 10 than its predecessors... - Dark applications (such as File Explorer). MUCH easier on the eyes. - Seamless Bluetooth switching between e.g., speakers and headphones just by turning devices on/off. - All new hardware I've plugged in has just worked. I spent quite a while on the above list and could really only think of these three. A few ongoing frustrations: - An occasional 30 second stall when working with Explorer (e.g., sometimes when opening a context menu). - Now I have to have an application running that works around the cursor catching in corners; that used to be fixable via a registry tweak. - Loss of the ability to easily differentiate windows from one another on the desktop (Aero Glass and Big Muscle's tool are long gone). - SO many useless processes chewing up system resources just to have an empty desktop. - Desktop interactivity not improved in any practical sense even with much better hardware. - Microsoft trying to prevent me from managing my own system through sneaky permissions settings, "waas medic", scheduled tasks, etc. - More communications with more sites online, all the time, without clear benefit. Someone mentioned better multi-monitor support, and I guess things may be improving, but TBH having run multiple monitors since XP I'm not sure I agree things are all that much better. Once setup I don't change monitors though. I suppose things could be worse. And they could be better. -Noel

With Win 7, then with more effort with Win 8.1, I had developed a fully secure, private system setup that I managed with a deny-by-default firewall setup and a number of layers of atypical protection against malware. I was involved with every decision whether to allow an application to communicate online. With Win 10 I have been forced to give up the deny-by-default firewall setup. Nowadays, too many applications require too much complex network communication to make it practical to manage such a setup, and they keep changing! I have retained some of what I had set up before, but I don't feel nearly as secure, because I just am not able to keep on top of what talks to what. There is a real cost to having an extra 100 processes running. What's curious is that I'm not really doing any more work - I mean, back then I had Skype teleconferencing and eMail and web browsing and remote control over other systems, etc. on my Win 8.1 setup. It was initially a bit of a feat to get things like Skype - which is promiscuous as hell online - to work within constraints but I ultimately accomplished it. But now we have Teams and shared Office documents and Bluejeans and Zoom and 50 different ways to get those same things done that someone else requires in order for me to do my job. Because someone else thinks those things are important to be able to do. If anything the slightly less stable nature of the latest OSs cut into my productive time. I can never seem to print anything reliably any more. That never used to be a problem; now it is. The most useful things I do are still done the "old fashioned" way - developed right here locally on my computer system then shared later. Who thinks they're more productive while on a video call? Who isn't overloaded by all the inputs? But because everyone else seems to have swallowed the hype that "cloud apps are better" there's no getting away from it. It's a bit like walking quietly along a street to go to the store then being swept up by an overwhelming crowd of people headed to a riot. You end up being pushed and shoved to where you don't want to go, rather than reaching your intended destination, and you don't get to do what you wanted to do. You can't even remember what you wanted to do. And there is nothing you could have done to create a different outcome. -Noel

In Windows XP there is sometimes usefull, but most times annoying functionality - moving folder to screen edge a Desk Band toolbar is created with this folder's contents. The problem is - this changes workarea size and therefore (most of the time) this will cause explorer icons position (those that were in the way) to reset. This can get particulary annoying in VM - using Drag&Drop from Guest OS to Host OS, if mouse is released too soon. Solution: Windows Registry Editor Version 5.00 [-HKEY_CLASSES_ROOT\CLSID\{3CCF8A41-5C85-11d0-9796-00AA00B90ADF}] (Log Off or Close&Restart explorer is needed (L.CTRL+L.SHIFT+L.ALT + press Cancel on Shutdown dialog)) This will stop creation of Desk Band toolbar, and still allow user to use Language bar (both in TaskBar & on desktop), Quick Launch or other toolbars. To restore functionality, import back: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\CLSID\{3CCF8A41-5C85-11d0-9796-00AA00B90ADF}] @="Shell DeskBarApp" [HKEY_CLASSES_ROOT\CLSID\{3CCF8A41-5C85-11d0-9796-00AA00B90ADF}\InProcServer32] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,62,00,72,00,\ 6f,00,77,00,73,00,65,00,75,00,69,00,2e,00,64,00,6c,00,6c,00,00,00 "ThreadingModel"="Apartment" ----------------- Before I found it, I used this one, but, while this disables creation of Desk Band toolbar, problem is (from the name of it) it also prohibit user of closing other toolbars [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer] "NoCloseDragDropBands"=dword:00000001