Leaderboard
Popular Content
Showing content with the highest reputation on 03/09/2023 in Posts
-
Hello, MSFN! So I'm a computer enthusiast, and I love to mess around with any hardware/software I can find - old or new, good or bad, etc. I have a passion for computer and information science, and I'm currently working on making a career of it. Nice to meet everyone!2 points
-
2 points
-
@win32 released a revised version of the March 6 extended kernel, Chromium problem resolved2 points
-
Yes, they seem to work together, I hope they work on Windows 2000 as well2 points
-
I think that this is not the problem, because a simple kernel redirect is enough, everything except the message about the lack of support for Vista and XP then works. By the way, for some reason applications that need the osver.ini file to work, or rather their installers are not able to create shortcuts, an error appears.2 points
-
2 points
-
that's what you get nowadays with pretty much any company there only in it for the money and profit (not the customer)2 points
-
Hi win32, magnificent work on your extended kernel as always, thanks for that! I was wondering if you had any progress running Adobe Acrobat Reader DC application on Vista. Thanks.2 points
-
A wider assortment of 32 bit applications run, including up to Chromium ~107 and Electron applications such as Spotify (Discord's updater is buggy, apparently it's reliant on IE). Firefox goes up into the 90s. Chromium 110 x64 works. Chromium 111 x64 may work, with --no-sandbox and ChromiumFix=1 set in a osver.ini override for the application. OBS Studio 29 works, Calibre is fixed and PCSX2 1.7.3195 QT6 works, but later versions have issues. And Premiere Pro 2019 working now, which I did not expect. There are two known issues; Chromium's access to audio devices is broken. The cause was discovered and it has been fixed, but I am waiting on a fix for the second issue to include it in an update. There is an issue with userenv.dll which breaks audio on various systems. As the updates to userenv.dll are only needed for Chromium 110+, you can temporarily replace it with the original version to restore sound if it has been lost.2 points
-
@D.Draker Please do not quote me again ever. I have come to realize that WinClient5270 was very wise, and my New Years resolution is to forget about the problems of using Windows Vista in 2022. All forums (not just this one) are now dominated by people who are either rude or mentally ill (it is hard to be certain when they barely know English). My Vista hardware sits in a closet awaiting a refurbishment that it will probably never get, since running Vista no longer strikes me as a good idea. Happy New Year!2 points
-
"If you "opt-in" for the security risk (the extent is often debated, so "your call") of enabling WebGL, then you need to remove the --disable-webgl switch in 360Loader.ini ."1 point
-
OT ...Then, most probably, this one: https://www.youtube.com/watch?v=N2qqfafRdEQ /OT1 point
-
1 point
-
great work as always @win32 and I want to thankyou from the whole community for what you have done and continue to do here your amazing!1 point
-
Yes it does! You have to enable WebGL which is disabled by default due to security risks associated with WebGL.1 point
-
After Effects / Photoshop 2019 do not launch because of missing entry points in the Kernel32 dll, Audition 2020 works up to a certain update, which just so happened to be the one that changed their icon to their modern variants, an issue with MFTranscode will pop up but you'll just have to ignore it and wait until it launches, as soon as you interact with the error window the program will crash, Direct2D is also disabled for stability. Photoshop / After Effects 2018 ( Unchecked )1 point
-
It is possibly related to the bug where it cannot access audio devices. I have solved it along with the general audio issues, but now need to solve another issue with .NET applications.1 point
-
Instead of changing your picture all the time, could you help me, please?1 point
-
You can try modifying the inf file of the latest driver for Vista x86, but I'm not sure if that will work. The drivers modified by win32 are probably only for the x64 version1 point
-
I agree with the issues with avast and have switched to panda antivirus as my new lightweight antivirus and has worked really well for as long as I have used it (even on vista which is what i use now)1 point
-
Hm, apparently what I read was just the comment on Reddit saying to search YouTube for "Cinema Therapy, radical acceptance". Nice find, though some situations are just beyond messed up that one shouldn't have to just accept. Sigh, back at wrong thought patterns, huh?1 point
-
To be fair, and I always fair, I'm a judge of some sorts - no such dll even present here ! Would be polite to check this browser *before* you posted an article from 11 years old. On the other hand, we must be grateful you didn't find an article from 1986. That upvote I gave you yesterday, was by mistake, retracted now. I used this browser a couple of years ago and observed no such behaviour. The browser was good while it lasted circa (2020-2021), now it's obsolete, struggles with twitter, etc. I'd move back to it, if the engine bumps to say Chrome 103 (at least).1 point
-
Well, I certainly found number of reasons that still makes me prefer it over Chromium flavors. @VistaLover Sure, I generally don't like the number of things in this world, including the way a number of websites are designed. I've got a hint from another place to look into radical acceptance, a specific video or podcast about it...not sure as I can't find it again...but yeah, that was the main thing - "radical acceptance".1 point
-
Ugh, every once in a while I need a printer and Windows goofed up...again! Just nothing happened when I tried to print, no error, just nothing. I'm so fed up with darned OS corrupting itself in random ways, no matter how careful I am to not goof it up. On Linux, I've been able to print/scan consistently without a single fail. I'm also considering going Linux full-time for normal everyday tasks, maybe keep Windows around for some specifics. I don't need much these days, a web browser, a media player, password manager, maybe a virtualizer and office suite (just for viewing). Just not sure on what distro to settle. I'm sure I don't want rolling-release distro. I'm most familiar with Ubuntu. Edit: Or maybe just more time...1 point
-
Yes, WiseVector StopX require SSE2 (tested on a computer with a Duron 1,6 Ghz last year). Regards I think whether WiseVector StopX requires SSE2 or not is no longer important. It has been abandoned by the developers. Their interests now seem to be focused on an enterprise version to make money.1 point
-
Seems there's not much interest in documenting which games actually use it. Not much results if you Google "D3D12On7 site:www.pcgamingwiki.com". But you may get a rough list of games on Steam that use it Googling "dxilconv7.dll site:steamdb.info". dxilconv7.dll is a unique dependency of D3D12On7 and SteamDB records list of files that come with each game on Steam among other information.1 point
-
No issues, D.Draker. Carry on. I'll add this thread to my "out-of-site, out-of-mind" Stylus sheet. I was not trying to take sides but see how it probably looked that way. But correcting people's grammar (not just me, I've seen this done to others) ??? I'm not submitting any of my replies for a doctorate thesis - so I could care less if I mipsel wards are had grammar miptaques hear are their. No dog in this fight. Moving on. "Out of sight, out of mind."1 point
-
you know what. you have to be right every time, don't you? You are one of the reasons I left vista community. Since you can't use vista without the help of this forum I knew that it makes no sense. You basically disagree with everything. I will say just this and say no further reply. D3D12on7 is real, it is being used in wow,red dead, cyberpunk. it was used in call of duty series and probably many other games I'm not even aware. I'm glad that over on 8.1 topics, you're not present. I think that you and I should avoid each other. My computer meets requirements to play modern titles and I'm glad. I don't know anyone who would use an old gtx 770. 1650 super has no problems whatsoever with playing my favorite games (including cyberpunk btw). It might not be on the highest details, but it works. Windows 7 is and will be for a while a supported os unlike vista. once chrome drops support then I will consider it EOL. anyone but D.Draker and Dixel is welcome to join the discussion with me.1 point
-
Actually Vincent Price was quite good. jaclaz1 point
-
Try this on for size -- that website shows a tiny 0.49% of worldwide desktops run XP. Sounds about right to me. Then according to here we have 339.77 million Personal Computers in 2021. 339,770,000 times 0.0049 = 1,664,873. I love my XP, but I was expecting worldwide XP machines to only be in the tens of thousands, not 1.66 million.1 point
-
cyberpunk implemented it, red dead redemption 2 etc.. it is being utilized1 point
-
8.1 exists. it has around 4% of marketshare1 point
-
The forum is not bound by what is and isn't supported. Windows 7 is a top-level sub-forum due to the activity. It has come up in private discussion to move it, the question was then: why? There is no harm to keep it the way it is.1 point
-
Change those bytes for steam.exe, steam.dll, and steamservice.dll1 point
-
I installed 12.0.1202, which is a pre-release of 360 Extreme Explorer 12, based on Chromium 78. It can be obtained here: http://www.qiuquan.cc/browser/360chrome.html (behind some other stuff and semi-broken classic captchas) I installed it on Windows 2000 and XP. However it is quite broken as the first few attempts to use ended in freezes; now it is more stable. However it tries to use IE6 to render everything on Windows 2000; as IE6 is blocked in my firewall that went nowhere quick. XP is being a pill on my T60 so haven't tested as much there, but it was able to load the post-install page without apparently relying on IE. There is no indication that XP has been dropped so hopefully they will continue refining the product in time for its final release! Two other notes: -I had to rename the installer because my English NT5.x installations had a hard time with the Chinese characters and kept telling me "file not found". XP went into a classic GDI+ resource shortage fit and required a logoff when I tried renaming it there. -I had to copy the EN-US locale file from my v11 install to get v12 to start. However everything is still displayed in Chinese.1 point
-
No warez is contained within the distributed ISOs. And there may be some value in providing such packages to newcomers to win2k, but there are some issues: -did you obtain permission from @blackwingcat or the creator of USP 5.1 to redistribute their files? -SP4 UR1 and USP 5.1 are roughly equivalent; each one has its own issues and only one needs to be installed. -the win2k extended kernel has no relation to the 9x kernelex and is not open-source. -the high encryption pack was rolled into the OS in SP2. -there is no indication that extended kernel development has stopped -all extended kernel releases are cumulative: no previous versions need to be installed before the current version1 point
-
Can you do unit conversions in the classic win32 calculator? It crashes on me in LTSC 2019. But yes, the OS is finally usable on a 5400 rpm HDD after replacing an OEM-bloated Windows 10 Home!1 point
-
I installed right over 3.0b with no issue. The only issue seems to be that a few resources were left in Japanese (descriptions of Downloads/My Documents/My Videos in Explorer). Aside from that it's solid. 19 1/2 years later and the OS keeps getting better1 point
-
I just had an idea; for open source software we could try recompiling them with Visual Studio 2005/2008 or anything else that will let us target win2k.1 point
-
Windows NT 4 service packs are cumulative. You can go from RTM to SP6a in one shot. And VirtualBox guest additions were available for NT4, well at least eight years ago when I last virtualized it, which would negate the need for the SNAP driver. For reference there is also a SNAP video driver for NT4.1 point
-
Latest FileZilla 3.42.1 32-bit won't launch under Vista SP2 because of only one missing function in Vista's shell32.dll system file: ... and, actually, the very last Vista SP2 compatible version of FileZilla is 3.40.0-rc2, released on Jan 22nd 2019: You can download this Vista EoS version from the official repository at https://download.filezilla-project.org/client/ Final 3.40.0 was released three days later (Jan 25th 2019) but, as you've found out, it would run only on Win7+ FileZilla is open source, so perhaps one could recompile more recent source code to again target at least NT 6.0; here's hoping1 point
-
Windows 2000 Server: 4 CPUs/threads Windows 2000 Advanced Server: 8 CPUs/threads Windows 2000 Datacenter Server: 32 CPUs/threads The theoretical limit is 2^16 CPUs/threads if the appropriate registry hack is made, with all editions of Windows 2000.1 point
-
uFile 2018 (Canadian tax prep software) works on Vista SP2 according to the box.1 point
-
Yes, all I did was use Orca to remove the version check from the msi (for X6 that is).1 point
-
The riched20.dll included in the v2.9bG English package is corrupted. It breaks WordPad and Windows Installers (with error code 2894). The remedy is to transplant an older version from my USP 5.1 installation media (dated November 2006; not sure which version). Then the extended kernel works great. The latest version of WPS Office, as well as PotPlayer v1.7.16291 (a later beta version was less stable) are functioning without issue. Keep fighting the good fight!1 point
-
yea i was just asking , it felt a bit odd , not picking a fight or so1 point
-
It is all explained (but not in a convincing fashion) in https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c19 https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c66 as a result of: https://bugs.chromium.org/p/chromium/issues/detail?id=426573 TL;DR : At the time that decision was made, Vista user base was very thin, compared to either the XP or Win7+ one, so for code refactoring/simplification they decided to merge the Vista codepath to the XP one; for Google, it is only numbers that count ; plus, that gave them a perfect opportunity to dump Vista altogether (along with XP) a whole one year prior to Vista SP2 becoming EOL by M$ (and close to 5 years before Vista's Server counterpart, Windows Server 2008 SP2, reaches EOL in Jan 2020 ). Once Google made the first move (dragging along with them all webkit-based browsers), many other software makers soon followed (they had a "nice" justification) in a trend that put Vista, 1.5 years after its official EOL, in the sorry state it is currently in... The only way to properly fix this is to first grab the source for Chromium 41 (-50?) - Chromium, yes, because Google Chrome itself is closed-source - and then revert https://chromium.googlesource.com/chromium/src.git/+/f29562d138f8c2222c6f24bddbd1a665ed036658 Some additional details in https://bugs.chromium.org/p/chromium/issues/detail?id=426573#c10 => https://codereview.chromium.org/755293003/diff/1/ui/base/win/shell.cc#newcode153 This isn't a task for the faint-hearted ... You would need a Win7+, 64-bit, machine with lots of RAM and a powerful multi-core CPU, MS Visual Studio 2013+, lots of time/patience and, of course, you should be well versed in that field (compiling open-source browsers in VS)... Two MSFN members come to mind, @roytam1 and @FranceBB, but I am unsure whether they're interested in compiling Google Chrome 49.0.2623.112 (last officially supported build on Vista) or 50.0.2661.102 (last Vista compatible, but not officially supported) with Aero-Glass enabled in Vista... I, as much as other Vista users, would be all up for this, even if it is realised purely as a challenge only, given that both Chrome 49+50 are quite outdated (in both security and performance aspects) when dealing with the web of 2019... Those two screenshots @VistaPAE posted in OP are not from his own system ... First one is taken from https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c83 That person compiled Chromium 49.0.2579.0 64-bit with the aero-disabling commits reverted... So did this one (Chromium 45.0.2415.0 64-bit) : https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c68 The second screenshot in the OP is taken from https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c67 It emerged that this was actually a hoax/cheat ; the OS used to generate the shot is Win7 SP1 64-bit, disguised as Windows Vista (much like @WinClient5270 's guide found in his signature...) So now you know PS: For the history of it, the last build on Vista SP2 with Aero turned ON was Google Chrome 41.0.2243.0 in the dev channel; I keep a portable copy of it on my system just for fun, it's not used for normal browsing: Next build 41.0.2245.0 had Aero turned OFF in Vista...1 point
-
IE9 (32-bit) on Vista SP2 Home Premium 32-bit here The youtube.com/html5 test is correct when it comes to IE9 on Vista (no VP8 support here): IE9 has no support for MSE; after Google ceased supporting Adobe Flash Player (all 3 variants of it, i.e. activeX, NPAPI, PPAPI) on youtube, the only thing left for IE9 to handle was progressive download of mp4 files (encoded in h264/aac) over HTML5, and I recollect the limitation of not being able to go Fullscreen on the embedded player (a message about unsupported browser was displayed ) ... It was at the start of summer that I accidentally noticed yt was unplayable on IE9, as I'm hardly using IE9 for anything this day and age... I did not lament the loss of yt on IE9, in any case it had been an unsupported browser many moons ago already... But it was this thread that made me want to investigate things... So: Well, youtube claim they don't officially support any IE version anymore, yet tests show that IE10/IE11 still work, while (obviously) previous versions don't... Loading Introducing iPhone XS, iPhone XS Max, and iPhone XR in IE9 (after you declined to upgrade your browser, that is...), you get the empty embedded player, as per OP: For troubleshooting, open IE9's developer tools (F12) and load (browser) Console; refresh youtube page: To load their embedded player, yt use, among other things, a JS script named base.js; URI for my locale is: https://www.youtube.com/yts/jsbin/player-vflkUTZn2/el_GR/base.js That script uses in 19 instances the window.matchMedia code snippet; a Google search on matchMedia yields the following two results (among others): https://developer.mozilla.org/en-US/docs/Web/API/Window/matchMedia#Browser_compatibility https://caniuse.com/#feat=matchmedia where one can see that the needed API was introduced only in IE10+, i.e. IE9 does not understand window.matchMedia and chokes, failing to load the HTML5 youtube player: Mozilla Firefox, OTOH, supports the function from an early version 6 - and Chrome from version 9... Not strange anymore, is it?1 point
-
While the proper .exe setup won't install on Vista itself, you can download and install on Vista the portable (PAF) setup, available from portableapps repo: https://downloads.sourceforge.net/portableapps/FirefoxPortable_53.0.3_English.paf.exe So no need for a Win7+ box; I have used myself pe_patch.exe http://www.the-sz.com/products/pe_patch/ to change subsys version to 6.0; place pe_patch.exe inside /App/firefox/ and simply drag & drop firefox.exe onto it - its GUI opens; just manually change "Sub System Version", then click "Save" & "Exit" in the bottom. What pe_patch.exe patching does is actually reverting bugzilla bug 1322646 ; since the Firefox 53.0 code doesn't include functions not present in the Vista (in fact XP, too) kernell, the patched firefox executable will perfectly launch on Vista SP2 (should also do on XP SP3 !). While Fx 53.0.3 should be fine on Vista for casual browsing, your "it works flawlessly" statement is, sadly, not entirely true . The Firefox devs (namely a Japanese guy who harbours some unusual aversion to Vista) were very quick/keen to excise vital Vista support code; I tried to fight their decisions in the relevant bugzilla bugs back in the day, but, as you may assume, to no avail... In fact, at the initial bugs, Mozilla were to only drop support for XP, but, in another Google Chrome aping, Vista was put in the same boat... But I'm going OT here... Bug 1324183 has removed WMF support from Firefox on Vista, so Fx 53.0.x can't use system codecs (MP3, AAC, h264) to play back standalone .mp3/.mp4/.m4a media files or play back mp3/mp4 streams via HTML5. Adobe CDM has been removed, so has support for Quicktime/VLC NPAPI plugins, so media playback is a serious drawback here... Another bug (1329547) completes what 1324183 started... You can check yourself by visiting HTML5 test or youtube html5 . In another bug, WebGL(2) renderers, at least on my machine, can't use D3D11 and fall back to D3D9x; in Fx 52.2.0, about:support, graphics section: WebGL Renderer Google Inc. -- ANGLE (Software Adapter Direct3D11 vs_4_1 ps_4_1) WebGL2 Renderer Google Inc. -- ANGLE (Software Adapter Direct3D11 vs_4_1 ps_4_1) In Fx 53.0.3: WebGL Renderer Google Inc. -- ANGLE (Mobile Intel(R) 965 Express Chipset Family Direct3D9Ex vs_3_0 ps_3_0) WebGL2 Renderer WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps. There is additional XP/Vista specific code that was removed in the transition from 52.0 -> 53.0, I can't go on in detail here, so after my curiosity tests running 53.0.x, I saw no real gain in running that on Vista and went back to the supported 52ESR branch (currently on 52.2.0). And to save someone the trouble of trying to launch Fx 54.0 on Vista just by lowering subsys version, it doesn't work : ... As was reported by me 14 months ago ; again, the portable installation was used. Opera 37.0.2178.54 is based on Chrome 50.0.2661.102 code, so that is why it runs fine on Vista: As Opera 36 for XP/Vista has turned out to be a sort of a "joke" (hasn't been updated since August 2016), why not use (on Vista) Opera 37 ? They should be probably equally vulnerable, security-wise ...1 point