Leaderboard

StartAllBack 3.8.1

@Cixert I only use WSUS Offline Update 9.2.6 for downloading Windows XP updates. The download of Office 2007 updates was just for testing purpose to help you. As I already mentioned, I downloaded all of them in the past. There is nothing new to download anymore. Regarding Windows XP, I deleted all references to files which are not XP-compatible. "I deleted the default download links pointing to .NET Frameworks installer files higher than 4.0 inside WSUS Offline Update 9.2.6" means to remove all these references in the StaticDownloadLinks-dotnet.txt and "and then enabled their download." actually means that I checked the box in the main programme window with the option to download C++ Libraries and .NET Frameworks for the next download session. I wrote that before I found out to better set exclusions. Setting exclusions is very effective to avoid unwanted downloads. And the last pause gives the user the possibility to add missing or remove unwanted files before creating the iso image. Please let me know if now all is working for you regarding the Office 2007 updates as it should! Whether it also works for Office 2003, I can't say anything about as I didn't test it. You have to check this on your own. Greetings from Germany, AstroSkipper

Windows 7 never supported D3D11.1. It's a rumour/fake news. D3D11.1 is windows 8+ only. Some DXGI 1.2 API and the ID3DUserDefinedAnnotation were ported on windows 7, but most of the really useful functionality, no. You can get only partial/miserable/fake Direct3D 11.1 by installing the Platform Update for Windows 7 And, for example, this component is not available: DirectComposition (DComp) All information is taken from Microsoft website. https://learn.microsoft.com/en-gb/windows/win32/direct3darticles/platform-update-for-windows-7

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.

Just for the sake of comparison, I tested the last version 10.9.2 of WSUS Offline Update, which still supports downloading Office 2007 updates, on a Windows 10 computer. As with Windows XP and WSUS Offline Update 9.2.6, the result is disastrous. Tons of updates are downloaded that have nothing to do with Office 2007. So my method of replacing the wsusscn2.cab file with a suitable one is probably the only way to download Office 2007 updates with WSUS Offline Update today. I suspect that Microsoft has changed the download links for old Office products from a certain version of wsusscn2.cab onwards, although most of the files are still on their servers. All that means we have to be tricky in these days to get such old updates from Microsoft's servers.

.

No, it's not. Here's a MonoBleedingEdge (Engine version from 2019) log file for you from: OS-Version: 6.1.0 (win 7). Renderer: NVIDIA GeForce GTX 1070 (ID=0x1b81) GTX 1070 supports all the way up tp 12_1. Yet the log for Windows 7 says: "Forcing GfxDevice: Direct3D 11 GfxDevice: creating device client; threaded=1 d3d11: QueryInterface(IDXGIFactory5) failed (80004002). Direct3D: Version: Direct3D 11.0 [level 11.0]" Source: https://steamcommunity.com/app/251570/discussions/1/2646361461399067327/ It's from 2020! Eight years after the alleged 11.1 update KB came out.

Nothing weird, I always suspected win32 stood behind all Kernel releases to begin with, it's just my personal opinion after looking at the code. Not seeking an argument over it.

From this first sentence it's clear as day that you implied that Microsoft actually did bring "D3D11.1 API to Win 7" And no matter how many games I tried to run on Win 7, even after the aforementioned update applied, they all fall back to just 11.0. So, D3D11.1 on Win 7 is just a stub, it's not "API" like you wrote. What it does, it simply tells a game, go on, run, it runs, but with 11.0 since the 11.1 features are absent. One would need to rewrite Win 7 to actually add the real D3D 11,1. That's what D.Draker tried to explain to you. As of now, Vista and Win 7 have the same 11.0. Is it more clear now?

It doesn't let me to download. https://web.archive.org/web/20240727151625/https://github.com/i486/VxKex/releases/tag/Version1.1.1.1375

Good! Thanks for coming out with the confession, then the supervisor will keep an eye on you, too.

Yes, thank you very much, if it weren't for your help I wouldn't have achieved anything. After everything works correctly I will make a summary of all the necessary steps. Let's go by systems, for the moment the question is as follows: WSUS 9.2.6 option XP x86 with .NET Framework and C++: Adding these lines to ExcludeList-dotnet-x86.txt & ExcludeList-dotnet-x64.txt does work. ndp35- ndp45- ndp46- ndp47- ndp48- The .NET 3.5 installer is normally downloaded, what is not downloaded are the updates for .NET 3.5 but are for .NET 2.0, 3.0... The problem was that on my computer WSUS does not work well with the temporary files that contain the download lists, the strange thing is that downloading the XP updates without .NET did work but with .NET it failed. I have run it on another computer and it worked with the latest wsusscn2.cab version. The following files are not downloaded but I add them manually thanks to your pause functions on the correct lines: \client\dotnet -NDP40-KB2600211-x86.exe \client\win\glb -Silverlight.exe \client\wxp\esn -wmp11-windowsxp-x86-ES-ES.exe \client\wxp\glb -WindowsXP-KB942288-v3-x86.exe Also I delete for x64: \client\cpp -vc_redist_x64.exe (all) \client\win\glb -Silverlight64.exe and... dotnetfx35langpack_x86de.exe (only for German language) Now I have this problem in the log and I don't know how to add these missing downloads or what the message exactly means, I see in some old forums that there are more than 2 downloads: 2024-08-02 22:09:12,83 - Info: Downloaded/validated 2 statically defined updates for dotnet x86-glb failed: Unknown error. failed: Unknown error. 2024-08-02 22:15:09,45 - Info: Downloaded/validated 14 statically defined updates for wxp esn failed: Unknown error. failed: Unknown error. All other files download correctly, how do I guess which ones are missing? The error does not occur with the XP option without .NET I don't know what "statically defined updates" means. I think it's the links contained in the "static" folder. EDIT: I have tried with old wsusscn2.cab (2019-04-06) and these files have been downloaded correctly. The pity is that this file has 54 dynamic updates less. I will try to make a mix between both. And also the pity is that this wsusscn2.cab is dated 3 days before the end of support for Windows XP Embedded. It seems to make no sense that if they are URLs contained in a .txt file, they are downloaded or not depending on the version wsusscn2.cab and whether or not the .NET option is checked in WSUS.

"Russian Businesses Can Now Legally Steal Intellectual Property from ‘Unfriendly Countries’" "As of Monday, March 7, 2022, the Russian government has legalised intellectual property (IP) theft. With this move, businesses in Russia can now violate IP rights, as they no longer need to compensate patent holders from “unfriendly countries.” The list of “unfriendly countries” includes the United States, Canada, Australia, Switzerland, Norway, Iceland, the United Kingdom, Japan, South Korea, New Zealand, Singapore, Taiwan and all 27 European Union (EU) member countries." That includes software. https://ipwatchdog.com/2022/03/16/russian-businesses-can-now-legally-steal-intellectual-property-unfriendly-countries/id=147528/

Hello! No, no solution. Switch to Nvidia only in the BIOS. Intel card is weak and crappy anyways.

In this weird modern World, it doesn't work the way you assume. The US hosts a super large portion of openly anti-American population, most of them aren't even citizens, they broke all the laws, yet they aren't deported, they are even subsidised. It's the same with the github since they are an American entity, they resonate on the same (current) agenda frequencies. Also, regarding github, github works for the international market, they can't just throw away whomever they don't like. Or they would've needed to implement the only US members demand.

What is POSReady2009? And how it's related to Win7 Kernel? Win7 was released only at the end of 2009.

Some folks are like children, do the opposite. Or may be he really is, we can't see his age.

My developer friend on github said they usually send an official letter demanding to remove the content in question, so not likely the case.

It can't be classified as an "attack" in either of the cases, Microsoft has the right to defend what's theirs. Closed source Kernel modifications aren't allowed in the US,

You confuse hardware level with software level. "11_1 feature level" is a hardware level, it can't be "implemented" in just "soft" mode. Here you can educate yourself regarding the topic. Microsoft article with precise and simple explanations. https://learn.microsoft.com/en-us/windows/win32/direct3d12/hardware-feature-levels

I follow your instructions @AstroSkipper I put download .NET and C++ for Windows XP in Spanish and it tries to download .NET 4.6.2 in German. Maybe because the program WSUS is made by Germans... EDIT: FIXED: I have deleted most the links contents in StaticDownloadLinks-dotnet.txt Which most contains links in German. Delete for all languages except German.

I have exactly the same problem. All shortcuts from the taskbar on the first monitor also appeared on the taskbar on the second monitor and cannot be deleted on the second monitor. Because of this, I had to revert to an older version of StartAllBack.

Philippe, hello and welcome to the neighbour from the South of France!

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.

Source, please.

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

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's the manual https://www.tyan.com/manuals/m_s5360_100.pdf It says 184-pin DDR 333/266 Registered ECC with single chip sizes of 256, 512 or 1024Mb. (their nomenclature) Whether an unregistered will work, it is not going to be a 100% answer because all boards and RAM are different. You can go further by looking up the spec sheets of the RAM itself and compare them. But my experience tells me that there are going to be some boards where using UDIMM on RDIMM is going to either a) work fine, b) not work, c) not work fine or d) cause damage. So unless you can find any post online of someone who has tried the same exact RAM that you have in the same board rev and they say it works, then it will probably work. But real world isn't so handy to be able to find that info, so you are likely to have to try it yourself to see if it works or not. I've also not experienced any situation where having an unsupported type of memory in a board has caused damage. Either with old Pentium systems or modern server boards. I suspect those instances of damage were likely caused by something other than mismatched memory, such as dirt or some other situation.

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. I have found a way to make it even easier, faster and, above all, more convenient. You can set exclusions in WSUS Offline Update 9.2.6. To do this, you must insert the following strings in the ExcludeList-dotnet-x86.txt and ExcludeList-dotnet-x64.txt files in the exclude folder: ndp45- ndp46- ndp47- ndp48- Doing so, the download of files containing these strings will be skipped. And in order not to miss the right moment to press the pause button when adding the missing updates, you can add the following command in line 3 of the CreateISOImage.cmd file in the cmd folder: echo The script has paused. Now, you can manually add all updates whose download has failed. When done, press a key to continue! pause 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.

No, on the contrary, your English is good. I wish many others had at least your level. Today, I wanted to stick forks in my eyes when I saw "maded" written by a dude who claims to be a "developer", lol. So, I just made you a compliment, as you see, I'm not here "against you", either. What I wanted to tell, we know that Kernel developer from here, he is a member, I don't trust github either, I trust MSFN. Edit. Nothing personal, it's just we had some MSFN haters joined as of lately. So some folks may be a bit agitated and over-protective.

Agree! Only good PR for MSFN.

Compare with what? What if the user is new, and doesn't have any of these from before? Since the original repo is gone, as you wrote yourself.

No one is "paranoid", we are just being on the safe side. I mean, do you realise how serious is to install kernel from unknown, non-developer sources!? MSFN only hosts and provides 100% clean originals. The same with external links. We can't just take someone's word for it, sorry.

Probably, the same case as with the forceful takedown of Supermium. Guys, someone knows, does it support Win7 without the bloated SP1?

Yes, looks very weird it's still not there, I mean for a fifteen years old totally out-of-support buggy OS.