Wireless network cards and Pro/E license 1

[Guest0527211403]

Hello Everyone

I'm having some problems with my laptop and hopefully someone has run into this before...

I have recently purchased a wireless network card for my laptop to connect to networks at a few different sites. I am also running Pro/E with a node-locked license.

The problem that I am having is that Pro/E is looking to my wireless card for its CPU ID (or MAC address) upon startup. I have a regular network card installed on my machine (and that's what my license is tied to), but Pro/E doesn't see it! It's becoming kind of irritating, because I can't use Pro/E and the internet at the same time.

I don't want to change my license configuration, since I still use my regular NIC card at locations where there is no wireless network available.

This is likely a Windows issue more than a Pro/E issue. Has anyone run into anything like this in the past? If so, was there any way around this?

Thanks
Mark

 

[samoth]

I HAD A SIMILAR PROBLEM HERE AT WORK TOO. THE ONLY DIFFERENCE IS THAT I HAVE TWO NETWORK CARDS INSTALLED, ONE IS ON THE MOTHERBOARD AND THE OTHER IS A GIGABYTE PCI CARD.
I HAD TO EDIT THE MICROSOFT REGISTRY, LOOK AT:
HKEY_LOCAL_MACHINES\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\NetworkCards

YOU SHOULD HAVE TO NUMBERED ENTIRIES, ONE FOR EACH CARD,
PROE USES THE ONE WITH THE LOWEST NUMER. I CHANGED THE NEW GIGABYTE CARD TO 1 AND THE MOTHERBOARD CARD TO 30 (JUST TO MAKE SURE ) AND HENCE I'VE HAD NO MORE PROBLEMS!! BUT LIKE ALWAYS I CAN'T TAKE ANY RESPNSABILITY FOR YOU WHEN YOU EDIT THE REGISTRY )) HOPE IT HELPS!!!

 

[sunthorn]

Try setting up multiple hardware profiles. In Windows, CONTROL PANEL, SYSTEM, HARDWARE, HARDWARE PROFILE. Create a copy of your current windows hardware profile.

Then in one of them remove the wireless card from the hardware list and set it so windows will not detect the PNP device at start up.

The other one have it set with the wireless card.

At boot up windows will them list a menu of which hardware configuration to use. I had to do this with my laptop for pro-e at one time.

Sunthorn Ingersoll

 

[peglor]

I've had a similar problem with ProE and Windows XP.

I had a node locked licence and ProE worked perfectly while the computer was plugged into a network. When the network was unplugged and ProE was started/running ProE shut down giving a licence error.

There's a registry modification here to fix this problem:

http://support.microsoft.com/kb/q239924/

I don't know if this will help you though.