Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/28/2020 in all areas

  1. That's bad... I mean, putting notifications, fair enough, introducing a banner saying that it will be discontinued, fair enough, but removing the whole archive and putting a time-bomb inside an executable?! I mean, c'mon... I know that they're doing it for security concerns, but honestly, they shouldn't take such an extreme measure, 'cause perhaps I'm not on a machine connected to internet, perhaps I wanna run .swf files locally... Adobe shouldn't artificially block Flash, it should be up to the users, really...
    3 points
  2. 12.0.7601,23471 is also good. That's what I'm using. But I'm struggling with ntdll. Either (or possibly both) the x64 kernel extension rule book is thrown out with this file, or my failure to install a custom signature with signtool from Windows 7 DDK is complicating things (it fails to initialize even without driver signing enforcement). So I decided to focus on the x86 kernel32.dll. There are 26 complete functions in there, with a few more to be added soon. In addition to local DLL redirection, it can be applied to syswow64 folder on x64 Vista and system32 on x86 Vista. Extended versions of shell32 and user32 will also follow soon. Some of the work I've done for this project should help with my Kernel Sanders project for some earlier releases of Windows (which predate the digital signing of system files, making modding even easier!). Like, knowing that Shell_NotifyIconGetRect can redirect to Shell_NotifyIconW will prove useful for the other OSes that also only have the latter implemented.
    3 points
  3. ... Actually, at the time of this writing, DIRECT links from Adobe STILL work, if you know beforehand the correct filename for the .ZIP file: https://fpdownload.macromedia.com/pub/flashplayer/installers/archive/fp_32.0.0.371_archive.zip Surely, that won't last for long...
    3 points
  4. All versions Adobe Flash Player newer than 32.0.0.371 contain a time-bomb. After 12-Jan-2021 local SWF-files does not playback. The latest working version is 32.0.0.371. Use a virtual machine to check. Install the Adobe Flash Player and set the clock to January 2021.
    3 points
  5. Thank you, I do believe that it is an x86 application, that must be the issue. EDIT: I've also made a firefox installer (Version 79.0B9) I opened up the firefox.exe file in CFF Explorer and set the entry point in ntdll.dll from RtlQueryPerformanceCounter to NtQueryInformationProcess and it worked perfectly fine. It runs perfectly! I also credited Win32 in the installer. I hope you find my installer useful Here's the link: https://mega.nz/file/7jRymQYT#FCZXhFv9C8nWLF9hV7AJqGZQ8deh6oh31vBhP3wJSFY Best regards, Looking forward to hearing from you all soon.
    3 points
  6. I just need K32EnumProcesses and maybe another function or two in the x86 kernel32.dll to get the Office 2013/2016 installers to run.
    2 points
  7. ... Well, that was quick of them : five whole months before actual deprecation... Perhaps that expedited removal was a knee-jerk reaction on their part, caused by recently increased batch-downloading traffic on the hosting CDN: https://forum.palemoon.org/viewtopic.php?p=193860#p193860 https://web.archive.org/web/20200630185339/https://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html ... however, expect these web archive snapshots to be hunted down by Adobe, as they do not allow redistribution of their closed-source material...
    2 points
  8. I use https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200725-4d76d4e-uxp-1e0bb1d35-xpmod-ia32.7z on my AthlonXP. (although it says 2020-07-20 in the about window, huh?!) Probably the ones whose name start with basilisk55, i never tried those though. Check the folder list and pick one.
    1 point
  9. @VistaLover Thanks, i got it already. Turns out, that v.29.0.0.171 is the last version for AthlonXP. The next one v.30.0.0.113 needs SSE2.
    1 point
  10. ... Does also work in Serpent 52.9.0/Serpent 55.0.0 ; should also work in FirefoxESR 52.9.x, though haven't checked there, TBH...
    1 point
  11. Yep, as I see it: Vista is a bettered XP, only worse 7 is a bettered Vista, actually better 8 is a bettered 7, only much, much worse 8.1 is a bettered 8, only worse 10[1] is a bettered (and bettered, and worsened and updated, and re-realeased and re-bettered and re-worsened) 8.1, actually better[2][3] jaclaz [1] thanks to continuous updates/changes you never know what you are actually running [2] actually bettering 8.1 is kid's play [3] though there is still a loooong way to get to the levels 7 reached.
    1 point
  12. Yep, which means - as expected - that the issue is not TLS 1.2 in itself (as a protocol for browsing) but rather that the *whatever* system IS3 uses makes use of *something* (possibly actually the IE9 "engine" or "subsytem") and that this latter might need to be TLS 1.2 enabled (and possibly something else), So, back to work. Did you finally manage to install the KB4056564 successfully? AFAIK if your system is 64-bit, then you must have the WOW6432Node, unless the OS has been heavily modified, (and even if you hadn't it before, the update should have added it). Since - reportedly - the update creates the keys in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\ that registry path must exist. On the other hand, if your OS is actuallt 32 bit the 64-bit wouldn't install. The 32-bit version would create the: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2 paths, that you also don't have, so maybe - and for *whatever reasons* the issue is that on your system the KB405654 didn't install properly. Maybe there is a pre-requisite of some other updates? jaclaz
    1 point
  13. Good news. Guru JustOff has released a fork of the "Windscribe VPN" extension. For Pale Moon, MyPal, New Moon e.t.c. https://github.com/JustOff/moonscribe/releases Windscribe VPN service - https://windscribe.com/ Need registration on any email. 10Gb monthly limit on a free account. Checked in New Moon 28.10.1 and MyPal 28.10.0. Works great.
    1 point
  14. 1 point
  15. It should be. Each NT6 system file is applicable to all languages, with the mui files doing the hard work.
    1 point
  16. Awesome! Can confirm that your method is working for me here on 78 ESR
    1 point
  17. Using the W7 versions of mf.dll, mfplat.dll plus msmpeg2adec.dll and msmpeg2vdec.dll (plus my newest kernel32.dll), I have restored H.264/AAC support to newer Firefoxes. You will have to use a tool like CFF Explorer to change the Operating System and Subsystem Versions from 6.1/6.2 to 6.0 before applying these files to your system. The issues facing later releases of Chromium, as far as I can tell, seem to be rooted in RtlFreeOemString's subroutines, which seem to differ between Vista and 7. With this in mind, I may start tampering with ntdll.dll in spite of its lack of redirect-ability and its digital signature (which other usermode dlls lack; but that changes in Windows 8). If I were to start extending ntdll, you would have no choice but to boot with my version and likely have to disable driver signing enforcement (which is how I run my 2012R2 in order to use my GPU drivers anyway). While I'm at it I could add NtOpenKeyEx (which later Chromiums ask for) as well as RtlQueryPerformanceCounter in order to simplify the process of preparing new Firefoxes. And all of those functions that some installers call when running with my kernel32.dll! And maybe ensure that winSAT works when display drivers use my user32.dll!
    1 point
  18. Don't worry about it dude. You can create a video if you like.
    1 point
  19. I am on it. I should have it done by the end of the week
    1 point
  20. Vista SP2's WMF patented decoders (h264/aac), which are installed via the Platform Update Supplement (PUS, KB2117917), have filenames (H.264 decoder is in mfh264dec.dll, the AAC decoder is in mfheaacdec.dll) different to the respective patented decoders already present in Win7 OEM; starting from Firefox 53.0a1, the Mozilla devs have completely removed any support for Vista's WMF decoders, so while e.g. Firefox Quantum 68 may launch under Vista SP2 64-bit with this Extended Kernel (which simply satisfies kernel functions missing in vanilla Vista SP2), it is not instructed in code to search for mfh264dec.dll / mfheaacdec.dll; it does try to locate decoders present in Win7+ (since it properly targets those OSes), but, of course, fails... The only way to tackle this serious shortcoming is if you recompile from source, having first reverted those changesets responsible for disabling Vista's WMF decoders... Related Bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1324183 (and my relevant comment https://bugzilla.mozilla.org/show_bug.cgi?id=1324183#c15 which, needless to say, caused a stir with those damn developers...)
    1 point
  21. Finally got around to trying this today (Firefox Quantum), and I must say this is simply amazing. I'm still in awe that this project even exists, after wishing for it for years. Thank you @win32 for all the work you're putting in. I will definitely have to make a video on this project soon.
    1 point
  22. That is the intention. I do believe that the logon init problems are connected to the random services/explorer having trouble starting. Though windbg hasn't helped at all. Sticking onto a VM with my file causes it to freeze when the boot screen is running. But I've noticed that BSODs ceased after making the wildcard import call RtlGetFileMUIPath, though it still causes automatic reboots. Others to try are: LdrGetDllHandleEx and RtlDetermineDosPathNameType_U, I also noticed that the Vista x64 implementation of LoadLibraryExW was very similar to the one in XP x64 (except for not calling SRWLock functions and some other minor differences), which doesn't have the same problem. Though I'm not sure if NT 5 versions of functions would be a good fit for an NT 6 kernel. Then I looked at the One-Core-API version of the function, where an auxiliary LoadLibraryExW is called in its kernelbase.dll, which leads back to the original one in kernel32.dll. Maybe I could use something like that. In the meantime I added K32GetModuleBaseNameW, K32GetModuleBaseNameA and SetThreadGroupAffinity. This will allow Logitech Gaming Software 9.02 and .NET 4.8 to work.
    1 point
  23. CSS3 did not kill the web. CSS3 SAVED the web. And is saving us from these evil JS frameworks. (jQuery is one of them) Now that most browsers are standards-compliant (Thanks for the new Edge, Microsoft!) we will almost not suffer developing the sites for everyone. I can do things like slide menu, modal, dropdown, carousel, all without JS thanks to CSS3 and some clever tricks. We should all go back to writing vanilla JS and forget about jQuery really... Another thing that is killing the web is Bootstrap and similar frameworks. People now forget how to code a proper website, they just throw a framework at it, a few tags and classes and it's done, call it a day. Now every site I visit was made with Bootstrap and there is simply almost no difference between them. Where's the creativity? CSS frameworks should still exist, but we should do ours not use someone elses framework. I like to think of myself as a creative UI/UX Designer.
    1 point
×
×
  • Create New...