ClassicNick
Content Type
Profiles
Forums
Events
Posts posted by ClassicNick
-
-
@roytam1
I just finished the New Moon 27.9.6 build... The browser loads and seems to work, but I can't test if it can handle encrypted websites (I messed around a lot in the security directory). I also disabled webgl because I didn't want to solve the 18 "unresolved externals" I got while trying to link LibGLESv2.dll.0 -
1 hour ago, NotHereToPlayGames said:
I'm 37 degrees Celsius everywhere I go. Indoors. Outdoors. Traveling. Everywhere.
Do you have any way to stay cool? Edit: Do you mean your internal body temperature is 37 Celsius at all times? So the air temperature is appropriate for you to regulate your body temperature?
0 -
1 hour ago, mina7601 said:
Stay warm, man!
Unless the outside temperature is not within the range of -20 Celsius, and +10 Celsius, I'm a happy guy. On the other hand, in the interest of not getting banned, I shouldn't say how I really feel about the temperature @NotHereToPlayGames is subjected to. @roytam1
It fails early on in the compilation, so you can try it yourself if you get any free time (it certainly wouldn't work with Visual C++ 2010, so I'll just do what I've been doing so far). Also, my HP Pavilion g6 2218nr now has broken hinges, and something else causing nothing except a bright black screen to be displayed instead of normal OS booting. I'm presently using an HP Compaq DC5850 that is not connected to the internet. That means even if I make NSS 3.41 work with Visual C++ 2012 or earlier, I can't test that it actually connects to encrypted websites.1 -
4 hours ago, nicolaasjan said:
(Offtopic)
-34°C in Nikkaluokta (Sweden)...
Here in the Netherlands it's 11°C.
Off topic: 2 degrees Celsius where I live in Nova Scotia.
Partially on topic: @roytam1
In the past, you have said getting TLS 1.3 support working in older versions of Visual C++ will be difficult due to C keywords/types being used that do not work in older Visual C++ versions (forgive me I still don't know much about C/C++). I'm presently half way to making a New Moon 27.9.6 2019-02-23 source code snapshot compile using Visual C++ 2012. Should I be worried about tough to solve errors when I reach the security directory? Also, I replaced the modules/zlib directory with the one from PM27-pm27_eol because I couldn't figure out how to remove use of the align keyword without causing runtime execution failure.1 -
1 hour ago, PPeti66x said:
@roytam1
Hi! Is there any chance to fix/implement the Alt+CharCode text input support in the New Moon v27? This was removed by build 2024-02-02.
If you use the January 27th build, does the "Alt+CharCode text input" work? Do you have an example (web page presumably) that I can use to test it myself?
0 -
17 hours ago, UCyborg said:
As a new owner of Raspberry Pi 5, I shall demand an arm64 version with utmost stubbornness!
Oh, who am I kidding, I know nothing will happen unless I try to do it myself...
If you ever manage to build your preferred browser using a Raspberry Pi 5, remember to use the "ac_add_options --disable-debug-symbols" configure flag in your mozconfig file. I'm finally able to build NM27/Arctic-Fox from mid 2020 on wards, and UXP browsers due to that flag (although NM26 and UXP builds are slow, NM27 is almost tolerable), and I don't seem to have a problem with Visual C++ 2012 and later using too much RAM either. @roytam1 In my testing, all browsers starting with NM26 take ~400-500 MB RAM to link libxul. I would like to know what libxul RAM usage is in your testing (preferably with NM27/ArcticFox) with ac_add_options --disable-debug-symbols. As a bonus, compilation times should be reduced.
0 -
Update: After trying a snapshot of Mozilla's source code from May 10th 2007, and still having context menus fail to display, I decided to batch revert code from Firefox 3.0a4, and found out my problem is in the DOM directory (I haven't narrowed it down yet though). Also, I got my custom Firefox 3.0a4 build to work with Windows 95 (replaced db/sqlite3/src/os_win.c with an older version from July 24th 2006), but still no Windows NT 4.0 support yet.
0 -
48 minutes ago, VistaLover said:
Any impartial by-standard will admit that "us" here act, in an indirect way, as α-testers of upstream's UXP master branch, as being the first to be more widely exposed to that code, despite "our" tree's divergence from "official" UXP; this view is, actually, shared/recognised by @dbsoft in this post
; mind you, MC had himself abolished PM's unstable branch/releases some years ago, because very little of his target audience actually used them and reported existing bugs 
... And, FTR, I, personally, don't mind being "a guinea pig" 
; no-one forces me to update every single weekend (I usually just update once a month or when important webcompat fixes arrive), and before ever updating, I always take a back-up of my current "dirty" profile, in case things break (extremely rarely); going back to a previous build is "a piece of cake" under that scenario ...
I, and I suppose most here (excluding you
), wouldn't be able to compile that "upstream" sourcecode 
and test that URL on the resulting binaries...
I love this comment because if I have learned anything during the time I have been trying to make Firefox 3.0 compile targeting the Windows GFX toolkit, Visual C++ 6.0, and now, Windows 95, it is that alpha software is typically stable enough for use, and sometimes, works better than the official "stable" release. Due to that, I/we shouldn't mind running software just because it is "alpha" or "beta". Your second point is going to repeat like a broken record, because I work with source code as old as I do because that is all my hardware is compatible with. I did try compiling official UXP on Linux Mint 19.3 in ~September 2020, but it took 6 hours with 2 CPU cores enabled, and 2x that time with 1 CPU core enabled. I can compile roytam1's fork of Pale Moon 26.5.0 in ~3-4 hours with 2 CPU cores enabled, and 6-7 hours with 1 CPU core enabled, along with ~1.2 GiB RAM usage. With 1 CPU core enabled, I can compile RetroZilla in less than 1 hour, while using ~100 MiB RAM with Visual C++ 6.0 SP5. The Mozilla 1.9.0 codebase does not seem to have increased build times than the Mozilla 1.8.1 codebase, although 1.9.1 and 1.9.2 do come with ~15% increased build times, along with ~150-300 MiB RAM usage on Visual C++ 2003, which uses 40% more RAM than Visual C++ 6.0.
1 -
21 minutes ago, Rod Steel said:
I just tried, using New Moon (2023-11-30) to read twitter. And it suddenly gave me that:
This browser is no longer supported. Same on Serpent (2023-12-15).
Question - why? What is going on?
I was able to load the site without that error message by setting general.useragent.override.twitter.com to "Mozilla/5.0 (%OS_SLICE% rv:115.0) Gecko/20100101 Firefox/115.0". You can try a different numerical value in the rv: and Firefox section if that is desired. Note: you can reach that setting by typing about:config into the address bar, and searching for general.useragent.override.twitter.com. Also note: I'm not a twitter user, so my testing goes as far as loading the main Twitter page. EDIT: I seem to have a global useragent override set to Firefox 102.0. You should also be able to use "Mozilla/5.0 (%OS_SLICE% rv:102.0) Gecko/20100101 Firefox/102.0".
0 -
Locally, I have an unofficial build of Firefox 3.0a1 from June 22 2006 (bug 330276 reverted) working on Windows 95 (my favourite version of Windows preceding 2000), and a build from October 5 2006 that does not work in Windows 95. It fails with an error stating "This program has performed an illegal operation and will be shut down". Apparently Firefox causes an error in kernel32.dll. Between those 2 dates, Mozilla introduced problematic JavaScript code that breaks Windows 95 compatibility in the browser directory (nsSearchService.js, and nsSafeBrowsingApplication.js) in Firefox 2.0. I'm not sure if that is the only thing causing incompatibility with Windows 95 in 3.0a1 though. @roytam1 I can use the Windows Server 2003 R2 SDK if I add the directory paths to "start-l10n.bat". That means I can use the Thebes GFX toolkit using Visual C++ 6.0 SP5, however, it breaks Windows 9x and possibly NT4 support. I haven't tested whether usp10.h and usp10.lib in the October 1999 SDK will work with the Thebes GFX toolkit though (needed for Visual C++ 5.0 and Windows NT 3.1/3.50 support). 2 options are on the table: 1. Create a GetGlyphIndices stub that works in Firefox 3.0a5 and later, or 2. Use the Windows GFX toolkit with Windows 95 and NT4 support ready to go.
0 -
6 hours ago, shelby said:
Any news?
I found out that the last version of the Windows SDK that works in Visual C++ 5.0 is the October 1999 SDK. I can get Mozilla-Build working with both Visual C++ 5.0 and the October 1999 SDK, which does alleviate some compatibility issues throughout the codebase. I also learned I can remove the "friend class nsTHashtable<nsBaseHashtableET<KeyClass, DataType> >;" line and related code, which will get around the "6 unresolved externals" error when linking xpcom.dll. Doing this works in Visual C++ 6.0, but does have some minor issues. In Visual C++ 5.0 however, it compiles, but does not display a Window in Windows XP, only a broken title bar. In older versions of Windows (tested on 95), Firefox produces an illegal operation error. So I'm in a position where I can compile a build successfully, but runtime execution will fail. I do not presently know what is causing the problem. I do have similar problems with newer versions of Firefox than 1.1a2 or 1.5.
0 -
So far I got Firefox 3.0a4 working on Windows 98 SE, but not 95 or NT 3.51 or 4.0:
https://github.com/ClassicNick/Fx3.0a-VC6-mod/releases/tag/Fx3.0a4-Win98
0 -
7 hours ago, roytam1 said:
those are not going to be merged.
Is it possible to cherry pick commits using the web browser version of GitHub? Partially OT: Test: The Arctic-Fox developer has used Mozilla code changes that switch pointer references (namely nsAutoPtr references) into UniquePtr references. I couldn't get UniquePtr to work in Visual C++ 2008, so want to know if it is possible to revert those commits? I finally found the "Squash and Merge" function on GitHub, which means a lot to me because when I add support for Visual C++ 2008 in "KM75-gecko31-engine", Visual C++ 2010 support in "Arctic-Fox-fix-winbuild", and "palemoon27-classic" it would be easy to add just a couple of files per commit, which could mean in range of 100 commits. There have been many times I have wanted to upload incremental changes to GitHub, but was too scared to because I don't want hundreds of commits when I can have a few dozen larger commits. It would get some use if my dev machine was online... Also, I do not believe I'm leaving GitHub!
0 -
55 minutes ago, nicolaasjan said:
You can find an offline html TOTP Token Generator here.
Download the zip, extract and click on 'index.html' in the folder 'public'.
Paste in your secret key obtained from GitHub and voila. 🙂
That might be enough to fix my problem. 2AM UTC November 3rd is approximately when my 7 day grace period would have expired. With your tip, My GitHub account now sees 2FA as being enabled.
1 -
On 10/22/2023 at 11:35 AM, Mathwiz said:
I still believe that making it a hassle to sign out and back in was a motivating factor behind Github's decision to require what I call "burdensome" 2FA.
That is the reason why I'm leaving GitHub. I assume that when my 7 day grace period expires, I won't be able to sign in and use GitHub without 2FA?
0 -
@roytam1
Presently, I'm trying to compile New Moon 27.9.7 (palemoon27-classic in our GitHub repositories) using Visual C++ 2010 and Windows XP SP3. configure.in in the root "topsrc" directory has WINVER set to 502. In the js/src directory, WINVER is set to 600. Do you know if that version is still able to target Windows XP SP2? Confession: My goal is to make Arctic-Fox target Windows 2000 and XP using Visual C++ 2008 SP1, but I will still use Visual C++ 2010 to save on RAM (~1.3 GiB to link libxul in Firefox 38.8.0esr using Visual C++ 2010).0 -
5 hours ago, UCyborg said:
@NotHereToPlayGames
Yup, that's what I meant. None of the even remotely usable web browsers are built using Visual Studio 2010's toolchain, which was the last that worked on XP (and Vista) if I remember correctly. 360Chrome seems to be built using Visual Studio 2015's toolchain, as indicated by the LinkerVersion 14.0 in the Optional Header in 360chrome.exe (https://en.wikipedia.org/wiki/Visual_Studio#History). I suspect code changes would be needed for browsers to be even buildable on older toolchains and I doubt they'd be small ones. If I remember correctly, didn't roytam1 recently switch to 2019 toolchain? All these require Windows 7 as the minimum, which makes all of you indirectly dependent on Windows 7 (or newer), whether you care to admit it or not.Correction: roytam1 uses the Visual C++ 2017 toolchain. The last version of Firefox that was able to officially compile on Visual C++ 2010 was 36.0.4, however, I have only managed to compile up to Firefox 35.0.1 on Windows XP SP3. BTW, I have a local build of Firefox 30.0 that I compiled using Visual C++ 2008 SP1, although I did use the --disable-ion configure flag due to a crash in mozjs.dll, which removes jit support. My eventual goal is to get New Moon 27.9.4+ and Arctic-Fox 42.0 targeting Windows 2000 and XP RTM/SP1. In my testing on Windows XP, I get an error stating the program cannot start because the application configuration is incorrect. Apparently Visual C++ 2008 can target Windows 2000, but restricts Windows XP compatibility to SP2. @roytam1 Do I need to use Visual C++ 2005 SP1 for Windows XP and XP SP1 support?
0 -
@feodor2 How high does RAM usage usually go when building Mypal 68.13? How much does it consume (linking libxul is traditionally when RAM usage was at its highest)?
0 -
22 hours ago, feodor2 said:
First it does wrong, second why it messes with time at all, what a point to keep megabytes table like icudt63l.dat?
Now i see serpent still not use icu for time calculations, so i have removed icu there.
What this icu stand for, may be good for builds on linux, macos, etc. If you know you builds only for windows why not get rid it as useless s*** and save a good bunch of megabytes.
Skipping building the ICU files used to be possible until Firefox 48 or 49 by using the "--without-intl-api" configure flag. As a result of the relevant Mozilla bug report below, Mozilla decided to remove the --without-intl-api configure flag, meaning the ICU files must build and be present in the objdir/dist/bin directory in order for the browser to launch. OT: I'm trying to build Firefox 30 using Visual C++ 2008, and I do use the --without-intl-api flag in my mozconfig file. I haven't tested if that means intl.* functions will not work. https://bugzilla.mozilla.org/show_bug.cgi?id=1301882
1 -
FYI: The UXP browser builds (New Moon tested) compiled with Visual C++ 2017 still supports Windows XP SP2. @roytam1 Now that you're building UXP applications using Visual C++ 2017 (version 15.9?), will they still compile with Visual C++ 2015 update 2 if JPEG-XL is disabled?
0 -
8 hours ago, roytam1 said:
yeah, in shared mode it actually puts more extra codes and bindings into separated DLL.
static linking is indeed smaller with the cost of more memory and time in linking.
That's why on browsers that allow me to build with both static and shared linking options, I like to do local shared builds, but public static builds. RetroZilla takes ~126 MiB RAM using Windows XP SP3 and Visual C++ 6.0 SP5 to build rzbrowser.exe with static libraries, but only ~83 MiB RAM to link gklayout.dll with shared libraries. Using Visual C++ 2003 bumped the RAM usage of rzbrowser.exe from ~126 MiB to ~178 MiB, but I don't believe I tested that compiler with shared libraries (~117 MiB would be my guess if I did). Building shared libraries of RetroZilla Browser will result in a bin directory size of ~20.5 MiB excluding MSVCRT.DLL. Building static libraries results in a bin directory size of ~18.5 MiB (I don't remember the exact bin size because I more commonly do shared builds instead of static builds, not to mention the differing build configurations I often use that will sway the bin directory size slightly).
1 -
Update: I managed to do a modified Firefox 3.0b4, and Firefox 3.0b5 build, but the most notable problem with the builds is the absence of EnsureDeviceContext() in nsDocShell.cpp which is responsible for setting the font size for the menu bar to ~128 pixels. Also, most of the text in the context menus have font sizes ~1-2 pixels in size, which is too small to read, and at the moment, I'm unsure of how to remedy that problem.
My Firefox 3.0b4 Visual C++ 6.0 mod:
My Firefox 3.0b5 Visual C++ 6.0 mod:
My last successful build of Firefox 3.0 was 3.0a4, so I think I want to revert more of the code in suspicious directories (layout/* ?) to what existed in Firefox 3.0a4. @roytam1 I assume you know about comparing changes between files using diff file readers. Can you recommend some diff file viewers that are compatible with Windows 2000 and/or XP (specifically one with support for viewing multiple files)?
1 -
12 hours ago, roytam1 said:
some PITA about shared gkmedias and icu libraries finally solved and landed to st55 and myUXP.
If building "shared" libraries comes with the effect of them being split out of xul.dll, resulting in a smaller file size, does RAM usage while linking xul.dll decrease? If so, by how much?
0 -
19 minutes ago, Milkinis said:
I have not updated mine since last summer. how do you check this out ?
If you read the change logs between roytam1's UXP commit history, and Moonchild/upstream's UXP commit history, you will be able to draw the conclusion that the 2 UXP code bases are nearly identical. Following upstream UXP development, you will know that the defining features of Goanna 6.0 were the implementation of Regular Expression named capture groups, Regular Expression unicode property escapes, and Regular Expression lookaround/lookbehind, and the defining features of Goanna 6.1 were additions to the Shadow DOM v1 implementation (see issue "#2135"), along with a bug fix to make Custom Elements v1 work properly, which allowed "dom.webcomponents.enabled" to be set to "true" by default (see about:config). Also see pages 55, and 61 of this thread to view my favourite change logs of the UXP browser builds and search for issue #1361 on page 55, and #2135 on page 61.
https://www.palemoon.org/releasenotes.shtml
https://repo.palemoon.org/MoonchildProductions/UXP/commits/branch/master
https://github.com/roytam1/UXP/tree/custom
https://github.com/roytam1/UXP/blob/custom/config/milestone.txt
https://repo.palemoon.org/MoonchildProductions/UXP/src/branch/master/config/milestone.txt
1
My Browser Builds (Part 5)
in Browsers working on Older NT-Family OSes
Posted
I used VC 2012 at that time. However, your post came at a great time because I just built it using VC 2010, but using the Windows 8.1 SDK. Next up... Removing UniquePtr references, and move semantics from xpcom/glue/nsCOMPtr.h. In October 2023, I failed to make UniquePtr.h compile cleanly using VC++ 2008, so I think it will be easier to just do away with it completely.