All Activity

Hi, is it possible to have a checkbox added to NOT check for updates? I'm on a managed company laptop now and I get a notification so does IT every time SAB tries to check for updates. I did rename the update file, but I don't unnecessarily want to manipulate the program executables. Thanks for being the only software that does not require elevated access to install and manipulate the Win11 charade.

VIA VT1708B 8-ch @ nVIDIA MCP78 Driver installed and loaded, but I got only errors on any device access (like general error). WDM audio stack is working (I tested USB audio device).

Welp,it worked fine for me...i don't get why it doesn't work for you...

I should build out a DeviceIOControl interface so I can send codec verbs and dump the codec state from a user-mode program and don't need to rely on the kernel debugger. Will get to that when I have time. It's busy around the holidays.

There isn't supposed to be. A true "portable" will *NOT* be associated. If you want the association, you should probably be using the "regular" version instead of the "portable" version. "Portable" versions are generally for people that do *NOT* want the file associations. Your list does *NOT* narrow things down for me, they all do not create the "bin" / "profile" the same way. But if you do not have any issues running the program THEN opening a .pdf, then your "bin" / "profile" SHOULD be okay (ie, not corrupted). Again, if you want OS-Level ASSOCIATIONS, you technically shouldn't be using the PORTABLE version. Because there are "mime types" and GUIDS and CLSIDS and ProgIds and namespaces and file PATHS and other things to also "associate" above-and-beyond a simple "OpenWithList". ie, things that over-simplified "registry cleaners" would have wiped clean and all you are trying to bring back is the "OpenWithList" - won't *always* be enough (sometimes it is).

You can check if it's active with `vivetool /query /id:41356296`, and similarly, you can disable it with `vivetool /disable /id:41356296`. My problem seems to be fixed; I need a little more time to confirm.

Take your pic (my version is a older one that works fine) https://www.softpedia.com/get/Office-tools/PDF/PDF-XChange-Editor-Portable.shtml https://portableapps.com/apps/office/pdf-xchange-editor-portable https://www.portablefreeware.com/index.php?id=2832 https://www.fcportables.com/pdf-xchange-portable/ I have no problem running the portable application, then opening a .pdf file within it. There is no 'default' for .pdf files that I ever saw. I looked at that Registry key with file associations and the .pdf is assigned to PDF x extension ok.

Not sure on Win7, but never trust an Uptime claim on Win10. Why? Because you can "hibernate" and then leave the computer in the attic for DECADES. Then launch it DECADES later and the "uptime" will SAY it has been "up" for that ENTIRE time.

Do you have a link of where you obtained PDF-Xchange?

I'm down to one active computer using Windows 7, the one I am posting from. I do all of my daily driving with it and every site I need to use still works. My old Win7 is still connected but it stays off most of the time. That computer was the one that used to be my daily up until the end of June and was the one that I had posted about in the Uptime and HD Reliability threads.

I don't know if a 'Portable' application can be 're-launched. I don't know how to do that, if there is one.

That seems to be related to A/B switch 41356296. Check if it's enabled with vivetool

I have an FM Transmitter that I've modified to "jam" any radio within 50 feet. Overrides a local FM radio station and plays DEAD SILENCE instead. Not sure if I'm breaking any FCC rules or not. BUT it is a GODSEND for my SANITY! Why? Because I do not (and will not!) listen to COUNTRY MUSIC !!! :)

The same thing happens to me too

My ancient version of Kaspersky under Windows 10 My ancient version of Kaspersky installs, runs and works fine under WinXP. During the installation under WinXP I have de-selected the "Protection Components", I don't need them. Under Windows 10, however, immediately after clicking on the installer of the workstation edition of My ancient version of Kaspersky, the following message comes up: "Program Compatibility Assistant. This app can't run on this device Kaspersky Anti-Virus xxx This app can't run because it causes security or performance issues on Windows. A new version may be available. Check with your software provider for an updated version that runs on this version of Windows." The Program Compatibility Assistant of Windows 10 prevents the start of the installation of the workstation edition of My ancient version of Kaspersky under Windows 10. This blocking of the installation under Windows 10 by the MS Program Compatibility Assistant corroborates the BSI warning in the posting by AstroSkipper. The small print of the BSI warning of 15Mar2022 in the link by AstroSkipper indicates a possible non-technical motivation: "Im Kontext des Krieges, den Russland gegen die Ukraine führt, könnte ein russischer IT-Hersteller selbst offensive Operationen durchführen". [translation from German: "In the context of the war by Russia against Ukraine, it could be possible that a Russian information technology manufacturer could engage on their own in offensive operations"] I strongly doubt that the testing by the German BSI in 2022 included My ancient version of Kaspersky under Window XP (EOL of WinXP was 2014-2019). My ancient version of Kaspersky installs, runs and works fine with all versions of Windows from Windows 2000 thru Windows 7/Windows Server 2008, without being blocked by The MS Program Compatibility Assistant, they are listed in the User Guide as system requirements. The Program Compatibility Assistant was introduced with Windows Vista. The first posting I have found about Kaspersky being blocked by the MS Program Compatibility Assistant was of 10May2022 [the Russian invasion of Ukraine was on 24Feb2022] https://malwaretips.com/threads/problem-installing-kaspersky-anti-ransomware-tool.113730/ So the workstation edition of My ancient version of Kaspersky cannot be installed under windows 10. But hold it, there is another, little-known edition of My ancient version of Kaspersky. It is a specced-down workstation edition for virus-checking, without the "Protection Components". This edition is NOT blocked under Windows 10 by the Program Compatibility Assistant, i.e. it looks OK to the MS Program Compatibility Assistant. It installs, runs and works OK under Windows XP and Windows 10. The screenshot above shows this specced-down edition running OK under Windows 10. My ancient version of Kaspersky pre-dates Windows 10, and displays the Windows 10 operating system as "Microsoft Windows NT 6.2 x64 Edition (build 9200)". Screenshots above: This specced-down edition of My ancient version of Kaspersky updates OK under Windows 10. Comparing the specced-down edition under Windows 10 vs the normal workstation edition under WinXP 1) I made a virus check of "My personal in the Wild", a collection of 100 infected files from eMule, with the specced-down edition under Win10 and with the normal workstation edition under WinXP. Both test scans flagged the same number of infected files, so both the specced-down and the normal workstation versions are equally useful for virus-checking. Above: Scan result with the normal workstation edition under Windows XP SP3 Above: Scan result with the specced-down workstation edition under Windows 10 SUMMARY: Viruses. malware etc get flagged OK by both editions, under Windows XP and under Windows 10. The specced-down edition doesNOT get blocked by the MS Program Compatibility Assistant under Windows 10. 2) I also made another test-scan with the two editions under Windows 10 and Windows XP, this time with a set of clean, not-infected files (184 files, altogether 64GB). Above: Scan results of the set containing only clean files, with the normal workstation edition under Windows XP. Above: Scan results of the set containing only clean files, with the specced-down edition under Windows 10 The specced-down edition under Windows 10 produced four "processing error" messages, probably because of some incompatibility with Windows 10, but virus-checking continued uninterrupted, as usual. I would speculate that these processing error messages will not occur when the specced-down edition is run under WinXP. Virus-checking of clean files with the specced-down edition is more efficient (808,744 files scanned vs 1,105,804 files), reducing the scan-time substantially (1:14hrs vs 2:29hrs). The screenshots made under Windows 10 have a white title bar, while the screenshots made under Windows XP have a blue title bar. The above tests under Windows 10 and Windows XP were made on the same computer, which was set up for multi-booting into various operating systems. The specced-down edition seems to have fast virus-checking as objective. The Settings window of the specced-down edition, in contrast to the normal workstation edition, doesnot display a check-box for the selection/de-selection of the "iSwift" setting, which is a setting to speed up virus-checking on NTFS partitions. I manually changed three instances of the value "UseIStreams" in the KasperskyLab key in the Windows 10 registry in order to set "iSwift" to "off" for most of the checking by the specced-down edition under Windows 10, which is my preferred setting. Under WinXP I prefer the normal to the specced-down workstation edition, mainly because the normal version has worked fine for the past 10+ years.

It's not that bad, IF you tweak the CRAP out of it! I strongly (strongly!) suggest learning how / teaching yourself how to create installation media that removes the CRAP *BEFORE* the install! Do not (do not!) install FIRST then remove the crap LATER. You GOTTA remove the crap FIRST. There are some very good "scripts" (PowerShell) that make "decent" attempts at removing AFTER-THE-FACT (install first, remove later), but you really are BETTER-SERVED in not allowing the bloat to be installed in the first place. Install first then remove later method always (always!) leaves a "tangled mess" of a Windows Registry behind. For your radio station needs, I suspect that Win10 *1511* is really all that you need. I currently stick with *1607* and *21H2* the best I can (hardware-dependent). Good Luck! Don't "fear" Win10. Fear the BLOAT of "standard user, default installs", but don't fear The De-Bloated Advanced-User. Oh, last but not least, do not (do not!) save yourself legwork by using anything called "tiny" or "lite" or the names creatively change more than the underlying "debloatifying". Just trust me, you will NOT be satisfied unless YOU do the legwork. But do be warned, there *IS* a "learning curve". But I have no doubt whatsoever that you are smart enough to take on the task.

Hi! It's been awhile since I posted here! I'm mainly using Mac OS nowadays, but I still maintain a Windows 7 VM, and I have a Dell OptiPlex 7050 running Windows 7 Professional that I use for playlist automation (I run a small, unlicensed AM radio station; the neat part is that it's not illegal: look up Title 47, CFR Part 15, Subsection C, § 15.219 of the FCC rules). So, despite it being over 16 years old now and EOS since 2020, it's still perfectly usable and secure enough to at least get done what I'm trying to do, as you can see here: I had an earlier version of this running on XP, but unfortunately, it got too old to run the versions of the above apps I wanted (clockwise from top left: Butt, PlayIt! Live, Stereo Tool). 7 is still in that sweet spot where current versions of these things are still supported, so I'm going to use it while I still can (that said, I'm planning for an eventual upgrade to (ugh!) Windows 10 because, unfortunately, the fun doesn't last forever, and there's no Mac or Linux version of PlayIt! Live). Here's to keeping Windows 7 alive, one PC at a time! c

I would certainly recommend that over any "AI-generated" list! We are YEARS away from "AI" being a trusted and reputable source! In my not-so-humble opinion. AI, for now, is nothing but "Junk in, junk out". I get some reasonably good STARTING POINT javascript code from AI, but it is NEVER perfect or good-to-go without HUMAN intervention.

https://github.com/e3kskoy7wqk/Chromium-for-windows-7-REWORK/issues/7

If noone has cataloged them, then I probably have to go through them one by one.

It's excuse for alpha version but not for beta or release. As the [WDMPNPB003_Device.FactDef] section and other sections in HDA.inf too. Two controls (low and high "something", I don't remember exact names) are definitely visible and, yes, do nothing. P.S. Realtek ALC887 @ Intel Comet Point-V PCH (Intel Core gen 10 Desktop Motherboard) CSM does exactly the same job as at my notebook - all PCI devices on IRQ11. Version 11 of drivers set up without problems. Situation is exactly the same as MERCURY127 have - digital part of driver definitely works as expected but no analog sound. >low and high "something" Low and High Frequencies, I suppose (I have localized Windows).

Well, yes. I am also aware of the collections you uploaded to archive.org. But I was hoping that someone has cataloged the updates to know what's inside. It's still a long way from the state of having links to updates to the state of knowing which updates contain versions of win32k.sys. However, knowing the links is the first step. I have cataloged more than 400 Windows 2000 updates, but nearly no Windows XP updates.

You should go to this link. There will be a txt file containing: Links to all Microsoft files uploaded directly to the MS Catalog. In all languages. So you can find all the files you need. https://msfn.org/board/topic/182599-nt-5x-windows-update-urls-dump-inc-custom-support-updates/

Hello, as you are probably aware, Windows has problems with long paths (total length > 260 characters). --- In old Windows versions there is the "\\?\"-trick, which helps in a few situations: --- Starting with Windows 10, it is possible to allow specific applications to use longer paths. According to the documentation, Microsoft modified specific functions of the API to allow using longer paths for specific applications in Windows 10. So the list of functions is rather interesting. And here it is: CopyFileW CopyFile2 CopyFileExW CreateDirectoryW CreateDirectoryExW CreateFileW CreateFile2 CreateHardLinkW CreateSymbolicLinkW DeleteFileW FindFirstFileNameW FindFirstFileW FindFirstFileExW FindFirstStreamW FindNextFileNameW FindNextFileW FindNextStreamW GetCompressedFileSizeW GetCurrentDirectoryW GetFileAttributesW GetFileAttributesExW GetFinalPathNameByHandleW SetFileAttributesW GetFullPathNameW GetLongPathNameW MoveFileW MoveFileExW MoveFileWithProgressW RemoveDirectoryW ReplaceFileW SearchPathW SetCurrentDirectoryW --- Is anyone aware of any pioneer work that has been done to improve the situation with Windows versions older than Windows 10?

I've been having this for a while too with the entire Action Center/Quick Actions menu, it'll work on boot and then at some point it'll just stop showing up and no hotkeys like Win+P work until I kill explorer.exe 1-2 times. This is on latest 25H2 update with 3.9.20 of SAB as well.