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

7 Neutral

About Ascii2

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

1,408 profile views
  1. I have been having diffuculty finding decent Wireless, IEEE 802.11 client utilities for Windows XP. Windows XP comes with its Wireless Zero Configuration utility and service to manage and connect to Wireless networks, but the utility has notable shortcomings: Many EAP Authentication methods are not available. Only one of multiple access points with the same SSID/name is displayed. Identifying access points details such as frequency, channel, or MAC addresses is not possible. The purpose of this thread is to document and facilitate the identification and finding of alternative software wireless clients. I shall attempt to organize information into this post. Please provide information regarding known software clients and experiences. I am also available via PM for issues that some may rather not post directly here. For example, if there is a concern about a software mod that may break a license, about software that normally should not normally be distributed, or for other reasons, please, send a PM. I have been doing research for such clients recently, and have been able to identify some usable clients, but unfortunately, many such clients have been discontinued and are no longer easy to find. The sources for other wireless software client utilities are typically of the following classes: Enterprise software - software intended for business use and targeted for business customers. Hardware designers (ODMs) or manufactures (OEMs) - drivers for hardware products often also have included wireless client utilities. These software, however, can be limited to particular hardware. Party that provides wireless services (typically for a fee) - software may connect to a provider's services and also provide the means to connect to foreign/other networks. Other parties that provide wireless software clients - This may include open source software and other closed-source software released to the public. My notes about software found: Cisco AnyConnect Secure Mobility Client I have not found a copy of the software to try. No other known information yet. Cisco Secure Services Client I have not found a copy of the software to try. No other known information yet. SecureW2 Enterprise Client I have only found a restricted (trial) version of the software to try. No other known information yet. XpressConnect by Cloudpath Networks I have not found a copy of the software to try. No other known information yet. Juniper Odyssey Client I have not found a copy of the software to try. No other known information yet. Open1X No other known information yet. Boingo Wireless Utility Last known working version: 2.3.0073 (please post if there is a newer version) Status: Apparently Discontinued URL: https://web.archive.org/web/20071010213632/http://www.boingo.com/downloads/BW1201/boingoinstaller.exe Notes: Tested on Windows XP Professional with Service Pack 3. Although software has better support for EAP Authentication options, I have often not been able to achieve connections where I should. Other access points with the same SSID are also not shown. WPA/WPA2/IEEE 802.1X Supplicant Last known working version: 0.7.3 Status: Apparently Discontinued on Windows. URL: http://w1.fi/wpa_supplicant/ Similar threads to this issue have been posted here at MSFN.org for Windows 95/98 and Windows 2000, but not for Windows XP. The Windows 9x thread appears to provide all the information I found from the other sources and is available at:
  2. Correct, @i430VX. The problems that have experienced should affect POSReady and Windows Embedded Standard branded versions of Windows XP. The problem is one of quality control and, in my opinion, company management. The problems with updates are often not limited to Windows XP and troubles with updates may be seen with other Microsoft operating systems and software. There does not appear to be proper quality control anymore. I do not believe that Bill Gates would have tolerated the level of quality releases that are being provided now. The current Microsoft CEO, Satya Nadella, appears less concerned about the quality of the product and attempts to have profitability via other means or considerations. I believe that this had been well discussed earlier in this thread, but was unfortunately lost after what was reported to be a server crash. You are probably experiencing the affects of applying KB4487085. You may have system services that do tolerate what KB4487085 breaks very well and resulted in Blue Screens. If problems persists after truly removing KB4487085, an affected service may be damaged or other Windows component may be damaged. This is, unfortunately, something that many times happens when blue screens are experienced. To recover from the issue, try disabling system services that are unnecessary to load and try booting the machine again. I would also recommend running CHKDSK to check for a file system error. These things would have to be done after booting a different operating system instance such as Windows Recovery Console.
  3. @dencorso, The KB4486463 update does appear to have been correctly. The system "dllcache" and "Driver Cache\i386" versions of "ntkrnlmp.exe" were both updated to version 5.1.2600.7649 and without having to do anything special. Although I use a multicore processor, I use the ACPI Uniprocessor PC HAL, and am therefore not actually using the KB4486463 kernel. My "ntoskrnl.exe" in use is version 5.1.2600.7581.
  4. I had troubles after applying KB4487085. After installing KB4487085, many programs would not run correctly and I would sometimes receive errors like the following: "The procedure entry point sprinttf_s could not be located in the dynamic link library msvcrt.dll." "Error loading C:\WINDOWS\system32\NvCpl.dll" The second error message appear to be for the nVidia driver software. I removed KB4487085 and things seemed corrected.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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
  12. 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).
  13. 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.".
  14. 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.
  15. 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.