I there any other way (other than Ghost) to clone a Windows NT 4.0 Workstation with 4.0 Gb Primary and 15 GB on a Logical Drive.I have Tried to use ghost 2001 but it doesnt work I am not sure why, any software or any backup program that can clone the whole Hard disk.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Clone WIndows NT Workstation
- Thread starter AGA
- Start date
Perhaps you could post the problems you are having with Ghost as this software will do what you are looking for.
I am sure that you will find other free utils out there for ghosting, but keep in mind that not to many of them will do or have sid replacement apps. Ghost walker will change your NT sid which is something you must do.
I am sure that you will find other free utils out there for ghosting, but keep in mind that not to many of them will do or have sid replacement apps. Ghost walker will change your NT sid which is something you must do.
Guest_imported
New member
- Jan 1, 1970
- 0
u can use a cross over wire and transfer all the files that way too, but i think u mostly want to image the computer....right?
I personally don't even botter with wire or over network.
These days just about every pc has a CDRom. Using a very inexpensive CD writer you can make as many copies of your image as you need. No need to load trafic on the network for imaging.
These days just about every pc has a CDRom. Using a very inexpensive CD writer you can make as many copies of your image as you need. No need to load trafic on the network for imaging.
Symantec posts this fix on Ghost2001 and it works well:
Errors: "Error 37013: An internal inconsistency has been found" and "37013 Out of memory" while using Ghost
Situation:
While launching Ghost, creating an image file, or performing a disk-to-disk clone, you see the following or similar messages regarding Error 37013:
"Error 37013 An internal inconsistency has been detected. If the problem persists contact Symantec Technical Support"
"Abort 37013 Out of memory. Abort details output to Ghost.err. Please contact your local Symantec Support Center."
When you examine the Ghost error file, Ghost.err, or Ghosterr.txt, you find that Ghost reports the computer's total memory as less than the actual RAM on the computer. For instance, the error file might report Total Memory as 16 MB when the computer actually has 128 MB or more.
Solution:
These messages appear to be due to problem with how Ghost performs caching. To resolve the problem, use the -WS- and -WD- switches to turn off Ghost caching:
Ghost.exe -ws- -wd-
Steve Harder, MCSE
Errors: "Error 37013: An internal inconsistency has been found" and "37013 Out of memory" while using Ghost
Situation:
While launching Ghost, creating an image file, or performing a disk-to-disk clone, you see the following or similar messages regarding Error 37013:
"Error 37013 An internal inconsistency has been detected. If the problem persists contact Symantec Technical Support"
"Abort 37013 Out of memory. Abort details output to Ghost.err. Please contact your local Symantec Support Center."
When you examine the Ghost error file, Ghost.err, or Ghosterr.txt, you find that Ghost reports the computer's total memory as less than the actual RAM on the computer. For instance, the error file might report Total Memory as 16 MB when the computer actually has 128 MB or more.
Solution:
These messages appear to be due to problem with how Ghost performs caching. To resolve the problem, use the -WS- and -WD- switches to turn off Ghost caching:
Ghost.exe -ws- -wd-
Steve Harder, MCSE
where are you writing the ghost image to ?
I would only ghost the C drive and create the d: drive later manually. or otherwise copy the gost via the network to a server or other system.
We have now changed over to Powerquest software where we are using drive image pro 4.0
So far that works fine. create a dos bootable disk and copy it accross the network. it can also write directly to a CD writer.
I would only ghost the C drive and create the d: drive later manually. or otherwise copy the gost via the network to a server or other system.
We have now changed over to Powerquest software where we are using drive image pro 4.0
So far that works fine. create a dos bootable disk and copy it accross the network. it can also write directly to a CD writer.
I have had this same thing happen with ghost. I found if you create your bootdisk with MD-DOS instead of PC-DOS (as the program will do) the error went away. I'm not sure what causes this, but this works when creating an image. I've also had similar problems using pc133 ram. Go figure. If I turn the ram down to 100MHz the trouble went away.
You might want to try those solutions.
You might want to try those solutions.
As to where to Ghost the image to:
You can Ghost a partition to another partition on the same or alternate drive, to an LPT, network or USB connected computer, or to an alternate device like a CD Writer or Jaz drive; you cannot Ghost a drive to the same drive or to an image on the same drive.
You can Ghost a partition to another partition on the same or alternate drive, to an LPT, network or USB connected computer, or to an alternate device like a CD Writer or Jaz drive; you cannot Ghost a drive to the same drive or to an image on the same drive.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
