NT5INF.CAT file is missing after installing Win2k Pro. How do I fix this problem?
460115
you can find the file in windows2k pro CDROM\n\nCDROM&#92;I386&#92;NT5INF.CAT
1126392
locate setup.exe.... and double click it.\nIf you are not sure.... find readme.txt file first and read it.\n\nNote: Installation procedure of different program varies.
1004389
go to google download that specified mmissing dll and copy it into that software folder where all other dll files are...and also copy it windows folder where OS is installed...win 2000the path is C:&#92;WINNT&#92;system check it out in XP ..if this doesnt works all i can say download it again...
559908
best thing to do is get a full .iso of cd then mount that thru alcohol 120 then play\ntry mounting the main .exe file with the w3 icon
494818
There's a thread about just that here:\n\nhttp://www.neowin.net/forum/index.php?showtopic=152892\n\nHope that helps!
1142984
Yup, safe mode is the ticket.  Or get a startup manager like WinPatrol or StartupCop and kill them that way.\n\nSometimes you can just rename them - the next time Windows starts it may balk at the missing file but by then you  don't care.\n\nMake sure when you do a manual delete like this search for copies of that file stored as a "automatic backup DLL" to make sure it doesn't come back and haunt you.
586147
modify the boot.ini file in the <drive>:/boot.ini\n(it's hidden)\ngo here to see how you modify it:\nhttp://support.microsoft.com/?kbid=289022
139323
This might be due to winsock2 corruption.you can try the following  Solution \n\n\n#How to determine whether the Winsock2 key is corrupted \n\nTo determine if the symptoms are caused by a problem with the Winsock2 key, use one of the following methods. \n\n\nMethod 1: Use the Netdiag tool \nTo use the Netdiag tool, you must install the Microsoft Windows XP Support Tools. To do so, follow these steps: \nNote \nIf you already have Support Tools installed, go to the second procedure in this section. \nIf you do not have Support Tools installed and you do not have the Windows XP Setup CD, go to Method 2. \nInsert your Windows XP Setup CD \nLocate the Support&#92;Tools folder \nDouble-click the Setup.exe file \nFollow the steps on the screen until you reach the Select An Installation Type screen \nOn the Select An Installation Type screen \nClick Complete \nClick Next \nWhen the installation is complete, follow these steps: \nClick Start \nClick Run \nType the following in the Run box \nCommand \nClick OK \nType \nnetdiag /test:winsock \nPress Enter \nThe Netdiag tool will return the test results for several network components, including the Winsock. \nFor more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v \n\nMethod 2: Use the Msinfo32 program \nNote Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed. \nClick Start \nClick Run \nType in the Run box \nMsinfo32 \nClick OK \nExpand Components \nExpand Network \nClick Protocol \nYou will have ten sections under Protocol \nThe section headings will include the following names if the Winsock2 key is undamaged: \nMSAFD Tcpip [TCP/IP] \nMSAFD Tcpip [UDP/IP] \nRSVP UDP Service Provider \nRSVP TCP Service Provider \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nMSAFD NetBIOS [&#92;Device&#92;NetBT_Tcpip \nIf the names are anything different from those in this list, the Winsock2 key is corrupted, or you have a third-party add-on, such as proxy software, installed. \nIf you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list. \nIf there are more than ten sections in the list, you have third-party additions installed. \nIf there are fewer than ten sections, there is information missing. \nNote These entries represent an installation with only the TCP/IP protocol installed. You can have a working Winsock and see additional entries if another protocol is installed. For example, if you install NWLink IPX/SPX, you will see 7 additional sections, for a total of 17. Below is an example heading of one of the new sections: \nMSAFD nwlnkipx [IPX] \nAlso, each of the new sections that are created by installing NWLink IPX/SPX start with "MSAFD." Therefore, there are still only two sections that do not start with those letters. \nIf the Netdiag test fails, or if you determined that there is Winsock corruption by looking at Msinfo32, you must repair the Winsock2 key by using the steps in the next section. \nHow to Recover from Winsock2 Corruption \nTo resolve this issue, delete the corrupted registry keys, and then reinstall the TCP/IP protocol. \nStep 1: Delete the corrupted registry keys \nClick Start \nClick Run \nIn the Open box type \nregedit \nClick OK \nIn Registry Editor, locate the following keys, right-click each key, and then click Delete: \nHKEY_LOCAL_MACHINE&#92;System&#92;CurrentControlSet&#92;Services\n&#92;Winsock\nHKEY_LOCAL_MACHINE&#92;System&#92;CurrentControlSet&#92;Services\n&#92;Winsock2 \nWhen you are prompted to confirm the deletion, click Yes \nNote Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer aft
742618
Cause:\n\n   1. Keyboard issue\n   2. Miscellaneous corruption\n   3. Corrupt boot.ini file.\n   4. Missing boot.ini file.\n   5. Missing or corrupt ntoskrnl.exe file.\n   6. Windows NT installed on a partition bigger then 7.8GB \n   7. Corrupted hard disk drive or severely corrupted Windows.\n\nSolution:\n\nKeyboard issue\n\n    This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer. \n\nMiscellaneous corruption\n\n    Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626. \n\nCorrupt boot.ini file\n\n    This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.\n\n    Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492. \n\nMissing boot.ini file\n\n    Microsoft Windows XP users:\n\n    If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.\n\n    Microsoft Windows NT and Windows 2000  users:\n\n    To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.\n\n       1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.\n       2. In the setup menu, type R to start the repair.\n       3. When prompted for the ERD diskette insert the diskette and inspect the startup environment.\n\nMissing or corrupt ntoskrnl.exe file\n\n    If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.\n\n       1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.\n       2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.\n       3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.\n       4. Select the operating system you wish to fix, and then enter the administrator password.\n       5. Type expand d:&#92;i386&#92;ntoskrnl.ex_ c:&#92;windows&#92;system32\n       6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.\n       7. Type exit to reboot the computer.\n\nWindows NT installed on a partition bigger then 7.8GB\n\n    If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below.\n\n    OS Loader v4.01\n    Disk I/O error status=00000001\n    Windows NT could not start because the below file is missing or corrupt: winnt&#92;system32&#92;Ntoskrnl.exe\n    Please reinstall a copy of the above file.\n\n    If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.  \n\nCorrupted hard disk drive or severely corrupted Windows\n\n    Attempt to check the hard disk drive for any errors by running the chkdsk error. To d
962072
well seems u have done everything, almost. here is something u can try. if u have a winxp cd, try sfc/scan now
240032
Well, it appears that it more than likely has to do with either the Windows Installer version or account permissions on the folder where the .msi (Windows Installer) file is located. Please check the reference link that I have supplied. It explains the problem, and provides a way or two to fix it. =)
533151
it would be in the recycle bin of the system on which the disk is physically located. instead of going through the ntwk drive, log in to that system and check the recycle bin. \nBest Of Luck.
69911
Create an account on a win2k box - login name has to be the same that you're using to log in to Win98 comp. \n\nShould work.
552493
yo boobooed\nthe easiest fix, is to boot from your windows xp cd, and when given options, the first time it asks, say intstall, the secon time say repair, it will do a non-destructive install and replace any bad or missing files or associations.\nYou could check in the recycle bin and if it is in there, restore it
598898
Try System Restore, and if that does not work, you have to buy the "Windows XP PRO, or Home Installation CD."
39483
Assuming you're running WinXP and IE Ver. 6 - \n\nFirst, see if you've got a copy of wininet.dll in your C:&#92;I386 directory.  If so, just copy it to the C:&#92;WINDOWS&#92;SYSTEM32 directory, then restart your computer. \n\nIf that doesn't work, download the file from here:\n\nhttp://www.dll-files.com/dllindex/dll-files.shtml?wininet\n\nIt's not the most recent version, but should work.\n\nAfter you've downloaded the file, copy it to your C:&#92;WINDOWS&#92;SYSTEM32 directory\n\nRestart the computer.
139584
re-install the service pack if u r using win Xp. for other os sorry