G
Guest
Today I can give you guys more info about my problem.
This morning, after etprep the HD was still able to boot, but only if the pre-fba CDRom was inside.
Removing the CD the system could not be able to start anymore (BSOD).
I tought it was a letter problem, in fact "SET" command at the prompt showed many environment variables (i.e. "ProgramFiles") with the "C:\" prefix, not the "E:\".
I went into registry and manually modified the strings containing "C:\..." into "E:\..." and committed my changes to the HD, except for those in HKCM\System\MountedDevices (affected by etprep I suppose).
Now the HD was able to boot alone, with system root "E:\"!
I was full of hope! I burned the image of the HD (I created new SDI disk, copied all the files, made hd2iso on SDI disk, then burned the ISO).
Still 0x0000007b.
Am I going in the wrong direction? Is in this discussion group a solution that I've missed?
This morning, after etprep the HD was still able to boot, but only if the pre-fba CDRom was inside.
Removing the CD the system could not be able to start anymore (BSOD).
I tought it was a letter problem, in fact "SET" command at the prompt showed many environment variables (i.e. "ProgramFiles") with the "C:\" prefix, not the "E:\".
I went into registry and manually modified the strings containing "C:\..." into "E:\..." and committed my changes to the HD, except for those in HKCM\System\MountedDevices (affected by etprep I suppose).
Now the HD was able to boot alone, with system root "E:\"!
I was full of hope! I burned the image of the HD (I created new SDI disk, copied all the files, made hd2iso on SDI disk, then burned the ISO).
Still 0x0000007b.
Am I going in the wrong direction? Is in this discussion group a solution that I've missed?