TeraByte Unlimited

Hello,

I am using a different product for imaging Windows. Am trying to restore my Windows 7 (32bit) image taken in ATA(Compatibility) mode from Dell Vostro 2520 laptop to Toshiba C850 laptop. Unfortunately providing HDD drivers using OSD Tool Suite has not helped me and the OS keeps throwing blue screen with 0x0000007B errors all the time. Are there any other drivers that I need to provide?

Please help.

Are both laptops set for ATA mode in the bios? If the Toshiba is set for AHCI, this could cause the problem. Are you sure you have the right drivers for the mode you want on the Toshiba? Normally, the 7B errors are generated by not having the right drivers for the required mode, in this case, ATA mode.

Most importantly, if you are restoring a Dell OEM version of Windows 7, you will need a retail key to activate Windows on the Toshiba. The Windows 7 OEM versions access the bios to verify and activate. If your purchased the Dell Vostro directly from Dell with the Windows 7 preinstalled, then it is an OEM version.

Good luck,

rich071 wrote:
> Are both laptops set for ATA mode in the bios? If the Toshiba is set for AHCI, this
> could cause the problem. Are you sure you have the right drivers for the mode you
> want on the Toshiba? Normally, the 7B errors are generated by not having the right
> drivers for the required mode, in this case, ATA mode.

Yes both the laptops are set to ATA mode. But the ATA drivers are native to Windows 7
isn't it?? I've also downloaded all the possible HDD drivers from Intel/Toshiba/Other sources from
the net. Do you think I also need to provide Chipset drivers as well for Toshiba laptop?

rich071 wrote:
> Most importantly, if you are restoring a Dell OEM version of Windows 7, you will
> need a retail key to activate Windows on the Toshiba. The Windows 7 OEM versions
> access the bios to verify and activate. If your purchased the Dell Vostro directly
> from Dell with the Windows 7 preinstalled, then it is an OEM version.

Nopes its a retail version.
,

Was the image being restored taken while Windows was running?

Are you using Windows 7 x86 drivers? What are the names of the .INF files for the drivers?

Have you tried running OSDTool on the drive after you get the 7B error or only just after restoring (before booting)? For example, have you tried restoring, booting it (getting the 7B error), then running OSDTool and installing the drivers?

Have you tried removing the installed drivers and installing the default IDE/AHCI drivers with the OSDTool script?

You shouldn't need to install the chipset drivers to get it to boot.

TeraByte Support(PP) wrote:
> Was the image being restored taken while Windows was running?

No. The image was taken using USB bootable Acronis True Image Home.

> Are you using Windows 7 x86 drivers? What are the names of the .INF files
> for the drivers?

Yes I am using Win 7 x86 drivers. The name of the inf driver for HDD is iaAHCIC.inf

> Have you tried running OSDTool on the drive after you get the 7B error or
> only just after restoring (before booting)? For example, have you tried
> restoring, booting it (getting the 7B error), then running OSDTool and
> installing the drivers?

I have tried both ways once directly after restoring it and once after restoring, BSODing.

> Have you tried removing the installed drivers and installing the default
> IDE/AHCI drivers with the OSDTool script?

Yes I've tried that but BSOD again

> You shouldn't need to install the chipset drivers to get it to boot.

ohk...hmmm

You are probably missing another drivers.
Is there another Windows working on that laptop? If so, we can compare the two SYSTEM reg to see what is missing on the non-working one.

Eric wrote:
> Is there another Windows working on that laptop? If so, we can compare the two SYSTEM
> reg to see what is missing on the non-working one.

No there's just one Windows on C drive. I just realised on my source laptop (Dell 2520) in disk management there's a 350mb OEM partition before C: Could that be the source of the problem? But when I had taken its image it was only C drive and nothing else.

Well, don't know if that the source of the problem. If it is 350 MiB, then it's probably the "EFI System partition", and it contains the BCD. Is the source a GPT drive?

However, if you get the 0x0000007B error, then you might already have the BCD inside the Win7 partition. That BCD should be adjusted to fit the target. Does your imaging software doing that correctly?

You can try to image it, copy it (so the type of drive would have to be GPT), and adjust it (if you use the Image from TB, you'll have to use the "update boot partition" option).

Also, is the C: drive letter correctly assigned? You can check that with the setwindl.tbs script.

Silly question but are you copying the entire driver folder (multiple files) to your UFD or just using iaAHCI.inf?

When your computer restarts after using TBOSDT do you get an initial screen where you see the driver being installed and then a reboot?

in general 7b means windows can't find the boot device, typically that is
when the storage driver can't be found, but have seen it when a system
doesn't have enough memory, when chkdsk /f is needed on the file systems,
and when the wrong os was being booted (different than the one intended).

.. and of course corrupted data.

"exus69" wrote in message news:7556@public.tbosdt...

Eric wrote:
> Is there another Windows working on that laptop? If so, we can compare the
> two SYSTEM
> reg to see what is missing on the non-working one.

No there's just one Windows on C drive. I just realised on my source laptop
(Dell 2520) in disk management there's a 350mb OEM partition before C: Could
that be the source of the problem? But when I had taken its image it was
only C drive and nothing else.