Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/06/2019 in all areas

  1. I will never understand what motivates people to try to appease other people who are disagreeable, arrogant, condescending, and clearly would never reciprocate such efforts. As VistaLover said, full rebranding would not change a single thing about how "upstream" views this project or its users, and those who are now pushing rebranding again are only echoing MCP and Tobin's agendas. Apparently Tobin doesn't even need to come back here again to keep the subject alive. Why would anyone here spend the first second attempting to do anything they "demand?"
    2 points
  2. @Vistapocalypse, I installed the latest version from the site at the moment I reported this. Yes, I have these values in the registry.
    2 points
  3. actually that means I need to setup a redirector in my binary repo in order to keep app.support.* URLs working. EDIT: it seems that I can just create a blog static page for this purpose by setting app.support.baseURL as "https://rtfreesoft.blogspot.com/p/browser-help.html#"?
    2 points
  4. Dedicated to fans of windows XP/2003 running on moderm (Acpi 2.0) PC Main purpose of patcher is help with eliminate/fixing Acpi 2.0 opcodes and 64-bit fields/regions/math without touching bios. Patch modify acpi tables every time when os start, it change current state of acpi tables in RAM memory (Bios load tables from flash chips to ram). Patcher works only with CSM (compatibility) mode, it will never works in UEFI boot mode. Using: 1) All custom files must named in old "8.3" DOS way ! 2) Create folder "ACPI_PAT" at root of you boot drive where installed target OS, this folder is place for storing all custom files (except bootloader) 3) Replace original bootloader (NTLDR for windows 2000/2003/XP, BOOTMGR for Vista/7/8/10, GRLDR for grub4dos) with patcher, original bootloader save as "xpldr" in ACPI_PAT folder 4) Place acpi_pat.img at ACPI_PAT folder 5) Place main configuration file ACPI_PAT.CFG: [DSDT] reload.bin bnum_fix.dif iotr_fix.dif,201904 test1.dif test2.hex [SSDT1] ; patch1 ;SSDT_FI1.HEX [SSDT3] ; patch 3 ;SSDT_FI3.HEX [SSDT*] # universal ssdt patch #SSDT_UNI.HEX [FACS] ;APIC_FIX.HEX [DSDT] [SSDT] - name of acpi table, only 4 chars !!! [SSDT3] - patch 3rd ssdt table, order of the ssdt table is determined by its position in the rsdt/xsdt tables [SSDT*] - special name to modify all ssdt tables ; patch1 - comments start with ";" or "#" reload.bin - BIN override table from binary file bnum_fix.dif - DIF is text format for GNU Patch iotr_fix.dif,201904 - DIF format with forcing iasl compiler version test2.hex - HEX is text format of "Find&Replace" hex strings 6) Order of applying patches is up-to-down, better to place first .bin patch, then .dif or .hex 7) Example of .hex format: ; comment 706869637320/706869637420 ;without spaces 70 68 69 63 73 20 / 70 68 69 63 74 20 ;with spaces, more readable 70 68 69 63 73 20 - hex string to find 70 68 69 63 74 20 - hex string to replace you can increase/decrease count of replaced bytes, size of table will be changed dynamicaly 8) Patcher supplied with 3 versions of iasl compiler/decompiler: IA201604.EXE IA201612.EXE IA201904.EXE These versions are equivalent of 20160422, 20161222, 20190405 at acpica.org Default version for processing dsdt/ssdt tables maded before 2016-12-31 is IA201612.EXE, for later dates is IA201904.EXE. You can also use your own version (DOS VERSION, compile yourself from acpica sources), name it "iaXXXX.exe" and place inside EXE.7z archive on floppy image. 9) Examples of .dif format: Fix BNUM Decompiling Bug: --- DSDT.dsl +++ DSDT.dsl @@ -1,1 +1,0 @@ - External (BNUM, UnknownObj) Fix Resource conflicting on Windows XP for Gigabyte H110-HD2 bioses: --- DSDT.dsl +++ DSDT.dsl @@ -1,36 +1,13 @@ AMI1 = ITA1 /* \ITA1 */ AMA1 = ITA1 /* \ITA1 */ AMI2 = ITA2 /* \ITA2 */ AMA2 = ITA2 /* \ITA2 */ AMI3 = ITA3 /* \ITA3 */ AMA3 = ITA3 /* \ITA3 */ - If ((ITS0 == One)) - { - ConcatenateResTemplate (Local0, BUF0, Local1) - Local0 = Local1 - } - - If ((ITS1 == One)) - { - ConcatenateResTemplate (Local0, BUF1, Local1) - Local0 = Local1 - } - - If ((ITS2 == One)) - { - ConcatenateResTemplate (Local0, BUF2, Local1) - Local0 = Local1 - } - - If ((ITS3 == One)) - { - ConcatenateResTemplate (Local0, BUF3, Local1) - Local0 = Local1 - } Return (Local0) } } } Scope (_SB.PCI0.LPCB) Patches generated by invoking (you can change/remove "-u6" option) Diff : diff -u6 --strip-trailing-cr OLD.DSL NEW.DSL > my_patch.dif Keep in mind that different versions of the compiler generate different versions of the ASL text. So context of .dif file is in most cases bound to specific version of the compiler 10) If using .dif patches, need additional file external.txt this is text format for using iasl.exe decompiler "-fe" option like this: External (AL6F, MethodObj, 0) External (HLVT, MethodObj, 0) External (P0L6, MethodObj, 0) External (P1L6, MethodObj, 0) External (P2L6, MethodObj, 0) External (PS0X, MethodObj, 0) External (PS2X, MethodObj, 0) External (PS3X, MethodObj, 0) External (_SB_.PCI0.GFX0.IUEH, MethodObj, 1) External (_SB_.PCI0.GFX0.GSCI, MethodObj, 0) External (_SB_.PCI0.PAUD.PUAM, MethodObj, 0) External (_SB_.PCI0.PEG0.HPME, MethodObj, 0) External (_SB_.PCI0.PEG1.HPME, MethodObj, 0) External (_SB_.PCI0.PEG2.HPME, MethodObj, 0) External (_SB_.PCI0.XHC_.DUAM, MethodObj, 0) External (_SB_.PCI0.XHC_.RHUB.INIR, MethodObj, 0) External (_SB_.PCI0.SAT0.SDSM, MethodObj, 4) External (MDBG, MethodObj, 1) External (_SB_.TPM_.PTS_, MethodObj, 1) 11) If using .dif patches, may be need additional file ignores.txt this is text format for filter iasl.exe decompiler errors, example of file: [BNUM] Namespace lookup failure, AE_ALREADY_EXISTS Many kabylake/coffelake bioses created with uncorrected asl code around BNUM fileld, when you decompile it, you will get "ACPI Error: [BNUM] Namespace lookup failure, AE_ALREADY_EXISTS (20161222/dswload-390)" error. With ignores.txt possible to filter/ignore these errors 12) When using .bin files, take care about override DSDT/SSDT tables, "template" from BIOS image is bad choice for such files. Bios patch some parts inside table before deploying to OS (bios usualy set absolute adresses). In this case run OS and save tables from runned state. Regards & Copyrights: FreeDOS by FreeDOS Project SHSURDRV by Jason Hood 7zdec by Igor Pavlov/7-zip.org Move by Joe Cosentino/Imre Leber XCOPY by Rene Ableidinger/Eric Auer GRUB4DOS by GRUB4DOS Developers FAT module for grub4dos by chenall.net Volkov Commander by Vsevolod V. Volkov NTFS for DOS by Avira GmbH iASL by Intel/Acpica DJGPP by DJ Delorie CWSDPMI by CW Sandmann inih by benhoyt Internals & Hacks: - acpi_pat.img is bootable 2.88MB FAT12 floppy image with FreeDOS & utils - When pressing any SHIFT key when starting, Patcher will go to debug mode, it will stop loading OS and run shell - Patcher replace original bootloader with grub4dos, when all job is done, patcher run grub4dos.exe for loading original loader - Patcher reserve 2Mb of RAM for storing acpi tables (Windows will report -2Mb available memory) - Before decompiling any table, all ssdt and dsdt tables stored at disk and used as external files "iasl -e ssdt1 ssdt 2 ... " History: v1 - Initial (Beta) Download Binaries https://github.com/MovAX0xDEAD/ACPI-Patcher/releases Download Sources https://github.com/MovAX0xDEAD/ACPI-Patcher
    1 point
  5. Thanks again for investigating this artomberus, as I am not currently running build 6003 and cannot readily investigate myself. If I finally understand this issue correctly, any Server 2008 update that changed the build number to 6003 would have caused Win32k.sys BSODs on Vista systems with Avast/AVG installed - but not anymore! The micro-update is not actually present in the legacy installer (signed in November 2018), but is downloaded automatically - the user doesn't even have to be logged in (see this April article). Edit: I suppose the online installer might supply the micro-update immediately.
    1 point
  6. This is a tough one to solve ; selecting in Serpent 52.9.0 "Help => Keyboard Shortcuts" is, code-wise, contained in: https://github.com/roytam1/UXP/blob/master/application/basilisk/base/content/baseMenuOverlay.xul#L55-L56 <menuitem id="menu_keyboardShortcuts" oncommand="openHelpLink('keyboard-shortcuts')" The code to execute the command is contained within: https://github.com/roytam1/UXP/blob/master/application/basilisk/base/content/utilityOverlay.js#L818-L823 function getHelpLinkURL(aHelpTopic) { var url = Components.classes["@mozilla.org/toolkit/URLFormatterService;1"] .getService(Components.interfaces.nsIURLFormatter) .formatURLPref("app.support.baseURL"); return url + aHelpTopic; } The default value for app.support.baseURL is https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/ so the URL returned is https://support.mozilla.org/1/firefox/52.9.0/WINNT/en-US/keyboard-shortcuts which then auto-redirects to https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly?redirectlocale=en-US&as=u&redirectslug=Keyboard+shortcuts&utm_source=inproduct ... As for the browser.slowstartup.help.url, I merely proposed what appeared to me as a simple (but functional) enough solution, provided @dencorso obliges ; but, since this is basically your PR and your call, you are free to proceed as you see fit...
    1 point
  7. Avast (including AVG) actually ended support for Vista beginning December 1, 2018 (see End of support for Windows XP/Vista), and only promised definition updates for version18.8 or older. However I have been following a thread at another forum that @Stevo might find very interesting, Windows Bluekeep patches causing Win32k.sys BSOD. The OP was running Server 2008 SP2 and using AVG 18, which attracted the attention of Avast representative Peter. On June 4, Peter posted: (KB4489887 was a preview released in March, and was the first update to change the build number to 6003.) It is difficult to believe that Avast would take any action that benefits legacy versions of their free products. On the other hand, this could explain why artomberus had no issues with AVG Free 18.8 in his June 4 post despite running build 6003: Perhaps he was among the first beneficiaries of the micro-update? Still, the only further information I can find relates to business products, e.g. BSOD/Failure to Boot after Installing AVG Business Edition on Windows Server 2008. There is some general information about micro-updates in an earlier article:
    1 point
  8. Thanks @VistaLover. PM has a "slow startup" help page? (FF and Serpent don't seem to.) Do you have a suggested replacement URL? (For app.support.baseURL I was just going to point to Mozilla.) Yeah, I tried both. Actually I tried <install dir>/defaults/pref first, since that path already existed; when it didn't work I created defaults/preferences/ under browser/ but had the same result: it added new prefs but didn't override the built-in ones. It probably depends on the order the .js files are run at startup, with the last file to set a pref "winning." Now I didn't try it with Firefox, so maybe it works there, but we're not changing FF! I tried with both Serpent and New Moon and got that result. In the omni.ja I extracted, there are several subdirectories under defaults/: autoconfig/, pref/, and preferences/. I haven't done extensive testing but at this point it appears the contents of preferences/ are run last; hence, can't be overridden (except by user prefs). It's certainly possible MCP changed the order these run at startup. Or maybe even palemoon-branding.js, which is the one I changed (unofficial branch only, of course).
    1 point
  9. If overriding omni prefs with external pref files doesn't work, there's something wrong. Perhaps the folder path?? Try both locations, the ancient and the new one? Many years ago in Firefox the path for defaults was changed from "Firefox/defaults/pref" to "Firefox/browser/defaults/preferences". By the way the same structure as just seen inside omni.ja Yet here in the forum it keeps me riddling that still the old path gets recommended over and over, but then again, who knows. And meanwhile saw that actually Palemoon builds etc. still do come with the old path in the zip. And quite obviously, so many experienced people here who know 100x more than myself would long since have noticed if the old path wouldn't work anymore! But since now you're saying the external overrides don't work, here's a quick theory: What if perhaps, who knows, the browser still considers both paths as valid, but if there's conflicting content, the values in the newer default path get priority? Regardless if inside omni.ja or outside?
    1 point
  10. No not before every delivery. Just once. Putting the new file into the secret hiding place ;-) where the other independant non-compiled files in prefs folder are coming from too. Those are surely not manually copied every single time either. If the original code gets changed, it will probably get exchanged in the forks too. Then all own fixes are lost if they were embedded deep in the source, and the issue must be investigated again and the fix applied again, or rather gets just forgotten. To me looks like more work not less. Provided of course the fixes are as harmless as exchanging the support URLs in a prefs file. Of course I'm mighty glad of roytams immense work too, it blows my mind, my own browsing depends on him, and basically a single person has to 'save the world' (xp world) in his spare time ;-) No idea how he manages that, but sad enough for the state of the world today. Still just saying that I find it so extremely out of proportion, that a workload of 1000:1 for two people to reach the same goal is today considered as normal. And even as desirable. The prob is that other people are usually not bored to death either, what everyone seems to assume, and have to struggle for their own little spare time. So comparing a minute for a one-time action of copying a file, with the act of learning github, setting up an account, copying a giant mass of files, learning howt to edit and etc. from scratch, it's just so extremely... oh well, not my prob :) (It's just that I'm too forced again and again to waste endless struggling time with stuff that experts could do with a fingersnip, but just don't care, in all areas of life)
    1 point
  11. if you want to save roytam1's time for doing this before every delivery, don't go this way. Not to say of possible problems, if the Moonchilds/Tobins/whoever elses code he forks from gets changed and incompatible with this simple drag'n'drop. So no, if we need to get this changed and help roytam to develop this, forking his github and doing pull request as he asked is the best way.
    1 point
  12. Hmm... but what makes this so hard to understand, seen from the outside (zero clue of confusing source/dev/compiling/github stuff): in the final product there are some pref files hidden inside omni.ja, which has internally the same folder structure, but there are also some pref files freely accessible outside, in the defaults/pref or browser/defaults/preferences folder. Those I can't find inside the omni's, no duplicates. Especially K-Meleon has several files, but NewMoon at least one. They must come from somewhere too? And especially, not being embedded anywhere, and their content not refering any dll's or exe's etc, they look like they don't have much to do with 'compiling', and it would be very easy to just add those in some simpler way - like just drag-drop them there in the final zip? And in that defaults folder they override any hidden prefs in the omni's, so wouldn't matter if those still contain other pref values.
    1 point
  13. For such stuff I simply unzip the 2 omnis and do a text search inside. Instant hit: palemoon.js in browser/omni.ja/defaults/preferences. But wouldn't it be a lot easier to just create a separate little prefs file in browser/defaults/preferences, as was already suggested? But perhaps I'm getting something wrong...
    1 point
  14. The "instagram" issue in UXP browsers (NM28, Serpent 52) has been covered in fine detail in previous pages of this thread, when it first manifested itself ; it's a case similar to player.pl, that is due to new UXP defaults (general.useragent.compatMode.version;60.9), instagram sends JS code the platform can't cope with... The solution is similar to the one suggested for player.pl, i.e. use a SSUAO for instagram that advertises a Firefox < 60.0 version; DON'T touch the "general.useragent.compatMode.version" pref, just create: general.useragent.override.instagram.com;Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0
    1 point
×
×
  • Create New...