Leaderboard

Microsoft’s official explanation says error code 80244019 means, “The device cannot connect to Windows Update.”

Well I'm not sure what that actually is, but surely not being able to access the database doesn't mean that it doesn't exist any more?

i happy, that u solve ur problem! it very informative! now we know, that 98se2me and RevPack can cause big problems...

Picked up a free CRT monitor recently. The ad provided little information other than a picture of it sitting on the ground of a dirty patio. I requested more information and the response was terse, only that it could be found in the front yard by his plow. True, he had a nice antique plow. I'm no spring chicken so yes the seller was hiding something. Well it was free, sort of on my way doing errands and my annual spring cleaning run to the recycle centre is coming up soon. So i picked it up, it was dark, the monitor was sitting on the edge of a flowerbed, it felt light. Took it home, it's only 15". Disappointed, was hoping for at least a 17" CRT. Gave the monitor a nice exterior clean and let it sit for a couple days (die COVID die). It has several scuffs on the case but the screen is immaculate. Finally tested it today, runs nice, all buttons and controls work, extremely crisp image, very good colour, no flicker. Samsung SyncMaster 550s, the default Windows 98 driver provides max resolution of 1024x768, not too shabby. Ran it in Windows and DOS. Running DOS applications in 80x25 and 80x50 is superb with Gopherus and Lynx web browser. If i live long enough this monitor will eventually sit on my desk with a new (old) PC build - my slowest hardware available running Windows 95 primarily for DOS use. I'm spoiled and have a large corner desk (back desk edges 6' x 6') with a two tiered monitor stand (6" tall central stand, two 5" tall side stands). Will set this small monitor up beside my main CRT. Will open up this monitor case later in the week and clean out the inside. Was on a real hardware cleaning kick this summer and went through all of my monitors, televisions, etc. Of note from this experience, old CRT monitors and tube televisions are definitely worth cleaning out, the deep horizontal cases and cooling slots collect a lot of dust over the years. Don't bother taking apart and cleaning more modern flat screen monitors, they are sealed quite well and do not collect dust in the same fashion.

... A quick search found a few mentions (mostly in Chinese and Russian sites) of an interim release v1.7.21469.0 with the "version number", again, assumed to apply to the main potplayer.dll file ... That release, apparently, took place on Mar 25th 2021, and has already been superseded/replaced by (potplayer.dll) v1.7.21472.0 (that I downloaded directly from vendor: https://t1.daumcdn.net/potplayer/PotPlayer/Version/Latest/PotPlayerSetup.exe ); while searching, I did come across several PotPlayerSetup.exe releases with the same file version 1.7.21465, but with different versions of contained DLL and different digital sigs (DS): Setup v1.7.21465.0/DLL v1.7.21466]/DS 20210318 Setup v1.7.21465.0/DLL v1.7.21467]/DS 20210319 Setup v1.7.21465.0/DLL v1.7.21469]/DS 20210325 Setup v1.7.21465.0/DLL v1.7.21472]/DS 20210402 (latest as of this time) None of the above are expected to run under Windows XP... But, as I told already, standardisation of the released binaries has gone out the window... To be frank, I don't expect them to restore XP-compatibility, it might be a while before their main homepage reflects this, but it's the sad reality... FWIW, Vista will be also dropped like a hot potato at first opportunity, by introducing Win7+ function(s)... In light of the above sad developments, any further discussion of PP versions > 210209/1.7.21419.0 would be OT for this thread... Let me close by sharing another disturbing piece of news about current owners of PP: https://old.reddit.com/r/potplayer/comments/lxsozp/potplayer_official_english_forum_was_closed/ Thus, international PP users likely have to turn to third-party forums for support...

i uninstall the 98se2me program(for win98 get the windows ME theme).. and then i reinstall the audio drivers. and now i must found the windows me\2000 theme for windows 98.(the Revolutions Pack give me the same audio problems) thanks for all

I recollect this as having been already discussed in this thread... Upon searching, I did locate a post from June 2019, by one of your compatriots: I have never experienced this under Vista SP2 32-bit, so, as hinted, it might be an issue specific to XP... I am convinced, through local testing, that PotPlayer uses system resources (TLS implementation/cipher suites/crypto libs/cert store) to establish HTTPS connections, since (recently) many web services abandoned TLS v1.0/1.1 and moved on to TLS v1.2+, this might be a manifestation of such an implementation... A similar issue I'm facing with PP recently is its inability to play back several audio streams served securely, like the newly introduced BBC Radio Icecast ones, e.g. https://stream.live.vc.bbcmedia.co.uk/bbc_radio_one A test on SSL Labs shows it demands exclusively TLS v1.2 and cipher suites IE[9] can't cope with... The same stream plays back fine in VLC 3.0.x (which bundles its own crypto libs). This was indeed deduced from a changelog on subsequent (beta?) release 1.7.18193 two years ago, VH have since then a permanent link on https://www.videohelp.com/software/PotPlayer for what "they" claim to be the last XP-compatible version... OTOH, the very same site hosts, what I believe to be, a copy of the official stable releases changelog, https://www.videohelp.com/software/PotPlayer/version-history which jumps from v [1.7.17508] 2019/02/12 straight to v [1.7.18344] 2019/04/17 with no word about drop of XP support... That VideoHelp misconception/misunderstanding was also rooted among XP users based on the "H/W accelerated HEVC" debacle, read here ; FTR, stable release 1.7.18346 (second after 1.7.17508) was confirmed as being XP-compatible already in this thread by our very own PP guru! So, the moral of this short story is, don't always believe what you read at first, consult a second opinion, if you are a "Doubting Thomas" (like myself), try for yourself (except, of course, when "trying" goes against your principles - this is acknowledged and respected! ) ... Practically not "mine", merely hosted currently on VH - if you peruse this thread, you'll find I'm not the first one to suggest VH's archive as a source of previous PP releases... I genuinely thank you for your time and efforts conducting this conclusive test, which proves that the last, at the time of writing, XP-compatible release of PotPlayer is the one versioned [new scheme] 210209/[old scheme] 1.7.21419 . Lastly, it has been posted that the latest PortableApps offering of PotPlayer, package with filename "PotPlayerPortable_1.7.21419.paf.exe", has been erroneously declared as being XP-compatible, ie. in reality it isn't ... The above statement had me really perplexed, because @FranceBB has proven, beyond any doubt, that v1.7.21419 (packaged inside the PAF version) IS XP-worthy; the answer to my pondering is that XP-compatibility has been broken not on appVersion itself, but on the fact the packager omitted the inclusion of file PotPlayerMiniXP.exe inside ".\App\PotPlayer\" (in the PAF folder structure); this can be mitigated quite easily, if that missing file is 1. extracted (7-zip) from the installer of v1.7.21419 2. copied inside the PotPlayer directory (besides PotPlayerMini.exe, which you can delete, if on XP) 3. you modify the portable launcher's configuration, in ".\App\AppInfo\Launcher\PotPlayerPortable.ini" as below [Launch] -ProgramExecutable=PotPlayer\PotPlayerMini.exe +ProgramExecutable=PotPlayer\PotPlayerMiniXP.exe -: deletion of line +:addition of line Hope it works, it should... Best wishes

Well, not bad, you will still need to patch io.sys for working Safe mode with 512+ RAM. Otherwise you can got up to X58,X79 with working Dos (Win98 one and pure DOS) sounds, because these board are last with DMA sound magic in chipset needed for DOS.. Otherwise there is not limit for Win98 sound only. https://www.dropbox.com/s/ulaptg9pd7pzb9q/2017-08-20 03.40.07-5960X-Win98.jpg?dl=0

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 ) ...

I've seen many individuals use newer GPUs with older Legacy BIOS systems just fine. According to this forum post, it seems to be an issue with AMD cards mainly. Video of a GTX 1050 running in a legacy bios system. His channel has many more examples, too.

I concur. In fact, I'm using it now, on my Mac Pro (arguably best machines you can find for XP x64, in my opinion). I do like that XP-32 is more well supported, though (XP-64 is this weird thing that sits somewhere between XP-32, w2k3-64 and Vista-64, being relatively compatible with all three (thus being capable of running 90%+ of all software written for them), yet barely supported by anyone). This makes it a bit of a challenge to get it working just right, but not impossible. c

XPx64 is rock solid under proper hardware .