Home› AMX User Forum› NetLinx Studio

NS3 Output Bar Frozen on Windows 7

the8thstthe8thst Posts: 470
in NetLinx Studio
A few days ago I ran into a problem on my desktop computer at home. It is running Win7 Home Premium and NS 3.1.0.374. The output bar at the bottom of Studio (the frame for Status, find in files, file transfer, etc) is frozen and unclickable. I am able to hide/unhide the output bar by using the button in the top toolbar, but not by clicking the "x" on the output bar itself.

Studio is able to print text to the frame when compiling, but I cannot change tabs or click on any errors or warnings that come up while compiling.

I have tried uninstalling NS3 and reinstalling. I have also tried to run NS with administrator privileges, but nothing has fixed it.

The same version of windows and NS3 work perfectly on my laptop, so I know that isn't the problem.

Does anyone have any ideas as to what would have caused this or how to go about fixing it?

I work on my desktop at home when I am really busy because there is nobody to walk into my office with questions, so this is really hurting my productivity.

Thanks.

Comments

  • the8thstthe8thst Posts: 470
    Welll... I guess I'm on my own for this one.
  • DHawthorneDHawthorne Posts: 4,584
    Well, I suppose I ought to hold off upgrading to Win7 if this is a common issue ... anyone else having it? It occurs to me that it sounds like a DLL or OCX conflict, and it's possible another program is causing it, not Win7 itself.
  • the8thstthe8thst Posts: 470
    [Fixed]

    I fixed it by uninstalling NS3. Manually searching and removing all NS3 related keys in the registry. Then reinstalling NS3.

    I am not sure which key had a problem or what corrupted the keys to begin with, but the fix didn't take too long.
  • DHawthorneDHawthorne Posts: 4,584
    It still sounds like a DLL or OCX conflict. Un/re-installing NS just assured that NS was now talking to the correct version of the DLL or OCX. So it is still possible a third-party program overwrote one along the way. Not all installation programs catch versions properly and might replace a new module with an older one. I remeber this as being quite the nightmare when I was coding for Windows ... my stuff was just fine, but there was always someone somewhere dumping an older redistributable on top of something my program needed, and then the tech support e-mails started coming in ....
  • jjamesjjames Posts: 2,908
    Dave, just to let you know: I've been running NS3 on Win7 64 for the better part of the year - no issues whatsoever. It crashes on a VERY rare occasion (I can't even remember the last time it did, it's gotta be over a month or two.)
  • the8thstthe8thst Posts: 470
    I think NS3 on my laptop (Win 7 Ultimate 32bit) has crashed less than 5 times in the last ~14 months, so I would not hold off on upgrading to Win7 because of NS3.

    My issue with NS3 at home is probably just a fluke event that was caused by something else going on with my computer. I had NS3 running on that box with Win7 for about 10 months before this problem cropped up.

    Now that I have cleaned up the registry for NS3 I fully expect it to run without issue from now on.
  • tom goeztom goez Posts: 75
    NS3 Output Bar Frozen on Windows 7

    I run W7 Pro (32) at the shop with no problems whatsoever. Occasionally, there is a delay when sending TP4 files, but it seems to freeze for a short while, then resumes as if nothing happened.

    Make sure your anti-virus program is off when installing AMX programs and use Run as Administrator to launch.

    Someone at AMX named an installation file NSX.EXE, which is the name of an old W32 Trojan virus, so you might have to write an exception in your anti-virus program to get NS3 to install properly. Why they did that? I'll never know.
  • DHawthorneDHawthorne Posts: 4,584
    tom goez wrote: »
    I run W7 Pro (32) at the shop with no problems whatsoever. Occasionally, there is a delay when sending TP4 files, but it seems to freeze for a short while, then resumes as if nothing happened.

    Make sure your anti-virus program is off when installing AMX programs and use Run as Administrator to launch.

    Someone at AMX named an installation file NSX.EXE, which is the name of an old W32 Trojan virus, so you might have to write an exception in your anti-virus program to get NS3 to install properly. Why they did that? I'll never know.

    It's a sorry anti-virus program that goes by name alone.
Sign In or Register to comment.