(Following folder is hidden) Windows\inf\netnwlnk.inf Windows\inf\netnwlnk.pnf
to C:\Temp, and to corresponding Vista folders.
2) Control Panel->Network Center->Manage network connections. Right-click your LAN connection and select Properties.
Click Install. select Protocol and click Add.
The NWLink IPX/SPX/NetBIOS protocol may be listed on the Network Protocol list. DO NOT SELECT IT.
Click Have Disk. Browse to C:\Temp. Select netnwlnk.inf. Click OK. Select NWLink IPX/SPX/NetBIOS from the list. Vista will tell you that the publisher could not be verified. Click Install.
If all goes well, the protocol should be now installed. Restart computer.
В общем проделал я всё это, и. пишет: «Не удалось добавить запрошенную возможность. Ошибка: не найден указанный модуль»
Вопрос: есть какой-нить способ подружить их, а то винду влом переустанавливать?
The following forum(s) have migrated to Microsoft Q&A: All English Windows 7 IT Pro forums! Visit Microsoft Q&A to post new questions.
Answered by:
Question
Answers
There is no native IPX/SPX support from Microsoft starting with Windows Vista and Windows Server 2003 x64 (see here and here). You will need to contact Novell for any IPX/SPX support needs:
http://www.novell.com/home/index.html Ned Pyle [MSFT] — MS Enterprise Platforms Support — Beta Team
All replies
There is a «solution» that is posted on a few places for Vista. Be aware though, that the solution first only works on 32-bit, and that the «solution» probably don’t even work. (It’s more of a hack than a clean install.) There are a few obvious things, like the properties button on IPX protocol is grayed out (meaning you can’t change frame type), and you can’t bind IPX to the client of Windows Networking protocol.
Don’t see this as a serious solution, more as a desperate try to get it working, until the protocol is officially added to protocol list.
What you need: a working installation of Windows XP sp2 (according to instructions).
Step 1. Ctrate a new folder c:\temp
Step 2. Copy the following files to the directory c:\temp *and* to the corrsponding vista directories: Note: You might need to open up an «elevated» command prompt, «run as administrator», (to get write access to directories).
Step 3. Go to «manage network connection» (in control panel-> network). Right click your LAN adapter connection, click «install», «protocol», «Add», Do not select the IPX that is already in the list, be sure to select «have disk». Navigate to «c:\temp» and select file «netnwlnk.inf», now select «WLink IPX/SPX/NetBIOS». You will get a warning it’s not verifyable, install anyway (or not..).
If you get an error message about a missing module, you forgot to copy the above files to the windows 7 directories.
Step 4. Reboot computer.
Now you will have the IPX protocol in installed protocol list (if everything works as it should), but it will probably not work.
The following website may also be helpful.
There is no native IPX/SPX support from Microsoft starting with Windows Vista and Windows Server 2003 x64 (see here and here). You will need to contact Novell for any IPX/SPX support needs:
http://www.novell.com/home/index.html Ned Pyle [MSFT] — MS Enterprise Platforms Support — Beta Team
You are a big help Ned. Typical holier than though techie response. I wonder why everyone hates IT support staff? Could it be because they (Tech Support) can’t see past their own needs/likes?
Pretty sure I can’t run my legacy game on a Novel OS.
I used to use IPX/SPX because I don’t like to have my production machines exposed to the Internet any more than absolutely necessary. With IPX, I could run a local area net and keep TCP/Internet turned off completely on all but one machine. Now, I feel very exposed to all the potential garbage that the Internet can bring.
I also note that Windows 7 is slow to find other machines. Seems it is searching the whole world where IPX was, virtually instant access and no big searching lag. More risk and slower response, oh yeah, that’s a good marketing plan — just cover it up with some bad art work so you can look more Mac-like. Someone please fire who ever made these decisions.
Killing off legacy essentials in Windows7 and Vista is almost as bad as taking old OS maintenance tools that have been in the same place for many years, renaming them and hiding them under lame artwork all over the place. Why its so much fun to go on an Easter Egg hunt when you have real work to do.
There are a lot of things I like about Windows 7, but they are mostly performance related due to changes in processors and graphics cards. The organization and window dressing is pure BS. As the old maxim of good design goes: Form follows function. Someone at MS seems to have suffered Mac envy and was more interested in window dressing than functionality.
Moving old utilities around and renaming them annoys me every day. Who ever did that should be looking for a new job. Taking out the old «horizontal span» that every stereoscopic program on earth needed and replacing it with something that is not compatible is a sign of ignorance, arrogance or bad marketing (or some combination of the foregoing).
