![]() So all pre-reset builds (even those with Windows XP boot screen and winver.exe) and all post-reset builds with the Windows Code Name Longhorn boot screen (even builds 3790 50 with Longhorn EULA). Note: I considered "Longhorn" builds all builds that have "Code-Name "Longhorn"" refferences. If anyone knows why build 4074 is the only "modern" Longhorn build? None of the browsers I mentioned earlier, except RetroZilla didn't work on other Longhorn builds (neither pre-reset, nor post-reset). I couldn't get Mypal or Arctic Fox or Serpent, because they crashed upon launch. RetroZilla 2.2 (usable, but Gecko version a little bit outdated). Pale Moon 27.x BETA (a little bit slow, but usable) K-Meleon 76 Release Candidate 1 (interface very buggy, even with Klassic theme, but otherwise usable) Chrome 25 (slow and sometimes buggy, but usable) I have tried other browsers on build 4074, and this is what I got: ![]() Can anyone tell me why Longhorn build 4074 supported the "most up-to-date" version of Firefox? It is almost as good as Firefox 52.9.0esr on Windows Vista. Builds 5098, 5112, 5219 support Firefox 10.0esr, and if you modify the installer they support Firefox 20.0. Builds 50, with kernel version NT 6.0 support Firefox 38.8.0esr, but build 5048 supports versions lower than 10.0esr. (That is very logical as this build has the number NT 5.2 so it will be recognized as Windows XP). The development reset: build 3790 (if updated to SP2) can support Firefox 52.9.0esr, otherwise Firefox 12.0 will be the last. All Longhorn pre-reset builds were able to support Firefox 12.0, but build 4074 jumped to Firefox 45.9.0esr and even 46.0b1! Builds after 4074 returned to Firefox 12.0. I tried to install some modern web browsers, as well as other types of software. Hello, Arcive users! I have encountered something very wired in Longhorn builds (both pre-reset and post-reset builds).
0 Comments
Leave a Reply. |