466 replies to this topic

[Wonko the Sane]

Anything else I should look at?

Well, you could explain how come you have GRUB2 (which is the thing that fails and goes to "grub rescue>") booting.
Or if you prefer, follow the standard litany:
http://homepages.tes...ard-litany.html
Unless you describe the EXACT steps you took with the most detail you can, it is unlikely that someone can guess what happened.
Most probably all you have to do is to re-write the Windows 7 MBR code, but cannot really say without knowing WHAT you used to partition/format that hard disk and HOW you used the tool(s).
http://technet.microsoft.com/en-us/library/dd744577(WS.10).aspx

or:
http://www.sysint.no...ting/mbrfix.htm


Wonko

[Robert Vorster]

Well, you could explain how come you have GRUB2 (which is the thing that fails and goes to "grub rescue>") booting.
Or if you prefer, follow the standard litany:
http://homepages.tes...ard-litany.html
Unless you describe the EXACT steps you took with the most detail you can, it is unlikely that someone can guess what happened.
Most probably all you have to do is to re-write the Windows 7 MBR code, but cannot really say without knowing WHAT you used to partition/format that hard disk and HOW you used the tool(s).
http://technet.micro...577(WS.10).aspx

or:
http://www.sysint.no...ting/mbrfix.htm


Wonko

Well, Windows XP Format utility was used on one of my workstations to do a full format on the drive which is a old Cipherwave 160GB drive.

Secondly, I used my Windows 7 32bit CD and the pack provided here with the required 32bit files to prep the drive.

Lastly plugged in the drive in the netbook once it told me the process was complete and started up the netbook which went to the error provided.

Same process I have used a good deal of 20 times before...

So ya, don't really know what you want to know. Worked with this before, worked fine. Didn't change the process and I am 110% sure I know how the tools and utilities work. Kinda my specialization for the last 20 odd years.

[steve6375]

If nothing has changed then it would work just as before. So something has changed. What about the data on the drive - did you do something different with it before this?
When you say 'one of my stations' - was this by any chance a different one from the one you normally use?

[Robert Vorster]

If nothing has changed then it would work just as before. So something has changed. What about the data on the drive - did you do something different with it before this?
When you say 'one of my stations' - was this by any chance a different one from the one you normally use?

Nothing special was done with the data on the drive. Like always, I plug in the drive start the process and leave it be until it is finished, after which I shut down the machine and unplug the drive.

I have used this workstation before for all the previous prep work. I have a few different machines and servers for varying tasks. This particular one is used for data recovery, drive preparations, drive scans and virus removal etc. So it is the same machine, no new software, no changes in the process, no additional or lack of steps. The netbook just pops out the error when booting off of the drive.

I'll sit and work through it myself in the meantime. Does not appear as if anyone on here has had this error before. Use the script as is, no changes and the error pops up. But I'll work it out.

[steve6375]

try wiping the drive starting sectors with 0's - unplug - re-plug and then start again.

[Wonko the Sane]

Well, Windows XP Format utility was used on one of my workstations to do a full format on the drive which is a old Cipherwave 160GB drive.

.....
So ya, don't really know what you want to know. Worked with this before, worked fine. Didn't change the process and I am 110% sure I know how the tools and utilities work. Kinda my specialization for the last 20 odd years.

In the last 20 odd years you must have missed that FORMATting a hard disk does NOT affect the MBR code contents.
Additionally if you formatted it under XP, most of the data on it was not touched.
The message you got seemingly comes from GRUB2.
This normally comes from a GRUB2 installed to the MBR.
If you didn't wantingly install GRUB2, it means that it was there before and that the format under XP and "prep" (whatever it was) under 7 left it where it was OR that you are using "something" else that installs GRUB2 without you knowing.
You need to check the MBR on that hard disk drive (Sector 0 or first sector of it) and install to it the "normal" Windows 7 MBR code.
Two different ways to do so were provided.


Wonko

[Escorpiom]

To remove the Grub2 code from the MBR you can simply -rebuild- the MBR or wipe the first say 100 sectors and partition the drive again.
Grub2 bootcode can come from some earlier Linux installation. Format only won't solve that as Wonky already said.

Cheers.

[vesilp]

Hi everybody,
I am new to this forum and this is my first post.
I am not sure if fujianabc is still active in this/his topic, started long ago, but maybe somebody else can help instead.
Last week I found out this GREAT solution of fujianabc and successfully installed Win 7 on a USB hard drive, using NT6.X_fast_installer_100219.7z installer (from fujianabc's post #2-02 January 2010-08:20 PM) from a desktop with Win 7 as well. I was very happy with the installation. The USB-Windows worked just fine ! The newly created boot menu has 2 lines for the two OS, which I renamed to "External OS" and "Internal OS", respectively. On the 3-rd day I decided to try fujianabc's PS:point 3. to make USB OS bootable from another PC, running recommended command:
\Windows\System32\sysprep\sysprep.exe /oobe /generalize /shutdown
(didn't know much about sysprep.exe before, deeply sorry about that)
After sysprep completed his work, I pluged the USB HDD to the 2nd PC, but it won't boot ! Which is WORST, it won't boot any more with the first, "installation" PC as well - now it boots from desktop-Windows 7 only, nevertheless which line from the boot menu (externel or internel) I choose !
How can I restore the USB HDD as bootable again ?
Any help will be appreciated.
Regards, vesilp

[steve6375]

This internal/external menu - is it on the USB drive? If so then the USB drive is booting - at least to a menu? So is the menu a grub4dos menu or a windows bootmgr menu or what?
Can you post the contents of this menu.
Sysprep would not stop the drive from at least trying to boot to Windows.

[vesilp]

Hi steve6375 and thank you for your attention !
This menu should be not on the USB drive (I am not at the same PC now, can't check it for sure) - the menu is still in place, just unchanged and looks like this:
Windows 7 (initially) - External OS (after I renamed it; this is the USB Windows)
Windows 7 (initially) - Internal OS (after I renamed it; this is the desktop Windows)
boot.ini (if I'm not mistaken; something that crashes the system, not usable and not harmfull, if I dom't click on it)
Now I still see this menu, but it boots only to the desktop Windows, from eather the first or the second line.
The menu can not be a grub4dos, as to me, there is no Linux nearby. It must be bootmgr menu rather.
If I could guess, that sysprep may stop the USB from booting, I would have never tried to use it ...
Tomorrow, when at my workplace again, I'l be able to supply additional details on the issue.

[vesilp]

Hi
Here are some more details (I'm now at my workplace).
The menu is a Windows Boot Manager's and reads the following:
Windows Boot Manager
Choose an operating system to start, or pres TAB to select a tool:
(use the arrow keys...)
External OS
Internal OS
boot.ini Menu
To specify advanced options for this choice, pres F8
Tools:
Windows Memory Diagnostic

[vesilp]

Hi
I'm ready to post still more details about the issue, but I don't know how to add attachment to a post in this forum.
I mean, that I can post the output listing of the bcdedit.exe command, which I used to rename the boot menu items. Unfortunately I didn't save this output, corresponding to the initial working configuration of the boot manager. In that case I probably could try to edit-restore the right configuration for the multiboot menu.

[steve6375]

But can you boot directly from the USB drive using the BIOS boot selection menu or by setting the USB drive to boot first in the BIOS boot order?

[vesilp]

NO, I can not !
The BIOS - 2005 AMI version - is of the type:
1st Boot device ...
2nd Boot device ...
3rd Boot device ...
> Hard Disk drives (to choose from list)
After the incident I found, in the HDD list, twice the local/internal hard drive
When I replaced the 1st HDD with the USB drive ID, the Boot stop with the message:
"NTLDR is missing
Press Ctrl+Alt+Del to restart" (and there is no Boot menu)
When I replaced the 2nd HDD with the USB drive ID, it shows the boot menu, but boots only to the "Internal" Windows, as previously.

[steve6375]

NTLDR is missing is the message that an XP bootsector gives. If you are sure that this message is coming from the USB drive, then somehow it has got an active partition which has an XP bootsector.
To make it boot to Win7 you will need to run bootsect /nt60 J: (where J: is the USB drive).
Maybe running RMPrepUSB driveInfo would shed some light (look at MBR and PBR).

[vesilp]

Yes, I know NTLDR is XP-connected. I'm not absolutely sure, that the message is comming from the USB drive, but the fact is, that it appears when the USB drive is set to be the Boot device. The USB drive is formatted (long, long ago...) to NTFS file system (which it MUST be in order to be used to install Windows). Long ago I had made a try to install XP on it, using another technology, but don't remember if I had formatted it after all. At the same time I'm sure, that it has been recognized as "Active" partition by the Windows Setup.
As to your suggestion to try bootsect /nt62 J: Note, that now I see, in Windows Explorer, these 3 partitions:
Win7_System(C:) - the loaded Windows 7 partition, from the internal hard drive;
Data Disk(D:) - a second partition on the phisical internal drive;
USB-Samsung(F:) - the USB hard drive, acting simply as another pluged drive
In this configuration there are 3 instances of bootsect.exe:
D:\WAIK Files\bootsect.exe - 103 312 bytes / 14.07.2009 (you shold know this directory, suggested by the fujianabc' installation guide)
D:\Windows Files\boot\bootsect.exe - 97 280 bytes / 09.11.2009 ( "" "" see above "" "" "" )
D:\Windows Files\boot\en-us\bootsect.exe - some ~15k
The actual bootsect.exe, I think, should be the 103kB instance. But, where/how you suggest to run bootsect.exe and is it expected to do it's job, while not as a part of running Windows ?
Should I simly do this: D:\WAIK Files\bootsect.exe <Enter> (from a logged as Administrator command prompt, in safe mode), or not exactly ?
As to the RMPrepUSB: I downloaded and installed it, in the only available "INTERNAL" Windows 7, of course. Run it and can mention this - the "Drive Info" button returned the HEX contents of Sector 0, where the only readable data is "Invalid partition table. Error loading operationg system. Missing operationg system..."
But, I could not see WHERE to look at MBR and PBR ?
That's for now...

[vesilp]

Sorry, forgot this more detail:
among the options of bootsect.exe there are /nt52 and /nt60, but no /nt62 ?

[steve6375]

sorry I meant /nt60

re. RMPrepUSb info - at the end of the hex dump you should see some info about partitions and if one is active. The listing below shows the 1st partition is FAT32 and is Active (bootable).

It shows that the partition starts at sector 32, If you now re-click the DriveInfo and enter P1 (for first partition) you will see hex dump which should show you what the boot code is (see end of the 512 bytes which usually has name of boot file) - example below shows MSDOS boot code.

Partition 1   SIZE=476940.008MiB   Type: 0B FAT32 (2047GB max)  *ACTIVE*

START POS   = CYL:0 HD:1 SEC:1  END POS = CYL:1023 HD:254 SEC:63

START (LBA) = 32 (00000020)	  SIZE (LBA) = 976,773,136 (3A386010)



Partition 2   SIZE=0MiB   Type: 00		

START POS   = CYL:0 HD:0 SEC:0  END POS = CYL:0 HD:0 SEC:0

START (LBA) = 0 (00000000)	  SIZE (LBA) = 0 (00000000)



Partition 3   SIZE=0MiB   Type: 00		

START POS   = CYL:0 HD:0 SEC:0  END POS = CYL:0 HD:0 SEC:0

START (LBA) = 0 (00000000)	  SIZE (LBA) = 0 (00000000)



Partition 4   SIZE=0MiB   Type: 00		

START POS   = CYL:0 HD:0 SEC:0  END POS = CYL:0 HD:0 SEC:0

START (LBA) = 0 (00000000)	  SIZE (LBA) = 0 (00000000)



Drive 1 ST950056 20AS is 500,107,862,016 bytes long (465.762GiB)

F/W Rev.=SD22  Serial No.= [ 00 00 00 00 00 00 00 00 ]

[Sector 32]  0MB

0000 EB 58 90 4D 53 44 4F 53 - 35 2E 31 00 02 20 22 00  ëXMSDOS 5.1.. ".

0010 02 00 00 00 00 F8 00 00 - 3F 00 FF 00 20 00 00 00  .....ø.. ?.ÿ. ...

0020 10 60 38 3A 87 A3 03 00 - 00 00 00 00 02 00 00 00  `8:‡£.. ........

0030 01 00 06 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ........ ........

0040 80 00 29 72 5F 38 7D 4E - 4F 20 4E 41 4D 45 20 20  €.)r_8}N O NAME  

0050 20 20 46 41 54 33 32 20 - 20 20 FA 33 C9 8E D1 BC	FAT32	ú3ɎѼ

0060 F8 7B 8E C1 BD 78 00 C5 - 76 00 1E 56 16 55 BF 22  ø{ŽÁ½x.Å v.VU¿"

0070 05 89 7E 00 89 4E 02 B1 - 0B FC F3 A4 8E D9 BD 00  .‰~.‰N.± .üó¤ŽÙ½.

0080 7C C6 45 FE 0F 8B 46 18 - 88 45 F9 38 4E 40 7D 25  |ÆEþ‹F ˆEÙ8N@}%

0090 8B C1 99 BB 00 07 E8 97 - 00 72 1A 83 EB 3A 66 A1  ‹Á™»..è— .rƒë:f¡

00A0 1C 7C 66 3B 07 8A 57 FC - 75 06 80 CA 02 88 56 02  |f;.ŠWü u.€Ê.ˆV.

00B0 80 C3 10 73 ED BF 02 00 - 83 7E 16 00 75 45 8B 46  €Ãsí¿.. ƒ~.uE‹F

00C0 1C 8B 56 1E B9 03 00 49 - 40 75 01 42 BB 00 7E E8  ‹V¹..I @u.B».~è

00D0 5F 00 73 26 B0 F8 4F 74 - 1D 8B 46 32 33 D2 B9 03  _.s&°øOt ‹F23Ò¹.

00E0 00 3B C8 77 1E 8B 76 0E - 3B CE 73 17 2B F1 03 46  .;èw‹v ;Îs+Ñ.F

00F0 1C 13 56 1E EB D1 73 0B - EB 27 83 7E 2A 00 77 03  VëÑs. ë'ƒ~*.w.

0100 E9 FD 02 BE 7E 7D AC 98 - 03 F0 AC 84 C0 74 17 3C  Éý.¾~}¬˜ .ð¬„Àt<

0110 FF 74 09 B4 0E BB 07 00 - CD 10 EB EE BE 81 7D EB  ÿt.´».. íëξ}ë

0120 E5 BE 7F 7D EB E0 98 CD - 16 5E 1F 66 8F 04 CD 19  ž}ëÀ˜í ^f.í

0130 41 56 66 6A 00 52 50 06 - 53 6A 01 6A 10 8B F4 60  AVfj.RP. Sj.j‹ô`

0140 80 7E 02 0E 75 04 B4 42 - EB 1D 91 92 33 D2 F7 76  €~.u.´B ë‘’3Ò÷v

0150 18 91 F7 76 18 42 87 CA - F7 76 1A 8A F2 8A E8 C0  ‘÷vB‡Ê ÷vŠÒŠèÀ

0160 CC 02 0A CC B8 01 02 8A - 56 40 CD 13 61 8D 64 10  Ì..̸..Š V@íad

0170 5E 72 0A 40 75 01 42 03 - 5E 0B 49 75 B4 C3 03 18  ^r.@u.B. ^.Iu´Ã.

0180 01 27 0D 0A 49 6E 76 61 - 6C 69 64 20 73 79 73 74  .'..Inva lid syst

0190 65 6D 20 64 69 73 6B FF - 0D 0A 44 69 73 6B 20 49  em diskÿ ..Disk I

01A0 2F 4F 20 65 72 72 6F 72 - FF 0D 0A 52 65 70 6C 61  /O error ÿ..Repla

01B0 63 65 20 74 68 65 20 64 - 69 73 6B 2C 20 61 6E 64  ce the d isk, and

01C0 20 74 68 65 6E 20 70 72 - 65 73 73 20 61 6E 79 20   then pr ess any

01D0 6B 65 79 0D 0A 00 00 00 - 49 4F 20 20 20 20 20 20  key..... IO	  

01E0 53 59 53 4D 53 44 4F 53 - 20 20 20 53 59 53 7E 01  SYSMSDOS	SYS~.

01F0 00 57 49 4E 42 4F 4F 54 - 20 53 59 53 00 00 55 AA  .WINBOOT  SYS..Uª

[steve6375]

sorry I meant /nt60

re. RMPrepUSb info - at the end of the hex dump you should see some info about partitions and if one is active. The listing below shows the 1st partition is FAT32 and is Active (bootable).

It shows that the partition starts at sector 32, If you now re-click the DriveInfo and enter P1 (for first partition) you will see hex dump which should show you what the boot code is (see end of the 512 bytes which usually has name of boot file) - example below shows MSDOS boot code.

Partition 1   SIZE=476940.008MiB   Type: 0B FAT32 (2047GB max)  *ACTIVE*

START POS   = CYL:0 HD:1 SEC:1  END POS = CYL:1023 HD:254 SEC:63

START (LBA) = 32 (00000020)	  SIZE (LBA) = 976,773,136 (3A386010)



Partition 2   SIZE=0MiB   Type: 00		

START POS   = CYL:0 HD:0 SEC:0  END POS = CYL:0 HD:0 SEC:0

START (LBA) = 0 (00000000)	  SIZE (LBA) = 0 (00000000)



Partition 3   SIZE=0MiB   Type: 00		

START POS   = CYL:0 HD:0 SEC:0  END POS = CYL:0 HD:0 SEC:0

START (LBA) = 0 (00000000)	  SIZE (LBA) = 0 (00000000)



Partition 4   SIZE=0MiB   Type: 00		

START POS   = CYL:0 HD:0 SEC:0  END POS = CYL:0 HD:0 SEC:0

START (LBA) = 0 (00000000)	  SIZE (LBA) = 0 (00000000)



Drive 1 ST950056 20AS is 500,107,862,016 bytes long (465.762GiB)

F/W Rev.=SD22  Serial No.= [ 00 00 00 00 00 00 00 00 ]

[Sector 32]  0MB

0000 EB 58 90 4D 53 44 4F 53 - 35 2E 31 00 02 20 22 00  ëXMSDOS 5.1.. ".

0010 02 00 00 00 00 F8 00 00 - 3F 00 FF 00 20 00 00 00  .....ø.. ?.ÿ. ...

0020 10 60 38 3A 87 A3 03 00 - 00 00 00 00 02 00 00 00  `8:‡£.. ........

0030 01 00 06 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ........ ........

0040 80 00 29 72 5F 38 7D 4E - 4F 20 4E 41 4D 45 20 20  €.)r_8}N O NAME  

0050 20 20 46 41 54 33 32 20 - 20 20 FA 33 C9 8E D1 BC	FAT32	ú3ɎѼ

0060 F8 7B 8E C1 BD 78 00 C5 - 76 00 1E 56 16 55 BF 22  ø{ŽÁ½x.Å v.VU¿"

0070 05 89 7E 00 89 4E 02 B1 - 0B FC F3 A4 8E D9 BD 00  .‰~.‰N.± .üó¤ŽÙ½.

0080 7C C6 45 FE 0F 8B 46 18 - 88 45 F9 38 4E 40 7D 25  |ÆEþ‹F ˆEÙ8N@}%

0090 8B C1 99 BB 00 07 E8 97 - 00 72 1A 83 EB 3A 66 A1  ‹Á™»..è— .rƒë:f¡

00A0 1C 7C 66 3B 07 8A 57 FC - 75 06 80 CA 02 88 56 02  |f;.ŠWü u.€Ê.ˆV.

00B0 80 C3 10 73 ED BF 02 00 - 83 7E 16 00 75 45 8B 46  €Ãsí¿.. ƒ~.uE‹F

00C0 1C 8B 56 1E B9 03 00 49 - 40 75 01 42 BB 00 7E E8  ‹V¹..I @u.B».~è

00D0 5F 00 73 26 B0 F8 4F 74 - 1D 8B 46 32 33 D2 B9 03  _.s&°øOt ‹F23Ò¹.

00E0 00 3B C8 77 1E 8B 76 0E - 3B CE 73 17 2B F1 03 46  .;èw‹v ;Îs+Ñ.F

00F0 1C 13 56 1E EB D1 73 0B - EB 27 83 7E 2A 00 77 03  VëÑs. ë'ƒ~*.w.

0100 E9 FD 02 BE 7E 7D AC 98 - 03 F0 AC 84 C0 74 17 3C  Éý.¾~}¬˜ .ð¬„Àt<

0110 FF 74 09 B4 0E BB 07 00 - CD 10 EB EE BE 81 7D EB  ÿt.´».. íëξ}ë

0120 E5 BE 7F 7D EB E0 98 CD - 16 5E 1F 66 8F 04 CD 19  ž}ëÀ˜í ^f.í

0130 41 56 66 6A 00 52 50 06 - 53 6A 01 6A 10 8B F4 60  AVfj.RP. Sj.j‹ô`

0140 80 7E 02 0E 75 04 B4 42 - EB 1D 91 92 33 D2 F7 76  €~.u.´B ë‘’3Ò÷v

0150 18 91 F7 76 18 42 87 CA - F7 76 1A 8A F2 8A E8 C0  ‘÷vB‡Ê ÷vŠÒŠèÀ

0160 CC 02 0A CC B8 01 02 8A - 56 40 CD 13 61 8D 64 10  Ì..̸..Š V@íad

0170 5E 72 0A 40 75 01 42 03 - 5E 0B 49 75 B4 C3 03 18  ^r.@u.B. ^.Iu´Ã.

0180 01 27 0D 0A 49 6E 76 61 - 6C 69 64 20 73 79 73 74  .'..Inva lid syst

0190 65 6D 20 64 69 73 6B FF - 0D 0A 44 69 73 6B 20 49  em diskÿ ..Disk I

01A0 2F 4F 20 65 72 72 6F 72 - FF 0D 0A 52 65 70 6C 61  /O error ÿ..Repla

01B0 63 65 20 74 68 65 20 64 - 69 73 6B 2C 20 61 6E 64  ce the d isk, and

01C0 20 74 68 65 6E 20 70 72 - 65 73 73 20 61 6E 79 20   then pr ess any

01D0 6B 65 79 0D 0A 00 00 00 - 49 4F 20 20 20 20 20 20  key..... IO	  

01E0 53 59 53 4D 53 44 4F 53 - 20 20 20 53 59 53 7E 01  SYSMSDOS	SYS~.

01F0 00 57 49 4E 42 4F 4F 54 - 20 53 59 53 00 00 55 AA  .WINBOOT  SYS..Uª

[vesilp]

Thank you very much again, steve, for your support !
Here is my RMPrepUSB info:

Partition 1 SIZE=152633,158MiB Type: 07 NTFS *ACTIVE*
START POS = CYL:0 HD:1 SEC:1 END POS = CYL:1023 HD:254 SEC:63
START (LBA) = 63 (0000003F) SIZE (LBA) = 312 592 707 (12A1C943)

Partition 2 SIZE=0MiB Type: 00
START POS = CYL:0 HD:0 SEC:0 END POS = CYL:0 HD:0 SEC:0
START (LBA) = 0 (00000000) SIZE (LBA) = 0 (00000000)

Partition 3 SIZE=0MiB Type: 00
START POS = CYL:0 HD:0 SEC:0 END POS = CYL:0 HD:0 SEC:0
START (LBA) = 0 (00000000) SIZE (LBA) = 0 (00000000)

Partition 4 SIZE=0MiB Type: 00
START POS = CYL:0 HD:0 SEC:0 END POS = CYL:0 HD:0 SEC:0
START (LBA) = 0 (00000000) SIZE (LBA) = 0 (00000000)

Drive 1 Samsung S2 Portable is 160 041 885 696 bytes long (149,051GiB)
Serial No.=j329 [ 6A 33 32 39 ]


[Sector 63] 0MB
0000 EB 52 90 4E 54 46 53 20 - 20 20 20 00 02 08 00 00 лRђNTFS .....
0010 00 00 00 00 00 F8 00 00 - 3F 00 FF 00 3F 00 00 00 .....ш.. ?.я.?...
0020 00 00 00 00 80 00 80 00 - 70 9E A1 12 00 00 00 00 ....Ђ.Ђ. pћЎ....
0030 00 00 0C 00 00 00 00 00 - E7 19 2A 01 00 00 00 00 ........ з*.....
0040 F6 00 00 00 01 00 00 00 - 10 1B 23 54 3A 23 54 98 ц....... #T:#T˜
0050 00 00 00 00 FA 33 C0 8E - D0 BC 00 7C FB B8 C0 07 ....ъ3АЋ Рј.|ыёА.
0060 8E D8 E8 16 00 B8 00 0D - 8E C0 33 DB C6 06 0E 00 ЋШи.ё.. ЋА3ЫЖ..
0070 10 E8 53 00 68 00 0D 68 - 6A 02 CB 8A 16 24 00 B4 иS.h..h j.ЛЉ$.ґ
0080 08 CD 13 73 05 B9 FF FF - 8A F1 66 0F B6 C6 40 66 .Нs.№яя Љсf¶Ж@f
0090 0F B6 D1 80 E2 3F F7 E2 - 86 CD C0 ED 06 41 66 0F ¶СЂв?чв †НАн.Af
00A0 B7 C9 66 F7 E1 66 A3 20 - 00 C3 B4 41 BB AA 55 8A ·ЙfчбfЈ .ГґA»ЄUЉ
00B0 16 24 00 CD 13 72 0F 81 - FB 55 AA 75 09 F6 C1 01 $.НrЃ ыUЄu.цБ.
00C0 74 04 FE 06 14 00 C3 66 - 60 1E 06 66 A1 10 00 66 t.ю..Гf `.fЎ.f
00D0 03 06 1C 00 66 3B 06 20 - 00 0F 82 3A 00 1E 66 6A ...f;. .‚:.fj
00E0 00 66 50 06 53 66 68 10 - 00 01 00 80 3E 14 00 00 .fP.Sfh ...Ђ>..
00F0 0F 85 0C 00 E8 B3 FF 80 - 3E 14 00 00 0F 84 61 00 …..иіяЂ >..„a.
0100 B4 42 8A 16 24 00 16 1F - 8B F4 CD 13 66 58 5B 07 ґBЉ$. ‹фНfX[.
0110 66 58 66 58 1F EB 2D 66 - 33 D2 66 0F B7 0E 18 00 fXfXл-f 3Тf·.
0120 66 F7 F1 FE C2 8A CA 66 - 8B D0 66 C1 EA 10 F7 36 fчсюВЉКf ‹РfБкч6
0130 1A 00 86 D6 8A 16 24 00 - 8A E8 C0 E4 06 0A CC B8 .†ЦЉ$. ЉиАд..Мё
0140 01 02 CD 13 0F 82 19 00 - 8C C0 05 20 00 8E C0 66 ..Н‚. ЊА. .ЋАf
0150 FF 06 10 00 FF 0E 0E 00 - 0F 85 6F FF 07 1F 66 61 я..я. …oя.fa
0160 C3 A0 F8 01 E8 09 00 A0 - FB 01 E8 03 00 FB EB FE Г ш.и.. ы.и..ылю
0170 B4 01 8B F0 AC 3C 00 74 - 09 B4 0E BB 07 00 CD 10 ґ.‹р¬<.t .ґ»..Н
0180 EB F2 C3 0D 0A 41 20 64 - 69 73 6B 20 72 65 61 64 лтГ..A d isk read
0190 20 65 72 72 6F 72 20 6F - 63 63 75 72 72 65 64 00 error o ccurred.
01A0 0D 0A 4E 54 4C 44 52 20 - 69 73 20 6D 69 73 73 69 ..NTLDR is missi
01B0 6E 67 00 0D 0A 4E 54 4C - 44 52 20 69 73 20 63 6F ng...NTL DR is co
01C0 6D 70 72 65 73 73 65 64 - 00 0D 0A 50 72 65 73 73 mpressed ...Press
01D0 20 43 74 72 6C 2B 41 6C - 74 2B 44 65 6C 20 74 6F Ctrl+Al t+Del to
01E0 20 72 65 73 74 61 72 74 - 0D 0A 00 00 00 00 00 00 restart ........
01F0 00 00 00 00 00 00 00 00 - 83 A0 B3 C9 00 00 55 AA ........ ѓ іЙ..UЄ

So, what next you can suggest ?
Should I try bootsect.exe and which way ?

[steve6375]

OK - well this shows that it will want to boot to WinPE v1/XP. So if Win7 is on the disk, you need to run bootsect on it. Then it should boot to Win7 if it has valid win7 boot files.

[Wonko the Sane]

It shows that the partition starts at sector 32, If you now re-click the DriveInfo and enter P1 (for first partition) you will see hex dump which should show you what the boot code is (see end of the 512 bytes which usually has name of boot file) - example below shows MSDOS boot code.

To be picky, on NTFS formatted disks, that area contains the Error messages, the boot file name is on SECOND sector.
It is possible (though VERY UNprobable) that a tool like Makebs:
http://reboot.pro/2362/
has been used (or the same kind of mods made manually) and that you have an error message with a given boot file, but the actual code invokes another one.


Wonko

[vesilp]

OK - well this shows that it will want to boot to WinPE v1/XP. So if Win7 is on the disk, you need to run bootsect on it. Then it should boot to Win7 if it has valid win7 boot files.

Thank you again, steve !
I am now at home, but tomorrow will try this:

1. Boot to (the only available) Internal-HDD Windows 7
2. Navigate to D:\WAIK Files directory, where the actual bootsect.exe is located
3. Run D:\WAIK Files\bootsect /nt60 F:

and then will post the result.

[vesilp]

My attempt failed, sorry !
Maybe I made a mistake ...
At the last minute I decided, that it will be better to run bootsect.exe from this path (after copying to):
F:\Windows\system32>bootsect /nt60 F:
as this is the target system volume, after all...
And this decision was obviously wrong ? Bootsect returned this result:

"Target volumes will be updated with BOOTMGR compatible bootcode.
F: <.... long alphanumeric string ...>
Updated NTFS filesystem bootcode. The update may be unreliable
since the volume could not be locked during update:
Access is denied
Bootcode was successfully updated on all target volumes"

Probably, access is denied because of the attempt to update the drive from ITSELF ?

Then I made a second attempt, this time from
D:\WAIK Files\bootsect /nt60 F: (as initialy meant)
The result was different, as expected:

"Target volumes will be updated with BOOTMGR compatible bootcode.
F: <.... long alphanumeric string ...>
Successfully updated NTFS filesystem bootcode.
Bootcode was successfully updated on all target volumes"

BUT - nothing chainged !
The system still boots only to it's internal-HDD Windows, regardless of the Boot menu choice !

[steve6375]

Does the external drive boot using the QEMU button in RMPrepUSB? If not then something is wrong with the drive contents - if it does boot (or at least tries to boot) then something is wrong with your BIOS/computer(s).