Nothing to do with the ordinal 201 problem.
New install of MASM32 on to the tester (AMD A10-7850K, Windows 7 Ultimate x64).
Get to the testinst build and it freezes. Look at task manager and polink has stopped.
Can't kill it, restarting the computer hung at shutdown.
Tried just running polink (to get a help screen), same freeze.
Tried on my old install on the main box (i7, Windows 8.1 Pro x64) and the same freeze.
I've never used polink et al, just ml/link.
Two things in common on both boxes, MSE/Defender and Malwarebytes.
Win7: starting from cmd shows cmd using 25% (1 of 4 cores), start another from explorer and another 25%, this time explorer.
Win8.1 seems to load it but not exec - windbg loads then "debugee not connected" but no cpu time.
Strange...Unless anyone else has the same problem I have to assume it's at my end.
Funny, POLINK works perfectly on my win7 64 box and I run the standard Microsoft AV that it upgrades very often so I guess its either your OS settings or AV scanner that does not like it.
> POLINK works perfectly on my win7 64 box
Same for me. There has been an update of Pelles C some months ago, though, and problems with some AVs, see here (http://forum.pellesc.de/index.php?topic=5981.msg21872#msg21872).
The POLINK that I have been using on my Windows7-64 system, which is running MSE, is from a recent installation of Pelles C, and it works fine.
Hi sinsi,
What's the version of Polink.exe on your system?
Hi Vortex, it's from the latest masm32 download, polink 6.50.0.0
edit: poasm does the same, polib and porc work as usual.
Hi sinsi,
Could you try the tools from Pelles C V8 RC6? The command-line tools are dating August 2014.
http://smorgasbordet.com/pellesc/download.htm
Yes, all the latest are working. Guess I have to install masm32 manually...