Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/04/2019 in all areas

  1. Microsoft has shut down the Search Assistant. "ie.search.msn.com" now redirects to "bing.com" which doesn't support "srchasst\srchasst.htm" (or "srchcust.htm"). Scan your registry for the string "ie.search.msn.com" or "srchasst" and replace that URL with a new one of your choice such as "http://ie.search.yahoo.com/{sub_rfc1766}/srchasst/srchasst.htm". See: &tab; answers.yahoo.com/question/index?qid=1006043010329 (Alternately, you can install some mid-2000's malware and let it hijack the search assistant for you!)
    2 points
  2. https://cutt.ly/M5nX0 so "the incident" is over.
    2 points
  3. One thing I still use my vintage Vista system for is watching and recording TV, and I wonder if the list needs a DVR/PVR category. (Of course there are hardware requirements: a suitable TV tuner of some sort, but hardware is OT here.) Vista Home Premium and Ultimate included Windows Media Center, which in most cases was not really different from Windows XP Media Center Edition. Some later Vista systems shipped with TV Pack 2008, which was almost equivalent to Windows 7's Media Center. (The first page or two of a 2015 Green Button thread might be of interest to some Vista users.) Of course Media Center with TV Pack is only supported insofar as Microsoft/Rovi are still providing electronic program guide data, which might end when support for Windows 7 ends. For those who are running Vista Basic or Business, or who wouldn't dare to download TV Pack from a third party, or who have TV Pack but are dissatisfied with Rovi's North American EPG data, or who want something that can be used as a "back end" for Kodi (formerly XBMC), one alternative is NextPVR. I recently installed the current 4.2.3 version of NextPVR on Vista, and I'm very satisfied with it. This was the first time I had a reason to install .NET Framework 4.6, which is now a prerequisite. The 4.2.3 installer will install Visual C++ 2017 for you. Newbies may find this software to be not very user-friendly, but MSFN members generally seem to be the kind of users who could handle it. You may have to download one or more decoders, e.g. in North America you are going to need an AC3 audio decoder (perhaps AC3Filter or LAV). Unfortunately there is no free guide data for North America beyond the several hours' worth that can be obtained from over-the-air ATSC broadcasts, so a Schedules Direct subscription is highly desirable.
    1 point
  4. after adding manifest: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" processorArchitecture="*" name="GetVersion" type="win32" /> <description>GetVersion</description> <ms_asmv3:trustInfo xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"> <ms_asmv3:security> <ms_asmv3:requestedPrivileges> <ms_asmv3:requestedExecutionLevel level="asInvoker" uiAccess="false" /> </ms_asmv3:requestedPrivileges> </ms_asmv3:security> </ms_asmv3:trustInfo> <ms_asmv3:application xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"> <ms_asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings"> <dpiAware>true</dpiAware> </ms_asmv3:windowsSettings> </ms_asmv3:application> <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <!-- Windows 10 --> <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/> <!-- Windows 8.1 --> <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/> <!-- Windows 8 --> <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/> <!-- Windows 7 --> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> <!-- Windows Vista --> <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/> </application> </compatibility> </assembly> it shows in win10 1703: GetVersion: 0x3AD7000A GetVersionExA (OSVERSIONINFOA*): dwOSVersionInfoSize 0x00000094 dwMajorVersion 0x0000000A dwMinorVersion 0x00000000 dwBuildNumber 0x00003AD7 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] return TRUE GetVersionExA (OSVERSIONINFOEXA*): dwOSVersionInfoSize 0x0000009C dwMajorVersion 0x0000000A dwMinorVersion 0x00000000 dwBuildNumber 0x00003AD7 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] wServicePackMajor 0x0000 wServicePackMinor 0x0000 wSuiteMask 0x0100 wProductType 0x01 wReserved 0x00 return TRUE GetVersionExW (OSVERSIONINFOW*): dwOSVersionInfoSize 0x00000114 dwMajorVersion 0x0000000A dwMinorVersion 0x00000000 dwBuildNumber 0x00003AD7 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] return TRUE GetVersionExW (OSVERSIONINFOEXW*): dwOSVersionInfoSize 0x0000011C dwMajorVersion 0x0000000A dwMinorVersion 0x00000000 dwBuildNumber 0x00003AD7 dwPlatformId 0x00000002 szCSDVersion[128] "" [00 00 00 00 ...] wServicePackMajor 0x0000 wServicePackMinor 0x0000 wSuiteMask 0x0100 wProductType 0x01 wReserved 0x00 return TRUE gv=0x3AD7000A gvex=A,0,3AD7,2,,0,0,100,1,0
    1 point
  5. My Windows 10 Pro was a (free) upgrade to Windows 7 Ultimate, years ago. Thats all I know. Today I tested a computer with Microsoft Windows 8.1 Pro (64 bit, sorry no x86 available): gv=0x23F00206 gvex=6,2,23F0,2,,0,0,100,1,0 BTW: my XPSP3 (x86) gave exactly the same values as IntMD's According to this document the return values for Windows 10/8.1 can be (should be?) the same as 8.0's: https://docs.microsoft.com/en-us/windows/desktop/sysinfo/operating-system-version
    1 point
  6. While I'm already also a Win 7 SP1 user, and sometimes even provide it support, my main, day-to-day OS is XP SP3, and I'll cling to it until it becomes nearly impossible to use (I've used 98SE from late 1999 to about 2014, so ca. 14 years as main day-to-day OS, and I hope to use XP SP3 like that for even longer, but my 1st XP install was from late 2007, so I'm not even 12 years on it, yet). I doubt I'll transition fully to 7 SP1 much before 2021 !!!
    1 point
  7. Hmm.. let's see. "Not doing a good job" could easily be defined as "breaking things that already work." For example existing code support for older operating systems. Nice and simple. I fail to see how roytam's software is "abused," give that he is actually fixing things you or Moonchild have broken, on purpose. See above. No one claimed they are official. In fact the About dialog in these builds clearly states they are not. "Not doing a good job" again..? See above. I'd like to see some proof of this supposed "massive confusion." If there is any confusion, it must come from those who are clueless in the first place. You cannot fault roytam for users who are too ignorant to read the About dialog or to deal with any issues here, where the builds are linked, rather than going to you or to the official PaleMoon forum. Also I'd love to see even one example where you or Moonchild or anyone else in your "group" has "cleaned up a mess when something goes wrong" that addressed the first single issue that affected these older operating systems or users of the unofficial builds on these systems. It sounds more to me like you're just a butthurt jerk who is having a tantrum because someone is making your toy work in places where you don't want it to. If you don't like it, write your own closed source program and stop "abusing" Mozilla's existing code. Without Mozilla's existing code, which once again I will remind you already provides compatibility for the systems roytam is targeting, and which you have intentionally broken, your pet projects would be nonexistent.
    1 point
×
×
  • Create New...