Leaderboard

... OK @Dave-H, I think I have solved this difficult riddle of yours, so I'd kindly ask for "preferential treatment" for the rest of the year ; joking aside, I bet you 100 quid you have toggled the following pref chrome://flags/#enable-experimental-web-platform-features to "Enabled", to squeeze more out of the old Chromium 86 JS+CSS engine, have you not? On an epiphany (pun intended, it's already Jan 6th here), I remembered a discussion inside the Supermium issue tracker, where Client Hints was the topic... The aforementioned pref, in versions of Chrome ranging in the mid-to-late 80s, enables an alpha/gestational form of the CH API, which was only finalised in the early-to-mid 90s (and sometime after Cr87 it was put behind its own flag, decoupled from experimental-web-platform-features) ... If you visit https://browserleaks.com/client-hints do you get under "Client Hints JavaScript API: API Support" -> True ? If yes, that's the origin of your VM issue; I can replicate your 360EEv13.5 VM issue myself if I do enable that pref ("Disabled" in a fresh/default profile), please see below: The behaviour you're experiencing is caused by Violentmonkey (and Tampermonkey ?) code but in defence of the VM maintainers, they couldn't possibly author code to cover ALL cases of users messing with the "you're-not-supposed-to-touch" Chrome's "Experiments", aka "chrome://flags/"; more so, when they're currently supporting Cr 61-131 (and each of those has its own, unique, set of "Experiments") ... Technical stuff: The culprit commit is the one below: https://github.com/violentmonkey/violentmonkey/commit/d2dda25d91e3718e5b20ba4648e82baf730e6178 from May 2024; this one assumes the browser comes equipped with the final iteration of the Client Hints API, which isn't true for Cr86/87; no CH API (the default in Cr86/87) doesn't break VM >= 2.19.1, but a draft/RC CH API does ... Mitigations: If you want to install and use the latest version of VM in 360EEv13.x (Cr86), you'd have to a) disable/never enable "chrome://flags/#enable-experimental-web-platform-features"; this will reduce, somewhat, web compatibility with certain sites that expect recent Chromium-based web engines... b) if you opt to enable "chrome://flags/#enable-experimental-web-platform-features" for webcompat purposes, then you should disable Cr86's draft CH API via the cmdline switch: " --disable-features=UserAgentClientHint" (e.g., add that to loader's "Parameters"); some recent websites which rely on sniffing UA CHs may break... If the website of interest remains functional ONLY when detecting some Client Hints (e.g., some sites "take you for a bot" and outright block you when no CHs are sent), then you'd have to enable "chrome://flags/#enable-experimental-web-platform-features" in 360EEv13.x but opt for an older version of VM, one < 2.19.1 (crx4chrome should afford those...). Well, that's it ; detective work concluded successfully: case filed! Best wishes ...

Hi, I do a lot of search for a new tower for any motherboard, that has the Hot Plug (hot swap) possibility for a 3.5 HD. The Corsair 800D and 900D have it, but only the 800D at its front side. To integrate a Hot Plug case into the tower as the 900D did, is for me without any sense. And I do not want any screws, as the Server Tower Supermicro SC745 // CSE-745 has. Crazy search without any success. Modern tower even dont have any 5.25 slots because of no optical drive. But then I come to the idea to use such a tower with a free 5.25 slot. Waaooh.., her it is: Icy Dock MB795SP-B Speicherlaufwerksgehäuse 2.5/3.5" HDD / SSD-Gehäuse Schwarz (MB795SP-B). It sits in a 5.25 case, has place for a 2.5 and a 3.5 Sata harddisk. AND you can switch them off individually, without disconnecting. They have one power connection, but both Sata connectors are separate. So it is just connected as a normal Sata harddrive. This is near to an ideal solution for me, tell me your thoughts and experiance Dietmar "MB795SP-B"

I once had a similar device, but had to add a very thin, flat air ventilator for the cooling, Oh, and for XP. 1) "Optimize for Quick Removal - This setting disables write caching on the disk and in Windows, so you can disconnect this device without using the Safe Removal icon" 2) "Optimize for performance - This setting enables write caching in Windows to improve disk performance. To disconnect this device from the computer, click the 'Safely Remove Hardware' icon in the taskbar notification area". https://forums.tomshardware.com/threads/hot-swapping-a-sata-drive-in-windows-2000-and-xp.1097903/

Dietmar, that device isn't locked to any specific OS, Anything starting Vista would do just fine. Bear in mind, the temps might get hot there with any HDD above 6TB, or even 4TB,

@Mark-XP After a really loong search I buy this PC Tower new SilverStone SETA D1 It has 4x 5.25 slot extern and a lot of possibilities to change all the cases for HD etc. Dietmar

Mylene Farmer 2003 Remixes, also in 24bit. Yes, I do listen to pop sometimes.

Mike Oldfield's 1984 The Killing Fields (Original Motion Picture Soundtrack) remastered in 2016, with 24bit depth.

... First do as instructed: If you're using one of the "portable" (with X-Loader) distributions, it's quite easy to back-up your current profile (dir "USER DATA") and restore it when testing is over; also back-up your loader config file (360Loader.ini), if custom-modified, and use the stock version for testing; on the fresh profile, install just VM (stable or BETA), install some userscripts and test their correct functioning; if they do work as designed, then your predicament in your dirty profile is due to a) a custom browser setting, b) a custom chrome://flags/, c) a custom cmdline switch defined inside 360Loader.ini (under "Parameters"), d) an interaction with one of the rest of the installed extensions, e) something else I can't think off-the-top-of-my-head ... Almost all Web Extensions targeting Google Chrome will have to migrate, eventually, to MV3, which by itself requires Chrome 88+, and this is just for the simplest of extensions; many require even higher Chrome versions, because the needed MV3 APIs were introduced well after v88... Violentmonkey will also have to migrate, there's an open GH issue about it: https://github.com/violentmonkey/violentmonkey/issues/1934 Thus, if you need to keep using 360EEv13.x, you'd have to freeze extensions to their last MV2 iteration... PS: I inadvertently submitted this post before its conclusion, so your copy delivered through e-mail notification will have ended abruptly; apologies ...

Yep, that's the one. I keep it at the HIGH preset ALL OF THE TIME. I'm too old to have to turn up the volume to hear the normal scenes then get BLASTED TO H#LL with LOUD VOLUMES during action scenes.

From what we all see on numerous forums/posts, Seagate is/was always in the lead of all failures, be it their build quality, firmware, poor warranty or anything else. The question is, why even bother buying them? This information is all over the internet for many decades.

I never understood those people who continued to use non-80s-made drivers when their health drops below 100%.

Powering it down is also not advisable, since it can just never spin up again. In such cases I usually flip those poor dying b*stards in an attempt to spin them up. Some models do spin up when placed upside down, make it very gently, while they're powered on.

No videocard?

Hiya to you on behalf of the Community.

One of the most notorious fingerprints Supermium has, it's the "version 99" tag, whereas all normal chromes have 24, https://github.com/win32ss/supermium/issues/1101

Then, why ask?

F.R. David 1982 Words