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

[Skybuck Flying]

Hello,

I build the "checked" netvmini.sys (virtual network adapter) driver from
Windows Driver/Development Kit 7 (WDK7).

Then I try to install it into Windows 7 Ultimate RTM and Windows 7
complains:

"
Windows cannot verify the digital signature for the drivers required for
this device. A recent hardware or software change might have installed a
file that is signed incorrectly or damaged, or that might be malicious
software from an unknown source. (Code 52)
"

Windows 7 does not add tcp/ip to this...

Also the device does not show up in network properties ?

Also Windows 7 GUI is pretty much fucked, I don't think I am gonna like it
ever.

Bye,
Skybuck.

[Shenan Stanley]

Post by Skybuck Flying
I build the "checked" netvmini.sys (virtual network adapter) driver
from Windows Driver/Development Kit 7 (WDK7).
Then I try to install it into Windows 7 Ultimate RTM and Windows 7
"Windows cannot verify the digital signature for the drivers
required for this device. A recent hardware or software change
might have installed a file that is signed incorrectly or damaged,
or that might be malicious software from an unknown source. (Code
52)"
Windows 7 does not add tcp/ip to this...
Also the device does not show up in network properties ?
Also Windows 7 GUI is pretty much #$%^*&#, I don't think I am gonna
like it ever.

Stop trying to use it then and move on. If you cannot figure it out and you
don't think you are going to like it - then don't use it. Not a difficult
thing. ;-)

I have seen people (including myself) installing Windows 7 beta and RC1 in
various forms for months and recently installed the RTM on a few machines
myself (physical machines, VMware VMs and VirtualBox VMs) without issue.

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 (more so, in my experience, than Windows Vista
32-bit pre-SP2.) It seems better prepared for the business environment in
some ways as well - which is nice in my opinion.

There will be driver issues as it becomes public (it is not officially
public until October.) If you have it now legitimately, it is because you
were a beta tester, are an OEM or subscribe to TechNet or MSDN. Yes - it
went RTM, but that means that the hardware device manufacturer's have a
couple of months to come up with working drivers, OEMs have time to build
their systems so things will work properly, etc.

There's always driver issues when a new OS comes out - no matter the OS.
Hardware vendors have to create drivers for the OS, not the other way
around. They get to choose whether or not they support it for another round
of OS changes. Same for software vendors.

In any case - again - if you cannot get whatever it is you are trying to do
to work and you think you aren't going to like it anyway (your words) - then
your wisest course of action is to stop trying. Hand on stove, ouch that is
hot - if you repeat it, that's just not wise.

[Skybuck Flying]

Microsoft has a huge GUI problem.

That has become apperent from using Windows 7...

As far as I can tell there is no XP gui in Windows 7 ?

Is this why microsoft is working so hard for an XP virtual machine inside
Windows 7 ?!?!

That's apperently an admission that they are scared shitless of losing a
HUGE customer base...

Because I am pretty sure that they huge customer base that uses XP right now
is gonna hate Windows 7 GUI IN A BIG WAY.

That means that the only new customers for Microsoft might be little
kiddies.

Windows 7 has truely become a Kiddy operating system ?!

Maybe it's becaue of Bill Gates children ? ;)

Maybe Bill wants a nice fisher price operating system for his KIDS ?! LOL.

And now we all have to suffer for it ?! NO FUCKING WAY BITCH ! =D

WHY THE FUCK WOULD I INSTALL WINDOWS 7 with an XP FUCKING MODE ?!?

I might as well keep XP and install Windows 7 in VMWARE BLEH.

NASTY BS that's what it is !

I got a very sauer/acid taste in my mouth after seeing windows 7 gui in
action. BAH YAKES IIIIEEEWWWWWWW.

At least linux has an old school gui.

Bye,
Skybuck.

[Skybuck Flying]

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

[Maxim S. Shatskih]

Post by Shenan Stanley
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.

Post by Shenan Stanley
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.

[Skybuck Flying]

Apperently windows 7 has strong enforcing rules for drivers.

If a driver is unsigned it won't load.

some say to press F8 and to disable enforcement during boot ?!

I tried this... (in VMware)...

IT DIDN'T WORK.

I didn't get a menu at all... it just happily booted ?!

CRAP.

It's supposed to be my fricking operating system ?!

If I want to mess around with drivers than what's the big deal really ?!

Bye,
Skybuck.

[Shenan Stanley]

Post by Skybuck Flying
Apperently windows 7 has strong enforcing rules for drivers.
If a driver is unsigned it won't load.
some say to press F8 and to disable enforcement during boot ?!
I tried this... (in VMware)...
IT DIDN'T WORK.
I didn't get a menu at all... it just happily booted ?!
CRAP.
It's supposed to be my fricking operating system ?!
If I want to mess around with drivers than what's the big deal
really ?!

Incorrect. You are granted the right to use, within the limits of the
license agreement, said software (Windows.)

It's not your " fricking operating system ", but if you want to write one -
it might be yours then. ;-)

Only one of the cross-posted groups you have chosen is relevant. None of
the ones with "Windows XP" in the title of the newsgroup should be used. I
am cross-posting one last time to them all, but will remove them from future
posts, if I answer again.

There are a couple of places (at this time) you can go with your Windows 7
issues:

Windows 7 Beta Support Forum (technical)
http://social.technet.microsoft.com/Forums/en/category/w7itpro/

Getting Ready for Win7 Forum (less technical)
http://social.answers.microsoft.com/Forums/en-US/GettingReadyforWindows7/threads

Otherwise - you have chosen to be an early adopter of sorts, expect your
growing pains to be more intense than someone who waits even as little time
as when the OS is available in retail stores. ;-)

Here's your best source for help at this time:
http://www.google.com/search?q=%22Windows+7%22+force+unsigned+drivers

[Skybuck Flying]

I am a developer too.

I just want to develop some software for the windows operating system on my
pc ?!

How I am supposed to do that if I don't have any signing tools ?

If I had signing tools then it wouldn't be a problem.

I would even be willing to register at a microsoft website.

So people can always see that it was my software, signed by me ?!

But it must be free tools !

The signing could be linked to my hotmail/live messenger account which I
use.

Ofcourse bad people could make many hotmail bullshit addresses..

But then it's up the user to decide if he believes it's a safe person or a
bad person.

This should give microsoft a little bit more control over "banning" bad
persons from live hotmail stuff.

And thus the good people like me can use the signing future too.

Bye,
Skybuck.

[Skybuck Flying]

Apperently this is a shitty problem with VMware work station 6.5.1.

The F8 key just doesn't work ?!

No solution found yet.

Shitty.

Some say some anti-mac setting but 6.5.1 doesn't have it ?!?

Bye,
Skybuck.

[Skybuck Flying]

Hmm I am starting to see where this motherfucking chkdsk bug might come into
play ?!

Somebody writes: Pause/Break is now used instead of F8 ?!?

I didn't know what the fuck this motherfucker ment... so I pressed a whole
lot of motherfucking keys.

And ofcourse windows completely freaked out.. and the boot menu went crazy.

Not very ape-monkey resistent is it ? ;)

Anyway I am getting bored with all this retarded bs... so I decide to
fucking reset the motherfucking os/vm machine..

Hoping that windows will work just like windows 95 and happily reboot...

and I do press the pause/break key... which apperently on some keyboard is F
lock ?

But anyway... it only says: "repair ?" or "normal ?".

But I did see a disable signing bs the first time...

I guess I now first have to repair the installation before it will give me
the normal/advanced menu.

Now it's doing a repair scan in a gui... it finished and it asks if I want
to do a restore point ?

Pretty crazy why would I want that ? ;)

I don't even know if there was any damgae... probably not.

Restoring might actually create damage/loss of work ?!

Pretty stupid.

Ok I choose cancel.. and it continues "repairing".

Well wasting time again.

Bye,
Skybuck.

Post by Skybuck Flying
Apperently this is a shitty problem with VMware work station 6.5.1.
The F8 key just doesn't work ?!
No solution found yet.
Shitty.
Some say some anti-mac setting but 6.5.1 doesn't have it ?!?
Bye,
Skybuck.

[Skybuck Flying]

I think this repairing is probably bullshit,.

I will fucking reset this motherfucking bitch... and do a normal boot and
then a normal shutdown...

Then it will see that it shutdown properly...

Apperently if it doesn't shutdown normally it triggers this repair bullshit.

Byhe, <- hehe.
Skybuck.

Post by Skybuck Flying
Hmm I am starting to see where this motherfucking chkdsk bug might come
into play ?!
Somebody writes: Pause/Break is now used instead of F8 ?!?
I didn't know what the fuck this motherfucker ment... so I pressed a whole
lot of motherfucking keys.
And ofcourse windows completely freaked out.. and the boot menu went crazy.
Not very ape-monkey resistent is it ? ;)
Anyway I am getting bored with all this retarded bs... so I decide to
fucking reset the motherfucking os/vm machine..
Hoping that windows will work just like windows 95 and happily reboot...
and I do press the pause/break key... which apperently on some keyboard is
F lock ?
But anyway... it only says: "repair ?" or "normal ?".
But I did see a disable signing bs the first time...
I guess I now first have to repair the installation before it will give me
the normal/advanced menu.
Now it's doing a repair scan in a gui... it finished and it asks if I want
to do a restore point ?
Pretty crazy why would I want that ? ;)
I don't even know if there was any damgae... probably not.
Restoring might actually create damage/loss of work ?!
Pretty stupid.
Ok I choose cancel.. and it continues "repairing".
Well wasting time again.
Bye,
Skybuck.

Post by Skybuck Flying
Apperently this is a shitty problem with VMware work station 6.5.1.
The F8 key just doesn't work ?!
No solution found yet.
Shitty.
Some say some anti-mac setting but 6.5.1 doesn't have it ?!?
Bye,
Skybuck.

[Skybuck Flying]

Pretty ridicilous that I first have to do a startup/shutdown cycle before I
get the advanced boot menu ?

Or is there a trick to getting it ?!?

Fortunately the boot/shutdown is fast on vmware...

Bye,
Skybuck.

Post by Skybuck Flying
I think this repairing is probably bullshit,.
I will fucking reset this motherfucking bitch... and do a normal boot and
then a normal shutdown...
Then it will see that it shutdown properly...
Apperently if it doesn't shutdown normally it triggers this repair bullshit.
Byhe, <- hehe.
Skybuck.

Post by Skybuck Flying
Hmm I am starting to see where this motherfucking chkdsk bug might come
into play ?!
Somebody writes: Pause/Break is now used instead of F8 ?!?
I didn't know what the fuck this motherfucker ment... so I pressed a
whole lot of motherfucking keys.
And ofcourse windows completely freaked out.. and the boot menu went crazy.
Not very ape-monkey resistent is it ? ;)
Anyway I am getting bored with all this retarded bs... so I decide to
fucking reset the motherfucking os/vm machine..
Hoping that windows will work just like windows 95 and happily reboot...
and I do press the pause/break key... which apperently on some keyboard
is F lock ?
But anyway... it only says: "repair ?" or "normal ?".
But I did see a disable signing bs the first time...
I guess I now first have to repair the installation before it will give
me the normal/advanced menu.
Now it's doing a repair scan in a gui... it finished and it asks if I
want to do a restore point ?
Pretty crazy why would I want that ? ;)
I don't even know if there was any damgae... probably not.
Restoring might actually create damage/loss of work ?!
Pretty stupid.
Ok I choose cancel.. and it continues "repairing".
Well wasting time again.
Bye,
Skybuck.

Post by Skybuck Flying
Apperently this is a shitty problem with VMware work station 6.5.1.
The F8 key just doesn't work ?!
No solution found yet.
Shitty.
Some say some anti-mac setting but 6.5.1 doesn't have it ?!?
Bye,
Skybuck.

[Skybuck Flying]

Fucking piece of shit is booting up again.

Why can't they simply display a message:

"Press KEY X for boot menu ?!"

BLEH.

Bye,
Skybuck.

[Skybuck Flying]

There is some short/stupid vmware message at the start... I am not sure if
that's for bios or for windows but it says to press escape for some kind of
boot menu,,,, it has bios drive menu and god what..

Gonna try escape again...

Maybe it combination of escape and break.

Bye,
Skybuck.

Post by Skybuck Flying
Fucking piece of shit is booting up again.
"Press KEY X for boot menu ?!"
BLEH.
Bye,
Skybuck.

[Skybuck Flying]

The fucking popups in vmware are very annoying.

Network popups because I disabled their bs vmware connections dont want no
hackers in there ?!

But because of the fucking popups I now can't read the fucking boot
messages.

I tried escape still no luck...

This is getting a bit annoying time wise..

Bye,
Skybuck.

Post by Skybuck Flying
There is some short/stupid vmware message at the start... I am not sure if
that's for bios or for windows but it says to press escape for some kind
of boot menu,,,, it has bios drive menu and god what..
Gonna try escape again...
Maybe it combination of escape and break.
Bye,
Skybuck.

Post by Skybuck Flying
Fucking piece of shit is booting up again.
"Press KEY X for boot menu ?!"
BLEH.
Bye,
Skybuck.

[Skybuck Flying]

Ok I give up windows 7 is just a piece of turd.

I don't give a fuck what happened

I just want a fucking menu during the fucking boot.

What;'s the big fucking deal..

and vmware people are idiots too displaying a boot message for like 1
second...

I can't even read it and the keys not working.

Bye,
Skybuck.

Post by Skybuck Flying
There is some short/stupid vmware message at the start... I am not sure if
that's for bios or for windows but it says to press escape for some kind
of boot menu,,,, it has bios drive menu and god what..
Gonna try escape again...
Maybe it combination of escape and break.
Bye,
Skybuck.

Post by Skybuck Flying
Fucking piece of shit is booting up again.
"Press KEY X for boot menu ?!"
BLEH.
Bye,
Skybuck.

[Skybuck Flying]

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.

[Shenan Stanley]

Post by Skybuck Flying
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."

[Skybuck Flying]

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.

[Skybuck Flying]

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.

[Skybuck Flying]

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.

Post by Skybuck Flying
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.

[Skybuck Flying]

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.

Post by Skybuck Flying
"pop-up/hint messages are evil !".
"Use a nicely integrated status or hint bar... that doesn't get in the way
! ;)"
Bye,
Skybuck.

Post by Skybuck Flying
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.

[Skybuck Flying]

Ok,

As promised now it works.

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

Fucking shit.

Now the network situation looks much better :)

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

Bye,
Skybuck.

[Maxim S. Shatskih]

Post by Skybuck Flying
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.

Post by Skybuck Flying
I tried this... (in VMware)...
IT DIDN'T WORK.

I also tried this. It works always.

[Skybuck Flying]

People,

Even the load screen is screwed/fucked... also vmware freaks out a little
bit with the resolution changes.

The load screen of Windows 7 is fucked:

It doesn't do anything ?!?

It's just black...

No progess indicator..

Only after it's done loading to the balls come together to form what ? Bill
Gates glowing sack ? LOL.

His diamond sack ? :) LOL.

W7 has thoughtless worthless crap written all over it ! ;)

They say this is the RTM which I am running... I can't really believe it...
but if it is... then I will think long and hard before I install windows 7
on any future computer... it will be a while anyway before I will get a new
computer probably...

Something like a few years or so...

So it's still not to late for Microsoft to dump the vista code base, the
windows 7 code base... and go back to windows xp...

At the very least they should "port" the XP gui over to windows 7.

Otherwise there is a 99.999999999999999999999999999999999999999999999999999%
probablity that I will never ever leave XP... :)

I might even be forced to go to something else.

For now they can rip "my" XP from my cold dead fingers ! LOL.

Bye,
Skybuck.