mhost
09-03-2004, 12:47
Qualche giorno fa ho scritto sul forum per sapere come mai incontravo difficoltà nel trasferire il mio SO (Win2K Sp4) da un vecchio Hd ad uno nuovo. Credevo il problema fosse mio e fossi l'unico a non sapere fare una cosa che con Win98 è semplicissima. Ma leggendo l'ultimo numero di PC Professionale ho scoperto che solo tramite dedicate impostazioni è possibile copiare l'intero contenuto dell Hd.
Questo è quello che sta scritto nel readme di Norton Ghost:
==============================================
5. Cloning Windows 2000 and XP
==============================================
Windows 2000 and XP boot failures
---------------------------------
Boot failures after cloning Windows 2000 and XP systems can usually
be attributed to one of two causes:
Cause 1
-------
Differences between the position and layout of partitions after
the clone have resulted in new drive letters being assigned to
existing volumes by the booting system.
Some elements of the Windows boot process appear to access files
using paths with drive letters.
As a result, when the booting operating system fails to locate the
file due to the drive being allocated a new drive letter, a boot
failure occurs.
Solution
--------
a. Initialize the disk signature using the -FDSZ (force disk
signature zero) switch. Initializing the disk signature forces
Windows to discard any existing drive letters and to start
re-allocating new drive letters from scratch.
Note: Ghost generally performs this during a Windows disk load
operation. It will not perform this initialization if you are
only loading a partition. In this case the -FDSZ switch should
be used to fix a boot failure.
b. Alternately, if you wish to retain the allocated drive letters
use the -FDSP switch (force disk signature preserve). This will
only be required on Windows 2000 and XP disk load operations
that result in a boot failure.
c. To login to the machine you may need to change the absolute
path for the user interface executable in the Windows registry.
Refer to the Microsoft Knowledgebase article Q249321 for
details.
This process will allow the user to login but some other
applications may fail. Refer to the Microsoft Knowledgebase
article Q223188 for details.
Cause 2
-------
Windows did not have the correct mass storage controller driver
configured and loaded for the hardware it is booting on due to
hardware differences between the source and destination machines.
Solution
--------
Clone to machines with similar hardware or if this is not possible
you can use the Microsoft tool Sysprep. The Sysprep INF file,
Sysprep.inf, contains a section [SysprepMassStorage] for
specifying one or more mass storage controllers that you want
Windows 2000 to load before it continues to boot.
Microsoft provides one version of Sysprep for Windows 2000, and
one version for Windows XP Pro. Microsoft do not provide a version
for Windows XP Home.
View the Microsoft Sysprep documentation for Windows 2000 at:
http://www.microsoft.com/windows2000/techinfo/planning/incremental
/sysprep11.asp
You can obtain information on deploying Microsoft Windows XP using
Sysprep from the Microsoft Windows XP Professional CD:
Support \Tools\Deploy.cab\Deploy.chm
Support\Tools\Deploy.cab\Ref.chm
Buona Fortuna
Questo è quello che sta scritto nel readme di Norton Ghost:
==============================================
5. Cloning Windows 2000 and XP
==============================================
Windows 2000 and XP boot failures
---------------------------------
Boot failures after cloning Windows 2000 and XP systems can usually
be attributed to one of two causes:
Cause 1
-------
Differences between the position and layout of partitions after
the clone have resulted in new drive letters being assigned to
existing volumes by the booting system.
Some elements of the Windows boot process appear to access files
using paths with drive letters.
As a result, when the booting operating system fails to locate the
file due to the drive being allocated a new drive letter, a boot
failure occurs.
Solution
--------
a. Initialize the disk signature using the -FDSZ (force disk
signature zero) switch. Initializing the disk signature forces
Windows to discard any existing drive letters and to start
re-allocating new drive letters from scratch.
Note: Ghost generally performs this during a Windows disk load
operation. It will not perform this initialization if you are
only loading a partition. In this case the -FDSZ switch should
be used to fix a boot failure.
b. Alternately, if you wish to retain the allocated drive letters
use the -FDSP switch (force disk signature preserve). This will
only be required on Windows 2000 and XP disk load operations
that result in a boot failure.
c. To login to the machine you may need to change the absolute
path for the user interface executable in the Windows registry.
Refer to the Microsoft Knowledgebase article Q249321 for
details.
This process will allow the user to login but some other
applications may fail. Refer to the Microsoft Knowledgebase
article Q223188 for details.
Cause 2
-------
Windows did not have the correct mass storage controller driver
configured and loaded for the hardware it is booting on due to
hardware differences between the source and destination machines.
Solution
--------
Clone to machines with similar hardware or if this is not possible
you can use the Microsoft tool Sysprep. The Sysprep INF file,
Sysprep.inf, contains a section [SysprepMassStorage] for
specifying one or more mass storage controllers that you want
Windows 2000 to load before it continues to boot.
Microsoft provides one version of Sysprep for Windows 2000, and
one version for Windows XP Pro. Microsoft do not provide a version
for Windows XP Home.
View the Microsoft Sysprep documentation for Windows 2000 at:
http://www.microsoft.com/windows2000/techinfo/planning/incremental
/sysprep11.asp
You can obtain information on deploying Microsoft Windows XP using
Sysprep from the Microsoft Windows XP Professional CD:
Support \Tools\Deploy.cab\Deploy.chm
Support\Tools\Deploy.cab\Ref.chm
Buona Fortuna