Leaderboard

StartAllBack 3.8 is a major update with fully recreated taskbar. It will be necessary for August 24H2/23H2 update. It's like 70% new app. It's free update and it's buggy and it's your fault for not testing!

Blur, blur, blur, even in VR. "r/assettocorsa on Reddit: VR quality looks grainy/blurry" "The headset works fine. But this game looks grainy and blurry in the distance. I have MSAA on 4x sometimes 8x" https://www.reddit.com/r/assettocorsa/comments/njdz13/vr_quality_looks_grainyblurry/

Funny to see how people who read the propaganda from developers encounter MSAA in real life, but still can't understand what's wrong. "anti aliasing Looks like blurry garbage :: Red Dead Redemption 2" "TAA and FXAA just blurs the game and MSAA is just broken" https://steamcommunity.com/app/1174180/discussions/0/1750142311549097531/

is doomed to be a troublemaker due to the heightened "security" measures against modded drivers and older games copy protections,

First thanks! And now just for clarification, I am not the creator of ProxHTTPSProxy. But I am the creator of the package ProxHTTPSProxy's PopMenu TLS 1.3 3V3. And as you can see inside the name of this package, it is based on a TLS 1.3 proxy since 2022. Unfortunately, the rest of your comment does not match our recent discussion about the tool WSUS Offline Update and how one can get Office 2007 updates today. To be honest, I don't understand at all what your comment here is actually referring to.

Did you replace the wsusscn2.cab file by an older one which is dated short after the EoS of Office 2007 in 2017 in the way I described in my previous posts? I checked this method, and it works. Even under Windows XP. No 2529 updates but 580 related to Office 2007 ofc glb. For me, the wsusscn2.cab file from 12.02.2019 also worked fine. In any case, the most current wsusscn2.cab files do not properly work at all. Too much files are downloaded which are not related to Office 2007. I have the impression that you haven't read my posts properly. The proof that my method works is the download log I provided in this post: https://msfn.org/board/topic/181623-updates-office-2007/?do=findComment&comment=1270043 Try, for example, this one from 29.01.2019: https://web.archive.org/web/20190129233558/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab or this one from 05.10.2017: https://web.archive.org/web/20171005192358/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab

At the moment, I am performing a download of all Office 2007 updates under Windows XP to check my theory. It seems to work as I planned. I inserted the pause command into the script and was able to replace the wsusscn2.cab file by a version from 12.02.2019 at the right time. Sorry, but I can't confirm your statement. I haven't got such errors. The files which were generated in the temp folder could be accessed and processed correctly. This doesn't seem a problem related to WSUS Offline Update 9.2.6 but rather to your system or whatever else. In any case, I got a valid UpdateTable-ofc-glb.csv file, and the download started successfully. When all has been finished, I'll post the download log.

@Cixert Another idea I have is to pause the script directly (very important!!!) after the download of the wsusscn2.cab file to replace it by an older version of this file. I would do that with the pause command inside the script. Doing so, this could reduce the download of unwanted files and maybe offer links that no longer exist in the most recent wsusscn2.cab file which has been automatically downloaded by the script. However, this is only a theory. I haven't tested it yet.

Didn't you create an archive for Office 2003 and/or 2007 back then? I never had Office 2003, but Office 2007. Years ago, I downloaded all updates for Office 2007 with WSUS Offline Update (logically with an older version), but of course only for the German version. Therefore, I think that won't help you. But in any case, depending on the OS you are targeting, you should set exclusions to reduce the download of unwanted files. For Office, it is the file ExcludeList-ofc.txt in the exclude folder.

To prevent any possible interventions insinuating something about my alleged bad sight, just a couple of links from most popular games with these new techniques. "Why does MSAA in Assassin's Creed IV blur the image? - Reddit" https://www.reddit.com/r/nvidia/comments/5efoaj/why_does_msaa_in_assassins_creed_iv_blur_the_image/ "New Anti-Aliasing options are blurry. - CD PROJEKT RED" https://forums.cdprojektred.com/index.php?threads/new-anti-aliasing-options-are-blurry.11111398/

MSAA and SGSSAA look blurry, and there are a lot of posts all over the internet regarding this. Which is your screen resolution? If you don't notice, 1080p most likely, but then again, for me it's noticeable even on a 1200p monitor.

Overall agree, but 900 series lack CSAA, which is a must have for old games.

https://startallback.com/download.php?v=3.7.11

Yessaaaa I succeed to start XP SP3 on this HP Omen Notebook ax009ng. The idea, to use an external XP from my Asrock z370 k6, where I install "wrong" the GTX 960M was the breaktrough. Lan so Internet, sound, USB2,3, Cam, all works. The driver for the 960M just now not started, I think because until now all is in "Standard PC", means no acpi at all. But it can also be a more serious problem. The driver for the GTX 960M (mobile) for XP SP3 from Nvidia is there, but who knows, if it works on all notebooks. Dietmar PS: Acpi will come, but this will be a hard fight with the Acpi tables DSDT, SSDT..

Updating to 3.8.0 brought all the shortcuts fixed to the taskbar in monitor 1 to the second monitor (img 01)... and I can't get rid of them anymore!!! Them I downgraded and now it's working (imag 02) how it should be… Please, fix it!

Yes it's very safe, you should have no problems with it. I use it on 23H2 and it works normally. Yet some of the tools that were working with legacy tasbkar before do not work anymore, like 7+ Taskbar Tweaker.

Maybe, this one is already too new. Try one of the versions I linked to! Start with the version from 29.01.2019! You can't manually pause the script as you will never match the right time. WSUS Offline Update actually starts extracting the wsusscn2.cab file immediately after downloading it. Pausing must be carried out in the script using the Pause command. Apart from that, the older version of the wsusscn2.cab file must be inserted several times. With each extraction process, WSUS Offline Update checks whether it is still up-to-date. If not, it downloads the latest version again, which we can't avoid at this point. Otherwise you would have to completely adapt the script for downloading older Office products, which I will not do, of course. Therefore, the Pause command must be placed in the correct position in the DownloadUpdates.cmd script. I have inserted the following in line 978, right before the extracting of Microsoft's update catalog file package.xml: echo The script has paused. Now, you can manually replace the file wsusscn2.cab by an older one. When done, press a key to continue! pause Each time this message is displayed, the wsusscn2.cab file must be replaced. And don't forget to also modify the CreateISOImage.cmd script, as described in one of my previous posts! A positive side effect of the Pause command is of course that you can simply leave the script running unattended and just insert the file and press a key from time to time, no matter when. If none of this works for you again, you're probably doing something wrong. Because it was tested by me and definitely works here.

New weird crash: I've been opening several .ods (LibreOffice Calc) files from FAR Manager (Shift+Enter on the file, which opens the file in default application, in my case LibreOffice 7.5.3.2); every now and then Explorer crashes: explorer.exe caused an Access Violation at location 00007FFCC4A51878 in module StartAllBackX64.dll Reading from location 0000000000000018. AddrPC Params 00007FFCC4A51878 0000000000000000 000000000413F060 0000000003A701E0 StartAllBackX64.dll!LoadSVG+0x11838 00007FFCC4A48A81 0000000003A701E0 0000000003A4A890 0000000003AA0670 StartAllBackX64.dll!LoadSVG+0x8a41 00007FFCC4A46836 0000000000000000 00000000039B8EB0 00000000000C0A5A StartAllBackX64.dll!LoadSVG+0x67f6 00007FFCC4A32890 0000000000000000 0000000000000000 0000000080000022 StartAllBackX64.dll!PickGlyphDlg+0x17614 00007FFCCE2C89A1 00000000000C0A5A 00007FFCC4A32800 00000000000C0A5A user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFCCE2C81EB 0000000000000001 0000000003A701E0 000000000413F5E4 user32.dll!CallWindowProcW+0x8b 00007FFCB34A8252 0000000000000001 00000000086E0200 00000000000C0A5A comctl32.dll!CallNextSubclassProc+0xb2 00007FFCB34A8178 0000000003A701E0 0000000000000000 000000000000044A comctl32.dll!DefSubclassProc+0x88 00007FFCC67D6149 0000000001794AA0 00007FFCCED16B17 0000D83807A955ED DarkMagicX64.dll!0x6149 00007FFCB34A8252 0000000000000001 0000000000000000 00000000000C0A5A comctl32.dll!CallNextSubclassProc+0xb2 00007FFCB34A8037 0000000000060438 0000000000000000 0000000000000000 comctl32.dll!MasterSubclassProc+0xa7 00007FFCCE2C89A1 00000000000C0A5A 00007FFCB34A7F90 00000000000C0A5A user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFCCE2C81EB 0000000000000000 0000000003A701E0 0000000000000000 user32.dll!CallWindowProcW+0x8b 00007FFCC4A7C284 0000000000000000 0000000000000000 000000000413FAB9 StartAllBackX64.dll!DllGetClassObject+0x18a4 00007FFCCE2C89A1 0000000000000000 00007FFCC4A7BEF8 00000000000C0A5A user32.dll!UserCallWinProcCheckWow+0x2d1 00007FFCCE2C8461 000000000413FA58 0000000000000000 00007FF6DCF8F3E0 user32.dll!DispatchMessageWorker+0x1f1 00007FF6DCBDA34F 0000F1B750FD56D5 00000000037E0A70 000000000000282A explorer.exe!CTray::_MessageLoop+0x1af 00007FF6DCBDA110 0000000000000000 00000000037E0A70 000000000000282A explorer.exe!CTray::MainThreadProc+0x60 00007FFCCCA560DD 0000000000000001 00000000037E0A70 0000000000000000 shcore.dll!_WrapperThreadProc+0x11d 00007FFCCE5D257D 0000000000000000 0000000000000000 0000000000000000 KERNEL32.DLL!BaseThreadInitThunk+0x1d 00007FFCCED4AF28 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!RtlUserThreadStart+0x28 StartAllBack 3.8, Windows 11 23H2 22631.3380

No. Please try to unlock the taskbar before attempting to add/remove toolbars.

Source, please.

These files are only temporarily generated for further processing to get a final csv list of updates which is then saved inside the corresponding folder of WSUS Offline Update and whose links have to be downloaded in the end. For example, the UpdateTable-ofc-glb.csv file I already mentioned. After processing, these files are immediately removed from the temp folder. The temp folder is, so to speak, the working directory of WSUS Offline Update when the links to be loaded are extracted from the wsusscn2.cab file.

Off-topic posts removed.

Here is a part of my log in terms of ofc glb with a download of 580 files in the folder client\ofc\glb (only 3 files less downloaded than in 2019): q.e.d The updates whose download failed can be downloaded from external sources and as previously described added before creating the iso image. Cheers, AstroSkipper

I own a GTX Titan X (Top Maxwell card), the iconic Spellforce series doesn't support MSAA, and with CSAA it would've looked fantastic, I know this because I also own a 780Ti. Old games don't need VRAM economy. The OP wanted to run vry old games (securom protected), so we can safely assume his games are approx. up to 2006-2007.

Yep. And thanks! Reviving, modifying and fixing programmes that no longer work properly is one of my favorite things to do. Just for clarification. The Wget option --no-check-certificate has nothing to do with the download option "Verify downloads updates" in the main programme window. In my first download logs generated by WSUS Offline Update 9.2.6, I noticed some errors related to certificate checks when connecting to servers. The Wget option --no-check-certificate is meant to not check these server certificates. The programme option "Verify downloads updates" on the other hand, switches on or off the signature verification of downloaded files by the Sysinternals programme Sigcheck. This is the full list of files that can no longer be downloaded by WSUS Offline Update 9.2.6 for Windows XP: The wmp11-windowsxp-x86-DE-DE.exe file is of course the German version and must be replaced by the desired language version. And yes, they can be downloaded from other sources and easily inserted before the iso image is created. If the user enables the programme option "Include C++ Runtime Libraries and .Net Frameworks", the download script should also be paused before the iso image is created just to remove tons of .Net Frameworks 4.5, 4.6, 4.7. and 4.8 files which are no longer work under Windows XP.

What if you disable "safe" downloading or whatever they call it in Firefox?

I deleted the default download links pointing to .NET Frameworks installer files higher than 4.0 inside WSUS Offline Update 9.2.6 and then enabled their download. No errors anymore. After the download of all updates for .NET Frameworks, I additionally removed all downloaded updates for higher versions than 4.0 just before the iso image was created. This measure significantly reduces the overal size. Personally, I do not really use anymore Microsoft Office but I assume that the dowload of Office updates will also work in the same way as it does for Windows XP updates. I mention this as Office 2007 was actually the topic here.

To be sure that WSUS Offline Update 9.2.6 really works I ran it a second time and activated some more options as, for example, the download of Windows Service Packs. Works. Only if you enable .NET Frameworks, the downloads can't be done as some links don't match anymore. The log file shows the code 404 in the end. So, some scripts would have to be updated regarding download links for .NET Frameworks and maybe for more. But generally, WSUS Offline Update 9.2.6 works great with a few modifications, even in 2024.

Try portable.

Oh, and win 8.0 might be too old for the 2022 redist. But then again, try locally.

Why would you ever need to install that bloat? Just use them locally. See what VC file your game asks you to have and place it in the game folder.

You asked about Securom, specifically, Windows 8 has known troubles with Securom drivers, it treats them as exploits, hence the fact I suggested Vista.

Test RC3 regarding progress bars

Securom was removed even in Vista with updates since it's officially considered to be an exploit and unsafe. So, I'd suggest to run your old games on un-patched Vista, not 7/8. For that purpose buy a PC made in up to the year 2012. And a GTX Titan 6GB card (or GTX780). If you are you going to run a 32bit Vista, then all 2013 Haswell/Skylake/Kabylake* systems would do just fine, too. *Skylake/Kabylake would need a PS/2 port for an easy install.

Could be more specific about the bugs? Thank you.