Error bootfile, if it launches image on non-priority drive.

User discussion and information resource forum for the TeraByte OS Deployment Tool Suite.

Error bootfile, if it launches image on non-priority drive.

Postby ostapvoip » Fri Feb 08, 2013 3:43 pm

Hi.
Sorry for bad english.
Error bootfile Windows version, if it launches image on non-priority drive :(

I have two hard drives. First hard drive Samsung HD0, the second Western DIGITAL HD1.
Windows loaded from the first hard drive Samsung HD0, that is, the loader bootmgr on HD0. Kernel Windows 7 on Western DIGITAL HD1.
If I run a bootfile to launch IFD of Western DIGITAL HD1, get lost MBR partition table on the disk Western DIGITAL HD1. Because the priority HDD in the BIOS - Samsung.

How to beat this bug?
Is it possible to use script Windows version TBOSDTS for determining the priority HDD in BIOS and validation correct run bootfile on priority HDD? How :?:
Use script diskpart sel disk=system possible, but not desirable ...
Thank you.
ostapvoip
 
Posts: 7
Joined: Fri Feb 08, 2013 3:32 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby TeraByte Support(PP) » Fri Feb 08, 2013 4:18 pm

Do you have TARGETDIR configured to create the files on the booting drive (HD0)? If HD0 is the booting drive you need to configure and run from HD0 for it to work.
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1108
Joined: Thu Aug 11, 2011 5:51 pm

Re: Error bootfile, if it launches image on non-priority drive.

Postby TeraByte Support » Fri Feb 08, 2013 7:51 pm

you can run the /restore option to put back any mbr data.

"ostapvoip" wrote in message news:4641@public.tbosdt...

Hi.
Sorry for bad english.
Error bootfile Windows version, if it launches image on non-priority drive

![:(]({SMILIES_PATH}/icon_e_sad.gif)

I have two hard drives. First hard drive Samsung HD0, the second Western
DIGITAL HD1.
Windows loaded from the first hard drive Samsung HD0, that is, the loader
bootmgr on HD0. Kernel Windows 7 on Western DIGITAL HD1.
If I run a bootfile to launch IFD of Western DIGITAL HD1, get lost MBR
partition table on the disk Western DIGITAL HD1. Because the priority HDD in
the BIOS - Samsung.

How to beat this bug?
Is it possible to use script Windows version TBOSDTS for determining the
priority HDD in BIOS and validation correct run bootfile on priority HDD?
How

![:?:]({SMILIES_PATH}/icon_question.gif)

Use script diskpart sel disk=system possible, but not desirable ...
Thank you.

TeraByte Support
 
Posts: 2325
Joined: Thu May 05, 2011 3:37 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby ostapvoip » Fri Feb 08, 2013 9:22 pm

You probably joking?
Quote from help:
MBR RESTORE ONLY USAGE (DOS/Linux only):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bootfile [/noui] [/ignoresig] [/verbose]

/noui -- [optional] This switch prevents the message box from
showing if a problem occurs. The errorlevel returned
by BOOTFILE can be used in a script to detect a problem.

/ignoresig -- [optional] This switch allows the saved MBR to be
restored even if the NT disk signatures do not match.

/verbose -- [optional] Outputs additional information

This will not help.

I asked a simple question:
How to check with commands TBOSDTS drive HDD priority (HD0 or HD1 or ...) . Nothing more.
Because the bootfile is not fully thought out, I want to do a scan self.
Thank you.
ostapvoip
 
Posts: 7
Joined: Fri Feb 08, 2013 3:32 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby TeraByte Support » Fri Feb 08, 2013 11:56 pm

He's talking about the script. Did you follow the steps and use the script
from the tutorial:

http://www.terabyteunlimited.com/howto/howto-ifl-bootfile.htm

or

http://www.terabyteunlimited.com/howto/howto-ifd-bootfile.htm

?

As I mentioned before, you can run bootfile /restore from Windows to reset
the MBR on the other drive - it scans all drives.

You have to run things from and on your boot drive - that's where the files
need to go and where it looks to make it bootable.




"ostapvoip" wrote in message news:4649@public.tbosdt...

You probably joking?
Quote from help:
MBR RESTORE ONLY USAGE (DOS/Linux only):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bootfile [/noui] [/ignoresig] [/verbose]

/noui -- [optional] This switch prevents the message box
from
showing if a problem occurs. The errorlevel
returned
by BOOTFILE can be used in a script to detect a
problem.

/ignoresig -- [optional] This switch allows the saved MBR to be
restored even if the NT disk signatures do not
match.

/verbose -- [optional] Outputs additional information

This will not help.

I asked a simple question:
How to check with commands TBOSDTS drive HDD priority (HD0 or HD1 or ...)
.. Nothing more.
Because the bootfile is not fully thought out, I want to do a scan self.
Thank you.

TeraByte Support
 
Posts: 2325
Joined: Thu May 05, 2011 3:37 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby ostapvoip » Sat Feb 09, 2013 4:34 am

As I mentioned before, you can run bootfile /restore from Windows to reset
the MBR on the other drive - it scans all drives.

ok. check it out.
write the result.
ostapvoip
 
Posts: 7
Joined: Fri Feb 08, 2013 3:32 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby ostapvoip » Sat Feb 09, 2013 4:40 pm

Уou wrote:
As I mentioned before, you can run bootfile /restore from Windows to reset
the MBR on the other drive - it scans all drives.

ОК. Only problem is that it does not work out Linux and DOS. They do not have that option. Only I didn't loaded Windows.
Therefore will http://img17.imageshack.us/img17/3577/2 ... 004323.png

You still have not answered:
How to check with commands TBOSDTS drive HDD priority (HD0 or HD1 or ...) Because the bootfile is not fully thought out, I want to do a scan self.

I have tried
h = gethdinfo(n) and h.BIOSHDNUM 0x80 and etc..
But the priority drive BIOS not correct. :(
Only diskpart sel disk=system correct.

Thank you.
ostapvoip
 
Posts: 7
Joined: Fri Feb 08, 2013 3:32 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby TeraByte Support » Sat Feb 09, 2013 6:14 pm

for DOS/Linux you just run bootfile and it assumes /restore (switch not
available) and scans all drives to restore.

You can get the BIOS drive number as you mentioned, but if you're running
from a boot disk, the BIOS order may not match the boot order because they
don't change the order of the drives until you boot the hard drive. If you
had a simple setup you could say the drive with the active partition was the
boot drive, but it's common for multiple drives to have an active partition.

But as far as bootfile, you put the files on a drive letter that exists on
the boot drive.


"ostapvoip" wrote in message news:4653@public.tbosdt...

?ou wrote:
As I mentioned before, you can run bootfile /restore from Windows to reset
the MBR on the other drive - it scans all drives.

??. Only problem is that it does not work out Linux and DOS. They do not
have that option. Only I didn't loaded Windows.
Therefore will

[
http://img17.imageshack.us/img17/3577/2 ... 004323.png
](http://img17.imageshack.us/img17/3577/20130210004323.png)

You still have not answered:
How to check with commands TBOSDTS drive HDD priority (HD0 or HD1 or ...)
Because the bootfile is not fully thought out, I want to do a scan self.

I have tried
h = gethdinfo(n) and h.BIOSHDNUM 0x80 and etc..
But the priority drive BIOS not correct.

![:(]({SMILIES_PATH}/icon_e_sad.gif)

Only diskpart sel disk=system correct.

Thank you.

TeraByte Support
 
Posts: 2325
Joined: Thu May 05, 2011 3:37 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby ostapvoip » Sat Feb 09, 2013 7:49 pm

Maybe you do not understand my problem?
I am wondering how to get the number priority HDD from Windows (before running bootfile+image) without using diskpart (I do not like diskpart).
If properly understood - with Windows version TBOSDT can not get the number priority disk was last loaded Windows. Yes?

I want to write a script that warns the user that bootfile does not run on the drive.
And stop c:\bootfile.exe c:\my.img.
ostapvoip
 
Posts: 7
Joined: Fri Feb 08, 2013 3:32 pm

Re: Error bootfile, if it launches image on non-priority dri

Postby TeraByte Support » Sun Feb 10, 2013 11:28 pm

Unfortunately windows doesn't seem to report the bios drive number of a
particular drive. You'd have to find a registry entry that tells you which
drive is which or look for an active SRP partition, or parse the BCD. If
there was a drive letter available on the boot drive (which windows calls
the system drive or system volume) then you could use gethdinfo after
enabling drive letters to find the drive with that drive letter. Windows
reports the OS drive letter (which windows calls the boot drive or boot
volume). Not to be confused with %SystemDrive% which is the boot volume.
Using a bunch of logic, you may be able to figure it out across different
systems (looking for the active partitions, comparing with drive letters,
etc.. - but it is possible that the main boot drive doesn't have any drive
letters available on it).

"ostapvoip" wrote in message news:4655@public.tbosdt...

Maybe you do not understand my problem?
I am wondering how to get the number priority HDD from Windows (before
running bootfile+image) without using diskpart (I do not like diskpart).
If properly understood - with Windows version TBOSDT can not get the number
priority disk was last loaded Windows. Yes?

I want to write a script that warns the user that bootfile does not run on
the drive.
And stop c:\bootfile.exe c:\my.img.

TeraByte Support
 
Posts: 2325
Joined: Thu May 05, 2011 3:37 pm

Next

Return to OSD Tool Suite