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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Ascii2

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

1,359 profile views
  1. WinUSB is an access driver with API/functions to access USB devices in a generic manner. It is often installed for use with mobile devices (such mobile-marketed tablet computing devices, GPS navigation systems, etc.). Modern MTP implementations and connectivity software for mobile devices are often implemented via WinUSB. I believe that 6.1.7600.16385 was the last/latest compatible version of WinUSB for Windows XP.
  2. It looks like Amazon.com has corrected or made changes to allow Silverlight to work again (it was supposed to) on Amazon.com; previously an error would be returned. You do not need to pay to use all Amazon video content that requires DRM. Instead of trying to watch the main video, view the trailer if it is available. The trailer has the same requirements as the paid streaming videos.
  3. Ascii2

    Antivirus for xp?

    ESET's current antivirus appear about as lightwieght as Kaspersky Endpoint Security 10 with the Endpoint control options turned-off. It should be noted that current Kaspersky products for Home users are no longer decent, as they now require Microsoft .NET Framework. @Dibya - Can you confirm whether you believe that your ability to use ESET NOD32 Antivirus 11 series is due to your compatibility updates? I recommend the following pages to determine current version numbers and, support status, and official Windows XP support: ESET Home Products End-of-Life Policy: https://support.eset.com/kb3678/ ESET Business Products End-of-Life Policy: https://support.eset.com/kb3592/ Also, ESET Endpoint Antivirus appears to be intended by ESET to support Windows XP with Service Pack 3 for a longer time than its ESET NOD32 branded products.
  4. I license for Windows Embedded POSReady 2009 or other version should not be needed to report a bug. Further, Windows Embedded POSReady 2009 and Windows Embedded Standard 2009 were (and might still be) offered as trials for evaluation. Although heinoganda has kindly offered his modified patches, it is still preferable that Microsoft actually does its job properly and fixes its product. If one can afford to take the time to report the issue, it may be beneficial to do so.
  5. For those that are unfamiliar with LvlLord Intelligent TCPIP.SYS patcher / EventID 4226 patch 2.23d, if interested, see for more information: http://www.lvllord.de/?url=tools http://www.lvllord.de/?url=downloads I do wish that the patcher were updated to allow for better automation of the patch to allow the patcher to be used unattended.
  6. Yes it certainty is. On a related note, the boolean preference variable "plugin.load_flash_only" should be set to false to disable the blocking of the NPAPI plugins, Flash Player notwithstanding (which is not blocked regardless). On the Firefox 52 ESR channel, this variable is set to false by default; the variable is set to true by default on some of the other Firefox channels. That method may be used; however, if your goal is to be on a true ESR version of Firefox (such as Firefox 52.1.0), then it is more reliable to use the Firefox installer to update the installation of Firefox. The installer is intended to update, upgrade, and downgrade installations of Firefox and is also converts the Firefox channel in the process. I am using the last version of Pale Moon for Windows XP, (version 26.5.0). Pale Moon was intended to not have support for the the Gecko Media Plugins and should not work with them.
  7. You can delete the "plugin-container.exe" file to prevent the plugin-container from being used. However, the code to otherwise allow the use of a plugin without the plugin-container has been removed in Firefox 43; if there is no plugin-container, the plugin will fail to be used. The plugin-container troubles is a major problem, especially for those of us using Windows 2000, Windows XP, or Windows Server 2003. Its concept seemed decent, but its implementation never worked well. I had previously submitted a Bugzilla bug report to Mozilla in hopes that the forced use of plugin-container may be reverted, but, so far, the idea was rejected. I would recommend that support for the changes in the Bugzilla bug report be given. Perhaps a favorable change may result. The Bugzilla bug report is located: https://bugzilla.mozilla.org/show_bug.cgi?id=1348630
  8. Thank you for the information and leads. They have been quite useful. The timestamp detail I found interesting before can now also be explained (the files timestamps are preserved from the ZIP archive decompressions rather than downloading the timestamp information).
  9. The "OpenH264 Video Codec provided by Cisco Systems, Inc." (pseudo) plugin is not what it purports to be or what Cisco or Mozilla have purported it to be. I wonder what it actually does and whether or not it is a dependency for other Gecko Media Plugins (GMPs). I intend to test whether the "Primetime Content Decryption Module provided by Adobe Systems, Incorporated" can work without "OpenH264 Video Codec provided by Cisco Systems, Inc.".
  10. First of all, thank you very much, mixit, for your great guide. I do find it interesting that retention of the original plugin file timestamps from server are preserved. Firefox no longer allows preservation of the file timestamps normally in the new Firefox download API (other download API was available for Firefox of version lesser than 26). To actually change the file timestamp for a user downloaded file using the former download API, an extension was necessary; particulary, the Preserve Download Modification Timestamp extension. I guess things are different when the action is being performed on Mozilla's behalf. Are the downloaded plugin files the same for All versions of Firefox on the different supported operating systems? If not, how do the vary? Can the files downloaded from 32-bit Firefox be used with 64-bit Firefox or vice-versa? The default down URL for the files appear to be: https://aus5.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml Is there a way or a guide to determine what the various possible values for the variable in the URL are? Those variables appear to be: %VERSION% %BUILD_ID% %BUILD_TARGET% %LOCALE% %CHANNEL% %OS_VERSION% %DISTRIBUTION% %DISTRIBUTION_VERSION% It would be good to be able to download and preserve those combinations.
  11. I do not believe that you overlooked something. It rather appears that Intel failed to property write the driver to support Windows Small Business Server 2008.
  12. I do note that the in somewhat, much earlier Intel USB 3.0 driver packages, Windows Small Business Server 2008 was not originally represented as supported, but Windows 7 and Windows Server 2008 R2 were. Later versions of the Intel USB 3.0 driver were documented by Intel to support Windows Small Business Server 2008. Thank you 2008WindowsVista for your report. Did you try your test on the x86-64 version of Windows Vista? It would seem that the driver's documentation might be erroneous with regards to Windows Small Business Server 2008 support or Windows Small Business Server 2008 may provide something different that allow it to be compatible. If Windows Small Business Server 2008 is truly compatible, perhaps the changes or differences between Windows Vista and Windows Small Business Server 2008 can be applied to Windows Vista (then I would think the driver should install).
  13. The information regarding the AMD Catalyst 15.6 Beta Drivers package I was able to find is available: https://web.archive.org/web/20150629000845/http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspx The AMD Catalyst 15.6 Beta Drivers package downloads from AMD have apparently been made unavailable. I download what appear to be the AMD Catalyst 15.6 Beta Drivers package from the links referenced in: http://forums.videocardz.com/topic/1243-amd-catalyst-156-beta/ The AMD Catalyst 15.6 Beta driver package does not contain recent (since about year 2011) AMD motherboard chipset drivers. I was wondering I the latest Windows 7 AMD chipset drivers should be used on Windows Vista or another version or versions.
  14. Apparently, Intel provides actual USB 3.0 drivers, but in USB driver specific packages. The drivers are supposedly available for (given information from the Read Me files): Windows 7 Windows Server 2008 R2 Operating System Windows Small Business Server 2008 Although, Windows Vista is not is officially supported, Windows Small Business Server 2008 (only available as x86-64 operating system) is given as supported. My understanding about Windows Small Business Server 2008 is that it is based on Windows Server 2008, which shares are code-base with Windows Vista. Perhaps the Intel USB 3.0 drivers may be installed on Windows Vista (at least the x84-64 version). I do not have Windows Vista installed, myself, and it would be difficult for me to test this. The latest Intel USB 3.0 driver package for Windows Small Business Server 2008 appears to be version https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22824
  15. Intel chipsets through Z87 and Intel C226 are officially supported by Intel for Windows Vista and Windows XP. The last version of the Intel chipset driver installation utility for Windows XP is version which can be found: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23061 (Disregard operating system list specified on the page; it is erroneous. View the Read Me file for correct operating system listing) The Intel chipset configuration utility of version, officially supports the following operating systems: Microsoft Windows 2000 Microsoft Windows XP Microsoft Windows XP Professional x64 Microsoft Windows Vista Microsoft Windows Vista x64 Microsoft Windows 7 Microsoft Windows 7 x64 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2008 R2 x64 Microsoft Windows 8 Microsoft Windows 8 x64 Microsoft Windows Server 2012 Microsoft Windows Server 2012 x64 Microsoft Windows 8.1 Microsoft Windows 8.1 x64 Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 R2 x64 The version of the Intel chipset configuration utility is supposed to also support Windows Vista. Later version of the Intel Chip Driver installation software do not support Windows XP and do not officially support Windows Vista, but they do Windows 7. Perhaps the Windows 7 chipset driver INFs are also applicable to Windows Vista? My understanding is that the Intel Chipset driver installation utilities do not actually install driver files on Windows; the driver files are included with the Windows or its updates. The Intel Driver installation utility selects and configures the drivers and defines their parameters.