Ascii2

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.

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.

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.

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

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).

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.".

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.

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.

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).

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.

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 4.0.4.51: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22824

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 9.4.0.1027 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 9.4.0.1027, 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 9.4.0.1027 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.

The AMD Catalyst 15.6 beta package (or packages?) is no longer available from AMD. I was able to acquire what I believe to be the AMD Catalyst 15.6 beta package. The package, however, contains the display drivers, but does not contain the AMD motherboard chipset, southbridge, or storage controller drivers. Is there an AMD Catalyst 15.6 beta package with the AMD motherboard chipset, southbridge, or storage controller drivers? What packages should be used to install the AMD motherboard chipset, southbridge, and storage controller drivers on Windows Vista?

It may be partially true but they did remove some older files like the IPv6 stack and several other very old updates for Win2k. Many of the Visual Studio 6.0 downloads are also missing.

Thanks xpclient. Also, the updates are now appearing on Microsoft Update for me. For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats with Service Pack 3, Microsoft Update now lists: Security Update for Microsoft Office 2007 suites (KB2596856) Security Update for Microsoft Office 2007 suites (KB2596615) Security Update for Microsoft Office 2007 suites (KB2596880) Security Update for Microsoft Office 2007 suites (KB2596672) Security Update for Microsoft Office 2007 suites (KB2597162) Security Update for Microsoft Office PowerPoint 2007 (KB2596843) Security Update for Microsoft Office 2007 suites (KB2596785)

Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats with Service Pack 3, updates are not appearing on Windows Update, though I have been able to verify that some security updates do exist. What are the update for Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats with Service Pack 3?

WinHex 16.6 SR-4 x86 ( http://www.winhex.com/winhex/index-m.html ) is also able to find an NTFS file by file number. The issue described in this thread in now solved. Thanks again for the contributions.

I have seen many workstations with Pentium 4 processors (typically while at business locations). The machines seem to have no trouble with YouTube so long as bandwidth is sufficient (sometimes an ISP may throttle some content, or, especially in the case of Google, the content provided throttles the content to select ISPs (to varying degrees)).These machines, however, run (my) customized software sets. I have configured and picked-myself the software and configurations of the machines (inefficient software that results in poor system resource use is rejected). Many machines have been running for over 10 years and running software and content well.

I have a (I think t5hat I had gotten my installation files from a Microsoft CD of a special older version of Visual Studio or Visual Studio .NET that had many extras such as the installation files for Internet Explorer 6 with SP1). I try to always maintain original file dates for my files; if there are files that I may have for which the file dates are uncertain, let me know, and I my check my copies for verification.

No; if a program or utility kills itself after killing all active processes, it cannot then invoke the SHUTDOWN.EXE utility.

In the past Microsoft has been inconsistent regarding correctly supporting products they should support for the entirety of the product planned life.I suspect that Microsoft will try to determine the impact to itself of failing to support the Windows XP Embedded series and whether it is preferable to fail to correctly support.

I have used Windows XP Embedded, Windows XP Embedded with Service Pack 2, and the re-branded Service pack 3 version of the product, "Windows Embedded Standard" or sometimes "Windows Embedded 2009" or "Windows Embedded Standard 2009" (this is when the namings of the embedded operating systems become much more confusing). Windows XP Embedded (and its variants at other Service Pack levels) is a software suite that builds an instance of Windows XP using the many sets of components (organized using SQL database). The components are Windows XP components that come with Windows XP Professional plus other sets of components that do not come with Windows XP (such components are or were, however, available on the Microsoft website in various places for download). I believe that instances of Windows XP Embedded could all the components of Windows XP Professional (I, however, would use a less components) as well as just the bare components for Windows XP to run. The updates specific to Windows XP Embedded typically address issues that do not manifest in the other version of Windows XP (typically licensing files bugs). I have not used the "Windows Embedded POSReady 2009" variant, but I expect that it is a re-branded version of Windows XP Embedded with predefined sets of components that are thought to be used at a point-of-sale. Also, from looking at the pictures provided by tomasz86, it seems that the POSReady version comes with an installer that may fully install the Windows XP components. Windows XP Embedded distribution was mostly manually installed, with only an initialization at first boot (which is probably where the REGSVR32 entries are run and the Windows Registration files are merged). The POSReady version seems to fully install the instance of Windows XP.

Thanks for the suggestions. I shall examine them in the coming days.

CHKDSK has just run on a computer with multiple disks. CHKDSK was invoked by Windows XP Professional with Service Pack 1. The main part of the CHKDSK report is: Checking file system on G: The type of the file system is NTFS. Volume label is Local Disk. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. The segment number 0x1a0f900000000 in file 0x1b0f9 is incorrect. Correcting a minor error in file 110841. Cleaning up 173 unused index entries from index $SII of file 0x9. Cleaning up 173 unused index entries from index $SDH of file 0x9. Cleaning up 173 unused security descriptors. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Windows has made corrections to the file system. 1465136000 KB total disk space. 525536320 KB in 232542 files. 98532 KB in 36439 indexes. 0 KB in bad sectors. 326440 KB in use by the system. 2048 KB occupied by the log file. 939174708 KB available on disk. 4096 bytes in each allocation unit. 366284000 total allocation units on disk. 234793677 allocation units available on disk. It seems that there may have been a problem in file 110841 on the G: volume. How would I determine which file file 110841 is?

Also, I noticed that Dogway has stated the he is using Window XP Professional x64 Edition. QCHAIN.EXE was developed originally for use on 32-bit Windows 2000 family operating systems; it may or may or work well on that operating system. I am not sufficiently familiar with 64-bit versions of Windows Server 2003 to be able give good council on this. Also, the FOR loops above are only applicable when it is desired that updates packages with branching start evaluating from the default branch.