Syncdocs

IT can be coded in as custom code.

as Gord pointed out above. Problem I am having is that the online installer is not working I doe snot seem to even try to download the file. I have done a few other online installers but none that had to extract an exe file. I checked with the 7zip and basically just appear to be able to open it with extract and move the files to location needed, just can not get grasp on why it is not working. feel free to take a look see. Once I can get the installer.ini working I can do a custom job to run the vault cleaner on exit.

I haven't chosen a Licence to release this under, so:
Please Do NOT Reply To This Post Until I Have Edited It To State Which Licence I Have Chosen! (see here)

I'm unsure if you even still need this, and I haven't actually tested to be certain it works, so let me know if it's wrong somewhere, but here's my solution to your Credential Remaining After Exit issue:

In the beginning of your Custom.nsh you'll need to !include the CredDelete.nsh file (Contents Included Here), then when you want to delete the credentials from Windows' Credential Manager call it in the following manner (where CRED_TYPE is the Type of Credential it is, possibilities are under "Type" on This Page; TARGET_NAME is the name of the Credential to Delete; and ERROR_CONTAINER is a Variable which is contain)

${CredDelete} CRED_TYPE TARGET_NAME ERROR_CONTAINER

Contents of the CredDelete.nsh

; CredDelete 1.0
;
; Deletes a Credential from Windows' Credential Manager, after which ERROR_CONTAINER will contain "SUCCESS" if successful, or an Error Status Code if unsuccessful.
; Copyright 2012 3D1T0R
; Based in part on works Copyrighted 2008-2012 John T Haller of PortableApps.com
; Released under The ... Licence
;
; CredDelete Usage: ${CredDelete} CRED_TYPE TARGET_NAME ERROR_CONTAINER
;
; History:
; 1.0 (2012-03-13): 3D1T0R

!macro CredDelete CRED_TYPE TARGET_NAME ERROR_CONTAINER
  ; Make some working space
  Push $0
  Push $1
  Push $2

  ; Get our Parameters
  StrCpy $0 "${TARGET_NAME}"
  StrCpy $1 "${CRED_TYPE}"

    ; Delete the Credential
    System::Call 'Advapi32.dll::CredDelete(t r0, i r1, i 0) i.r2 ? e'

  ; If it didn't work, find out what the error is, If it did, return "SUCCESS"
  ${If} $2 = 0
    Pop $2
  ${ElseIf} $2 = 1
    Pop $0 ; Just to get rid of it.
    StrCpy $2 "SUCCESS"
  ${EndIf}
  StrCpy "${ERROR_CONTAINER}" $2

  ; Return our working space to previous state
  Pop $2
  Pop $1
  Pop $0
!macroend

!define CredDelete '!insertmacro "CredDelete"'

Re: Licence
I don't know what Licence to release this under, so if somebody (who knows what they're talking about) could recommend one I'd be grateful.
In the mean-time:
Please Do NOT Reply To This Post Until I Have Edited It To State Which Licence I Have Chosen!

P.S. Sorry it took so long to get this to you.

But somehow I discovered/accidentally found/got real lucky/was just dumb luck away to actually have it not write to credential manager at all, between saving the actual file and managing some reg keys it works, get written to manager while program is running, then goes away upon clean up and closure. Fixed this:Now just nee to figure why I can not manage a desktop icon which is no more than a shortcut to a folder. Very odd, tried to even do a custom.nsh to delete it but either my code is all wrong or I can not get it done. Shortcut name is My Google Docs with no extension. Stupid me I was dealing with a folder not a file

I hope I did this right, I responded to my post not your?

I don't have any Credentials in my Credential Manager, so I'd be interested to know if that CredDelete code works for you, even if you don't find it necessary, plus I don't know for sure, but I think changing the Files & Registry Entries directly could cause problems, so I'd personally recommend using the systems Microsoft put in place for doing what you want instead.

Also, if it'll help I could extend code to wrap other Credential Management functions as well, I just put it out with CredDelete only 'cause some of the other functions were a little more complicated.

& Regarding Legality of this project, I don't know what would happen if it got taken to court of course, but I think the parts of the Terms of Service and Conditions of Use that say ‘You may not modify the Doc Freedom Software or use it in any way not expressly authorised by these Terms and Conditions of Use. ... You may not authorise or assist any third party to do any of the foregoing.’ are pretty clear that you need express authorisation from DocFreedom even to tell people what would be necessary to use “the Doc Freedom Software” with a PortableApps.com Launcher, let alone to package one up minus the software and say ‘Just download [InsertFileNameHere] extract [InsertFileNamesHere], put them in [InsertDirectoryNameHere], then run it via [InsertLauncherFileNameHere]’

& on a side note: @Pyromaniac:
The section VF2NSR quoted said "Doc Freedom Software", not "Doc Freedom Products" (or "Doc Freedom Products or Services")

“Doc Freedom Products and Services - Terms of Service and Conditions of Use”
1. Definition of Terms (d) "Doc Freedom Software" (whether or not capitalised) means software provided to you or for your use by Doc Freedom.

I think that the "Doc Freedom Products" are the programs you can download through sycdocs--not the app itself.

While you can't distribute, and perhaps not create an online installer, I think you can post a [Launcher Only] version and tell the user to download syncdocs manually and extract it to the App folder. After all, the users are still to the site manually, and voluntarily by themselves, and manually and voluntarily downloading syncdocs by themselves without your direct intervention.

I highly doubt anyone would persecute you for telling the users how to do it themselves, but creating an online installer may be moving to a grey area.

And if you do release it, make sure their icon isn't trademarked or anything either.