Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

Leaderboard


Popular Content

Showing content with the highest reputation since 02/17/2018 in all areas

  1. 7 points
    But... but... then, why reply to this thread if all you have to say is "never used 1.0 to 9x/ME"? This is, hands down, the most off-topic reply I've ever seen!
  2. 4 points
    First build of basilisk/UXP for XP! Test binary: Win32 http://o.rthost.cf/gpc/files1.rt/basilisk52-55.0.0a1.win32-git-20180220-d77729916-xpmod.7z Win64 http://o.rthost.cf/gpc/files1.rt/basilisk52-55.0.0a1.win64-git-20180220-d77729916-xpmod.7z diff: http://o.rthost.cf/gpc/files1.rt/UXP_RestoreXP_20180221.7z source patch of ffvpx H264/HEVC/AAC/MP3 Addition: http://o.rthost.cf/gpc/files1.rt/moebius-ffvpx-h264-aac-hevc-mp3-addition.7z My changes: * Added H264/HEVC/AAC/MP3 support in ffvpx * The following changesets are reverted: - Update exe manifest (drop Vista support) (756b27f58) - Adjust requirements (45f2fcd80) - Part 2 (d38f86569) - Stop shipping d3dcompiler_43.dll (b6c330e1c) - Prevent installing stand-alone installers on unsupported environments. (47b8c58d4) - Update executable manifests. (b55f0e7f0) - Remove unnecessary code in /widget. (a24398e42) - Remove no longer relevant ClearType prefs. (bc9ad467f) - Make the proper Windows APIs natively available to our tree. (85edb1c71) - Remove the use of GetProcAddress() for shell32 (c76689719) - Remove dead code in the Windows battery module. (e52c019ec) - Remove redundant Vista checks in toolkit/xre (2b01522cf) - Remove redundant Vista checks in dom/ipc (039f3e49c) - Remove useless version check from PDMFactory. (3d37f6181) - Remove always-false block from WMF. (ee70e3a36) - Remove always-false #if WINVER < 0x0600 (Windows Vista) checks in widget/windows. (66248cfbc) - Remove always-false #if WINVER < 0x0600 (Windows Vista) check in toolkit/win. (8f1c9fe4f) - Remove always-false #if WINVER < 0x0601 (Windows 7) checks in nsLookAndFeel.h. (2e0f80af4) - Remove always-false #if WINVER < 0x0601 (Windows 7) checks in nsWinGesture.h. (39578317e) - Use GetTickCount64 without a GetProcAddress check in Timestamp_windows.cpp. (a14048f0a) - Remove SEH try blocks from a11y code. (616475a0c) - Use thread_local calls on Win and Mac. (ce1bd4f24) - Remove StartupSpecialSystemDirectory() workaround. (01b1e411b) - Remove Windows shell integration checks for Windows Vista. (4f82d71df) - Remove XPCOM checks for Windows Vista and clean up unused header files. (13a9ea648) - Remove some gfx/thebes checks for Windows Vista+. (f297ef798) - Remove gfx/thebes checks for Windows 7+. (38ec1c796) - Remove some obsolete front-end code in Basilisk. (da8f20a3b) - Remove Windows XP specific code in netwerk. (40d8e355c) - Remove obsolete WinXPWifiScanner class. (a1bc6f33e) - Remove DLL blocklist checks for Windows XP. (20e533f6b) - Remove more Vista checks in dom/media (f1e863a49) - Remove more Vista checks in ipc code (a930db1c9) - Remove more obsolete checks in dom/media and ipc. (5d1eb0d3a) - Clean up Firefox specific considerations from WindowsVersion.h (9ecbf3331) - Fix build bustage: keep MF_WIN7_VERSION name (8826313be) - Remove Windows XP and Windows Vista theme components and resources. (fd9d8c20d) - Remove windows-xp and windows-vista from @media(-moz-os-version) (4c697043d) Tugging war begins, and my reverted changeset will become longer and longer in foreseeable future.
  3. 3 points
    I have analyzed the buggy oleaut32.dll vs the latest stable version (5.1.2600.7248). The following functions are missing from the buggy file: Statistical analysis shows no other differences, consequently using the old oleaut32.dll seems to have no security impact whatsoever.
  4. 3 points
    Last build of basilisk/moebius for XP! Test binary: Win32 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win32-git-20180218-868d263f2-xpmod.7z Win64 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win64-git-20180218-868d263f2-xpmod.7z diff: http://o.rthost.cf/gpc/files1.rt/moebius_restoreXP_20180128.7z source patch of ffvpx H264/HEVC/AAC/MP3 Addition: http://o.rthost.cf/gpc/files1.rt/moebius-ffvpx-h264-aac-hevc-mp3-addition.7z Official repo changes since my last build: - Storage Inspector should trim port from hosts for cookies (85b92c6a1) - Fix "help cmd" and "cmd refresh" in the Developer Toolbar (18b4c50bd) - Don't display storage-sidebar after deleting all cookies (156157c05) - Properly pass postData into new tab (37a2da481) - Merge pull request #346 from janekptacijarabaci/devtools_storage_cookies_port_1 (fc37a2cbc) - Merge pull request #348 from janekptacijarabaci/devtools_toolbar_cmd_1 (16d922f9a) - Merge pull request #350 from janekptacijarabaci/devtools_storage_noData_1 (13d79ee08) - Merge pull request #352 from janekptacijarabaci/devtools_network_openInNewTab_1 (16fa730b3) - Update readme for deprecation. (868d263f2)
  5. 3 points
    New Build! 32bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180218-3cf6a70ed-xpmod.7z 32bit noSSE https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win32-git-20180218-3cf6a70ed-xpmod-ia32.7z 64bit https://o.rthost.cf/palemoon/palemoon-27.8.0a1.win64-git-20180218-3cf6a70ed-xpmod.7z Official repo changes since my last build: - Tweak some more ellipses. (a55c51f39) - Address commit comments. (307fe019f) - Never shrink line heights as a result of minimumFontSize. (3ec6e75bd) - l10n: Split appMenu and menubar Restart entries for consistency. (3fb1113ac) - Use "getComplexValue" for new tab = home page. (45f933de8) - Match the start page URL for newtab with the default URL's scheme. (3cf6a70ed)
  6. 2 points
    Thank you @harkaz for pointing out the differences and thank you all for reporting the bug. As a matter of fact, we tested the update with both Windows XP (Real Machines), WES09 and PosReady 2009 (Virtual Machines) and the bug is still there. With all the informations collected here, I contacted Microsoft to let them know about the issue. I'm confident they'll fix it and roll out a new update in the future. Cheers.
  7. 2 points
    Thanks, but I'm already there. Thing is, I'm getting tired of RE-tweaking it, then having to watch carefully for all the ways Microsoft tries to untweak it (WaaS Medic, scheduled tasks, etc.). And lately my v1709 Win 10 VM just won't update any more. It just gets to near completion then reverts itself, without any clue about what's gone wrong. I restored my fresh install and even IT won't update either, not even from a .msu from the catalog. It shows that all viability of this OS being the basis for a serious computing environment is gone. At this point I'm just getting fatigued from paddling against Microsoft's formidable current of spew. When v1709 came out I fantasized about waiting until the waypoint formerly known as CBB, but I didn't and nothing good came of it. The magic is SO gone. That they've eliminated CBB entirely proves that they're no longer serious about Windows at all. For 1803 maybe I just won't make an updated VM at all, or maybe only if a customer reports a problem to me that requires I bring the latest version up. It was fun while it lasted. -Noel
  8. 2 points
    I'm 110% with you cc333. Windows 10 is simply too much of a moving target, and Microsoft doing all kinds of things - like scheduling jobs that re-enable disabled services, that schedule other jobs, etc. - is just too intrusive. They want control, and they will apparently stop at nothing to get it. It's not that they're doing a bad job technically; Win 10 doesn't crash a whole lot. It's just that their policies are, well, wrong. Of all the things I've craved from my computer operating system, ceding control to someone else - someone who has demonstrated incompetence and indifference to my needs - has never entered my thoughts! Windows, you're breaking my heart! You're going down a path I cannot follow! -Noel
  9. 2 points
    Thanks. I assumed it would work with the old oleaut32.dll, maybe I'll do the partial thing later if I get tired of waiting on MS to fix the problem. The way this one is affecting various software, it seems rather likely that "real" POSReady systems could get hindered by it (compared to the types of NTFS scenarios people have been seeing with the other patch), so I think maybe there's more hope for a fairly quick v2.
  10. 2 points
    Yeppers I'm a happy boy on Windows 8. Almost a hidden secret when you think of it. I really think it's the BEST option between modern support and "Leave me alone Microsoft" thinking.
  11. 2 points
    In other words, no news. jaclaz
  12. 2 points
    Just for reference, in my case KB4074852 prevented the GUI portion of Comodo Firewall from loading with message COMODO Security Agent could not be started. Would you like to run the diagnostics tool to fix this error? The diagnostics didn't detect anything; had to uninstall KB4074852 to get it working again. The machine in question has a fairly old version of Comodo (7.0.317799.4142), I don't feel like upgrading it right now just to test if newer versions work or not.
  13. 2 points
    Well, I guess this is a matter of taste, but for someone who strongly prefers the UI of Windows 7 and older (like myself), it's almost necessary to tweak things, like disabling/removing Metro (Classic Win32 is fine by me, and does 100% of what I want), adding translucency with Aero Glass, ClassicStartMenu (I have mine configured with the classic Windows 95-Vista menu, but it can do a Windows 7-styled one too), OldNewExplorer to get rid of the ribbon UI in Explorer, etc. But for some, it's totally fine out of the box, and that's OK. The fact that 8.1 *can* be is nice, because it feels like Windows 10 has caused nothing but problems for most people who try to use it for anything serious, and almost 100% of the time requires a bunch of fiddling with settings to be safe and useful to any meaningful extent (using the arcane Settings app, which I find totally ridiculous when the traditional Control Panel works just fine) (or maybe I'm exaggerating a bit, not sure). c
  14. 2 points
    Actually I'm kind of immune for now from the patches in general, since I don't use an AV package and thus nothing has written the QualityCompat value. That's not going to change. But this does mark my exit entirely from the update train, so I see some logic in what you're saying. Part of me feels like a weight is being lifted from my shoulders, though. I believe the chances of my needing patches to stabilize anything are near zero (the system runs for months without problems) and owing to the more or less atypical defenses I have put up around my systems I doubt malware will ever get close enough to probe for weaknesses. Having been on 8.1 for a long time, dropping back to 8.0 would feel, well, a little weird. That being said I do from time to time crave the file system performance that was lost in 8.1 vs. 8.0. And yeah, I already don't see any evidence of Metro at all. Thanks, though, for your "think outside the box" advice. :-) -Noel
  15. 1 point
    Makes sence since _IEnumConnections_RemoteNext_Proxy, and _IEnumConnectionPoints_RemoteNext_Proxy are missing.
  16. 1 point
    Not in this thread, no. If it's related to XP x64, open a new thread in the XP x64 subforum, that's how it's done.
  17. 1 point
    Wow! I wasn't cognizant you were the developer, @wfunction! Your tool rocks! But you do know that already, I guess... Anyway, sorry: I'll certainly report any further issue at the project page... I didn't because I'm tired of "XP? update your OS!" replies I get everywhere, my bad. I see now you're striving to keep it compatible all the way throughout the Win32 capable OSes. And yes, I do confirm 5.0.3 is working great on XP, so thank you! And, BTW, @Dave-H do try it, it's really great! And it's portable: no installation needed.
  18. 1 point
    Well, the functionality is still there. In fact, with this change it is better. When you click on an image and it shows in that black band, you can now do two things that you couldn't previously (or last time I tried). You can save-as in the preview and get the original image. Before, trying to do this would result in getting the thumbnail from google. You can view image (in the context menu on most browsers) and view the original image on the hosting domain, which is the equivalent of the "View Image" button that used to be on Google Images. These two things work in Firefox and Palemoon, and I suspect any browser that has "view image" in context menu. BUT I concede that the saving of images directly from the Google Images search results issues I mention were like that "in the past" and those behaviours may have changed sometimes between then and now, but I had not noticed this ability until the view image button was removed... because I hadn't the reason to try alternate methods.
  19. 1 point
    Hi Gang, I was recommended to post here, from another tech site, as my questions are NT4 related. For fun, I picked up an old laptop, a Dell Latitude D610 and installed NT 4.0 (workstation) on it. Got all drivers (plus USB) working fine, except the wireless card, and as near as I can tell, no drivers existed for that card that are older than Win2k. My problem comes in, that although I have Shell32,dll at version 4.72.something, I cannot get any browser better than IE 6.0 installed. Note, that's IE 6.0 no updates. Here's where I run into issues: (1) Any links to all the SPs and other fixes for IE6? (2) I have SP6a on the laptop, but I know there are tons more hotfixes out there. Rather than trying to install them 1 by 1, is there a more elegant method? Finally, VLC. Completely goes stupid with version 1.0.5, will install, won't run, throws a long error message missing somethingGDIsomething I think. Any solution for A/V streaming with modern formats? Thank you kindly for your help
  20. 1 point
    Hi! Programs don't generally do this themselves; installers do. Do you mean I should make an installer that does this? That seems unnecessary since it's just 1 executable. You can just put it in whatever folder you like and then create a shortcut yourself -- just right-click the file and go to Send To -> Desktop (create shortcut). Then you can drag the shortcut wherever you'd like.
  21. 1 point
    I can see too, but yes, it's extremely annoying because not everyone wants to have to load an ad-ridden, slow as heck, unorganized javascript website that immediately tells you to subscribe to their newsletter and put your first born up as a sacrifice before continuing onto their site. What honestly happened to fair use? How many times do (most) people take images and claim them as their own and then make a profit over them? Just like service animals, it's thanks to those few that take 7 miles when given an inch and it ruins it for everyone else.
  22. 1 point
  23. 1 point
    Updated first post, and sorry for leaving this thread non-updated for so long. With the death of my step-dad and other personal life issues getting in the way, I have not found much time to update this thread, and just barely enough to update the Windows Update Lists.
  24. 1 point
    I just found out something very interesting for both Vista and 7: https://support.microsoft.com/en-us/help/4012371 I also found this pdf file from Microsoft detailing this service: https://download.microsoft.com/download/C/5/1/C51D8E55-5538-4F21-8C9D-A66DB31C4B46/SQL_Server_and_Windows_Server_Premium_Assurance_Datasheet.pdf Microsoft probably knows how s*** Windows 10 (and its related Server offerings) are for enterprises, and is milking the NT 6.0/6.1 cashcow for all it's got. In fact, if you go to the lifecycle page, you can see it mentions the 6 years extended support: https://support.microsoft.com/en-us/lifecycle/search?alpha=windows server 2008 Seems like this agreement could extend to Server 2012/R2, but I haven't found concrete dates on that, aside from the same support page: https://support.microsoft.com/en-us/lifecycle/search?alpha=windows server 2012 Anyway, if we could get a hold of someone (anyone) who had access to this licensing agreement and could provide the updates, we could be seeing Windows Vista and 7 support up until 2026!!!
  25. 1 point
    MS18-02-2K8_INTL: https://community.ivanti.com/docs/DOC-66122
  26. 1 point
    Of course, if you actually use it and are aware of the risks. There are plenty of people, though, who have it installed simply because they did a full installation, have never used it and probably don't even know about the functionality. I think it makes sense for them to remove it.
  27. 1 point
    Congratulations Dave! You're now the OP of a new thread. I think I gave it a passable title, but you may change it at will, by editing the 1st post, as you know. I'm not positive I've caught all the pertinent posts, so please do revise both this an the parent thread for posts out of place. Is it fully solved now? Hope so. If not, then do try v. 3.5.1609.100... and read this, too: it's what makes me think all of those v. 3.5.1804.* may not work right. Of course, it's just my 2¢.
  28. 1 point
    I would say that 2.141 s is 75% faster than 3.752 s, while 2.141 s represents 57% of 3.752 s. (if fast/faster go with speed, not with time taken) Anyway 82% seems off. jaclaz
  29. 1 point
  30. 1 point
  31. 1 point
    It would be nice to have a released version, but why not just run the debug version until it's released? -Noel
  32. 1 point
  33. 1 point
    Hello. Dear bigmuscle, I would like to know about the new version of aero glass? Could you tell me please when will update build of Aero Glass with improving indexation? I ask this question because I can't use my Windows 10 without your program =) However I have big troubles with MS Office 2016, Microsoft Visual Studio, Microsoft C++ and other programs. When I type text I have bugs with real-time updating on my screen. It is the bug of indexation. If I uninstall Aero Glass from my PC than problem will be solved. I did it for being sure that it is Aero Glass affect to those problems with the invisible text. Unfortunately, I don't want to use Windows 10 without AERO GLASS, but I can't use a lot of programs because this bug creates impossible conditions for use.
  34. 1 point
    Validation occurs Error number: 0x80072F19 when updating Windows today WindowsUpdate.log Misc WARNING: DownloadFileInternal failed for https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab: error 0x80072f19 WUWeb FATAL: CheckIfClientUpdateNeeded failed: error 0x80072f19 Both methods can be used successfully overcome Redirect http:// to https:// or Enable Enable SSL 2.0 Note: If not successful, update to IE8 and Windows Update Agent 3.0
  35. 1 point
    For your information, this error occurs under Internet Explorer 8, traceable after a reinstallation of Windows XP. Installed is the Windows Update Agent v7.6 (Info). Furthermore, I create my own update rollups (which it certainly is not), as a little note. Maybe even a user has to deal with this problem, then at least there is a solution. @mixit Have also made a test with the Comodo Firewall 8.2.0.4591, with the original update KB4074852 it comes to your described error message, with the manipulated KB4074852 it works.
  36. 1 point
    Seems to be a general problem after the recent downtime: Also, since then I've been constantly getting the "please disable ad blockers" message (and don't see any ads), even though I'm not blocking anything on MSFN (tested with different browsers).
  37. 1 point
    I cannot post topic, site returns error code: EX1364 When I try to create a new one, site throws me an error. Posting here because, it seems, I can't start a new one, but I can reply. Topic that fails to get posted does not contain any fancy code or attachments, no reserved characters in title etc. Just long wall of plain text (3222 signs) with single [ code ] marker. I disabled all browser addons and still no clue what's wrong. I use Current Stable Firefox on Windows 7 x64. I also tried IE 11 for troubleshooting, plain, not modified version that is usually not used, and the same code is being returned. Attachment below:
  38. 1 point
    For experimental users I have modified KB4056615 and KB4074852. For KB4056615, the original NTFS.sys (The version was changed from 5.1.2600.5512 to 5.1.2600.7392) file was implemented, as well for KB4074852 the file oleaut32.dll (The version was changed from 5.1.2600.7248 to 5.1.2600.7424) and KB4018556-v2.CAT (name adapted to KB4018556-v2x.CAT) copied from KB4018556-v2. Available for the Windows language version ENU, DEU, ESN, FRA, ITA, NLD, PTB, PTG, CSY, DAN, ELL, FIN, HUN, NOR, PLK, RUS and SVE. AU, WU and MU are no longer offered after the installation of the modified updates KB4056615 and KB4074852. Before installation, the two original must be uninstalled before! If interested, send me a PM.
  39. 1 point
    8.1, if appropriately tweaked, isn't too bad, and is surprisingly similar to 7, but more up to date, so that isn't necessarily a bad thing. 10, on the other hand, *can* be tweaked to become somewhat sane, but because of this Windows as a service thing, most of the tweaks won't stick, and MS is constantly changing things so current tweaks stop working. As a result, it's a waste of time to even try at this point, unless one likes to spend most of their time tinkering, rather than doing any actual work. c
  40. 1 point
    As the problem is only in the oleaut32.dll file of KB4074852 and not in the whole update (Kernel32.dll, ntdll.dll, Ole32.dll, Rpcss.dll, Updspapi.dll) this is what I have done to fix it. I do not know if it will be a good procedure but it works: - Search in C:\WINDOWS for all oleaut32.dll files - Copy oleaut32.dll 5.1.2600.7248 550KB to C:\WINDOWS\system32\dllcache - Rename to C:\WINDOWS\system32\oleaut32zzzzz.dll 5.1.2600.7424 534KB - Wait a while for the system to automatically copy it to C:\WINDOWS\system32 - Restart (It may give some errors while shutting down the first time) Malwarebytes work, Find target work... --------------------------------------------------- I add that the list of cpu affected by Meltdown / Spectre is increasing and is already in version 7: https://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/ The Core 2 Duo already appear.
  41. 1 point
    A big hello to admins/mods I am trying to post the following content by starting a new topic in https://msfn.org/board/forum/23-site-amp-forum-issues/ but despite numerous attempts over the last 30mins, this has proved futile All I get after I hit Submit is an error code! ---------------------------------- Sorry, there is a problem Something went wrong. Please try again. Error code: EX1364 ---------------------------------- So am posting it here (as it's somewhat relevant), hopefully one of the mods can transfer it where it's best suited... ************************************* I am usually a poster in the Windows XP/Vista subforums; today, Fri Feb 16th 2018, the forums had been inaccessible from my location for several hours; now, thankfully, are back, but... ... Something has changed in the cipher suites supported by the msfn.org host; a test on the SSL Labs site indicates that TLS 1.2 is now mandatory and the only available choice, plus only four specific suites are supported: Host: msfn.org Cipher Suites TLS 1.2 (server has no preference) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) FS 128 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) FS 256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) FS 128 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) FS 256 I have enabled TLS 1.2 on my Vista laptop (as the original author of this) and could, till yesterday, access the site/forums with IE9, but this is no longer possible ; IE9 (with TLS 1.2 enabled) supports the following suites: IE9 on Vista SP2 with post EOL WS2008SP2 updates Cipher Suites (in order of preference) TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) WEAK 128 TLS_RSA_WITH_AES_256_CBC_SHA (0x35) WEAK 256 TLS_RSA_WITH_RC4_128_SHA (0x5) INSECURE 128 TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK 112 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) FS 128 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) FS 256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) FS 128 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) FS 256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x32) 128 TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x38) 256 TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x13) WEAK 112 TLS_RSA_WITH_RC4_128_MD5 (0x4) INSECURE 128 ... as you can see, there's now no common suite between it and msfn.org ; the same is true for some slightly older Firefox version I sometimes use (that worked OK till yesterday, too...). Posting this using Firefox 52 ESR on Vista, which connects via TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f). Was that configuration change a planned/imperative one put in place by the host owner(s), or perhaps one implemented by some third party such as Cloudflare? Is there some room/consideration for restoring IE9 support (without compromising security and/or forward secrecy)? Thanks in advance for any insight regarding this matter... And huge thanks for this magnificent place, too *************************************
  42. 1 point
    Install xp on MCP73 motherboard,add AHCI drivers via winntsetup,drivers from here . someone report 7B BSOD via winntsetup v3.8.8.6,but everything ok via winntsetup v2.3.6.3 .
  43. 1 point
    no sorry hapxhapx, you can not use the 2929781, 3161639 & 3042058 patches under Vista as those patches require Win7 (Server 2008 R2) or higher and will fail to install saying they're "not applicable to your computer". MS did not make any of those patches for Vista/Server 2008 R0 SP2. note to VistaLover (OP): the KB4019276 updates have been revised mid-November 2017 and there's also a KB4019276 patch available for POSReady 2009 users (ah for those still using XP). Download & install the "revised" KB4019276 patches, installing them on top of the older version.
  44. 1 point
    I don't think I can ever tolerate Windows-as-a-Scam. It's too demeaning to the end user.
  45. 1 point
    yes all are very vulnerable,also i wouldnt recommend using any of these,maybe only google chrome since its smooth and works but its still heavily vulnerable since its quite old now,also im not quite sure what you mean by "casual use" i use it for everything possible and i expect it to work the same as 52esr and yes dx9ex is being used and not dx11
  46. 1 point
    The US is one of the few places that use mm/dd/yy(yy)... most places in the world use dd/mm/yy(yy), while some use (yy)yy/mm/dd. In fact, the latter is more interesting because, if one drops the forward slashes it creates a continuous sequence of growing numbers (yy)yymmdd, unlike any of the other alternatives... This being an international forum, one should expect to see all possible formats, because people rarely realize the way they are most familiar with may be unusual in some English speaking places. In other words, YMMV.
  47. 1 point
    Hi Dibya I am here to support you and windows XP
  48. 1 point
    Thank you. Yes the use of NT4 in 2016 was just an experiment, to see if it was still usable and how much of a PITA it was to configure, patch, etc. It's a mental exercise, nothing more.
  49. 1 point
    Thank you kindly for the extra links. I will install shortly and see how it works. Cheers!
  50. 1 point
    For me the entire OS - every major and minor change is a regression. Cortana is worse than the old menu search, the Taskbar changes are awful, Explorer changes are bad, and there doesn't seem to be any major technical improvement that Windows 8.1 doesn't have. I can't find any positives at all - nothing that is really a big improvement. Probably only the RemoteFX vGPU in Client Hyper-V - but then Client Hyper-V remains crippled overall compared to what Windows Server gives you. The Cast To functionality in Windows 10 is genuinely improved over 8.1 and actually works with a wide range of DLNA and Miracast receiver devices, TVs etc. The Spotlight feature of showing random new beautiful images from Bing on the Lockscreen is very nice but then 8.1 has Lockscreen Slideshow. Or you can just use a nice Photos screensaver which would work on Windows 7 as well. The problems with Windows 10 are far too serious. We have a broken OS updating mechanism now that abuses your internet bandwidth, changes things on your PC however it wants, whenever it wants, downloads unwanted crap from the Store, shows annoying nags. Action Center is just one more headache to manage and clear all the notifications after reading them. Lots of stuff happening behind the scenes which I cannot control. Even if I can control updates somewhat by setting my Wifi to metered, I have no idea how big they are, what exactly are they going to change because many of the changes are undocumented, and so many of my customized tweaks get reset. I don't want to be bothered by large updates frequently so Windows as a Service is a complete deal-breaker. And then the UI which is still a disaster. For me, Windows 10 is a very strong case of negatives overwhemlingly outweighing any positives.
×