I've got a new PC and kind of forgot how i installed APN, I copied the following two folders from my old PC and APN launches and edit programs ok but getting script errors.. C:\Python27 C:\vm
Fading memory, do i have install something? maybe i cant just copy and past and need install Python via a setup etc?
The one known casualty in the BitBucket migration termination of Mercurial support (forcing the repositories to be converted to Git) was the accidental loss of the Wiki explaining how to install APN. (I thought it was part of the full download of the repository, but apparently not.) Anyway, it shouldn't be that difficult though. I suspect the main issue is that you need to actually run the Python 2.7 (not 3.x) installation. You may also need to create an environment variable APN pointing to your APN directory (mine points to c:\vm\apn)
Just make sure you didn't activate the "Trust Me" option (in which case it just assumes you didn't make any errors and instead uses the you-asked-for-it-you-got-it method).
Same problem as Steve had and I have had before. New PC, installed Python 2.7, copied APN and set APN env variable. Script errors.
PyPN directory is in APN directory but not shown in extension list and no Scripts.ABS shown in 'keyboard'.
Entering 'python' at the command prompt starts the Python interpretor.
I have downloaded latest APN installer (1.0.29) and tried repair and re-install.
I have also tried running c:\vm\APN\pn.exe --findexts.
None of above adds PyPN or the scripts links.
Any idea how I can add PyPN and the scripts to APN? Do you know what setting stores the fact that they exist?
When I had the problem before, I think that the answer was in the wiki link 'APN Search for Extensions'. However, that link would appear to be one of the ones that has been 'temporarily' mislaid!
Your procedure matches the 'APN Search for Extensions' notes, except that maybe you failed to set up the APN environment variable? In your case it should point to C:\VM\APN
Unfortunately, I do have the APN variable set. It is mentioned on the first line above, but not individually so probably missed.
As something is stopping the extensions from being found/added, I can only presume it is because I have Python 3 and 2 on the system.
However, I had that before and somehow managed to overcome it. Also, it is only Python 2 that is explicitly in the path and the only one that is launched when 'python' is entered in the command prompt or any terminal.
Python 3 is now part of Win 10 but only accesible via the 'py' command, so I am surprised if it is getting in the way, but it is the only obvious place I can think of to cause this problem.
Is there any way of explicitly defining the extensions to add, or is their inclusion stored in a file/setting that is editable?
Sorry, missed that detail. It was early here. While I actually don't yet have any clear idea of what the issue is, it doesn't seem as if it relates to the coexistence of Python 2 and 3, since that is extremely common now (as you say, with Win 10).
I'm not sure how much help this will be but here are a couple possible tips/observations...
1. The list of extensions are stored in the %APN%\settings\config.xml file. (This is primarily what the pn.exe --findexts command does.) Mine contains:
2. I scanned my registry for pypn.dll and there were no hits, suggesting (along with the fact that we are using the "portable" installation model) that it's mainly a matter of the files in the APN directory tree and the contents of the configuration files. There could of course be some issue with Python not working properly, but I don't see anything to suggest that there is a conflict between version 2 and 3.
3. I have confirmed that if I remove pypn.dll from the c:\vm\apn directory and then execute pn.exe --findexts, the PyPN extension disappears from the list (both in the config.xml and in the APN Tools > Options > Extensions). Which further suggests that it's mostly a matter of examining the dll's in that directory to see which ones work as "extensions" (although I haven't figure out just how it determines that). In any case, make sure you have the dlls listed above in the APN directory. FWIW, here's my complete list of DLLs..
Code
C:\vm\APN>dir *.dll
Volume in drive C is Windows
Volume Serial Number is 3853-BEE2
Directory of C:\vm\APN
08/26/2014 11:20 AM 216,576 boost_python-vc100-mt-1_53.dll
08/26/2014 11:20 AM 35,840 ctagsnavigator.dll
08/26/2014 11:20 AM 45,568 CustomScheme.dll
08/26/2014 11:20 AM 719,360 dbghelp.dll
08/26/2014 11:20 AM 140,288 libexpatw.dll
08/26/2014 11:20 AM 421,200 msvcp100.dll
08/26/2014 11:20 AM 770,384 msvcr100.dll
08/26/2014 11:20 AM 245,760 pnlang_1031_de-DE_2.4.0.2378.dll
02/06/2016 02:56 PM 245,248 pnlang_1038_hu-HU_2.4.0.2378.dll
08/26/2014 11:20 AM 247,296 pnlang_1040_it-IT_2.4.0.2378.dll
02/06/2016 02:56 PM 243,712 pnlang_1045_pl-PL_2.4.0.2378.dll
02/06/2016 02:56 PM 246,272 pnlang_1048_ro-RO_2.4.0.2378.dll
02/06/2016 02:56 PM 242,688 pnlang_1049_ru-RU_2.4.0.2378.dll
08/26/2014 11:20 AM 240,640 pnlang_1281_qps-ploc_2.4.0.2378.dll
02/06/2016 02:56 PM 223,744 pnlang_2052_zh-CN_2.4.0.2378.dll
08/26/2014 11:20 AM 247,296 pnlang_3082_es-ES_2.4.0.2378.dll
08/26/2014 11:20 AM 50,176 pnse.dll
08/26/2014 11:20 AM 401,920 pypn.dll
08/26/2014 11:20 AM 1,477,120 SciLexer.dll
I was hoping the config.xml lines might have been the answer, but again, unfortunately not. I have the same config.xml and all the same dlls except a few of the country ones, which I don't think will be the issue.
Having uninstalled Python 3 and re-installed APN with no change, I agree that it may not be anything to do with the Python version. This might imply that it is something a little simpler that I am missing. The problem occurs even if I try to go to the start of the page with 'Ctrl-Home'.
In the hope that it can give a clue to the problem, I get the error and a dialog box with a yellow triangle exclamation mark warning icon, as attached image.
Maybe the file and line number can provide suffcient info for you to determine the problem: Unexpected error in file: ScriptRegistry.cpp, line: 239, version: 2.4.0.14. No ScriptRunner for this script type!
I have uninstalled APN and removed the APN directory. I have also removed the PN entries from the registry, but when running the installation again it finds an existing installation. This implies there is another setting somewhere. Maybe if it is not being re-created, it might also not be being updated and perhaps this is the cause. Although, probably, I am just clutching at straws.
OK, solved. It is not just Python 2.x that APN requires, but it also needs the 32 bit version. I had installed the 64 bit version and something in that version is missing or incompatible.
Aha! That little detail needs to be highlighted somewhere! Thanks for figuring it out!
As an aside, the error message, while helpfully identifying its location, isn't that helpful since it doesn't identify the script that can't be run. But since all the APN scripts are Python, it's fairly obvious that the issue is the failure to identify the PyPN extension, which as you discovered was hung up on the 32 vs 64 bit issue.
Also, on the issue of the installer knowing about the previous installation, I misspoke when I said that APN wasn't really relying much on the Registry for locations of components. But the APN installer tool (SetupBuilder) automatically establishes a pair of GUIDs for each package and saves that in the Registry, one for Uninstall and one for the "Upgrade" installation option. That option doesn't really do anything different than the new install, other than use the prior location. The GUIDs are {235CEE70-F452-11E3-6784-0E73108F188BE} and {235CEE70-F452-11E3-3D6C-0E73108F4AE1} and will be found under HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall. But again, that's only information about the installer, not about APN or PN itself.
