top of page

GrowinGoodness Group

Public·15 members
Rezo Bragin
Rezo Bragin

Tips and Tricks for Creating and Using an Emergency Repair Disk for Windows NT 4.0

A Microsoft Windows Emergency Repair Disk (ERD) is a specially formatted diskette that creates backups of important system files and settings and is used to troubleshoot and repair problems in Microsoft Windows NT and Windows 2000 systems. An ERD is used in conjunction with the Windows repair option. The Emergency Repair Disk provides only the ability to restore the system to a bootable state. It is not a replacement for system and file backups.[1] Note: The emergency repair disk is not to be confused with a standard boot diskette as it cannot be used alone.

Windows Nt 40 Emergency Repair Disk Download

Unlike the ERD in Windows NT 4.0, the Windows 2000 ERD does not store registry information. Rather, Windows creates a copy of registry files in the \Winnt\Repair\RegBack directory when the ERD is created.[2] The ERD is not bootable. The original Windows NT or Windows 2000 setup disks need to be used to boot the computer. From there, choosing the option to repair the system will prompt the user for the ERD.[3]

Answer: (b) RDISK.EXEExplanation: There are the following steps to repair disk in windows NT 4.0:Step 1: Go to the search button in windows NT 4.0, then type Command Prompt.Step 2: Then type "RDISK.EXE" and press enter.Step 3: Then open a pop-up window. This pop-up window will update the emergency repair disk.

--MikeIn defeat: unbeatable. In victory: unbearable. -- Winston Churchill RE: Blue Screen - Windows NT jdunderhill (TechnicalUser)24 Jul 03 09:14You may need to register dlls using Regserv??Only a long shot but a possibility RE: Blue Screen - Windows NT fishax (MIS)(OP)24 Jul 03 18:49Blue Screen STOP Message C0000135 Appears at StartupThe information in this article applies to: Microsoft Windows NT Workstation 3.51 Microsoft Windows NT Workstation 4.0 Microsoft Windows NT Server 3.51 Microsoft Windows NT Server 4.0This article was previously published under Q173309 IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows RegistrySYMPTOMSWhen you start Windows NT 4.0, the system stops and displays the following message: Stop: c0000135 Unable to Locate DLLThe dynamic link library FILE_NAME could not be found in the specified path Default Load Path. CAUSEThis error can occur for any of the following reasons: File_name.dll is missing from the %SystemRoot%\system32 directory. Your computer is loading the Sermouse.sys file. If File_Name.dll exists, the software hive may be corrupted and, therefore, cannot load.RESOLUTIONThe method for checking whether File_name.dll exists varies, depending on the file system in use. For NTFS file systems, install a parallel copy of Windows NT into an unused directory, and then verify that File_name.dll exists in the %SystemRoot%\System32 directory. For FAT File Systems, an MS-DOS installation disk can be used. If the file exists, it is possible that the registry software hive has been corrupted. Check the integrity of the software hive by using the following procedure: WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" online Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" online Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. NOTE: In every case tested in which the software hive could not be loaded, the File_name was Winsrv.dll. From a parallel installation of Windows NT, click Start, and then click Run. In the dialog box, type Regedt32. On the toolbar for Registry Editor, click Window, and then click the window with the following name:HKEY_LOCAL_MACHINE ON LOCAL MACHI Select the HKEY_LOCAL_MACHINE key in the left pane of the window. On the menu bar, click Registry, and then click Load Hive. Browse to %SystemRoot%\System32\config, where %SystemRoot% is the correct installation of Windows NT that you want to check. Click the file named Software. In Windows NT 4.0, this will be the file named Software that does not have an extension, and has a generic Windows icon next to it, not the file with the Notepad icon. In Windows 3.51, the file name is System, has no extension, and has a generic Windows icon. The system will prompt for a key-name to use in loading the hive. You can type whatever you prefer in the dialogue box; Work would be a good choice. The hive is corrupted if you receive the following error message:Registry Editor could not load the key. The file is not a valid Registry file.After you have determined the problem, there are several ways to resolve it. The software hive can be restored by making a parallel installation from backup files. It can also be restored from the latest emergency repair disk (ERD), using the procedure outlined below. Note: Windows NT 4.0 requires the Setupdd.sys file to be copied to disk 2 of the Windows NT Setup disks to perform this repair without a CD-ROM. This file can be found in Service Pack 2 or later. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 150497 How to Repair Windows NT System Files Without a CD-ROM Attached Start the system with the Windows NT Setup disks. At the first screen, press R for repair. Use the arrow keys to move the cursor to Inspect boot sector, and then press the ENTER key to uncheck this selection. Then perform the same procedure to uncheck Verify Windows NT system files and Inspect startup environment. After this, only Inspect Registry Files should have a check mark. Next, move the cursor to Continue (Perform Selected Tasks), and then press ENTER. Let Windows NT perform the mass storage detection. When prompted, select S to specify additional drivers if your computer requires OEM drivers. When prompted to do so, insert the emergency repair disk that was originally created for this computer, or press ESC to let Windows NT search for repair information for version 3.51 or version 4.0. Setup will then ask which registry files should be replaced. Using the arrow keys, move the cursor to Software (Software Information) and press ENTER. Next, move the cursor to Continue (Perform Selected Tasks) and press ENTER. When finished, restart your computer when Setup prompts you to do so. RE: Blue Screen - Windows NT TreeHead (IS/IT--Management)25 Jul 03 12:20Refer to Microsoft TechNet, article Q173309. It states that hive corruption is the cause of this, most commonly reported as a problem with winsrv.dll - hope this helps. RE: Blue Screen - Windows NT oxfords1 (TechnicalUser)11 Aug 03 10:20the way i was able to fix this error was slaving the drive to another machine which became the f drive. then i went to f:\winnt\$ntservisepackuninstall$ folder and opened it. i double clicked on the spuninst folder and located the bat file. right click on it and hit the edit button. when notepad opens the bat file hit the edit button again and click on replace. put in the find box c: and in the replace box put in the drive letter that your drive is slaved at. in my case f:. hit replace all and once it finishes close save and then double click on that bat file. it's going to uninstall the service pack. restart your machine and you will be able to get in. then reload the service pack RE: Blue Screen - Windows NT chaositect (IS/IT--Management)8 Sep 03 15:02I just came across a machine with this problem. I had to slave the drive to another NT machine to work on it. After a little investigation, I found the winsrv.dll file and the software hive to be intact and functional. Investigating a little further, I found errors in the event log pointing to bad blocks on the slaved hard drive. I downloaded the appropriate hard drive utility (in this case fujitsu's fjtd.exe) and ran a diagnostic on the drive. The utility found and fixed the bad blocks. I put the hard drive back in the other computer and booted up without a problem. This may just be a fluke, but it's worth checking if the other options here don't work for you. RE: Blue Screen - Windows NT fishax (MIS)(OP)13 Sep 03 14:01Hi,I had similar problem, and eventually had to restore image to the drive. The winsrv.dll file was NOT corrupt. I narrowed it down to a file called SOFTWARE in the Winnt/Config (I believe was the location - which I guess is the Software Hive) file, and when it was replaced, it did boot up the sytem fine, but I did have some Network Card and TCP/IP binding issues. Eventually restored from an image I happened to find luckily. Interesting post regarding Uninstalling the Service Pack and Running the Diagnostic Utility on the would be worth trying this the next time it happens. Usually not all workstations have Repair Disks created. RE: Blue Screen - Windows NT jockovonred (TechnicalUser)25 Sep 03 11:54thank you oxfords1!!!i'm running win2ksp3. we are using the SUS server to push updates and one of these is win2ksp4.(i knew it was sp4 that it tried to install due to the timestamp and dates on the uninstall directory.)during a hang of the automatic updates, the server was rebooted which caused the "winsrv.dll - unable to locate dll" BSOD message.last known good and safe mode failed to start windows as it would continuously reboot after receiving the error message.i didn't need to slave the drive since i already had a parallel install so i tried loading the registry hive per the MS article Q173309/Q168646 and it would load i backed up and replaced the winsrv.dll from a different hotfix install with the same results and error message upon reboot.thus i tried your technique, to uninstall the service i ran the bat file, rebooted and i'm in.i reapplied sp3 (just to be sure) and am working without error.thanks for the great insight on this.cheers! umm...yea...sure RE: Blue Screen - Windows NT fishax (MIS)(OP)29 Sep 03 23:45Can you explain how exactly you unistalled the previous version of Service Pack. I had tried this solution, by modifying the "batch" file. It did uninstall the Service Pack from the Slave Drive in question, but not only did the Error STILL COME UP, but it messed up my original drive. Fortunately had an image to restore. RE: Blue Screen - Windows NT tnx01 (TechnicalUser)30 Sep 03 12:23Thank you, oxfords1! I became a member just to be able to say it. Your advice saved me time and efforts. I had this ptoblem under Win 2000 Pro. I installed second instanse of Win2k, went to original winnt\$ntservisepackuninstall$\spuninstal and run spunint.bat without editing it. Then restarted PC and it worked great! It was that simple, no Microsoft suggested hassle, no previuosly made backup required.Great tip, thanks again! RE: Blue Screen - Windows NT pkrohnert (MIS)2 Oct 03 23:22I'm going to echo tnx01's post - oxfords1's suggestion saved me a LOT of trouble! I didn't even bother doing the second install of a Win2k instance, I just dropped the drive into another computer as a slave drive, modified the spuninst.bat file (replacing all occurrences of c:\ with g:\), and then ran the batch file. I then put the hard drive back into the original computer, and booted up - with no problems at all. An easy, 10-minute (or less) fix. I'm re-applying SP4 now. Thanks again.PK googletag.cmd.push(function() googletag.display('div-gpt-ad-1406030581151-2'); ); Red Flag This PostPlease let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.CancelRed Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action.


Welcome to the group! You can connect with other members, ge...


Group Page: Groups_SingleGroup
bottom of page