WinFX
-
Posts
291 -
Joined
-
Last visited
-
Days Won
2 -
Donations
0.00 USD
Content Type
Profiles
Forums
Events
Everything posted by WinFX
-
But if you look closely all versions (or almost) until R563 store inv and bm. After this version there is nothing, for my Micro$oft I change a mechanism or I change the domain of inv and bm. And it would be illogical that in 10 years (2001 to 2011) there is not a single investment higher than R563.
-
The .as files are compiled in actionscript 1.0
-
On Windows 98 it only works in English with IE5.01, not 5.5 or 6.
-
The problem is that very old updates appear, like ie5.5rtm when windows 98 supports up to ie6sp1, or dx7.0a when it supports up to 9.0c. Also for some reason wayback machine stores only up to R563 of inv and bm, coming from the middle of 2000. Although WUv3 remained open for more than 10 years there is not a single inv of R1150 archived, or at least of a close version such as R1116 or R1097 , only up to R563!
-
And you are using a English version or German version of actsetup.cab?
-
Micro$oft removing updates from their servers.
-
Click on Vornext Technologies and install the certificate on local computer
-
https://drive.google.com/file/d/18SDovpwQ4JdUYkJ4ZwuxMzv4Hta5Q6Id/view?usp=sharing for Windows 95, 98 and NT 4.0 this works fine
-
The file 0x00000407.as, is it a renamed 0x00000409.as?
-
Add --concurrency 20 to the command
-
In the folder that you downloaded the entire site in wayback machine downloader, look for *.inv in the explorer, and that this is in the folder with the same numbering, for example 90704 is for Windows 2000 with IE5.01, I think it was 90724 for IE6 from what I see in your capture. Take that file and rename it, same with the bm.
-
After installing activex controls related to Windows Update v4 or v6, Windows Update v3 mysteriously stops working. I recommend that you try it on a clean English installation of Windows 2000 RTM, SP1 or SP2.
-
Show me a screenshot of your fiddler log
-
All 404 files except wutrack.bin are essential
-
Use the command that I leave you below, it will help you a lot with the lack of files as well as in the trial and error tests of searching for updates: wayback_machine_downloader http://windowsupdate.microsoft.com -t 20110707002618
-
Show me a screenshot of your fiddler log
-
No, only the critical update together with MSN Messenger 2.2
-
Try with this controls: https://drive.google.com/file/d/1dSiMExp0Wh4pgD-e6IHwmSJyhzx313F5/view?usp=sharing There are the actsetup.cab for Windows 2000, 98 and ME. Use the 98 one for Windows 95 and NT 4.0. And fiddler shows OSDET?
-
But I didn't even show the recommended updates on Windows 2000 both in RTM, SP2 and SP4.
-
Disappear after installing them
-
Windows 98 and Me crash because your folder is corrupted, only backup Home.htm and Mssupport.htm. Then copy and rename nt5 to w98 or mil. And in engine.htm replace nt5 with mil or w98.
-
More news about Windows Update V3, now has returned to Windows 98 first edition, and installs updates correctly. Perhaps our humid dream of working Windows Update in Windows 98 has been fulfilled, but there are still certain bugs: Regardless of the language of the operating system, the site is loaded in English Updates are only installed if the operating system are in English Although much of the updates are in download.windowsupdate.com, it only shows the critical updates package The recommended updates are not shown, although in @maile3241 first video on Windows 2000 they appear An annoying JavaScript error appears "document.style.all"
-
Install Fiddler Classic on your Windows Server and follow the following steps: https://docs.telerik.com/fiddler/configure-fiddler/tasks/monitorremotemachine. That way you can monitor Windows 95 and NT 4.0 HTTP traffic.
-
Hi, I'm testing the nginx method of Windows Update on Windows XP, and wuredir.cab needs to be digitally signed. I use the WDK like the Windows 10 SDK 1607 to sign the cab in SHA1, in my Windows 10 and Server 2012 R2 it appears that I have a valid signature, but in Windows XP or 2000 I don't. And it's because timestamps sign in SHA256 and Windows before 7 doesn't recognize it, and XP SP2 or 2000 outright doesn't know SHA256.
-
Most likely they are hardcoded. Although I understand that Windows Update v3 you have to install critical updates before anything else.
