
DanR20
Content Type
Profiles
Forums
Events
Posts posted by DanR20
-
-
1 hour ago, mina7601 said:
Actually, where did you get these codecs from? And do I also put them in Firefox 45 ESR's folder?
If the codecs aren't there it's probably using webm vp9. I've tried with a fresh profile and it's the same result, the audio is distorted.
You can get the codecs on the first page of this thread, Roy's got several links depending on the browser. This is the link to the ones I've been using with 45.0:
https://o.rthost.win/palemoon/lav.7z
You put the three files on the root firefox folder where firefox.exe is. You would also need to make sure "media.ogg.enabled" and "media.webm.enabled" are false while "media.mp4.enabled" is true.
2 -
5 minutes ago, mina7601 said:
Hello, which build of Firefox 45 ESR did you use? IA32 build or SSE build?
The SSE build, I didn't try the IA32 one.
Are you experiencing it?
1 -
Testing out today's new 45.0 version the mp4 codecs on youtube don't seem to be working right. At least the sound, the video is coming in but the sound is static. These are the codecs I'm using and were good in the April version:
avcodec-lav-57.dll
avresample-lav-3.dll
avutil-lav-55.dllThe solution for now is to disable mp4 and use ogg/webm vp9.
1 -
55.0 is back, as usual thanks to Roy for all his work. And as a bonus, formhistory and passwords are also functioning properly. :)
2 -
1 hour ago, NotHereToPlayGames said:
Although my Win7 on real hardware may not be of use, I completely disable DEP on all of my machines.
Never considered doing that but it probably would have saved me a lot of headaches.
1 -
2 minutes ago, mina7601 said:
@VistaLover Thanks for the link. Now I know what it is.
Also, I made a mistake here. I thought I was running Serpent 55 (2023-07-15), but it turns out I redownloaded (2023-07-07) again and opened it instead. Therefore, that's why it didn't crash for me, so I spread misinformation
Ok, so I had to go to https://o.rthost.win/basilisk/ to download Serpent 55 (2023-07-15) myself (since roytam didn't announce there's a new version here in this topic, and I download a new version every time it is announced here in this topic), I opened it, and can also confirm @DanR20's findings about Serpent 55. Sorry @DanR20 for the misinformation!
Yes, I can confirm your words too. Here is a picture:
No problem, I should have mentioned it was today's. Last week's runs perfect.
2 -
19 minutes ago, AstroSkipper said:
But running the most recent version of Serpent 55 (2023-07-14) from today, basilisk.exe is crashing in the module mozjs.dll at startup such as @DanR20 already reported. Here is a screenshot:
Cheers, AstroSkipperThanks for reporting, glad I'm not the only one.
3 -
Tried in XP and it's crashing there too. Also added Basilisk to Data Execution Prevention and attempted Safe Mode but both failed.
3 -
6 minutes ago, mina7601 said:
I'm on the win32 build.
My guess is it's OS related. I'll try it in Windows 10.
Here's the full crash report:
Problem Event Name: APPCRASH
Application Name: basilisk.exe
Application Version: 4.0.4.8577
Application Timestamp: 64b170e7
Fault Module Name: mozjs.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 64b0ca02
Exception Code: c0000005
Exception Offset: 002de536
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e7893 -
14 minutes ago, mina7601 said:
Must be something else going on, I downloaded it twice just to make sure and it won't start. I'm on Windows 7 so possibly it's related to that or drivers within the OS. The previous week's build works fine so I've gone back to that version. Same with 52 and the formhistory issue.
Are you on the win64 or win32 build? I'm using win32.
2 -
Several bugs with today's versions. Serpent 55 won't open, it's crashing at startup with the Fault Module Name: mozjs.dll. Tried with a new profile.
In 52.0 I can't get formhistory to work in text boxes or passwords. This was always a problem on and off, if it didn't show you could re-boot and that would usually fix it but today it's not coming in at all.
3 -
8 hours ago, roytam1 said:
a missing follow-up is pushed, and will be available in next build.
for the time being you can do it yourself:
- open omni.ja with winrar in application's folder
- goto omni.ja\chrome\toolkit\content\mozapps\extensions and extract extensions.xul (better keep this window opening)
- edit extracted extension.xul, following https://github.com/roytam1/UXP/commit/7c4d0444bd58b0726a2448e294738c1a7df3d298 to remove lines and save file
- drop edited extensions.xul back to previous window to update omni.ja
- start serpent
That worked perfectly. Had to deoptimize omni.ja first to make the change but that fixed it.
2 -
@roytam1 : It's probably caused by UXP #21 and the commits by FranklinDM you backported to our tree... NM28 behaves fine, because it uses the (old) TychoAM those commits target, but "our" Serpent 52.9.0 (unlike the official Basilisk 52.x.x.x) still uses the WebExtensions AM and thus broke
; so, those commits would either have to be reverted for St52 or somehow modified to accommodate St52's WE AM
...
The only two WebExtensions I use are simple-translate and Enhancer for YouTube. Thankfully they're still functional and working despite the about:addon page error.
0 -
In Serpent/UXP I'm getting this error with the about:addons page:
XML Parsing Error: undefined entity
Location: about:addons
Line Number 392, Column 19:Anybody else seeing this? It's fine in Serpent 55.
3 -
Ok dumb question, haven't been around in a while but what is v141, is this a Mozilla browser? The Serpent 52 versions haven't been updated lately, is that finished? I did catch some posts about C+ which could affect its future development.
0 -
If you have the hard drive space then it's worth considering adding an extra boot so that you'd have Win10 and 11. I may install it that way if it's still possible to bypass the requirements for Win11 but to be honest I'm not in any rush considering that Win10 seems to have stabilized pretty nicely in the last year.
1 -
Roy, the crash is fixed here in 55.0, thanks for all your work.
1 -
3 minutes ago, NotHereToPlayGames said:
Unless you are talking about two of the same programs running on the same monitor, then those can't be separated and diplay next to each other even if not opened in that order.
Correct and that's why I dreaded upgrading because it took a third party program to restore usability that Microsoft would always break. There are a few others as well.
2 -
3 minutes ago, NotHereToPlayGames said:
My taskbar only "groups" if the taskbar is completely full.
My taskbar(s) are never completely full because the taskbar icons only show up on their active monitor.
I can have close to FOURTY programs all running at the same time (and often do) and my taskbars still don't run out of room.
Is this Windows 10? If you're using XP it was easy to keep programs separated but from Windows 7 on the programs were grouped so if you opened two instances of the same program (like Winamp) you couldn't separate them. Taskbar Tweaker restores that ability. But it has other features as well like restoring the right click menu to minimize. I haven't even got to the nightmare of Win11 yet and thankfully won't have to for a while.
1 -
3 hours ago, yoltboy01 said:
I don‘t agree with this.
I am very glad that Windows 10 didn‘t stay in that 2015 aesthetic till now and that they kept it‘s developed active. If you compare 1507 to 2004, you will notice how much things evolved and got better. I‘m also a big fan of the newer Start Menu and the Fluent Design System
Even if you agree with some of the feature upgrades did it need to be twice a year? Literally with each one the last three years Taskbar Tweaker would break. It's a wonderful program that undoes Microsoft's forced taskbar grouping nonsense. Fortunately, the developer kept up with it .
1 -
8 hours ago, roytam1 said:
it hits a code path that it shouldn't (as it should be handled in IonControlFlow, not in IonBuilder) so it needs more investigations.
A temporary workaround: disabling javascript.options.ion stops the crash.
2 -
16 minutes ago, Saphir said:
No crash here in New Moon 28
It just seems to be happening in Serpent 55.0 only and only if javascript is on. Probably other sites are affected as well.
1 -
Spectrum is coming in again so it continues to get better.
There is a crash with this site using Serpent 55:
http://www.legacy.com/news/celebrity-deaths/notable-deaths?affiliateId=1859
The failure is with mozjs.dll. The last April 15th build was good so it just started. 52.0 is no problem.
1 -
3 minutes ago, legacyfan said:
unless you use ltsc which all.of those have combined at least until 2030 at most
Quotemina7601 said:
Well, who knows if we will get an extension or not for Windows 10, but it would be great if we got an extension, considering Windows 11 is still crappy., and Windows 10 is still used the most.
Just a hunch but given the difficulty for many to even upgrade to Windows 11 Microsoft will provide at least a three year ESU extension like they did for Win7. They're making security patches for it well past 2025 anyway so it would be a chance for them to make more money.
2
My Browser Builds (Part 4)
in Browsers working on Older NT-Family OSes
Posted
Thanks for confirming and I agree it is an ugly sound.