Windows Forum
It is important to note some RDISK limitations that result from its function and underlying objectives.
Don't use RDISK for backing up the Windows NT registry.
The RDISK utility is not intended for general use to backup the Windows NT 4.0 registry. The RDISK data files only contain essential data required for recovery, not the entire contents of the registry. For a complete backup of the Windows NT 4.0 registry, use a more comprehensive utility tool, some of which are provided in the Windows NT 4.0 Resource Kit.
Don't use RDISK /S or /S- switches on systems that have a large number of users and groups.
Microsoft does not recommend using the /S or /S- switches for RDISK on Windows NT systems that have a large number of users and groups defined in User Manager. The total size of the extracted files on systems with a large number of users and groups may exceed the capacity of a standard floppy disk. As a result, creation of an Emergency Repair Disk will fail. If this happens, an "Emergency Repair Disk" should be created without using one of these switches. In addition, the registry should be backed up.
Using RDISK /S to create an Emergency Repair Disk for Windows NT 4.0
http://www.cert.org/security-improvement/implementations/i028.01.html
(REMOVE SPACES from the pasted URL.)
That article has complete instruction with illustration and other featurea nad limitations.
Maxwell
.
.
Another possibly usefull article stated the flllowing:
"Windows NT disk configuration information is too large to fit on a floppy disk and cannot be saved"
01. As an Administrator in Windows NT, open Disk Administrator.
02. Insert a formated floppy in drive A:.
03. On the Partition menu, press Configuration and Save.
To work around this problem:
01. Run RDISK /S- from the Windows NT 4.0 install.
02. At a CMD prompt, change to the %SystemRoot%\Repair folder.
03. Type: expand system._ system
04. Use Regedt32 to select the HKEY_LOCAL_MACHINE key.
05. On the Registry menu, Load Hive.
06. Navigate to the %SystemRoot%\Repair folder and click the System file that you expanded in step 03.
07. When prompted, enter JSI for a Key Name.
08. Select the JSI key and delete all the ControlSet### keys and subkeys, ignoring the Access Denied message(s).
09. Select the JSI key.
10. On the Registry menu, Save Key and name it JSISYS.
11. On the Registry menu, Unload Hive.
12. Exit Regedt32.
13. Copy the JSISYS file to a floppy disk and then rename it, on the floppy, to System.
14. Resume tip 2119 at step 04.
Source:
http://www.jsiinc.com/SUBE/tip2100/rh2157.htm
(REMOVE SPACES from the pasted URL.)
Best of luck,
Maxwell
.
.
The entire contents of the %systemroot%\repair folder is copied to the ERD, so you must keep its size under 1.44MB. Should the folder grow too large, take the ERD from the original Windows NT installation (or from \repair2) and copy only the sam._ and security._ files into the %systemroot%\repair folder. The folder should now be small enough to make an ERD. If it’s not, you need to reduce the size of setup.log. Edit setup.log and locate the line “[Files.WinNt]”, which is followed by a long list of file names. You can safely delete any of these file names that do not begin with %systemroot%\SYSTEM32\. At some point in this list you may find a line “[Files.InRepairDirectory]”; do not delete anything after this line!
There are two things you should keep in mind:
See this link for the rest of the article:
http://www.hughes2k.com/files/erd.doc
(REMOVE SPACES from the pasted URL.)
That's all. I hope it helps,
Maxwell
by hughmiller
Thank you! Max, I has try your Idea and it work.
Hugh
by hughmiller
This discussion is closed to new replies.
Sort by Trending