I have a problem with the final stage of Windows 7 boot and would like to know if NeoSmart's tools will fix my problem.
I'm working on a Acer Aspire One 725, replacing the stock SATA HDD with a SATA SSD. The SSD is smaller than the stock HDD, a Crucial M550/128GB vs a WD/320GB.
The stock HDD is configured with 3 partitions: 1) diags/restore partition (19GB), 2) SYSTEM/boot partition (100MB), 3) Windows install (was ~209GB, now 119GB)
I successfully resized the System partition down to 119GB in order to fit the SSD and the system still successfully boots from the HDD
The SSD is partitioned with a 100MB partition for SYSTEM and 119GB for Windows, only 2 partitions - don't want the DIAG/Recovery partition.
I copied the SYSTEM and WINDOWS partitions from HDD to SSD using LINUX tools on the Clonezilla distribution, the partitions are clean, chkdsk completes OK.
I booted a Win7 PE disk, reinstalled the MBR and created new BCD files.
So, the bootmgr executes from the SYSTEM partition and loads the winload.exe process from the WINDOWS partition, which in turn loads:
\Windows\system32\config\system
\Windows\system32\ntoskernel.exe
\Windows\system32\hal.dll
\Windows\system32\kdcom.dll
\Windows\system32\mcupdate_AuthenicateAMD.dll
\Windows\system32\PSHED.dll
\Windows\system32\CLFS.sys
\Windows\system32\CI.dll
\Windows\system32\drivers\[***].sys
.....etc
\Windows\system32\drivers\CLASSPNP.sys
Then loading halts, nothing
So I suspect that the system registry file (\Windows\system32\config\system) has explicit parameters pointing to the former disk's partition 3 - if this is correct will EasyRE fix it?
I'm working on a Acer Aspire One 725, replacing the stock SATA HDD with a SATA SSD. The SSD is smaller than the stock HDD, a Crucial M550/128GB vs a WD/320GB.
The stock HDD is configured with 3 partitions: 1) diags/restore partition (19GB), 2) SYSTEM/boot partition (100MB), 3) Windows install (was ~209GB, now 119GB)
I successfully resized the System partition down to 119GB in order to fit the SSD and the system still successfully boots from the HDD
The SSD is partitioned with a 100MB partition for SYSTEM and 119GB for Windows, only 2 partitions - don't want the DIAG/Recovery partition.
I copied the SYSTEM and WINDOWS partitions from HDD to SSD using LINUX tools on the Clonezilla distribution, the partitions are clean, chkdsk completes OK.
I booted a Win7 PE disk, reinstalled the MBR and created new BCD files.
So, the bootmgr executes from the SYSTEM partition and loads the winload.exe process from the WINDOWS partition, which in turn loads:
\Windows\system32\config\system
\Windows\system32\ntoskernel.exe
\Windows\system32\hal.dll
\Windows\system32\kdcom.dll
\Windows\system32\mcupdate_AuthenicateAMD.dll
\Windows\system32\PSHED.dll
\Windows\system32\CLFS.sys
\Windows\system32\CI.dll
\Windows\system32\drivers\[***].sys
.....etc
\Windows\system32\drivers\CLASSPNP.sys
Then loading halts, nothing
So I suspect that the system registry file (\Windows\system32\config\system) has explicit parameters pointing to the former disk's partition 3 - if this is correct will EasyRE fix it?