Windows CE Platform Builder 2.11 QFEs
Download Summary:
The official patch updates released for Platform Builder 2.11.
You are not currently logged-in. To download you must be logged-in and be a subscriber or have met our community quality and reputation requirements as a free user - Find out more · Subscribe |
Version: | 1 - 35 |
Developer: | Microsoft Corporation |
Download Size: | 10 KB - 197.75 MB |
Release Date: | 26/01/2000 |
Language: | English |
Popularity: | 2667 |
Number of Downloads: | 0 |
Added By: | C:Amie on 28/04/2020 3:47:31 PM |
Overview:
Windows CE 2.11
QFE Pack - Fixes 1 ~ 29
(less 15, 17)
How to Install the QFE set:
QFE's should be installed on a uniform number basis. Starting at one, copy the files over to their respective location in your build tree. You will be overwriting the previous file, do not be afraid to do so. You may also overwrite a file numerous times in some instances. As long as you are following the copy through the order of QFE's (Starting at 1 and working through 28), you will have no problems. 15 & 17 have been omitted - they were absorbed by a later QFE.
If you have installed previous QFE's:
If you have installed previous QFE's (for Windows CE 2.11), you need only install the latest QFE's you don't already have installed. For instance, if you had 1~3 previously installed, all you need to install now is 4~28. You do NOT have to reinstall all the previous QFE's.
Fixes that were made in this QFE set:
QFE #1
Components: FATMAIN
FATFS was not rewinding the file pointer in cases where the cluster number was beyond the maximum cluster number used by the disk. Using OLE CopyTo function seemed to cause this problem (not caught by standard filesys tests).
QFE #2
Components: EDIMEJPN & CDLCTL
The edit control leaked memory if the user typed some characters, converted and then typed some new characters without hitting Enter.
Previously, the WM_SYSCOPYDATA, which had handwriting information, was being treated as an IME control message. The IME control does not permit recursively processing messages so when the WM_SYSCOPYDATA message was being processed, the IME could not update the composition window contents. Now, the WM_SYSCOPYDATA is not treated like an IME control message and the data is passed correctly to the default composition window.
QFE #3
Components: DHCP
For Windows CE 2.10 a mechanism was added to allow OEM's to request additional data from the DHCP server. The software that handled the registry information was incorrectly determining the length of the data, which could cause a crash. The DHCP component was updated to correctly set the length.
QFE #4
Components: TCPSTK
When the TCP/IP Stack received an ICMPRedirect message it would add an extra reference to the NTE structure. This would stop the adapter from being unloaded if the PCMCIA card was ejected (builtin adapters suffered no ill affects).
QFE #5
Components: NETBIOS & AFD
The redirector was not informed of built-in adapters at startup. This change will indicate to the Redirector component the existing adapters as well as handle the associated resolver addresses.
QFE #6
Components: WININET
The URL parsing functions were not correctly handling multi-byte strings.
QFE #7
Components: WAVEAPI
This QFE fixes two bugs in the Wave subsystem. First there was an error path where a critical section was not released (previous wave drivers had not reported errors in this place). The second change was to forward the FORMATCHOOSE_FORMAT_VERIFY messages to the replacement UI component so that it can correctly list the supported formats.
QFE #8
Components : MGFNTFIX
This allows the MGDI FontFix component to get the version number from the registry. Previously this was hardcoded to application version under 2.00. Fntfix looks for registry entries under "System\GDI\V1\FontAlias". Keys of the form"name:size"="name2:size2" will specify font mappings. When an app asks for a font with name=name and size=size, it will actually get a font with name2:size2. The new registry entry is of the form "version"=dword. Font fixes will be applied to all apps which were compiled previous to the version specified by the dword . (eg GetProcessVersion() < dword)
QFE #9
Components: LMem (component of COREDLL)
It was possible under certain circumstances that the memory system would fail to return freed memory back to the system. This happened with large block allocations at the end of the heap.
QFE #10
Components: DHCP & AFD
This QFE addresses three DHCP problems and one TCP issue:
DHCP: The Transaction ID used in exchanges should be updated for subsequent operations. For renewals Windows CE was not generating a new XID.
DHCP: If the server does not give T1 and T2 times the Windows CE DHCP code does not properly calculate the defaults.
DHCP: The DHCP client was not updating the Seconds field in the DHCP header. Some relay agents will filter packers with low values in the Seconds field. The change was to update the Seconds field correctly for each transmission.
TCP/IP: The Windows CE 2.10 release inadvertantly removed the ability to disable the Nagling option on a socket (setting the TCP_NODELAY socket option).
QFE #11
Components: PCL
The PCL printer driver was inheriting the GPE functions from the primary display driver. It was overwriting some of the ones it needed to but not the PowerHandler function. This caused it to call the primary displays power handler on suspend. Some OEM's display drivers did things in their PowerHandler function that could cause a crash if called twice. The fix is to have a private version of the power handler and use it.
QFE #12
Components: AFD
This changes the amount of virtual memory allocated to be used for socket memory in the protocol manager (AFD). The memory is not committed until used so this will not change existing memory usage but allow a higher peak memory usage for more total sockets in the system.
QFE #13
Components: LMem (component of COREDLL)
When a process does large heap allocations there was a situation where fragmentation could occur and the memory would never be reclaimed.
QFE #14
Components: TCPSTK, AFD, & NDIS
A collection of networking fixes.
TCPSTK: Added the initial KeepAliveInterval and KeepAliveTime to the registry.
NDIS: INdisMChangeEthAddresses should return PENDING, not SUCCESS.
TCPSTK: Increased the maximum connections to 200.
AFD Handle EnQSendData() returning short count in low memory.
NDIS Correct return code for IP Multicast support.
QFE #16
Components: AFD & TCPSTK
This QFE fixes two separate networking issues. Issue 1 (TCPSTK), if the DHCP server returns the same IP address for the client and default gateway then the client should issue ARP's for all network addresses. Issue 2, as part of QFE10 the return value for the unsupported SetSockOpt call was changed (inadvertently) this caused some Backward Compatibility issues with other components. This fix changes the return value back to the incorrect value.
QFE #18
Components: NK, CEPC OAL, DHCP, COREDLL, FATFS, & AFD
x86 NMI passed to the OAL.
Loss of DNS functionality while using UNIX DHCP server.
Heap allocation method changed.
Two programs writing data to files on an ATA disk at the same time caused data corruption.
AFD Exception occurs if packets arrive after the socket closed.
PCMCIA: Data corruption when data & code are on same storage card.
NDIS was leaking a thread handle for each card removal insertion.
NDIS hangs if two ethernet adapters of the same name are inserted.
QFE #19
Components: DHCP & NDIS
NDIS: System exception occurs with repeated insertion and removal of a network card.
The DHCP client now checks both the Transaction ID and the MAC addresses before accepting a DHCP ACK as it's own.
DHCP: Multiple built in adapters aren't handled correctly.
QFE #20
Components: DHCP
Data does not get throttled by AFD, causing the system to run out of memory if the app sends a lot of data.
TCP is being given a deleted NDIS ptr when out of pagebufs.
QFE #21
Components: NK
This QFE changes the OpenResource() function of the kernel to not take the loader critical section.
QFE #22
Components: TCPSTK
DevMan hang when removing NIC with UDP Multicast listener active.
QFE #23
Components: DHCP
DHCP bug in INIT_REBOOT. If options are requested from the server using the [HLM\Comm\<adapter instance>\Parms\Tcpip\DhcpOptions] key, the DHCP client will not handle the INIT-REBOOT (warm boot with existing DHCP lease) state correctly. In this case, the state machine will generate improperly formatted DISCOVER and REQUEST messages (the ciaddr field is filled in with the previous IP, which is not allowed in the INIT-REBOOT or SELECTING states in RFC 2131). Most servers will ignore these packets, causing DHCP to time out (after approx 36 seconds) and fall back to the INIT state, at which point DHCP operation should resume normally.
This bug does not appear if DHCP options aren't requested in the registry. The bug exists in the released versions of DHCP.DLL for CE 2.10, 2.11, and 2.12.
QFE #24
Components: AFD
The Windows CE DNS lookup code did not handle DNS responses with the tc (Truncate) bit set. Such messages were discarded causing gethostbyname() failures.
QFE #25
Components: SoftKB
There was a memory leak when calling SipSetCurrentIM.
QFE #26
Components: Object Store
There was a breakpoint in the FSDMGR code, which would fire in the case where there was more than one FSDMGR controlled file system driver, when an instance of such a driver was unloaded. If a kernel debugger was not attached to the system, this causes an unhandled exception. Once this occurs, subsequent storage card insertions will fail, requiring a warm boot of the device to recover.
QFE #27
Components: Kernel (Scheduler)
In certain circumstances, interrupt events could be lost on PPC platforms.
This was a problem caused by the PowerPC HandleException() routing not updating the PendEvents bit field atomically. If the scheduler happened to be clearing a bit in this flag when an external interrupt occurred, the bit for that interrupt could be lost when the scheduler resumed.
QFE #28
Components: COM
Memory leak in repeating Create/Destroy of ActiveX Control.
QFE #29
Components: TCPSTK
For built in network adapters, the DHCP client will send DISCOVER packets with the client identifier set to 0. Since this field is used by the server to identify clients, it may result in the same IP address being handed out to multiple devices on the network, leading to connectivity problems for all devices affected. The problem does not occur with installable (e.g. PCMCIA) network adapters. This problem was exposed by SP1 QFE19.
System Requirements:
Windows CE Platform Builder 2.11
Windows NT 4.0 SP3 or higher
Download:
You are not currently logged-in. To download you must be logged-in and be a subscriber or have met our community quality and reputation requirements as a free user - Find out more · Subscribe
Donate:
HPC:Factor believes that the Internet is a better place without the constant displaying of adverts on community website resources and as such does not carry 'ad-words', banners, pop-up's or any other form of paid advertising.
Please help to pay for the download that you are getting from us today and help to support our desire to run the site without paid subscriptions or advertising by making a donation to the site. It doesn't matter how much or little you donate, but by donating you will help to ensure that we can continue to offer some of the Internet's most popular, rarest and unusual downloads for Windows CE devices for now and for the future.