Cspman.dll - dll file called 'Creative CSP Manager' is a part of Microsoft Windows program developed by Creative Technology Ltd. Some applications or games may need this file to work properly. If cspman.dll is missing, whenever you start the application/game you may experience various kinds of errors. To fix those errors, please read the Recommended Solution below. Background: I have XPST500 which came with boot drive hooked to Promise Ultra 66 hard drive controller card, later upgraded to Promise Ultra 133.Am having great difficulty re-installing Win98SE OEM to the Promise Ultra 66 card using the Win98 OEM CD and floppy startup disk that came with the puter. No difficulty in re-installing to the motherboard IDE controller socket, but that is a tired.
WININET.DLL has so far existed in at least nine variations considered by Microsoft to have sufficient external impact to deserve at least a difference in the minor version number.
| WININET Version | Distribution | ||
|---|---|---|---|
| Internet Explorer | Windows | NT | |
| 4.0 | 3.00 | ||
| 4.70 | 3.01, 3.02 | Windows 95 OSR2 | |
| 4.71 | 4.0 | ||
| 4.72 | 4.01 | Windows 98 | Windows NT 4.0 (SP4 and higher) |
| 5.0 | 5.0, 5.01 | Windows 98 SE | Windows 2000 |
| 5.50 | 5.5 | Windows Me | |
| 6.0 | 6.0 | Windows XP Windows Server 2003 | |
| 7.0 | 7.0 | Windows Vista Windows Server 2008 | |
| 8.0 | 8.0 | Windows 7 Windows Server 2008 R2 | |
Note that the original Internet Explorer 3.0 has a WININET.DLL with a lower version number than was ever bundled into a Windows release.
- I tried to install the guest addition on windows 98 in order to share my folders but it gives me this message: The vboxwindowsadditions.exe file is linked to missing export ntdll.dll. It used to work before but now it doesn't. If i can't get support for this i am going to have to uninstall Virtual box and install it again.
- The Windows 98 OS was released by Microsoft on June 25, 1998, as an update to Windows 95. It was not actually a full update for Windows 95. It was an update only for critical and critical updates, fixes and new devices.
- If it finds a problem, it will try to replace the problematic system files from a cached version that’s on your PC. If SFC can’t replace the files, the Deployment Image Service and Management Tool (DISM) can check the corrupted files then download and replace the files through Windows Update. Press the Windows key + X on your keyboard.
Builds
Though the next table fusses over such details as build numbers and dates, it is certainly not meant as a comprehensive list even of builds that had formal, public releases. For that, consult Microsoft, who manufacture the software and are surely best able of anyone to present a definitive record. Bear in mind, however, that if Microsoft’s published documentation could sensibly be relied on as either comprehensive or accurate, then you could not now be reading these notes.
Builds are arranged in increasing order of the file version as recorded in the executable’s resources. This version number is readily visible using Windows Explorer either in a so-called infotip for the file or by accessing the Version tab in the Properties dialog for the file. Programmers know this version number as coming from the so-called root block of the version-information resource, specifically from the dwFileVersionMS and dwFileVersionLS members of a VS_FIXEDFILEINFO structure.
The date stamp shown for each version is more obscure. File dates are easily modified after the executable is built and are anyway liable to be shown differently when read from different time zones. However, there is in each executable’s header a date stamp which is set when the executable is built and is not commonly changed afterwards. It is readily accessible to anyone with programming knowledge and appropriate tools, e.g., Microsoft’s own DUMPBIN utility.
In the days when Microsoft had two operating systems named Windows, most Internet Explorer versions supplied the executable separately for Windows and NT (and in some cases with a further separation for NT 4.0 and Windows 2000). Where two date stamps are presented on the same row for an Internet Explorer release, it means that the Windows and NT executables differ only in the file header’s date stamp and checksum (and that the date stamps are from the same day).
| File Version | File Header Date Stamp | Size | Package |
|---|---|---|---|
| 4.0.1234.1 | 314061F3 (9th March 1996) | 140,592 | Internet Explorer 3.00 (NT) |
| 4.70.0.1157 | 321A64A6 (21st August 1996) | 289,552 | Windows 95 OSR2 |
| 4.70.0.1215 | 3262C54A (16th October 1996) | 291,600 | Internet Explorer 3.01 |
| 4.70.0.1300 | 33348AF2 (23rd March 1997) | 299,280 | Internet Explorer 3.02 |
| 4.71.1712.5 | 3421723A (19th September 1997) | 368,400 | Internet Explorer 4.0 (Windows) |
| 342173A1 (19th September 1997) | 368,400 | Internet Explorer 4.0 (NT) | |
| 4.72.2106.5 | 3472465D (19th November 1997) | 369,424 | Internet Explorer 4.01 (Windows) |
| 347247A2 (19th November 1997) | 369,424 | Internet Explorer 4.01 (NT) | |
| 4.72.3007.0 | 34DC2858 (7th February 1998) | 369,936 | Windows NT 4.0 SP4 Windows NT 4.0 SP5 Windows NT 4.0 SP6 |
| 4.72.3110.0 | 35474FB6 (30th April 1998) | 380,928 | Windows 98 |
| 3553AA2A (9th May 1998) | 370,448 | Internet Explorer 4.01 SP1 (Windows) | |
| 3553AB7D (9th May 1998) | 369,424 | Internet Explorer 4.01 SP1 (NT) | |
| 4.72.3612.1700 | 36EEB3DF (17th March 1999) | 371,984 | Internet Explorer 4.01 SP2 (Windows) |
| 36EEB5A8 (17th March 1999) | 371,984 | Internet Explorer 4.01 SP2 (NT) | |
| 5.0.2314.1003 | 36F1D8D8, 36F1DBA8 (19th March 1999) | 459,024 | Internet Explorer 5.0 |
| 5.0.2614.3500 | 3720A22F (24th April 1999) | 459,024 | Windows 98 SE |
| 5.0.2920.0 | 3844D03C (1st December 1999) | 467,728 | Windows 2000 |
| 5.0.3103.1000 | 391CC0EC (13th May 2000) | 443,664 | Internet Explorer 5.01 (Windows 2000) |
| 3947EB48 (15th June 2000) | 467,728 | Windows 2000 SP1 | |
| 5.0.3105.105 | 3941292C, 39412A8A (10th June 2000) | 459,024 | Internet Explorer 5.01 |
| 5.0.3502.4449 | 3C1FE612 (19th December 2001) | 465,168 | Windows 2000 SP2 |
| 5.0.3502.4619 | 3D3D0210 (23rd July 2002) | 461,584 | Windows 2000 SP3 |
| 5.0.3700.6713 | 3EF274DF (20th June 2003) | 466,704 | Windows 2000 SP4 |
| 5.50.4134.100 | 39403C4B (9th June 2000) | 495,616 | Windows Me |
| 5.50.4134.600 | 393D876E, 393D8BEB (7th June 2000) | 476,432 | Internet Explorer 5.5 |
| 5.50.4807.2300 | 3B5CD622, 3B5CD978 (24th July 2001) | 480,528 | Internet Explorer 5.5 SP2 |
| 6.0.2600.0 | 3B7DFE16 (18th August 2001) | 593,920 | Windows XP |
| 3B7DFE48, 3B7DFFE3 (18th August 2001) | 583,680 | Internet Explorer 6.0 | |
| 6.0.2800.1106 | 3D6DFA1C (29th August 2002) | 599,040 | Windows XP SP1 |
| 3D6E2AA6, 3D6E2BF1 (30th August 2002) | 585,728 | Internet Explorer 6.0 SP1 | |
| 6.0.2900.2180 | 411096D4 (4th August 2004) | 656,384 | Windows XP SP2 |
| 6.0.2900.5512 | 4802A13A (14th April 2008) | 666,112 | Windows XP SP3 |
| 6.0.3790.0 | 3E8024A0 (25th March 2003) | 623,616 | Windows Server 2003 |
| 6.0.3790.1830 | 424377F6 (25th March 2005) | 661,504 | Windows Server 2003 SP1 |
| 6.0.3790.3959 | 45D70AEE (18th February 2007) | 670,720 | Windows Server 2003 SP2 |
| 7.0.5730.11 | 45353713 (18th October 2006) 45516526 (8th November 2006) | 818,688 | Internet Explorer 7 for Windows Server 2003 Internet Explorer 7 for Windows XP |
| 7.0.6000.16386 | 4549BE19 (2nd November 2006) | 822,272 | Windows Vista |
| 7.0.6001.18000 | 4791A7B2 (19th January 2008) | 825,856 | Windows Vista SP1 Windows Server 2008 |
| 7.0.6002.18005 | 49E03852 (11th April 2009) | 828,416 | Windows Vista SP2 |
| 8.0.6001.18702 | 49B3AD54 (8th March 2009) | 914,944 | Internet Explorer 8 |
| 8.0.7600.16385 | 4A5BDB3F (14th July 2009) | 977,920 | Windows 7 |
The WININET.DLL executables for all three of the Windows NT 4.0 service packs that include WININET.DLL are identical.
The executables in the Internet Explorer 7 packages for Windows XP and Windows Server 2003 differ only because of rebasing, including to change the file header’s date stamp and checksum.
The executables for Windows Vista SP1 and Windows Server 2008 are identical.
64-Bit Windows (x64)
| File Version | File Header Date Stamp | Size | Package |
|---|---|---|---|
| 6.0.3790.1830 | 42438B4F (25th March 2005) | 1,186,304 | Windows Server 2003 SP1 |
| 6.0.3790.3959 | 45D6CCC7 (17th February 2007) | 1,190,912 | Windows Server 2003 SP2 |
| 7.0.6000.16386 | 4549D36B (2nd November 2006) | 1,018,880 | Windows Vista |
| 7.0.6001.18000 | 4791AE03 (19th January 2008) | 1,011,712 | Windows Vista SP1 Windows Server 2008 |
| 7.0.6002.18005 | 49E04252 (11th April 2009) | 1,014,272 | Windows Vista SP2 |
| 8.0.7600.16385 | 4A5BE0AB (14th July 2009) | 1,193,472 | Windows 7 Windows Server 2008 R2 |
Where two packages are shown for the same build, the executables are identical.
32-Bit Windows on 64-Bit Windows (wow64)
WININET is not sufficiently low-level that the 32-bit builds of WININET.DLL for 64-bit Windows differ from the corresponding builds in 32-bit Windows.
This page was created on 7th September 2010 and was last modified on 8th September 2010.
Copyright © 2010. Geoff Chappell. All rights reserved. Conditions apply.
Microsoft Layer for Unicode (or MSLU) is a software library for Windows software developers to simplify creating Unicode-aware applications for Windows 95, Windows 98, or Windows Me. It is also known as UnicoWS (Unicode for Windows 95/98/Me Systems) or UNICOWS.DLL, or even 'cows'.
Microsoft describes it as providing 'a layer over the Win32 API on Windows 95/98/Me so that you can write a single Unicode version of your application and have it run properly on all platforms.'[1] Previously, software developers had to either provide two separate versions of an application, or perform complex string translations and API decisions at runtime.
Availability[edit]
The MSLU was announced in March 2001, and first available in the July 2001 edition of Microsoft's Platform SDK, which is arguably long after the peak popularity[contradictory] of Windows 95/98/Me.[citation needed]
It had a codename of Godot, which is a reference to the play Waiting for Godot (centered around the failure of a man named 'Godot' to appear and the endless wait for him), because it was felt to be long overdue.[2]
How it works[edit]
Normally, the Windows API provides both A (ANSI) and W (wide-character) versions of most functions. On Windows 95/98/Me, only the A versions are implemented and attempting to call a W version will fail with an error code that indicates that the function is unimplemented. On the Windows NT line of operating systems, both the A and W versions are implemented (however, the operating system generally only internally implements the W version natively, and the A version is usually a translation thunk to the W version).
By adding the UNICOWS.LIB to the link command-line before KERNEL32.LIB, ADVAPI32.LIB, or any other supported Win32 system link library, the linker will resolve referenced symbols with the one provided by UNICOWS.LIB instead.
When a wide-character function is called for the first time at runtime, the function stub in UNICOWS.LIB first receives control and checks if it is running on a Windows 95/98/Me system:
- If so, it dynamically loads UNICOWS.DLL (if it hasn't been loaded yet) and passes control to the corresponding thunking stub in there. The thunking stub translates the wide-character arguments into ANSI strings and then invokes the native A version from the OS, and then translates any returned strings back into wide-character format.
- If the OS natively supports the W version (i.e. the Windows NT line of operating systems), then the function stub updates the in-memory import table so that future calls will directly invoke the native W version without any more overhead.
Because of this technique, when an application is linked against MSLU, only Windows 95/98/Me systems will need the UNICOWS.DLL at runtime, and on all other versions of Windows there is only a slight performance penalty for the first function call.
Cspman Dll Windows 98 Iso
A common problem encountered occurs when some updaters and uninstallers rename or delete the file OLEDLG.DLL, preventing the operating system from loading UNICOWS.DLL. This results in applications, such as OpenOffice.org, reporting that 'Application cannot start because one of the required libraries cannot be found.' This occurs even if UNICOWS.DLL is installed in the system.
References[edit]
- ^'The Microsoft Layer for Unicode on Windows 95/98/Me Systems'. Global Development and Computing Portal. Microsoft. Archived from the original on April 16, 2003. Retrieved April 25, 2019.
- ^Kaplan, Michael S. (February 12, 2005). 'Why/how MSLU came to be, and more'. Sorting it all Out V.. 2!. Archived from the original on June 25, 2014. Retrieved April 25, 2019.
External links[edit]
Microsoft[edit]
- Known bugs in each released MSLU version — maintained by an employee of Microsoft who is the principal developer for MSLU.
Open source alternatives[edit]
Cspman Dll Windows 98 Emulator
- libunicows — provides an MIT-licensed version of only the UNICOWS.LIB link-library, but still requires the Microsoft-provided UNICOWS.DLL or the Mozilla OPENCOW.DLL.
- opencow (previously MZLU) — reimplements both the DLL and LIB link-library as MPL 1.1/GPL 2.0/LGPL 2.1, originally for the Mozilla project.