Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/25/2019 in all areas

  1. That is a normal behavior, if the service (server) you will connect to has a certificate chain where you have deleted the root or intermediate certificate. So the connection is unsafe and will not established. This is the way it works...
    2 points
  2. I don't want to exaggerate now, but if you are so insecure and already want to delete certificates, then you should strictly avoid the Internet. Alternatively, only separate, secure end-to-end encryption of all data transfers that you control all by yourself would remain. You are not fully secure on internet, it was so and it will be so in future.
    2 points
  3. It does seem to work again! Thank you for checking .
    1 point
  4. Hi, here is the ACPI fixed BIOS. Only the ACPI table was modified. http://www.mediafire.com/file/g16d12a8wpw2yk9 Just flash in DOS using the modified Efiflash.exe included.
    1 point
  5. Hi. Now 2.9f and 2.9g (perlhaps test version 2.9h, too) have critical problems. * Certain security softwares collide with extended kernel. (It is almost resolved) * Chromium and Firefox based web browser will freeze. Regrettably I don't release English version untill fixed them. You may believe that Japanese only version is Beta Test :3 It may be released in March. You know the following article comes for correction problem reasons http://blog.livedoor.jp/blackwingcat/archives/1979072.html
    1 point
  6. Dave-H The same thing happens too me aswell
    1 point
  7. @FranceBB @jumper @someguy25 @i430VX @VistaLover @rloew @Dibya @I41Mar @Mathwiz @aviator @RED-CHAMBER @Tamris @CoRoNe SOLVED! Thank you all for your troubleshooting and input. After installing a fresh Dell OEM copy of Windows XP on my Inspiron 1420, and "one step at a time" trial and error, I discovered the missing culprit: Visual Studio 2013 (VS2013): https://download.microsoft.com/download/2/E/6/2E61CFA4-993B-4DD4-91DA-3737CD5CD6E3/vcredist_x86.exe I tried several different things, one at a time. Once I installed this package, Audacity 2.3.1 immediately began working. I'm thankful for this Audacity thread which helped me FINALLY discover the culprit: https://forum.audacityteam.org/viewtopic.php?p=272186#p272186 Note, my Dell XP copy is SP3 RTM with IE6. So, no further updates to Windows XP or IE are needed.
    1 point
  8. It seems to be working on my end? I can see all sorts of goodies using that link.
    1 point
  9. Time to go back to Windows 98. An incompatible OS is the best vaccine of all.
    1 point
  10. A person can probably find common ground with any other person on at least something. Sure, no problem.
    1 point
  11. I'd personally assume that what was said on public board can be quoted. It makes sense
    1 point
  12. @LoneCrusader, may I quote you on Ghacks. I don't need to identify you, but I just don't want to pretend that what you said was my original thought, and thus steal it.
    1 point
  13. See @LoneCrusader I agree with you quite a bit there (and usually we vehemently disagree with each other). But it makes no sense for developers of Pale Moon and Seamonkey (which both utilize classic interfaces) to abandon operating systems like Windows 2000 or Windows XP, when the older-styled application goes alongside it so well. Also the mass support for such browsers would come from the classic OS community. Moon-Matt will not talk with ANYONE with disagrees with their ideologies.
    1 point
  14. I actually had an "extended discussion" with Moonchild some time back and attempted to point out just how illogical his position was in regard to older OS'es. It of course fell on deaf ears and he ended the discussion without even attempting to answer any of my points. I tried to get across to him just how irrational it was to be committed to preserving an older "browser interface/UI" while at the same time being determined to discard support for any older operating system as soon as possible. With one hand he pushes the "latest and greatest" and insists people should "upgrade" and not use "outdated" operating systems; and with the other hand he promotes an "outdated" browser interface now built on "outdated" code and now using "outdated" addons (in the eyes of the same people who push similar "latest and greatest" rubbish), purposely breaking the already existing support for older systems that was already in place. How one can contort themselves into such a strange position and consider themselves as having a reasonable standpoint on the issue is beyond me. When PaleMoon eventually starts bleeding off its users who subscribe to the flawed logic of "latest and greatest"; or when those remaining are left without options for addon/plugin compatibility and compatibility with the "modern" web, then I've got a feeling those of us here will have the last laugh, and can tell Moonchild and company "Welcome to the party, pal!"
    1 point
  15. MC's post is a lot less hostile than Tobin's, and it sort of makes sense: if you're going to develop add-ons for PM, you need to test your add-ons with the "stock" PM build, because that's the version 99% of PM users will use your add-on with. And that, of course, means testing on a Win 7+ system, so that "stock" PM will run on it. It doesn't mean you have to prefer the stock build - only that you have to test with it. It's Tobin who seems to blow a gasket anytime he sees the letters "XP" together. Chill out, man! Whatever your feelings about XP, and however justified you believe them to be, it's not worth having a heart attack over. Let other folks make other choices for their own reasons. Freedom! As for MC's sig, I sort of sympathize; I often find myself rewriting some program that was cloned from another program, and in the rush to get it running, a lot of unneeded code from the "original" source code was left in. Or the programmer used a generic structure better suited to a much more complex program than the one she actually wrote. Either way, you can make the program much easier to read, understand, and debug by removing all that extra code. Where MC takes his sig too far is when he decides to remove functionality just for the sake of removing code, as in his recent decision to remove working WE APIs from Basilisk. Sure, that too can make your program easier to read, understand, and debug; but it also makes your program less useful!
    1 point
×
×
  • Create New...