Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/09/2021 in all areas

  1. These days many MSFN members read that many modern browses have blocked some ports to prevent NAT Slipstreaming attacks. For members who want to learn more: https://www.bleepingcomputer.com/news/security/google-chrome-to-block-port-554-to-stop-nat-slipstreaming-attacks/ If we want to take as an example the ports blocked by Google Chome these are: 69, 137, 161, 554, 1719, 1720, 1723, 5060, 5061, 6566. But are our browsers protected too? I did some testing with my NM28 and the answer is yes. For those who want to do a simple test: http://example.com:554/ or https://example.com:554/ Example of what we get on the screen: I ran all the blocked port tests in Chrome but unfortunately Pale Moon decided not to block port 69. To block a port: If our needs require that a locked port be reachable: about:config new string network.security.ports.banned.override
    2 points
  2. On the contrary , it was interesting to know what other people feel today/felt back in the day. You can always share with me. Yeah , lots of emotions , I agree , though I'm not emotional myself and even I always remember that times like it was something from some other world (in a good sense). So you're from the late 90's period .... I skipped that part completely due to the worsened music . I started as an ordinary DJ in the early 1994. Later I had a small club of my own, but the music/style just went bad , the club had became flooded with junkies , I fed up with it and quit in 1996 , I think it was November - December . I'm not sure why , but it wasn't the case in 1994 , people became different ? I dunno . Trance ... yeah , right : 1997 it's when the trance began to kick in (without me) xD . But, yeah , there are some good trance things , I just prefer the older ones . In 2012 I started clubbing again, mainly because I wanted to find a yonger GF (sorry for a slight off-topic) , well I succeeded , sorta ... 'cause somewhere in 2018/19 I felt the urge to find a younger GF again , but this damn "virus" began and all those restrictions , so I'm kinda in your shoes , I try not to go out without the real need , etc. Back to 2012 , I just tried to ignore what was played , of course it was nothing like the 90s and it will never be. Yeah , I miss that times , and I miss my Roland JW-50 !
    2 points
  3. You missed out VistaEX :) Yeah Dixel, I miss dancing in the clubs in the late 90's to the music ... oh the days when I was young and fearless. I would stay out in the clubs till 4AM in Greenwich Village ... drive home (I don't drive now) and do it again the next day. NYC was hot then, a bit risky, but nah, I didn't care. Now; come 9PM, I'm in my pajamas and enjoying camomile tea preparing for bed at 10 LMAO Oddly enough (I'm very odd Lol) I did enjoy some "Trance" music ... haha ... but it was getting too loud after a while and I got out of the club scene totally about 2001 and cleaned up my act; regrettably for me, that meant going into rehab, so I revisiting that music is somewhat of a "trigger". Now, I'm very much a 'homebody' Sorry if I I got carried away here, just a lot of emotion(s) - some good - some not so good.
    2 points
  4. Advance Notice: since there is no sufficient changes from upstream, there will be no UXP based build this week.
    2 points
  5. The best dance music in this genre (dance , techno) existed only for a short amount of time . Somewhere between 1991-1994, maybe early 1995. It was fast and catchy , but not too loud to the point of complete distortion . Everything after 1995 sounded too flat and loud (loud not like "good" loud , but like an overload). Why ? Maybe it's because they began to use notebooks instead of real recordiing studios, maybe the governments decided that the music was too cool and people spent too much at the clubs instead of having children and constantly working. But it is a fact . You can listen for yourself and compare . Though , I would advise to use a real Hi-Fi/Hi-end system and cd-s. P.S. It was just dance, yes , exactly that - simple "dance" or "techno" , not this ugly new term "Eurodance" that surfaced in 2000s. I totally understand that the 99% of that kind of music came from Holland (yes , it was Holland , not "The Netherlads), Germany , Austria , Italy , Belgium , Denmark and some other Western European countries , but this term "eurodance" just doesn't sound well . For those who don't remember , try to listen to the albums mostly from 1992-1994. 2-unlimited (Holland) , Masterboy (Holland), LaserDance by Erik Van Vliet (Holland), U-96 (Germany), Mo-Do , (Germany) , CAPELLA (Great Britain & Italy) (why in caps ? , it's a marvel , but no later than early 1995), Technotrax (many compilations came out under this name) , F.M. Present Jean Jane , Einstein Doctor DJ. If someone's interested , I can surely suggest more . And the special : Red Zone (Sega) game soundtrack by a super talented Danish composer Jesper Kyd. This game and music is not advisable to watch/listen for some members with the "modern" point of view, dictated by the modern media , esp. who thinks it's "their own opinion" , as it may hurt their feelings , since the game is from the good ol' days when we all knew who the real enemy is. This warning here is obvious , just do not watch and ignore . If someone will start off-topic political conversations , I will just block/ignore . Respect and be polite. All have a nice day/night.
    2 points
  6. WinNTSetup - a simple but powerful universal Windows Installer Features: Install (unattend) Windows 2k/XP/20??/Vista/7/8.x/10/11 x86/x64/arm64 Practically runs even on the most minimalistic WinPE selectable drive letter for the new Windows installation Fully automated with save/load setting in ini file and various command line options Install Windows also if nlite/vlite has remove winnt32.exe/setup.exe Integrate Drivers: normal PNP and Textmode Drivers Patch uxtheme to allow unsigned Themes Some common registry tweaks and *.reg file import DISM APPX removal, feature enable/disable Simple VHD creation and Installation Support "Windows to Go" for Windows 7 and later installs Supports WimBoot and CompactOS option for Windows 7 and later Supports all current WIM files: WIM/SWM/ESD and ISO files WinCapture - capture a Windows installation to WIM or ESD file MinWin - simple trimming WIM in memory before apply WinCopy - copy an existing Windows installation to another partition Offline Hotfix uninstall Offline password reset Not Supported: - No Windows embedded version (this includes WinFLP) - No upgrades of existing installations About driver installation: Every driver added in NT6.x windows will be added to the driver store. So it's not recommended to add countless driver, but rather more really required ones. NT5.x massstorage driver integration is possible thanks to Mr dUSHA powerful MSSTMake.exe tool To the Unattend option: It's possible to use an unattend.xml to run the Setup unattended. But as the actual WinPE Setup Phase isn't effective in that way of install, all Winpe related settings inside the unattend.xml won't be applied. Ini config file It's possible to save all GUI-settings to a ini file: push Ctrl + S to save all settings to an ini. push Ctrl + L to load all settings from an ini. A WinNTSetup.ini file in the same dir as the app itself will be loaded automatically at startup. It also can be selected via command line: WinNTSetup.exe /cfg:"C:\mysettings.ini" If you want to modify ini settings yourself, click-click has made a nice PDF for it. For advanced users there are also hidden settings described in the included WinNTSetup.ini.txt Command line: - Press F1 to get list of all options To install Windows in a VHD file: - requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as Source - create a partitioned VHD and assign a drive letter (push Ctrl + Shift + V to use build in diskpart wrapper for this) - select the VHD drive as installation drive (make sure you boot drive ist a active primary partition on a physical disk) If you get an Antivirus warning from your AV software, please report it to them as a false positive and let them check it. Current Version: 5.3.4 Download: Mega - MediaFire
    1 point
  7. I see , but you made me laugh (in a good sense) , not laughing at you . I mean it was funny . Thank you !
    1 point
  8. what i was trying to say was i missed the 90s by one year
    1 point
  9. Look here. https://drivers.softpedia.com/get/GRAPHICS-BOARD/INTEL/Intel-HD-Graphics-4000-Driver-918103222-64-bit.shtml
    1 point
  10. Guru 3d got them. Try use these to win10. I cannot say if works on win10 (since got personal ban to windows 8 and newer) but on win7 and hd4000 works no issues. they can be still used if got drivers. Dell site got ones to xp and vista.
    1 point
  11. Well , that's a damn good reason to get back to Vista ! I will send you the link to get Vista drivers . For the future , I'm guessing Texas has plenty of shops with affordable external storage solutions , so just buy an external HDD , USB stick or whatever you desire and copy your drivers/files there . Better to have at least two backups. Or just burn them onto a DVD (worst case scenario).
    1 point
  12. @THK2003 , WerRegisterRuntimeExceptionModule function registers a custom runtime exception handler that is used to provide custom error reporting for crashes. The key words are "error reporting" , so this is yet another spying "feature" . Absolutely not needed . Try replacing crashreporter.exe with a blank file. Create an empty txt file . Rename it from "New Text Document.txt" to crashreporter.exe and replace. Actually, you can replace all *.exe files in the firefox folder, except the firefox.exe itself.
    1 point
  13. shutup10 does good job. I recommend read all options trough. Even after that all telemetry is not gone. Nobody knows exactly what win10 got under hood
    1 point
  14. 1 point
  15. I'm gonna drive this old Clunker till the wheels fall off.
    1 point
  16. I very STRONGLY suggest using the REPACK version. The hurdles to jump through aren't nearly so GIGANTUOUS as far as telemetry-prevention with the REPACK version. I have personally only witnessed roughly 5% of Dixel's list so I would be curious to see screencaps of evidence that such a huge list is required even under the "official" (non-repack) version. My HOSTS file blocklist suggestions are much much smaller and I've not yet witnessed anything in Dixel's list outside of the below -- 0.0.0.0 browser.360.cn 0.0.0.0 cloud.browser.360.cn 0.0.0.0 dd.browser.360.cn 0.0.0.0 qurl.f.360.cn 0.0.0.0 chrome.360.cn 0.0.0.0 ext.chrome.360.cn 0.0.0.0 u.qurl.f.360.cn 0.0.0.0 puv.tt.browser.360.cn 0.0.0.0 p.ssl.qhimg.com 0.0.0.0 p0.ssl.qhimg.com 0.0.0.0 p1.ssl.qhimg.com 0.0.0.0 p2.ssl.qhimg.com 0.0.0.0 p3.ssl.qhimg.com 0.0.0.0 p4.ssl.qhimg.com 0.0.0.0 p5.ssl.qhimg.com 0.0.0.0 p.ssl.qhmsg.com 0.0.0.0 p0.ssl.qhmsg.com 0.0.0.0 p1.ssl.qhmsg.com 0.0.0.0 p2.ssl.qhmsg.com 0.0.0.0 p3.ssl.qhmsg.com 0.0.0.0 p4.ssl.qhmsg.com 0.0.0.0 p5.ssl.qhmsg.com I've personally not witnessed all of the .p0 through .p5 items, but I keep the full sequence blocked "just in case". I should point out that I delete errorpage.zip and newtab.zip and I've never used the "official" version, only the repack and only with a very large number of tweaks. Too many tweaks to list here, but one of them is to open chrome.dll in HxD Hex Editor and replace all 265 (build 2206) ocurrences of "360.cn" (without the quotes) with "killed" (without the quotes). Another tweak while in HxD Hex Editor is to zero-out the IP Address for "SystemHostResolverCall" (without the quotes).
    1 point
  17. Hmmm. Those must be "queer" or - to say the least "non conventional" tests ... jaclaz
    1 point
  18. It sounds like it might be at least a starting point for @Tengereckito get the look he wants back then. Thinking about it more, I now remember that I did some of the customisation using Classic/Open Shell. My inactive windows' title bars are grey, not white, as in my screen grab. That might well have been a Open Shell thing, as was the colour of the taskbar. Active windows' title bars are blue.
    1 point
  19. Another tip already mentioned previously in this thread is to launch 360EE with the cmdline argument: --process-per-site so that tabs under the same domain (e.g. all facebook.com tabs) are loaded by the same unique browser process; I tested this briefly in the past, but since I never get to having more than 25 open tabs and very few, if any, among them share the same domain, I did not witness a noticeable reduction in RAM consumption (tried on 360EEv12/v13) ... YMMV, of course...
    1 point
  20. Here are two overrides submitted back in Page 16. --enable-low-end-device-mode --enable-low-res-tiling I did not observe any effects when I tried these several months ago but maybe they will on your setup.
    1 point
  21. Please note that this thread discussed a similar crash back in pages 16 and 17. Tests then showed *better* RAM handling with v13 over v12 and with v12 over v11. It's not so cut-and-dried as looking at RAM amount and doing "simple math" as to which number is larger or smaller - IT IS NOT THAT "SIMPLE". We also have to factor in that v11 is based on Chrome 69 - which does not multi-thread or at the very least is "first generation" multi-threading. Keep us posted as you try v13 (or maybe even v12). As I suspect that NEITHER will have this "crash bug" that I cannot replicate on my hardware but seems consistent on your hardware. Keep us posted...
    1 point
  22. It's one I modified myself from the default, it's not one of the standard ones. I changed the taskbar to blue for instance, along with the highlights. Here it is if you'd like to try it! You can of course modify it to your own liking, but it might give you a starting point. Dave-H.theme
    1 point
  23. For the duration JustOff was the head of the official Pale Moon localisation project, he would maintain his own langpack (LP) GitHub repository, https://github.com/JustOff/pale-moon-localization/releases and his Pre-release LPs would target PM's unstable channel, with which NM28 has/had the closest affinity... Modifying the minVersion value inside the install.rdf file, to account for NM28's different versioning, would produce an installable and functioning langpack... This practice used to work up to a point in time (e.g. I know it worked till the end of May 2019, when NM28 was at v.28.6.0a1); but,"upstream" started making coding decisions that were deemed "unwanted" by the majority of members here; old code was kept by us, but removed by upstream (e.g. WebIDE inside devtools) and vice-versa, i.e. they introduced new code that was not adopted here... Whenever these code differences introduce string modifications (addition or removal), then the PM-targeting LP becomes incompatible with NM28 to a varying degree; slight modifications in parts of the browser you don't use often may stay unnoticed, but when major core strings have been altered, considerable breakage takes place, even to the point that the non en-US pack renders NM28 unable to launch with it; a "safety" mechanism then silently disables that LP and re-launches the browser in the default (en-US) locale... I wrote the above "summary" for the sake of those unfamiliar with NM's localisation scenarios; FWIW, roytam1, from the very start, said he would not provide himself LPs for his browsers, we, as fork users, were just lucky we could, up to a point, "freeload" the ones prepared for PM by MCP (and get all the hatred from them for doing so... ). Our (roytam1's ) source tree had already diverged significantly from upstream even before JustOff was ousted from the MCP localisation team, but lack of his "unstable" LPs currently means that a DIY person like you can't peek into them to find newly introduced strings there (that could be migrated to a NM28-specific LP); the sole source of PM localisation now are the LPs intended for its release channel, to be found: https://addons.palemoon.org/language-packs/ with NL on https://addons.palemoon.org/releases/pm-langpack-nl/ Save as .xpi file and extract with 7-zip, then look inside for new strings not yet incorporated into your own NM28 NL-pack; you have to be well versed in the folder/file structure of the LP, if you have a NM28 NL pack that used to work in previous NM versions, you can "build" on top of that and go forward towards more recent releases... You must use a file diff application (or a text editor) to inspect the string differences between the exact same files of the two LPs, so you can modify your DIY one accordingly (taking care to incorporate only the new strings needed by our fork, the PM file may contain other strings not compatible with NM). Indication of strings modification in code can be found also on roytam1's GitHub repo; whenever UXP and/or Pale Moon source files that have a path containing "*/locales/en-US/*" are being modified, this signals modification to the natively bundled en-US langpack; these modifications should be reflected (and translated into Dutch, where applicable) in your DIY NM28 langpack. For instance, for the "Media Formats" strings that you cited, the relevant commit is [Pale-Moon] Issue #1862 - Add media format controls in Preferences -> Content from which you can see the newly introduced (English) strings in file application/palemoon/locales/en-US/chrome/browser/preferences/content.dtd by loading: https://github.com/roytam1/UXP/commit/650abe2cb9eb02c14369a807a6225ebb053d0b17#diff-d3c90e964941daf05f84a5b5192bc0c94f6f629dcc424dd23e8f87cc766cd4f7 Many times, it is difficult to tell on which LP file to apply the string changes committed to source files, this ain't one of them : <LP root>\browser\chrome\nl\locale\browser\preferences\content.dtd In conclusion, the natively bundled en-US langpack is found split between NM28's two omni.ja files: ".\palemoon\browser\omni.ja\chrome\en-US\*" ".\palemoon\omni.ja\chrome\en-US\*" (use 7-zip to access); ultimately, these are all the files you have to translate into Dutch and then package appropriately (consult an existing LP) to make a functional NM28 nl-langpack.xpi; it ain't easy, is it? But I am open for any automation process you happen to be aware of (this extends to the rest of this community here ) ... Kind regards
    1 point
  24. Well, AFAIK, @JustOff only supports official Pale Moon, official Basilisk and SeaMonkey 2.53.x; he doesn't support pre-Quantum Mozilla Firefox (v52-56), nor any other Fx52ESR-based fork... (snipped) Imagine the case your wish has been granted by @JustOff and his extension installs out-of-the-box in Serpent 52.9.0; (snipped) The extension would have no issue installing in a 2018 build of Serpent 52 (on Firefox ESR 52.x.x, too), but obviously the GitHub experience there would be substandard... Do you think @JustOff is willing to deal with such scenarios? (snipped) ... so, things aren't as clear-cut as initially imagined; the ball is now in @JustOff's court, so let's wait for his reaction... ... And the man has spoken: https://github.com/JustOff/github-wc-polyfill/issues/21#issuecomment-813060443 ... Didn't I tell you so?
    1 point
  25. <OT> I'm sorry for your loss. Hope your government can further inspect if the death is related to vaccine or not. and for me, I got my first dose of BNT few weeks ago and will get second dose on Friday, hope everything will be fine. </OT>
    1 point
  26. @VistaLover Happy Easter to you too my friend. My Easter will be very sad. We are in the red zone for Covid-19. My father,who was very old,passed away after the Anti-Covid 19 vaccine. The governor of my region also banned the opening of grocery stores on Sunday and Monday. Good thing it is possible to visit relatives, my mother will not be alone. ___________________________________________________________ I wish all forum members who observe Easter, a peaceful day. ___________________________________________________________ Please forgive my OT.
    1 point
  27. Many thanks, indeed! palem's post there is, I think, highly representative/reflective of the major part of Moonchild browsers' userbase, and should also encompass users of Roytam1 forks here... The actual URI of the post (by M.A.T.) quoted is: https://forum.palemoon.org/viewtopic.php?p=211976&sid=0181647fb5c2204a1c681cd16e21004d#p211976 ... As far as I know, no-one here has already gone/will go nuts over it, all is needed is to keep a vigilant eye on UXP+PM issue trackers/UXP+PM master branches and selectively revert/omit what is deemed unneeded for our tree... Even if that, eventually, will just buy us more time (hopefully lots of it...), it would be highly worth it! E.g., I have already warned readers here of the new plan (envisioned by M.A.T.) to move to an install.json based extension ecosystem (deprecating the install.rdf one), I think these developments should be dealt with on a case-by-case basis/when they present themselves... OT: To Sampei and to all observing Easter tomorrow, may you have a very Happy Easter Sunday (... Unfortunately, divisions between communities of the same Faith mean that over here Easter Sunday won't "arrive" until May 2nd ) ...
    1 point
  28. I think we have to dig on the word "telemetry" here. Windows XP independent network activity wasn't called telemetry back then (at least from what I can tell here as a non-native speaker). Still, Windows XP is a chatty system in its standard settings. I don't measure this by today's (wasteful) standards for phoning home, it's a principle instead, that nothing should run except the stuff I was asking for. You basically have to deactivate 80% of the Windows services (under msconfig). I think Windows Update is the worst one. The NTP time program syncronises the system clock with a server from the internet, but do you really know it doesn't send any other data of your computer over the network? I don't know, but I don't care either. Everything has to blocked, that I didn't ask for (that's my stubborn opinion of course)! Therefore some entries to the dnsmasq.conf file of my OpenWRT router: address=/microsoft.com/0.0.0.0 address=/*.microsoft.com/0.0.0.0 address=/a-msedge.net/0.0.0.0 address=/msftncsi.com/0.0.0.0 address=/windowsmedia.com/0.0.0.0 address=/windows.com/0.0.0.0 Blocking some Akamai servers was also necessary if I recall correctly. Might be a bit bulldozer-style, but at least my Windows XP systems do what I tell them to do! Attention: The Hosts file doesn't work to block Microsoft servers on Windows XP! It did on Windows 98, but they've put holes in it to still let the Microsoft servers pass through. The exact entries can be found in the system file "dnsapi.dll". You can throw it into your Notepad, press Ctrl+F and search for "microsoft.com". More filtered domains are about to appear... Anyways, it's very likely that there was always "telemetry" in Windows XP. Too much suspicious network activity. Remember, it had to start somewhere to get where current Windows systems are now!
    1 point
  29. The programme is Power DVD (circa 2009). It was supplied with the PC . As of now, I have that dubious "feature" disabled. But that's not a permanent solution. That'ss not the programme that makes me wonder , that's all those firewalls that allow such kind of traffic . As far as I know, they have that MDNS "casting" in Power DVD for a long time , since version 7 or so.
    1 point
  30. i have no idea what music was like in the 90s because i was born in 2000 all i know about is the new disco style music and the country and rock music that is the new disco of the 2000s i wish i was around in the 90s to get to see all the cool stuff back then i missed the 90s by one year after the end of it
    1 point
  31. @Tripredacus As you can see in the detailed screenshot, the 4 cores show up in the device manager in both Professional and Home Edition, despite only two being usable on the latter. Each and every one is reported as "This device is working properly". Their device instance ID differs for each one: ACPI\AUTHENTICAMD_-_X86_FAMILY_23_MODEL_1\_0 ACPI\AUTHENTICAMD_-_X86_FAMILY_23_MODEL_1\_1 ACPI\AUTHENTICAMD_-_X86_FAMILY_23_MODEL_1\_2 ACPI\AUTHENTICAMD_-_X86_FAMILY_23_MODEL_1\_3 The exact same thing appears in Professional Edition and Home Edition in regard to the device manager. @Jaguarek62 Modern systems have an incompatible ACPI. For that reason, you will get something like 0x000000A5 BSOD. That can be fixed by installing a modified ACPI driver to the ISO image. Depending on your machine, you might have to add AHCI and USB3 drivers too. If you want to learn how to do that, i've made a guide you can check out here. There are many other guides you can follow as well, this is only my suggestion.
    1 point
×
×
  • Create New...