Page 1 of 1

Product key requested even though was used in install

Posted: Fri Feb 03, 2012 6:30 pm
by Bill
This morning when I brought my computer out of hibernate BIBM requested the user name and product key. When I created the boot media for install I know for certain that I entered the key then because I documented every step. I thought I was locked out of my computer since my only record of the key was on the computer! I was glad to see after hitting Cancel that there was just a 45 second delay, and then I could finish the boot. Why would BIBM ask for the key?

Also, after booting up following the initial request for the key, when I tried to access my laptop on my network, I couldn't see the laptop, and checking the laptop, it couldn't see my desktop. I don't know if that was related to BIBM, but once I entered the key after rebooting, my network worked fine.

Re: Product key requested even though was used in install

Posted: Sun Feb 05, 2012 5:09 am
by TeraByte Support
because it couldn't find a valid one. Either couldn't access the .ini file
or something changed it?

"Bill" wrote in message news:1280@public.bootitbm...

This morning when I brought my computer out of hibernate BIBM requested the
user name and product key. When I created the boot media for install I know
for certain that I entered the key then because I documented every step. I
thought I was locked out of my computer since my only record of the key was
on the computer! I was glad to see after hitting Cancel that there was just
a 45 second delay, and then I could finish the boot. Why would BIBM ask for
the key?

Also, after booting up following the initial request for the key, when I
tried to access my laptop on my network, I couldn't see the laptop, and
checking the laptop, it couldn't see my desktop. I don't know if that was
related to BIBM, but once I entered the key after rebooting, my network
worked fine.


Re: Product key requested even though was used in install

Posted: Sun Feb 05, 2012 10:34 am
by Bill
"TeraByte Support" wrote in message
news:1296@public.bootitbm...
> because it couldn't find a valid one. Either couldn't access the .ini
> file
> or something changed it?

Possible, but I don't know how or why. It hasn't happened again.