Guth, on 25 February 2013 - 15:39, said:
since this is bumped I wanted to ask, why are they saying "msvcrt.dl_"
whats the .dl_ all about?
On older versions of Windows NT (pre-Vista) Microsoft used per-file compression to keep the size of the install disk as small as possible. (This is in contrast to the way Microsoft has done compression since Vista - compressing the entire install image as one file.) Their naming convention for compressed files was to replace the last letter of the file extension with an underscore. Therefore msvcrt.dll
compressed to msvcrt.dl_
. Any of the compressed files on the installation disc may be expanded back to their original, uncompressed state using the expand
utility built into Windows.
Therefore the One Post Wonder who necroed this thread is suggesting replacing the damaged copy of msvcrt.dll
with the original one from the Windows XP installation disc. However, he is making the assumption that the i386
directory has been copied from the installation disc to the root of the C
drive. While that was once common practice for many OEMs, it is far from standard. If C:\i386
doesn't exist on your machine, you could substitute the path for your CD drive (i.e. D:\i386
) once you have inserted your original Windows XP installation disc.
In general in a situation where you need to replace a corrupt file installed on your system with a good copy from the Windows installation disc, it is probably better to run an SFC scan than to expand the file manually. System File Checker will check to make sure that each Windows system file is valid and replace it automatically if not. (It does still require your Windows installation disc, however.) As an additional advantage, while you cannot replace individual system files in Windows Vista and later the same way you could in earlier versions of Windows due to Vista's more modern installation method, SFC is supported by Microsoft and has been included with every version of Windows since Windows 2000. Enter the following command at an administrator command prompt to initiate an SFC scan: