Jump to content

Nicholas McAnespy

Member
  • Posts

    209
  • 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

10,636 profile views

Nicholas McAnespy's Achievements

54

Reputation

  1. @roytam1 Would it be possible for you to give me build instructions for K-Meleon 76 Goanna using Visual C++ 2013?
  2. Thank You for that decision! If your UXP fork can still compile using Python 2.7 and Mozilla Build 2.2, I would like it to stay that way.
  3. Developing a single browser engine for Windows XP is quite an interesting goal. My short list is Gecko 24, Goanna 2.2 (slow, but should build on XP), Gecko 38/Goanna 3.x (Faster, but will need a lot of work to compile using Visual C++ 2005 or 2008), Gecko 1.9.1 (Fast, and works with Visual C++ 2003). Personally, I'm in the process of Building Firefox 24.0a1 from May 30th 2013. K-Meleon 74 was originally based on Gecko 24, but @roytam1 does his builds using the Goanna 2.2 rendering engine. I would like to learn how to build K-Meleon 74.
  4. Where's Retrozilla 2.3 changes?

  5. @Goodwin @roytam1 I'm not a professional, I just compile Mozilla based browsers for my personal use and hope for the best. For instance, I'm trying to compile Firefox 13+ with Windows 2000 compatibility. One thing that sometimes (but not always) causes runtime execution failure is clicking on tools -> options -> applications which can cause an error in MSVCR71.DLL. Also, after reverting the commit that broke Windows 2000 compatibility, I had a minor problem that is caused by opening a new tab, and the message displayed on the new tab page was relating to an invalid address. That annoyance was caused by the commit for Mozilla bug 728429, which mandated ASLR on Windows. In order to find that, I had to cherry-pick a range of commits between the one that broke Windows 2000 compatibility, and the one mandating ASLR, then compile the source code a few times to narrow down my search. The point is, if a problem does not exist in one of roytam1's browser builds, then exists on a later browser version, the right thing to do is find out what the last good version, and the first bad version is, then it would be easier to find when the problem started, and what commit caused it. Also, it is possible a bug might not affect everybody.
  6. On the topic of New Moon 26, would it be possible to provide instructions on how to build K-Meleon 74?
  7. @roytam1 I have a build of Firefox 31.0a1 working with Visual C++ 2008. The build works on Windows XP RTM, but crashes in Windows 2000 due to missing uxtheme.dll. https://github.com/ClassicNick/gecko-vc9-dev/releases
  8. @roytam1https://github.com/ClassicNick/Arctic-Fox/releases/tag/2024-10-18 I now have a slightly updated source code release of Arctic-Fox winbuild available. I also set up a Linux Mint 19.3 build machine, so hopefully I'll be able to learn how to push git commits.
  9. If you can install Visual C++ 2008, it will produce Windows 2000 and XP compatible software (but with manifest errors affecting both Visual C++ 2005 and 2008). Mozilla got around that by building "mozcrt19.dll" somehow, but I have not been able to build it. Should I upload the source code and resulting executable?
  10. Yes I have, but my plan is actually to get New Moon 27 working with Windows 2000 (and XP/SP1), then create a Visual C++ 5.0 build of Firefox 3.0 (I have no idea how to make it work with Windows NT 3.50 or earlier, nor can I test it, but I'll eventually open the door to someone who can). I know I want Gecko 1.9, but I still struggle to figure out if I want the default theme of Firefox 1.5, 2.0, or 3.0.
  11. Can you see yourself ever using Visual C++ 2008 to produce Windows 2000 and XP RTM/SP1 compatible browsers, or do you need Visual C++ 2005 compatibility? I have a Visual C++ 2008/Windows 7 SDK compatible build of Firefox 35.0a1 I was thinking of uploading, but don't know if I should or not.
  12. That pull request actually has conflicts that I can't resolve using GitHub web, and I don't know how to upload anything to GitHub through git.
  13. Arctic-Fox now has an XML parsing error when run on Windows, but is unrelated to Visual C++ 2013/2015 compilation. If I make it work using Visual C++ 2013 update 4, would you still accept the compatibility changes?
  14. 1. I would still like to know more about the "kernelxp" wrapper, and how you're able to get around the EncodePointer, and DecodePointer errors in Windows XP. 2. Minor annoyance: Unless the Visual C++ 2005/2008 redist files are installed in Windows XP, I can't run a version of Firefox compiled with either Visual C++ 2005 or 2008 due to "This application has failed to start because the application configuration is incorrect". Setting WIN32_REDIST_DIR, or --enable-jemalloc didn't solve the problem. Do you know of a way I can build Firefox/New Moon so that I can just bundle the Visual C/C++ runtime files and have the browser load?
×
×
  • Create New...