Unable to bind tcp/ip to netvmini driver in Windows 7 ?!?!

Finally I figured it out.

The problem is with the son-of-a-whore VMware which boots way to fast,
popsup all kinds of hint messages...

Causing the keyboard not to function...

The trick is to quickly click away the pop up message...

And press Escape quickly to enter the boot menu bios menu or whatever...

Then discard changes....

And then press F8 will work as it always has.

This will bring up an advanced menu... as long as windows shutdown normally.

Here the disable option for the driver signing is available.

Took me like 15+ or so reboots to figure this shit out ! ;) :)

Bye,
Skybuck.

Skybuck Flying wrote:
> Finally I figured it out.
>
> The problem is with the son-of-a-whore VMware which boots way to
> fast, popsup all kinds of hint messages...
>
> Causing the keyboard not to function...
>
> The trick is to quickly click away the pop up message...
>
> And press Escape quickly to enter the boot menu bios menu or
> whatever...
> Then discard changes....
>
> And then press F8 will work as it always has.
>
> This will bring up an advanced menu... as long as windows shutdown
> normally.
> Here the disable option for the driver signing is available.
>
> Took me like 15+ or so reboots to figure this shit out ! ;) :)

So what you are saying is, "My Bad. I didn't know how to use the products I
was trying to use. Ignore all previous outbursts."

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Ok,

As promised now it works.

So binding seems possible after all... the problem solely has to do with the
****ing singing of the drivers ?!

****ing shit.

Now the network situation looks much better :)

And now I can go FINALLY after spending like 3 hours test some more.

Bye,
Skybuck.

Ok,

Part of the problem was network adapters/connections not showing up where
they should have been.

Therefore I was searching like crazy and ending up all over the place.

Now that the driver signing enforcement bs is disabled it looks better ;) :)

Bye,
Skybuck =D

I am saying that there is a lot of shit in these bitches ?!

Learn from my experiences ?!

Right now I am trying to boot:

1. Windows debug mode.

+

2. Driver signing disabled.

And VMware playing tricks on me again...

Or is it windows this time ?

I got some kind of boot menu saying:

"Windows debug mode" or something..

"Selecting operating system" or something..

But it disappeared again ?!?

Maybe I pressed escaped / F8 to many times ?!

Apperently escape cancels the windows boot menu ?!?!?!?!?!?!?!?!?!?!?

But VMware excepts me to press escape TO ENTER it's boot/bios menu ?!?!?!?!

Do you see the problem now ?!?

If I press escape to late I will miss the BIOS menu...

if I press F8 to late I will miss the windows boot menu...

If I then press escape again I might accidently exit the windows boot menu
?!

WHAT A FRICKING MESS !

Bye,
Skybuck.

Ok,

I think I figured it out now.

1. The vm network connections need to be enabled in the host operating
system to avoid the pop-ups.

Supposedly this would be safe as long as "vm bridge protocol" and "virtual
network connection" (virtual pc) is "unchecked/disabled".

(I use host only networking for the virtual machines).

2. Click never show warning message again for "CPU Clock" warning (power
saving related nag message).

3. Now simply let windows boot... as soon as the VMware bios message is gone
press F8 just once... maybe twice... maybe 100 times.. it probably can't
hurt...

But just press F8 and nothing else...

Now the windows boot menu should appear.

So under these conditions the boot menu will work.

But if I disable all kinds of stuff again... then it will be hell again.

But for now it's ok.

Bye,
Skybuck.

Lessons to be learned for VMware's developers:

"pop-up/hint messages are evil !".

"Use a nicely integrated status or hint bar... that doesn't get in the way !
;)"

Bye,
Skybuck.

"Skybuck Flying" <BloodyShame@hotmail.com> wrote in message
news:91da5$4a7e1f82$d53372a9$27343@cache2.tilbu1.nb.home.nl...
> Ok,
>
> I think I figured it out now.
>
> 1. The vm network connections need to be enabled in the host operating
> system to avoid the pop-ups.
>
> Supposedly this would be safe as long as "vm bridge protocol" and "virtual
> network connection" (virtual pc) is "unchecked/disabled".
>
> (I use host only networking for the virtual machines).
>
> 2. Click never show warning message again for "CPU Clock" warning (power
> saving related nag message).
>
> 3. Now simply let windows boot... as soon as the VMware bios message is
> gone press F8 just once... maybe twice... maybe 100 times.. it probably
> can't hurt...
>
> But just press F8 and nothing else...
>
> Now the windows boot menu should appear.
>
> So under these conditions the boot menu will work.
>
> But if I disable all kinds of stuff again... then it will be hell again.
>
> But for now it's ok.
>
> Bye,
> Skybuck.
>

Also,

I as user have to click into the window when I start it...

Hmmm...

I missed it again so have to reboot again.

Bye,
Skybuck.

"Skybuck Flying" <BloodyShame@hotmail.com> wrote in message
news:d5c35$4a7e1fe1$d53372a9$27635@cache2.tilbu1.nb.home.nl...
> Lessons to be learned for VMware's developers:
>
> "pop-up/hint messages are evil !".
>
> "Use a nicely integrated status or hint bar... that doesn't get in the way
> ! ;)"
>
> Bye,
> Skybuck.
>
> "Skybuck Flying" <BloodyShame@hotmail.com> wrote in message
> news:91da5$4a7e1f82$d53372a9$27343@cache2.tilbu1.nb.home.nl...
>> Ok,
>>
>> I think I figured it out now.
>>
>> 1. The vm network connections need to be enabled in the host operating
>> system to avoid the pop-ups.
>>
>> Supposedly this would be safe as long as "vm bridge protocol" and
>> "virtual network connection" (virtual pc) is "unchecked/disabled".
>>
>> (I use host only networking for the virtual machines).
>>
>> 2. Click never show warning message again for "CPU Clock" warning (power
>> saving related nag message).
>>
>> 3. Now simply let windows boot... as soon as the VMware bios message is
>> gone press F8 just once... maybe twice... maybe 100 times.. it probably
>> can't hurt...
>>
>> But just press F8 and nothing else...
>>
>> Now the windows boot menu should appear.
>>
>> So under these conditions the boot menu will work.
>>
>> But if I disable all kinds of stuff again... then it will be hell again.
>>
>> But for now it's ok.
>>
>> Bye,
>> Skybuck.
>>
>
>

> The interface is far from a jump if you have become used to Windows Vista
> (definitely not as much of a jump as the interface from XP to Vista was.)
> It has been extremely stable

Long walk over Win7's control panel with extensive use of Back button causes Explorer to crash.

It was not so in any Vista.

> There will be driver issues as it becomes public

Hardly. Most Vista drivers are OK for Win7, if not even _practically all_ Vista drivers.

Win7 and Vista differ the same way as XP and 2003. Most XP drivers were OK for 2003.

--
Maxim S. Shatskih
Windows DDK MVP
maxim@storagecraft.com
http://www.storagecraft.com

> Apperently windows 7 has strong enforcing rules for drivers.
>
> If a driver is unsigned it won't load.

On x64 versions only. It is also this way in Vista.

> I tried this... (in VMware)...
>
> IT DIDN'T WORK.

I also tried this. It works always.

--
Maxim S. Shatskih
Windows DDK MVP
maxim@storagecraft.com
http://www.storagecraft.com