Solved How can i make/install windows 7 using my external hard drive ?

[noelian13]

So you installed with C-drive in AHCI mode ... that should work. But when you change it to IDE mode in BIOS it can fix your problem. That is last thing I would advice you.

Because EVERYTHING is fine! bootmgr, bootmenu, MBR, bootsector. Stop 7B is an error you get when:

• moving the start point of a partition (with partition software)
• bios sata is in AHCI mode and win7 isn't or vice versa

But your system is up and running now?

yep just one more question

if i switch my SATA controller in bios from Compatability to AHCI windows 7 wouldn't complain right?

nah...toshiba complains and gives the bsod again...if i switch from compatability to ahci

 

[Kaktussoft]

So you installed with C-drive in AHCI mode ... that should work. But when you change it to IDE mode in BIOS it can fix your problem. That is last thing I would advice you.


Because EVERYTHING is fine! bootmgr, bootmenu, MBR, bootsector. Stop 7B is an error you get when:

• moving the start point of a partition (with partition software)
• bios sata is in AHCI mode and win7 isn't or vice versa

But your system is up and running now?

yep just one more question

if i switch my SATA controller in bios from Compatability to AHCI windows 7 wouldn't complain right?

nah...toshiba complains and gives the bsod again...if i switch from compatability to ahci

Swap to AHCI mode in windows first!
http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html

 

[noelian13]

So you installed with C-drive in AHCI mode ... that should work. But when you change it to IDE mode in BIOS it can fix your problem. That is last thing I would advice you.


Because EVERYTHING is fine! bootmgr, bootmenu, MBR, bootsector. Stop 7B is an error you get when:

• moving the start point of a partition (with partition software)
• bios sata is in AHCI mode and win7 isn't or vice versa

But your system is up and running now?

yep just one more question

if i switch my SATA controller in bios from Compatability to AHCI windows 7 wouldn't complain right?

nah...toshiba complains and gives the bsod again...if i switch from compatability to ahci

Swap to AHCI mode in windows first!
http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html

ohh ic...is there a performance difference between AHCI/comparability ?

 

[Kaktussoft]

ohh ic...is there a performance difference between AHCI/comparability ?

from wikipedia:
Some operating systems, notably Windows Vista and Windows 7, do not configure themselves to load the AHCI driver upon boot if the drive controller was not in AHCI mode at the time of installation. This can cause failure to boot with an error message if the SATA controller is later switched to AHCI mode. For this reason, Intel recommends changing the drive controller to AHCI or RAID before installing an operating system.

Did you change SATA settings to AHCI after installing windows? And that causes the boot failure.

===============
AHCI is separate from the SATA 3Gb/s standard, although it exposes SATA's advanced capabilities (such as hot swapping and native command queuing) such that host systems can utilize them.

Advanced Host Controller Interface - Wikipedia, the free encyclopedia

See also Native Command Queuing - Wikipedia, the free encyclopedia

AHCI is default on on most machines! Don't know exactly what performance gain is. Only diskperformance gain if your disk is on heavy load with a lot of applications

 

[gregrocker]

With the popularity of drive racks, AHCI is likely default due to convenience of hot-swapping. You can Safely Remove the HD just like an external.

 

[theog]

nah...toshiba complains and gives the bsod again

Can you report back on the HD Drive test.

 

[Solidus]

The partition E is NTFS and active ... cool.
the winxp bootsector nor mac bootsector is right!!! You have to put a win7 bootsector on E so it runs bootmgr

from command prompt:

E:\boot\bootsect /nt60 /force /mbr
E:\boot\bootsect /nt60 /force

post results. What happens when booting from usb drive? It is on top of "boot device"-list in BIOS?

I have done those two commands. Here are the results:

"bootsect {/help|/nt60|/nt52} {SYS|ALL|<DriveLetter>:} [/force] [/mbr]

Boot sector restoration tool

Bootsect.exe updates the master boot code for hard disk partitions in order to
switch between BOOTMGR and NTLDR. You can use this tool to restore the boot
sector on your computer.

Run "bootsect /help" for detailed usage instructions."

And I too have the boot order devices correct.

 

[Kaktussoft]

Command should be

E:\boot\bootsect   /nt60   E:  /force  /mbr
E:\boot\bootsect   /nt60   E:  /force

I put more spaces in commands for visibility. Only one space is needed

 

[Solidus]

Command should be

E:\boot\bootsect   /nt60   E:  /force  /mbr
E:\boot\bootsect   /nt60   E:  /force

I put more spaces in commands for visibility. Only one space is needed

The following message appears:

"Target volumes will be updated with BOOTMGR compatible bootcode.

E: (\\?\Volume{d96a3c36-39f2-11e1-a720-00265ebd4fa5})

Forced dismount complete, open handles to this volume are now invalid."

 

[Kaktussoft]

Command should be

E:\boot\bootsect   /nt60   E:  /force  /mbr
E:\boot\bootsect   /nt60   E:  /force

I put more spaces in commands for visibility. Only one space is needed

The following message appears:

"Target volumes will be updated with BOOTMGR compatible bootcode.

E: (\\?\Volume{d96a3c36-39f2-11e1-a720-00265ebd4fa5})

Forced dismount complete, open handles to this volume are now invalid."

that's exactly what I want. Replace the partition bootsector with bootmgr code (win7/vista bootsector)

Did you do E:\boot\bootsect /nt60 E: /force /mbr
as well? and succeeded succesfully?

 

[Solidus]

that's exactly what I want. Replace the partition bootsector with bootmgr code (win7/vista bootsector)

I got lost in here. What do I replace with what?

Did you do E:\boot\bootsect /nt60 E: /force /mbr
as well? and succeeded succesfully?

Yes and the same message appeared as well.

 

[Kaktussoft]

bootsect /nt60 E: /force /mbr =>this rewrites the mbr (master boot record) of the physical disk where partition E is on. When booting from that drive it reads the code which searches for an active partition which is E. Then it loads the boot sector of E.

bootsect /nt60 E: /force => this rewrites the boot sector of E-partition. /nt60 means vista/win7 style. The win7 boot sector has code in it that says ... run bootmgr. bootmgr loads the boot menu e:\boot\bcd and displays all configured Operating systems in that menu. There's only one (the installation) so it starts immediately

 

[Kaktussoft]

Try to start from external usb drive now. Tap F8 a lot of times during boot, so you see a bootmenu. Does that work? Are you very sure it tries to boot from usb?

 

[Solidus]

Try to start from external usb drive now. Tap F8 a lot of times during boot, so you see a bootmenu. Does that work? Are you very sure it tries to boot from usb?

The USB is definitely set first to boot and the boot menu appears after tapping F8 but it's a regular boot menu. Safe mode, start Windows, etc. Nothing related to the USB.

 

[Kaktussoft]

so it doesn't start from usb. remove harddisk from "boot device" in bios. just for test. what happens when you reboot afterwards? tap f8.

 

[Solidus]

so it doesn't start from usb. remove harddisk from "boot device" in bios. just for test. what happens when you reboot afterwards? tap f8.

My notebook doesn't have the possibility to remove the HDD from booting.

 

[Kaktussoft]

so usb is on top of "boot devices" in bios. HDD can't be removed from list are replaced by another option.
boot from usb (try to) and tap f8 so you see the menu.

Do you see any installations so does a menu appear? or only safe mode, normal etc?
try normal. does that start winxp or win7 install?

 

[Solidus]

Do you see any installations so does a menu appear? or only safe mode, normal etc?
try normal. does that start winxp or win7 install?

No installations, only the usual stuff and WinXP starts if I try normal.

I have the feeling I'm doing something wrong. I mean, it can't be this hard. When I was entering the command an error occurred in the Boot Sector Manipulation Tool. Could this be the reason?

 

[Kaktussoft]

This it should say (sorry it's in dutch)

D:\>[B]bootsect /nt60 c: /force[/B]
Target volumes will be updated with BOOTMGR compatible bootcode.
C: ([URL="file://\\?\Volume{d2602ac2-ded6-11e0-a821-806e6f6e6963"]\\?\Volume{d2602ac2-ded6-11e0-a821-806e6f6e6963[/URL]})
    Updated NTFS filesystem bootcode.  The update may be unreliable since the
    volume could not be dismounted during the update:
        Toegang geweigerd. (means access denied)
[B]Bootcode was successfully updated on all targeted volumes.[/B]
-------------------------------------------------------------
D:\>[B]bootsect /nt60 c: /force /mbr[/B]
Target volumes will be updated with BOOTMGR compatible bootcode.
C: ([URL="file://\\?\Volume{d2602ac2-ded6-11e0-a821-806e6f6e6963"]\\?\Volume{d2602ac2-ded6-11e0-a821-806e6f6e6963[/URL]})
    Updated NTFS filesystem bootcode.  The update may be unreliable since the
    volume could not be dismounted during the update:
        Toegang geweigerd. (means access denied)
[B]\??\PhysicalDrive0[/B]
[B]   Successfully updated disk bootcode.[/B]
[B]Bootcode was successfully updated on all targeted volumes.[/B]
D:\>

Did you get Bootcode was successfully updated on all targeted volumes. at first command?
Did you get
\??\PhysicalDrive0
Successfully updated disk bootcode.
Bootcode was successfully updated on all targeted volumes.
on second command?

Of course do it for E instead of C

 

[Kaktussoft]

Target volumes will be updated with BOOTMGR compatible bootcode.
E: (\\?\Volume{d2602ac3-ded6-11e0-a821-806e6f6e6963})
Forced dismount complete, open handles to this volume are now invalid.
Successfully updated NTFS filesystem bootcode.
Bootcode was successfully updated on all targeted volumes.

This is the message you should get