Shop OBEX P1 Docs P2 Docs Learn Events
Question about Propeller Tool Library — Parallax Forums

Question about Propeller Tool Library

bte2bte2 Posts: 154
edited 2013-04-13 10:54 in Propeller 1
So, I've been at this for a couple years, and I just had something 'happen' that kind of alarmed me.

I have been faithfully backing up my "C:\Program Files(x86)\Parallax Inc\Propeller Tool v1.3.2\Library" directory (into which I have some of my own spin files) (this is the default installation directory).

I assumed that I was backing up current versions until I restored the backup to the netbook for some field work, got to the site, and found that all the versions were old. My files existed on the netbook, but after the first time when I put them there they weren't updated there anymore (as best as I can tell).

It seems that my CURRENT versions are located in "C:\Users\bte2_000\AppData\Local\VirtualStore\Program Files (x86)\Parallax Inc\Propeller Tool v1.3.2\Library", and I have not been including them in my routine backups.

I tried to search the forum, and I did RTFM.

Anybody have any insight as to how this works, or maybe if I can get a little flexibility as to where I can locate my Library? I would LIKE to locate my Library files in another location, but can't seem to figure out exactly how.

Just a heads up to make sure you are actually backing up your important stuff. I was, but not nearly as often as I thought I was. I discovered what was actually happening by searching the entire drive for SPIN files. Everything worked fine on my desktop, it wasn't until I tried to use the files on another computer that I discovered there was a problem.

Thanks in advance.

ETA- Oh yeah- I have Viewport installed (don't use it much yet) - I don't know if that matters.

Comments

  • msrobotsmsrobots Posts: 3,709
    edited 2013-04-13 02:43
    bte2

    you stumbled over a windows security 'feature'.

    since Vista writing into 'System-Directories' is considered a security-thread.

    Program Files(x86) is one of those Directories.

    thus those writes get 'redirected' to the virtual store. And read from there for the same user.

    this has nothing to do with viewport...

    as far as I know you can NOT disable this 'feature' of windows.

    According to Mircrosoft Programs should save their settings and user-files in %APPDATA% not the Install-directory of the program.

    Parallax is not doing that and installs the library in the Program folder. So it does not work (since Vista) to change the content of that folder or even files within.

    Except you run proptool as Administrator (run as) then you can write there.

    I keep all my files for a project together in my project-directory, risking to have multiple copies of my own libraries with sync-problems between them...

    There are some discussions here about multiple libraries and path in the OBJ section. But as far as I know not supported yet.

    Enjoy!

    Mike
  • bte2bte2 Posts: 154
    edited 2015-07-01 22:53
    Thanks for the reply. It seems to me that this one *minimally* requires more prominence in the manual. I'd have been cheesed if I had been backing up my work for 3 years only to find I really wasn't. I actually like Propeller Tool, save for two issues: 1) the lack of an inline "include" directive, and 2) this.

    People spend a lot of time writing code (I just had to take two trips instead of one)(cost me about $100)(thank God I wasn't flying- I'd have been ticked), and I just think that it should be in bold type on the first page. All user file quirks should. Users should remain fully apprised when their hard work is at risk (like when your backups aren't really backups).
  • bte2bte2 Posts: 154
    edited 2013-04-13 03:09
    I'll just uninstall it and reinstall it to the root.

    ETA- So I uninstalled it and reinstalled it to another directory but now the editor pane will not show anything. The Explorer pane displays correctly but when I open a file it is not visible.
  • msrobotsmsrobots Posts: 3,709
    edited 2013-04-13 03:30
    Yes.

    That should work too.

    Never thought about that. Nice solution. Obvious, once spoken out.

    Enjoy!
    Mike
  • bte2bte2 Posts: 154
    edited 2013-04-13 05:42
    I edited out the references in the Registry and it is working now. Make sure if you do this that you have Propeller tool closed first, because it will rewrite the original values when you close it.
  • Mike GMike G Posts: 2,702
    edited 2013-04-13 06:09
    Why not save custom work in a path created on the C drive . This will separate your custom work from the default SPIN library - which is a good thing.
  • bte2bte2 Posts: 154
    edited 2013-04-13 06:48
    I do save my work in other places, but I have objects that I don't want multiple copies of that need to reside in the Library. Wouldn't be a problem if there was an "include" directive. A simple 'include' directive would negate the need to even HAVE a dedicated library. Not real sure why they did it the way they did.

    Besides, this is less about where I save the files and more about the fact that they weren't getting backed up properly, despite me thinking they were.
  • Mike GMike G Posts: 2,702
    edited 2013-04-13 06:55
    I'm with ya. I wish the Prop tool could look in custom folders for custom libraries or handled file paths in the OBJ block. It makes it tough to organize code.
  • bte2bte2 Posts: 154
    edited 2013-04-13 07:52
    It is particularly insidious because I have been managing my Library through the Propeller Tool Explorer controls, and there was no indication that the files in the list were not the ones I was working with. Put another way, there was ZERO indication that anything was amiss until I tried to use a new computer.

    I'm really glad my drive didn't smoke. I think Parallax should at least recommend NOT installing to this directory (assuming there are technical hurdles to overcome in fixing it).

    I'm not dishing on them- it is a great product and a great company, but I find this to be a very serious issue.
  • bte2bte2 Posts: 154
    edited 2013-04-13 08:14
    What I ended up doing is First search the root of your drive for anything *.spin, sort them by date, and get all of your work backed up safely. Then uninstall Propeller Tool (and in my case, Viewport)(make sure you back those up, too). After I was certain that I had my safety copies, I deleted the fake store directory "C:\User\...etc"

    Reinstall Propeller Tool using the 'custom' button, and what I did was just edit "C:\Program Files(x86)\Parallax Inc\Propeller Tool v1.3.2\" to read "C:\My Program Files\Parallax Inc\Propeller Tool v1.3.2\". Do the same with Viewport if you have it.

    At this point, Propeller Tool ran but the editor pane was garbled until I restarted my computer.

    After I restarted my computer, I opened Regedit and searched for "\Program Files(x86)\Parallax Inc\Propeller" and edited all of the library entries (should be 1, might be 2 or 3) as above. I kept my one edit and deleted the other one.

    After I did that Propeller Tool worked properly so I then pasted my files into the library.

    All appears well except now my Viewport don't work- it will not see my Parallax library. I'll try to figure it out later.

    Whatever you do, check the dates on your files before you conclude that you have the right ones.
  • WBA ConsultingWBA Consulting Posts: 2,934
    edited 2013-04-13 09:31
    bte2 wrote: »
    Reinstall Propeller Tool using the 'custom' button, and what I did was just edit "C:\Program Files(x86)\Parallax Inc\Propeller Tool v1.3.2\" to read "C:\My Program Files\Parallax Inc\Propeller Tool v1.3.2\".

    For whatever reason, I have learned to always do a full uninstall of the Propeller Tool before updating or re-installing. There are apparently some registry entries that should be touched during a re-install that are not and quirks show up. I experienced this on XP, Win7 Ultimate, Win7 Enterprise 64Bit.
  • lardomlardom Posts: 1,659
    edited 2013-04-13 10:12
    I use a portable HDD and a "Clickfree" backup drive which does automatic backups and works in the background. It is painful to lose several years of work.
    I also keep my Spin files separate from those in the Prop Tool library.
  • bte2bte2 Posts: 154
    edited 2013-04-13 10:54
    WBA Consulting wrote: »
    For whatever reason, I have learned to always do a full uninstall of the Propeller Tool before updating or re-installing. There are apparently some registry entries that should be touched during a re-install that are not and quirks show up. I experienced this on XP, Win7 Ultimate, Win7 Enterprise 64Bit.

    I just did the netbook, and cleaned the Registry before reinstalling. Uninstalling didn't remove the entries. Worked first time.

    lardom, you ain't kidding. I would love to keep my objects seperate but a) I shouldn't have to have them in their repository in the first place, and b) writing code is hard enough without wrestling with the compiler.

    If a person could merely specify a full path to the desired object, none of this would be an issue.
Sign In or Register to comment.