Options
NS2 crashes with Axcess
Spannertech
Posts: 53
Had a nasty shock today revisiting a very old Axcess job. It was originally created as a NS1.2 .pjs file, which NS2.4 can import and make into a .apw. I found that NS2.4 crashed every time it tried to compile this old axccess program. When I got home I found the same program compiles fine on my desktop machine. Then I compared versions:
Laptop (where problem occurs): Access compiler version 2.0.0.148
Desktop (works): Access compiler version 2.0.0.143
first of all, how did that happen? Both are Netlinx 2.4 installs.
But it gets better. I keep NS1.2 on both machines too. If you move only the .pjs, .axs and .axi, to a new directory it hangs when trying to compile. It seems to need the old .tok file before it will even do a compile. How could that be? Anyone shed some light on this kind of weirdness? The whole .pjs or .apw thing - my understanding is that it's really just a container for the files. The compiler is just looking at the .axs and any .axi's that you might have referenced, correct?
Thanks
OP
Laptop (where problem occurs): Access compiler version 2.0.0.148
Desktop (works): Access compiler version 2.0.0.143
first of all, how did that happen? Both are Netlinx 2.4 installs.
But it gets better. I keep NS1.2 on both machines too. If you move only the .pjs, .axs and .axi, to a new directory it hangs when trying to compile. It seems to need the old .tok file before it will even do a compile. How could that be? Anyone shed some light on this kind of weirdness? The whole .pjs or .apw thing - my understanding is that it's really just a container for the files. The compiler is just looking at the .axs and any .axi's that you might have referenced, correct?
Thanks
OP
0
Comments
So, maybe you installed from slightly different builds or something. But at least, it looks like someone may have already been semi-aware of some of the issues you're facing here.
I still don't see why you are crashing though, unless that older version simply won't run with the latest Studio (which doesn't seem quite right, it should).
Project files are, as you say, just a wrapper to make sure all your dependencies are in place. There is no reason you can't compile a single code block independent of the project. However, they do store path data, so moving them will break all the path information if it isn't updated (I think the paths are relative, so if the folder structure is identical, it should work, but I am not 100% certain of that). I have often deleted .tok files, so I know it doesn't depend on them. It is probably a path error. When moving projects, it works best to export them, then open the exported project in the new place.