Page 1 of 1

Bootnow; sometimes it works, other times it does not work

Posted: Fri Oct 14, 2011 1:17 am
by skipro
I have 8 entries in the boot menu [all on HD0] and also Bootnow shortcuts to
boot into each from each OS [XP, Win 7 & Win 8]. What is troublesome and
strange is that sometimes it works and sometimes the same shortcuts do not
work, get the "MDT not found" error. I can use Bootnow successfully and
immediately try it again and it may not work. When 1 shortcut does not work,
none of them work, not until after a reboot, then it may work. I never had
this issue with BING.
All the OS entries are simple and standard. This is not an administrator
issue.


Re: Bootnow; sometimes it works, other times it does not wor

Posted: Fri Oct 14, 2011 1:40 am
by Brian K
skipro wrote: get the "MDT not found" error.
Can this occur in each of your OS? WinXP too?

Re: Bootnow; sometimes it works, other times it does not work

Posted: Fri Oct 14, 2011 4:10 am
by TeraByte Support
If you have more than one hard drive, windows may be changing the drive
number on you, otherwise something is preventing access to the drive, or
providing a fake view of the drive. BootNow simply attempts to read from
HD0 or whatever the bootnow.ini points to. To determine what drive 0 is,
you need to look in computer management / drive management (in windows) when
you have the problem (such as having a USB drive attached or IDE drive
attached when normally not, etc..).

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

I have 8 entries in the boot menu [all on HD0] and also Bootnow shortcuts to
boot into each from each OS [XP, Win 7 & Win 8]. What is troublesome and
strange is that sometimes it works and sometimes the same shortcuts do not
work, get the "MDT not found" error. I can use Bootnow successfully and
immediately try it again and it may not work. When 1 shortcut does not work,
none of them work, not until after a reboot, then it may work. I never had
this issue with BING.
All the OS entries are simple and standard. This is not an administrator
issue.


Re: Bootnow; sometimes it works, other times it does not wor

Posted: Fri Oct 14, 2011 9:30 pm
by skipro
yes

"Brian K" wrote in message news:493@public.bootitbm...

[quote="skipro":3m8i07m0]
get the "MDT not found" error. [/quote:3m8i07m0]

Can this occur in each of your OS? WinXP too?

Re: Bootnow; sometimes it works, other times it does not work

Posted: Fri Oct 14, 2011 9:45 pm
by skipro
You nailed it. Windows sometimes sees HD0 as HD1. This begs the question,
why and what can I do? BIOS sees my primary drive as primary HD[SATA]. BIBM
sees it as HD0 and sometimes Windows sees it as HD0. Is this a BIOS issue?

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

If you have more than one hard drive, windows may be changing the drive
number on you, otherwise something is preventing access to the drive, or
providing a fake view of the drive. BootNow simply attempts to read from
HD0 or whatever the bootnow.ini points to. To determine what drive 0 is,
you need to look in computer management / drive management (in windows) when
you have the problem (such as having a USB drive attached or IDE drive
attached when normally not, etc..).

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

I have 8 entries in the boot menu [all on HD0] and also Bootnow shortcuts to
boot into each from each OS [XP, Win 7 & Win 8]. What is troublesome and
strange is that sometimes it works and sometimes the same shortcuts do not
work, get the "MDT not found" error. I can use Bootnow successfully and
immediately try it again and it may not work. When 1 shortcut does not work,
none of them work, not until after a reboot, then it may work. I never had
this issue with BING.
All the OS entries are simple and standard. This is not an administrator
issue.


Re: Bootnow; sometimes it works, other times it does not work

Posted: Sat Oct 15, 2011 5:27 am
by TeraByte Support
If windows tries to determine the drives via the BIOS EDD information then
it could be related to a BIOS bug or it could be related to a Windows bug.
If it didn't try then it would use some standard enumeration of bus/device,
if they tried doing multiple buses at the same time then the devices could
be inconsistent, How many drives and what types?

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

You nailed it. Windows sometimes sees HD0 as HD1. This begs the question,
why and what can I do? BIOS sees my primary drive as primary HD[SATA]. BIBM
sees it as HD0 and sometimes Windows sees it as HD0. Is this a BIOS issue?

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

If you have more than one hard drive, windows may be changing the drive
number on you, otherwise something is preventing access to the drive, or
providing a fake view of the drive. BootNow simply attempts to read from
HD0 or whatever the bootnow.ini points to. To determine what drive 0 is,
you need to look in computer management / drive management (in windows) when
you have the problem (such as having a USB drive attached or IDE drive
attached when normally not, etc..).

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

I have 8 entries in the boot menu [all on HD0] and also Bootnow shortcuts to
boot into each from each OS [XP, Win 7 & Win 8]. What is troublesome and
strange is that sometimes it works and sometimes the same shortcuts do not
work, get the "MDT not found" error. I can use Bootnow successfully and
immediately try it again and it may not work. When 1 shortcut does not work,
none of them work, not until after a reboot, then it may work. I never had
this issue with BING.
All the OS entries are simple and standard. This is not an administrator
issue.


Re: Bootnow; sometimes it works, other times it does not work

Posted: Sat Oct 15, 2011 11:43 pm
by skipro
I have 2 standard SATA drives, SATA port #1 has my primary drive [OSs], SATA
#2 has my backup drive. I am running these in native IDE mode.

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

If windows tries to determine the drives via the BIOS EDD information then
it could be related to a BIOS bug or it could be related to a Windows bug.
If it didn't try then it would use some standard enumeration of bus/device,
if they tried doing multiple buses at the same time then the devices could
be inconsistent, How many drives and what types?

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

You nailed it. Windows sometimes sees HD0 as HD1. This begs the question,
why and what can I do? BIOS sees my primary drive as primary HD[SATA]. BIBM
sees it as HD0 and sometimes Windows sees it as HD0. Is this a BIOS issue?

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

If you have more than one hard drive, windows may be changing the drive
number on you, otherwise something is preventing access to the drive, or
providing a fake view of the drive. BootNow simply attempts to read from
HD0 or whatever the bootnow.ini points to. To determine what drive 0 is,
you need to look in computer management / drive management (in windows) when
you have the problem (such as having a USB drive attached or IDE drive
attached when normally not, etc..).

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

I have 8 entries in the boot menu [all on HD0] and also Bootnow shortcuts to
boot into each from each OS [XP, Win 7 & Win 8]. What is troublesome and
strange is that sometimes it works and sometimes the same shortcuts do not
work, get the "MDT not found" error. I can use Bootnow successfully and
immediately try it again and it may not work. When 1 shortcut does not work,
none of them work, not until after a reboot, then it may work. I never had
this issue with BING.
All the OS entries are simple and standard. This is not an administrator
issue.


Re: Bootnow; sometimes it works, other times it does not work

Posted: Tue Oct 18, 2011 8:12 pm
by skipro
Is TB going to respond to my answer to their question?


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

I have 2 standard SATA drives, SATA port #1 has my primary drive [OSs], SATA
#2 has my backup drive. I am running these in native IDE mode.

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

If windows tries to determine the drives via the BIOS EDD information then
it could be related to a BIOS bug or it could be related to a Windows bug.
If it didn't try then it would use some standard enumeration of bus/device,
if they tried doing multiple buses at the same time then the devices could
be inconsistent, How many drives and what types?

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

You nailed it. Windows sometimes sees HD0 as HD1. This begs the question,
why and what can I do? BIOS sees my primary drive as primary HD[SATA]. BIBM
sees it as HD0 and sometimes Windows sees it as HD0. Is this a BIOS issue?

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

If you have more than one hard drive, windows may be changing the drive
number on you, otherwise something is preventing access to the drive, or
providing a fake view of the drive. BootNow simply attempts to read from
HD0 or whatever the bootnow.ini points to. To determine what drive 0 is,
you need to look in computer management / drive management (in windows) when
you have the problem (such as having a USB drive attached or IDE drive
attached when normally not, etc..).

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

I have 8 entries in the boot menu [all on HD0] and also Bootnow shortcuts to
boot into each from each OS [XP, Win 7 & Win 8]. What is troublesome and
strange is that sometimes it works and sometimes the same shortcuts do not
work, get the "MDT not found" error. I can use Bootnow successfully and
immediately try it again and it may not work. When 1 shortcut does not work,
none of them work, not until after a reboot, then it may work. I never had
this issue with BING.
All the OS entries are simple and standard. This is not an administrator
issue.


Re: Bootnow; sometimes it works, other times it does not work

Posted: Wed Oct 19, 2011 2:35 am
by TeraByte Support
There is no response, it's a BIOS or Windows problem depending on what
Windows is doing as mentioned before. The only thing you can do if you
can't get MS to fix it or tell you what would fix it, or the BIOS won't fix
it, then setup a batch file and have it try one drive, if it fails, copy or
modify a new bootnow.ini file and try again.


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

Is TB going to respond to my answer to their question?


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

I have 2 standard SATA drives, SATA port #1 has my primary drive [OSs], SATA
#2 has my backup drive. I am running these in native IDE mode.

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

If windows tries to determine the drives via the BIOS EDD information then
it could be related to a BIOS bug or it could be related to a Windows bug.
If it didn't try then it would use some standard enumeration of bus/device,
if they tried doing multiple buses at the same time then the devices could
be inconsistent, How many drives and what types?

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

You nailed it. Windows sometimes sees HD0 as HD1. This begs the question,
why and what can I do? BIOS sees my primary drive as primary HD[SATA]. BIBM
sees it as HD0 and sometimes Windows sees it as HD0. Is this a BIOS issue?

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

If you have more than one hard drive, windows may be changing the drive
number on you, otherwise something is preventing access to the drive, or
providing a fake view of the drive. BootNow simply attempts to read from
HD0 or whatever the bootnow.ini points to. To determine what drive 0 is,
you need to look in computer management / drive management (in windows) when
you have the problem (such as having a USB drive attached or IDE drive
attached when normally not, etc..).

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

I have 8 entries in the boot menu [all on HD0] and also Bootnow shortcuts to
boot into each from each OS [XP, Win 7 & Win 8]. What is troublesome and
strange is that sometimes it works and sometimes the same shortcuts do not
work, get the "MDT not found" error. I can use Bootnow successfully and
immediately try it again and it may not work. When 1 shortcut does not work,
none of them work, not until after a reboot, then it may work. I never had
this issue with BING.
All the OS entries are simple and standard. This is not an administrator
issue.