Leaderboard

A number of Jetpack SDK extensions can be force-installed (but non-guaranteed they'll function as designed) in NM27 via the Moon Tester Tool extension (v1.0.2 should be preferred in NM27, because it also supports Firefox Complete Themes and Mozilla dictionaries ; both were dropped in recent Pale Moon 28.1x.*/29.0.0a6, thus latest MTT 2.0.1 also axed support for those... ) https://repo.palemoon.org/MoonchildProductions/UXP/issues/120 was the upstream UXP issue that tracked this for the transition Pale Moon 27/Tycho -> Pale Moon 28/UXP

Hello gents! Very happy to report that after following this thread I have sound working in Win98SE on a HP 6710b laptop with Microsoft UAA (8086 27D4) and Soundmax AD1981HD (11D4 1981) on board. This laptop also has an Agere HDA modem attached and strangely the hdacfg.ini is registering this device as the codec.. I assume im not playing through the HDA modem codec as it sounds great! I typed up and rejigged the AD1984 HD HDAICOUT.HDA from DEOMSH's diagram to suit the widgets on the AD1981 but still no sound. I downloaded the HP manufacturer driver for the AD1981 and checked out the WDM inf to find verbs in there specific to this laptops configuration for the codec!! In this case I was trying to set mono out as the mixer by setting '00' after the '701' connection select verb. The inf file showed this set as '03' which worked! - 03 is the DAC I assume? as NID03 is the (only) DAC on this codec along with an S/PDIF on NID02. I found these 3 verbs - Set LineOut, HP and Mono out to the same initial levels (-3 dB) Whilst Lineout and HP used the '3B0' Amplifier gain/mute verb to set this, Mono out was set by '71F' verb - Config Def byte 4 (31:24) to '41'. - Still learning my bits and bytes so I have no idea what 41 means or how to calculate/find it other than the inf, but it works at full blast! Going to add some more to the HDAICOUT tomorrow and test with the volume control app. - To note the laptops volume button did not change levels (yet) but the mute button worked. Thanks very much to Deomsh and all of the testers on here for all of this great info! I will post back with any more updates. Side note: The laptop has an Intel 965GM video chip and is being driven by a patched version of the SVGA driver (1024x768x256) that was for Win3.1 \m/ Cheers!

I am going to come out and show what I referred to as project SUBJECT CLASSIFIED in the past to some people: People are starting to ask for newer programs to run on 7 and application compatibility is starting to collapse for the OS as well (though many of those incompatibilities remain truly forced for now). So a week ago I decided that it was about time to start a proactive response to the impeding avalanche (July 2021 or whenever Chromium is supposed to kill 7 support, and possibly .NET 5.0). In the four months working on Vista I learned many things which I will apply to this project. I had no idea what I was doing when I started this in mid-June, though after five days I realized what was necessary to get new applications running! Will it be difficult for me to manage the extension of four separate operating systems? Well, I think we will be back down to two in a few years as x86 slowly dies and the sources of our collective grief go x64 which is a considerably easier platform to expand on. Qihoo 360 is definitely ready...

8 bits = 1 byte (old, not S.I. !). Verbs use hexadecimal values for addressing and for payload of the commands (values of set/get commands are given by Intel's High Definition Audio Specification ) In a verb "41" means: 4 * 16^1 + 1 = 65. But datasheets use bit-values. 4 lower bits [27-24] calculated as such: 0001 = 0 * 2^3 + 0 * 2^2 + 0 * 2^1 + 1 * 2^0 = 1 4 higher bits [31-28] calculated as such: 0100 = 0 * 2^3 + 1 * 2^2 + 0 * 2^1 + 0 * 2^0 = 4 Lower and higher bits together gives "41" in hex. The reverse is also easygoing, but not needed if the datasheet is available. 4 bits: highest number = 15 = F in hex, so 8 bits gives hexadecimal numbers from 00 up to FF (0-255 decimal), but counting to fifteen is all what's needed (most at the time).

This does not work since october or november (can't tell exactly) 2019.

Need to edit the post, figured out it was an addon I had installed. For the tabs, you need to right click the address bar, the area between the buttons and the urlbar works, then select tabs on top, which is the second option from the bottom

though you need the 32bit runtime for 32bit programs and the 64bit runtime for... you know.

You need x86 variant in this case. This looks like an oversight though as runtime libraries are supposed to be bundled with the browser, so roytam1 should add the missing vcomp120.dll. I personally delete all such runtime DLLs from programs' folder and let them use the ones installed system-wide. Some, but not all Firefox browsers' dependentlibs.list file contains those DLLs' names, they should be deleted from it to avoid "Couldn't load XPCOM" error after deleting the DLLs.

I don't think THEY'll bat an eye. "Download more RAM"? What an immature response. So unless you want to build the entire browser from source yourself, roytam1's fork is probably going to be the most accessible option in the future. You also get some bells and whistles that the upstream dropped, like early WebExtension support. It might be a bit slower in places, at least theoretically, due to usage of critical sections instead of SRW locks. Maybe roytam1 could implement runtime check in the future, use SRW locks if available and critical sections otherwise. Some folks run Vista and they could benefit as well since Vista already supports SRW locks. When the time comes, I'll make a switch.

I'm not generally a huge fan of "benchmarks" because they focus too much on graphics and I don't do a lot of videos or YouTube. But here's one that touts to focus on "the responsiveness of web applications" - https://browserbench.org/Speedometer2.0/ Below are my results on an i7-4770 running XP x64 (I run 32bit browsers even though on a 64bit OS) [higher numbers are better], "mileage may vary". NM27 27.6.0a1 (2017-10-29) == 36.6 +/- 0.39 NM27 27.9.7 (2020-10-23) == 36.3 +/- 0.47 Arctic Fox 27.10.2a (2020-10-23) == 36.3 +/- 0.67 Mypal 28.2.2 (2018-12-12) == 27.2 +/- 0.64 Mypal 28.14.2 (2020-10-13) == 28.86 +/- 0.25 BNavigator 0.9.7559a1 (2020-10-09) == 27.5 +/- 0.31 Basilisk/Serpent 52.9.0 (2020-10-23) == 27.28 +/- 0.15 Chromium 49.0.2623.112 (2016-12-24) == 59.8 +/- 0.81 Chromium (Advanced Chrome) 54.15.5320.0 (2017-10-29) == 51.6 +/- 1.3

removed

Welcome to MSFN! Glad to have you here!

@i430VX I updated my Roytam1 installer scripts to account for: 1) Hostname changes (breaking) 2) MailNews directory renaming (breaking) and a few more things. Now, everything works as expected again. I also found other issues with the script I hadn't found before since I don't use the other programs. Those are fixed now to the best of my knowledge. CHANGE LOG: Last updated 2020-10-24 with following patches: - Hostname changes and MailNews rename fix - MailNews directory renames to match repository - Borealis to bnavigator dir renames to match repo - Created Borealis directory creation script (previously missing) - Fixed inherited K-Meleon Goanna directory inconsistencies and script issues - Fixed inherited Firefox 45 SSE script issues Latest revised scripts can be downloaded at the top of the page here: https://w2k.phreaknet.org/

You shouldn't hold your breath on getting a direct reply. Roytam offers SEVENTEEN different browser builds if I counted correctly. You need to find one that "balances" most of your needs - you will NOT find one that meets "all" of your needs. It took TWO YEARS for an "about:permissions" bug to get 'partially' fixed in NM27. I personally hold the view that a "patch" applied INCORRECTLY actually INTRODUCES security vulnerabilities. That didn't stop people from using NM27 during those TWO YEARS. We do have a "large following" here that FALSELY thinks they are "secure" just because they update their browser 'weekly'. That is NOT meant as any disprespect, so to speak. We all have differing perspectives on "security" - 'to each their own' :)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20201024-355db4de-uxp-3b224b2b2-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20201024-355db4de-uxp-3b224b2b2-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom-older * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20201024-id-eed0566-uxp-3b224b2b2-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20201024-id-eed0566-ia-41157bf-uxp-3b224b2b2-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.6.win32-git-20201024-14a9355-uxp-3b224b2b2-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.6.win64-git-20201024-14a9355-uxp-3b224b2b2-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.6.win32-git-20201024-14a9355-uxp-3b224b2b2-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20201024-3743f00d8-uxp-3b224b2b2-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201024-3743f00d8-uxp-3b224b2b2-xpmod.7z Official UXP changes since my last build: - Issue #1643 - Follow-up: Ensure we properly clear our pointers when the Presentation of a document is destroyed. (87c4c77ad) - Issue #1668 - Part 1: Implement support for caret-color property. (8e3832bac) - Issue #1668 - Part 2: Visited color and auto support for caret-color property. (1fc996152) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP into caret_color (95b4e5084) - Merge pull request #1670 from athenian200/caret_color (23a30020d) - Issue #1671 - Unprefix ::-moz-selection (5072843ee) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (e8ae76d47) - [DOM Fetch] Improve stability of Fetch API. (3e5962331) - [DOM Fetch] Detect broken pipes and propagate that write error to the caller. (33a402947) - [DOM] When failing to create a channel and an image request, make sure to set the image blocking status appropriately. (3b224b2b2) Official Basilisk changes since my last build: - Switch submodule to new repo location (14a9355) Official Pale-Moon changes since my last build: - Remove protected branding from the tree pending rewrite. (bccd610f4) - [branding] Stop relying on includes for unofficial branding. (43cfe0708) - [branding] Make unofficial branding fully independent. (c4b3179b9) - Update blocklist (704679438) - Switch submodule to new repo location (3743f00d8) My changes since last build: - skipped branding and blacklist related commits

Version 20.09 Microsoft removed the Windows Server 2003 Service Pack 1 files from their server, this affects the xpramboot option of GWT. It now will download the bugged SP2 version, see first post for an xdelta3 patch to get the desired SP1 setupldr.bin

@sweaterfish Nice you have taken interest in Watlers Win3x HDA-driver and trying to use it in Windows 98SE. I will try to support your Quest! Many desktops will run out of the box, especially the one with Realtek codecs, but success depends on the HD-Audio controller too, used by the specific chipset. Which steps are needed is not always to say beforehand. Once I had the idea to make a list of 'all' codes with their values for SleepingWidget=$.. & VolumeWidget=$.. & OutputWidget=$.. but without a community of testers I think it´s a waste of time. You´ve already done a great deal of work on your Thinkpad X61 - no installation problems, great! Once HDACFG.INI is set, following values can be changed (apart form setting [busmaster]-values): Mytimer= values 1 (default) or 0; Mytimer=0 needs HDARUN.EXE to produce sound (not needed in your case, as Sound recorder is playing) Verbinterface= $1 (default) or $0; two different ways to communicate with the codec through the HD-Audio controller wait1= value $100 is default; can be set higher if sending verbs to the codec needs more time wait2= value $100 is default; can be set higher if receiving verbs from the codec needs more time pcipatchB=$0000; changes ONE register of the HD-Audio controller PCI-register - up to $FFFF (changing register 100h is NOT possible) SleepingWidget= value $02 (default); powers up one widget, can be needed on Laptops VolumeWidget= value $14 (default); set the widget number that will set Volume - can be a DAC, a Mixer or even a PIN-widget OutputWidget= value $02 (default); set the widget that will receive Digital Audio from the HDA-link and convert to Analog Audio (DAC) - SP/DIF sends Digital Audio to output, not of interest for us. The three widgets are the most important settings. In that case their are more Audio Devices in the system, like modems or audio for HDTV. In that case their CODEC Index will show a higher value than $0 (cannot be set as far as I know) In case of reading a datasheet the most important part to start is the widget Function Block Diagram. The AD1984 gives this on page 1, but their numbers/interconnections in Table 5 on page 16! So read them together. Best is to try the simple stereo-channel, so DAC-0 => Mixer => Port A. Table 5 tells the DAC-0 is widget 03, connected to Mixer 07, connected to PIN-complex 11. According to Parameters on page 5, the DAC´s have output volumes, the Analog Mixers only input volumes. So I guess best to try is: SleepingWidget=$03 VolumeWidget=$03 (otherwise $07 but not likely) OutputWidget=$03 To use INTELHDA.EXE first study Intel´s High Definition Audio Specification http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/high-definition-audio-specification.pdf Chapter 2 and Chapter 7 both in depth (and a quick reading of Chapter 4 to have a global understanding of the difference between the two interfaces CORB and Immediate Command). I have never heard of this, can be some problem with the HD-Audio controller. First let´s neglect this and try the suggested HDACFG.INI settings and use "Restart in MS-DOS mode", in this stage please without HDAICOUT.HDA. Listen with Headphones if you hear the slightest tick´s or click´s during all bootup stages. Please report back and upload HDALOG.TXT and the version of HDACFG.INI after returing from MS-DOS mode.

I'm trying to set up Windows 98SE on a Thinkpad X61 and as I now gather is to be expected, I'm not getting any sound. This thread seems like the most promising thing I've seen anywhere, so I want to see if we can generalize this success a little. From what I understand at this point, though, every single audio device could potentially require unique troubleshooting. Is there any chance we can come up with some step-by-steps in this thread that allow people to do it themselves? My Thinkpad X61 has an Analog Devices AD1984 sound device running on Intel HDA (there's a datasheet for the AD1984 available here). Using the GENHDA16.INF deomsh posted on the first page of this thread, I've installed HDA2.DLL from HDADRV9J and added HDATSR.EXE to my autoexec. This seems to work okay. One of my unidentified PCI Cards in Device Manager becomes a High Definition Audio Controller and an HDA Sound playback option appears under Multimedia Properties. HDALOG.TXT and HDAcfg.ini are also generated and so is HDAICIN.TXT if HDAICOUT.HDA is present. See my attached files for what these look like on my system. I can open WAV files in mplayer or sndrec32 and they appear to play, but I get no sound. Not through the laptop's internal speaker or through the headphone jack. I think this is "The Sound of Silence" as deomsh calls it, so I tried changing the volume or playback widgets listed in the HDAcfg.ini. I don't really understand what I should be changing them to, though. According to the datasheet for the AD1984, I have Audio Output widgets on nodes $02 (S/PDIF DAC), $03 (DAC_0), and $04 (DAC_1). Are these what I want to put into HDAcfg.ini? Or do I actually want to use the "Pin Complexes," which are $11 (headphone jack), $12 (line out), and so on? Or something else altogether? I've also tried using INTELHDA.EXE from this post, which seems like it should be a super useful program if only I could understand it. At least it confirms most of the widget info from the datasheet and I can also use it to see that node $12 is my laptop's internal speakers and that node $11 sees headphones when I connect them. INTELHDA.EXE also suggests that maybe (?) there's another Audio Output on $01. So all I've been doing so far is just testing all sorts of combinations of these node values in the HDAcfg.ini, but I haven't come across anything that produces any sort of sound. I definitely don't actually know what I'm doing, though, and there's lots of combinations to try. Some advice about what these widgets are supposed to be and how to identify the right nodes from either a datasheet or the "widgets" tab from INTELHDA.EXE might be useful and allow more people to troubleshoot their setups. One other oddity I've noticed on my system is that when I cold boot Windows, HDALOG.TXT shows nothing is returning and the CODEC section of HDAcfg.ini is all zeroes, but if I "Restart in MS-DOS mode" and then return to Windows using an EXIT or WIN command HDAcfg.ini does seem to populate correctly. The log and cfg files I'm attaching here are what I get after doing that. With a cold boot, HDAcfg.ini has CODEC BITMAP=00000011, CODEC Index=$1, and all the other CODEC lines are zeros. This seems to be some sort of failure, I think, right? I'm actually "cold booting" Windows 98SE from GRUB4DOS, so I don't know if that's part of the issue or what. Any advice or feedback would be much appreciated. It would be amazing to get sound working in my 98SE install, especially since it's otherwise working very well. HDALOG.TXT HDAcfg.ini HDAICIN.TXT