Leaderboard

Anyone who sees the light at the end of this tunnel...is seeing another train.

This is a very interesting and needed project for all 10 users, still on development, but so far: See the project on Github: https://github.com/DavidXanatos/wumgr/releases/ Build using .NET Framework 4.6.0 alacran

In either New Moon (28.2.0a1) or Serpent 52.9.0, open a new tab and load about:config?filter=release Right click app.releaseNotesURL and select Modify (or the equivalent translated string if you're using a langpack in NM28); in the popup that opens, paste in the entry field the following URL: http://rtfreesoft.blogspot.com/search/label/browser Hit OK button and, optionally, restart browser... Now, when you go to about: (in a tab) => release notes or Help -> about New Moon -> (popup opens) Click Release Notes (botton right) a new tab will open to RT's Free Soft: browser , which has all the (latest) links you want (and even links to previous builds) (An even more elegant solution would be to just bookmark above URL! )

... If you're referring to the LAV filters : as stated, those are NOT NEEDED for either NM28/ Serpent52 ; these browsers, built on the UXP platform, have a different implementation of being able to play back media files with patented codecs (h264/aac) : they do not rely on LAV filter .dlls but use a modded version of the ffvpx library; this is on XP, where system decoders are unavailable - on Vista+, they can also use system decoders via Media Foundation framework, but I'll have to ask @roytam1 which decoders have priority there (WMF | ffvpx) when both are available to the browser (media.wmf.enabled;true, media.ffvpx.enabled;true)

i've been using wumt since it was released as that has a simple disable auto updates setting. wum looks good, didn't know someone else had made one, seems like it's got a few more features but still nice and simple. wumt hasn't been updated since dec 2016 but still works.

See this topic, this may help you: alacran

October 2018' updates are out! Direct links for WES09/POSReady 2009 updates (7 updates, English only), IE8 cumulative security update (English), Office 2003 security update and Office 2007 compatibility pack security update (international) http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/09/windowsxp-kb4458008-x86-embedded-enu_abc9e19593fcbcf30212a77493af05b144da8bb6.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/09/windowsxp-kb4462935-x86-embedded-enu_b5de399aa37284c81ca1e26ffb93893db035ec17.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/09/windowsxp-kb4462987-x86-embedded-enu_2ca3c3b7b4e2f9bee24af4e46eeb7e4624aabd3d.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/09/windowsxp-kb4463103-x86-embedded-enu_1d7cc48a7f1902bdd5953a1ab980db5832631339.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2018/09/windowsxp-kb4463361-x86-embedded-enu_794ed7af98b2db86a97d4fe3e2d6e45f739e21f7.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/09/windowsxp-kb4463545-x86-embedded-enu_2ef9f04e3467ca43b77de3ea7b96b847886a9f48.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/10/windowsxp-kb4463573-x86-embedded-enu_b0e76ad95da29d0ce8ba122a6b703660b93ed49b.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/09/ie8-windowsxp-kb4462949-x86-embedded-enu_1d397f10668187defcc5126c952d70db36f20abe.exe http://download.microsoft.com/download/9/6/7/96748D39-1846-4B5D-A887-00A1FA1F2C29/office2003-KB4092464-FullFile-ENU.exe http://download.microsoft.com/download/2/5/B/25BCBA66-02A1-496F-B372-53F07A3A89BB/ogl2007-kb4092444-fullfile-x86-glb.exe

In the United States, there are signage on or near existing 4G or 4G LTE transmitters, it looks like this: An actual (stock) photo example: https://c8.alamy.com/comp/B6P4B3/a-sign-warning-about-radio-frequency-fields-B6P4B3.jpg The statue that the sign claims to be in compliance with is this, but as with all law-speak, I can't really see where it says a sign is required. https://www.law.cornell.edu/cfr/text/47/1.1307 Addtionally, here is the section with technical details regarding Maximum Permissible Exposure: https://www.law.cornell.edu/cfr/text/47/1.1310 Safe distance isn't determined by any specific number, or general guideline. It wholly depends on the equipment, the power, etc. So the distances can vary greatly. I found a slide from a presentation that breaks down one company's approach to the different measurements and which type of signage to post. But these values only really exist within the same height of the transmitter. If you want a visualization of the general un-safe area, look up Fresnel Zone. As long as this area does not overlap with places where people are, there shouldn't be any issues in regards to health due to to the power in the air. The system is not designed to transmit to the ground, only through the air. As such, it is expected that even directly below the transmitter, any measured readings should be well within the safe zone, same as existing 4G and older setups. So the telecom company would only be able to put transmitters above houses. In my neighborhood, they would be fine to put them on the TOP of telephone poles because the heigh of a telephone poll is taller than the houses on my street. There are no three story or taller buildings. However, if they are placed somewhere between the top and say... the middle, this would put the 2nd floors of almost every house in the neighborhood into the broadcast zone and then that would be a real problem. I have seen some research on existing consumer 5G transmitters, and it seems there is around a 100 yard (300 foot, idk about meters) distance from the broadcast point in line of site to fall below that 20% example shown in the slide above. Of course, consumer transmitters and the ones used by telecoms may be totally different. More reading on this subject in general: http://hps.org/publicinformation/ate/faqs/cellphoneqa.html

Well, for the moment it seems like the first observed effect of 5G is the firing (after more than 30 years BTW) of John C. Dvorak from PC magazine, JFYI: https://medium.com/@dvorak/5g-got-me-fired-ce407e584c4a the actual article has been removed from the India version of PC Magazine too (please note the 403 and not the 404): https://in.pcmag.com/opinion/124983/the-problem-with-5g here it is via Wayback Machine: https://web.archive.org/web/20180823130336/https://in.pcmag.com/opinion/124983/the-problem-with-5g jaclaz

Adobe Flash Player 31 Final channel has been updated today to 31.0.0.122 (working on Windows XP SP3) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/31.0.0.122/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/31.0.0.122/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/31.0.0.122/install_flash_player_ppapi.exe

KernelEx core update 4.5.2016.18 (beta) - KexBeta.18.7z 206.93 KB VKrnlEx.vxd - System driver KernelEx.dll - Core logic Kexbases.dll - API extensions (Shared) Kexbasen.dll - API extensions (Non-shared) KexCOM.dll - COM extensions Sheet.dll - Property Sheet Handler ApiLog.exe - Debugging console ApiHook.dll - Debugging support Verify.exe - Verify installation is working. Core.ini - Settings for KernelEx.dll LZDLL.reg - Registry support for six missing (98/SE) DLL's LZDLL_ME.reg - Registry support for four missing (ME) DLL's API-MS-Win.reg - Registry support for Win7 API sets 1) Exit Windows or reboot to DOS. 2) Copy all files except KernelEx.dll to existing KernelEx folder. (Kexstubs users: edit Core.ini [BASE] contents= line here.) 3) Reboot to Windows. 4) Run Verify.exe 5) (Optional) Add registry entries as needed. More updates are already nearing completion: Ktree, Kexports; SList, SRW, PowerRequest. Specific API requests welcome.