Page 1 of 1

BIBM and Bootnow

PostPosted: Tue Sep 27, 2011 11:51 am
by skipro
4 Windows partitions in "Boot Edit". Latest version Bootnow.
I just upgraded from BING to BIBM 3 days ago. Bootnow worked in BING. After
upgrade, I
get the "MDT not found" message on all Bootnow shortcuts. If I go into BIBM
"Maintainence" and then into "Settings" or "PW", make no changes or even
save, just
cancel out, in other words, just open, then Bootnow works, but not 100%. It
may not work in one of the partitions and I have to redo the steps. Next day
same problem and I have to start over again.



Re: BIBM and Bootnow

PostPosted: Tue Sep 27, 2011 12:59 pm
by TeraByte Support
You have to right click your shortcut, compatibility tab, set it to run as
administrator.

MDT not found means it can't read the MDT of the EMBR which is only on HD0.
If the drive 0 is not the boot drive, you need to setup bootnow.ini file in
windows folder - see readme.txt included with bootnow.


"skipro" wrote in message news:402@public.bootitbm...

4 Windows partitions in "Boot Edit". Latest version Bootnow.
I just upgraded from BING to BIBM 3 days ago. Bootnow worked in BING. After
upgrade, I
get the "MDT not found" message on all Bootnow shortcuts. If I go into BIBM
"Maintainence" and then into "Settings" or "PW", make no changes or even
save, just
cancel out, in other words, just open, then Bootnow works, but not 100%. It
may not work in one of the partitions and I have to redo the steps. Next day
same problem and I have to start over again.



Re: BIBM and Bootnow

PostPosted: Tue Sep 27, 2011 2:55 pm
by skipro
HD0 is boot drive.
Why does it work without "run as administrator" eventually after I enter
BIBM [as described]?

"TeraByte Support" wrote in message news:403@public.bootitbm...

You have to right click your shortcut, compatibility tab, set it to run as
administrator.

MDT not found means it can't read the MDT of the EMBR which is only on HD0.
If the drive 0 is not the boot drive, you need to setup bootnow.ini file in
windows folder - see readme.txt included with bootnow.


"skipro" wrote in message news:402@public.bootitbm...

4 Windows partitions in "Boot Edit". Latest version Bootnow.
I just upgraded from BING to BIBM 3 days ago. Bootnow worked in BING. After
upgrade, I
get the "MDT not found" message on all Bootnow shortcuts. If I go into BIBM
"Maintainence" and then into "Settings" or "PW", make no changes or even
save, just
cancel out, in other words, just open, then Bootnow works, but not 100%. It
may not work in one of the partitions and I have to redo the steps. Next day
same problem and I have to start over again.



Re: BIBM and Bootnow

PostPosted: Tue Sep 27, 2011 2:57 pm
by skipro
"run as administrator." does not work.

"skipro" wrote in message news:405@public.bootitbm...

HD0 is boot drive.
Why does it work without "run as administrator" eventually after I enter
BIBM [as described]?

"TeraByte Support" wrote in message news:403@public.bootitbm...

You have to right click your shortcut, compatibility tab, set it to run as
administrator.

MDT not found means it can't read the MDT of the EMBR which is only on HD0.
If the drive 0 is not the boot drive, you need to setup bootnow.ini file in
windows folder - see readme.txt included with bootnow.


"skipro" wrote in message news:402@public.bootitbm...

4 Windows partitions in "Boot Edit". Latest version Bootnow.
I just upgraded from BING to BIBM 3 days ago. Bootnow worked in BING. After
upgrade, I
get the "MDT not found" message on all Bootnow shortcuts. If I go into BIBM
"Maintainence" and then into "Settings" or "PW", make no changes or even
save, just
cancel out, in other words, just open, then Bootnow works, but not 100%. It
may not work in one of the partitions and I have to redo the steps. Next day
same problem and I have to start over again.



Re: BIBM and Bootnow

PostPosted: Tue Sep 27, 2011 3:56 pm
by TeraByte Support
It has to run as administrator or it won't work. Only if your elevated to
administrator would it even work. But the MDT not found means the hard
drive doesn't contain an MDT so it may not be HD0 and require the
bootnow.ini file. Changing boot items won't affect MDT message. If you
have a root kit it may be altering reads to some other location that doesn't
contain the EMBR. Run partinfo (free downloads) to see what that outputs.

"skipro" wrote in message news:406@public.bootitbm...

"run as administrator." does not work.

"skipro" wrote in message news:405@public.bootitbm...

HD0 is boot drive.
Why does it work without "run as administrator" eventually after I enter
BIBM [as described]?

"TeraByte Support" wrote in message news:403@public.bootitbm...

You have to right click your shortcut, compatibility tab, set it to run as
administrator.

MDT not found means it can't read the MDT of the EMBR which is only on HD0.
If the drive 0 is not the boot drive, you need to setup bootnow.ini file in
windows folder - see readme.txt included with bootnow.


"skipro" wrote in message news:402@public.bootitbm...

4 Windows partitions in "Boot Edit". Latest version Bootnow.
I just upgraded from BING to BIBM 3 days ago. Bootnow worked in BING. After
upgrade, I
get the "MDT not found" message on all Bootnow shortcuts. If I go into BIBM
"Maintainence" and then into "Settings" or "PW", make no changes or even
save, just
cancel out, in other words, just open, then Bootnow works, but not 100%. It
may not work in one of the partitions and I have to redo the steps. Next day
same problem and I have to start over again.