Jump to content

Nicholas McAnespy

Member
 View Profile  See their activity

  • Posts

    196

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    Canada

About Nicholas McAnespy

  • Birthday 12/11/2001

Profile Information

  • OS
    Windows 2000 Professional

Recent Profile Visitors

6,484 profile views

Nicholas McAnespy's Achievements

50

Reputation

  1. Nicholas McAnespy
    @roytam1 I have a Visual C++ 2013 update 4 build of your New Moon 27.10.0 20241220 build, taken from the palemoon27-master branch in your repository. Previously, you had merged Arctic-Fox commits into your palemoon27 repository, and "squashed" them so that all the Arctic-Fox commits you merged will appear as 1 commit. If I have the source code to palemoon27-master, and the Arctic-Fox-master git information (presently at version 45.2 from January 6th 2025), what git command do you recommend I use in order to merge commits from Arctic-Fox (I only know git cherry-pick)? Also, I asked you if you could create a VC2015 branch in your palemoon27 repository, and see if you could merge the latest Arctic-Fox commits to that branch. I finally decided to try a VC2015 build of New Moon 27.10.0 20241220, and it failed 8 minutes in with errors in the type_traits file built into Visual C++ 2015, but when I tried a VC2013 build, it compiled cleanly taking 76 minutes. That means creating a "VC2015" branch for the purpose of evading Visual C++ 2013 compatibility is not necessary in my opinion, but a "tracking" branch that is not meant to be compiled but merged to may be helpful to determine if merging commits from Arctic-Fox will still work (I'm scared of git).
  2. Nicholas McAnespy
    Update: I managed to get half way through a Visual C++ 2008 compatible mod of New Moon 27.9.7, but I sometimes build with Visual C++ 2010 to see if the browser crashes or not. I managed to make tabbed web browsing impossible due to the content on the 1st tab spreading across all the tabs, and leaving only that 1st tab usable. Opening new windows for every tab still works though... I think the problem lies somewhere in the GFX directory, but I could be wrong. @roytam1 What do you recommend I do now? Edit: I will continue with my current build to get it compiling under Visual C++ 2008, and then try fixing my problem on the next build. Also, my way of getting around the decltype function used in layout/base/nsChangeHint.h breaks tabbed browsing anyway.
  3. Nicholas McAnespy
    @roytam1 Would it be possible to create a VC2015 branch in your palemoon27 repository, then merge the latest Arctic-Fox commits? If you can build it using Visual C++ 2015, that would be a great start so I can try my hand at a Visual C++ 2013 build.
  4. Nicholas McAnespy
    VC4 does not support the OPT:NOICF flag used in js/src/Makefile.in. As far as I remember, disabling optimization flags should work, but will mean using the resulting application will be slow. As a note, see bug 151066. It's been a while since I've tried compiling Mozilla source code using Visual C++ 4.x, but I do remember having an error in layout/style/nsRuleNode.h, but I don't remember the message or what caused it.
  5. Nicholas McAnespy
    @Leokids123 I have the project marked as cancelled because I'm still struggling to make Firefox 3.0 work with Windows 9x. Brutal honesty: After having runtime execution failure in Firefox 3.0b5, and having flaky Windows 98 compatibility in Firefox 3.0a7, I have become discouraged and scared of continuing with this project. I would like if someone (mainly @roytam1) could upload my Firefox 3.0a4 mods from GitHub, so I can try again at Firefox 3.0a7 Windows 9x compatibility before moving toward Firefox 3.0 Windows GFX builds.
  6. Nicholas McAnespy
    I was wondering why your GitHub account says UXP updated Y hours ago, but palemoon27 updated 2 weeks ago. I understand fully why you don't plan to release future New Moon 27 or K-Meleon 76.5 Goanna builds if it makes Visual C++ 2013 compatibility more difficult, especially seems how I never learned to use Visual C++ 2013. Confession: I'm getting crashes in mozjs.dll relating to js/public/HashTable.h in New Moon 27.9.6 when trying to use Visual C++ 2008 compatible syntax, so I think I will give up. Instead, I will opt for either a Firefox 24 (works well enough for me), or a Firefox 31 fork. Can you build K-Meleon 74 Gecko using the Mozilla 24.8.1 codebase?
  7. Nicholas McAnespy
    I heard they reduced the bitrate for their videos. I've never used a 1080p camera, and I don't have much experience with 720p either, but a 640x480 video needs a minimum bitrate of 500 Kbps, but 1 Mbps should typically be high enough if encoded using h264, but there are circumstances when even 2 Mbps isn't very high. Videos with high motion will need a higher bitrate than videos where the camera doesn't move. A bright location will need much higher bitrate than a dark location will. I also believe targeting a constant bitrate will cause more blurriness than targeting a variable bitrate.
  8. Nicholas McAnespy
    I remember when I use to be able to load YouTube in ~200 MB RAM including K-Meleon 76.1 Goanna, and ~250-400 MB after the switch to the "Polymer" UI. What caused RAM usage to increase to > 600 MB? I also noticed YouTube has much higher CPU consumption than it did 4 years ago.
  9. Nicholas McAnespy
    @roytam1 I downloaded your "palemoon27-pm27100-vc2010" source code, and tried removing C++ 11 move/forwarding references. I now get a crash in mozjs.dll. Also, I can't do a debug build due to a "program database manager mismatch" error. If you can upload the source code so I can see my changes on GitHub, that would be great. Note: I removed the delete constructors in js/src/jsobj.h lines 544-545. I also used Visual C++ 2010 to compile this, so I assume my modifications are incomplete. https://codeberg.org/Nicholas_McAnespy/palemoon27/releases/tag/2796-MoveRef-Busted
  10. Nicholas McAnespy
    @K4sum1 Thank you for doing public releases of lun3r and Hydra. I prefer to use a browser based on Pale Moon, and I build browsers based on Arctic-Fox/Pale Moon 27, so it's nice to have a browser that I can leave running, while testing my own browsers that share the Pale Moon profile.
  11. Nicholas McAnespy
    @roytam1 I have been getting some errors related to "NodeInfo is not a member of mozilla::dom::mozilla" while trying to compile New Moon 27.9.7 using Visual C++ 2008. My way of solving those errors means de-unifying the C++ sources.
  12. Nicholas McAnespy
    Update: Visual C++ 2008 doesn't like using <intrin.h> in nsprpub/pr/pratom.h, and prbit.h.
  13. Nicholas McAnespy
    With further testing, I noticed the older K-Meleon 76 Goanna builds (76.1.1) lack GetLogicalProcessorInformation in xul.dll, but have it in the gmp* files, libavcodec files, and MSVCR120.dll. I believe Firefox, Arctic-Fox, and Pale Moon have some sort of hack to allow execution on Windows XP SP2, even though Visual C++ 2010 and later do not naturally support it, which is probably why K-Meleon 76 Goanna doesn't work with Windows XP SP2. Since MSVCR90.dll is the last version to not call GetLogicalProcessorInformation, I hope this problem fixes itself if/when we get Tycho/Goanna3 compiling using Visual C++ 2005 and/or 2008.
  14. Nicholas McAnespy
    While you're doing that, I tried compiling the New Moon 27.9.7 VC2010 mod using Visual C++ 2008, and hit a roadblock due to compiler errors caused by C linkage where it's not appropriate for it to be specified. I do not know where the C linkage is though... If you can find where "GetLogicalProcessorInformation" is defined, that would be great, but could be difficult because it is called from xul.dll in K-Meleon 76 Goanna, but no such call exists in xul.dll from New Moon 27. Admittedly, I haven't tested whether xul.dll in K-Meleon 76 Gecko calls GetLogicalProcessorInformation, and thus, fails to execute in Windows XP SP2.
  15. Nicholas McAnespy
    The Source code containing git information is uploaded to https://github.com/ClassicNick/palemoon27/releases/tag/27.9.7-VC2010
×
×
  • Create New...