Anonymous_User Absent Member.
Absent Member.
1748 views

iFolder in Program Files

It appears that iFolder 3.2.x does not permit the creation of an iFolder in C:\Program Files\* on the Windows platform.

Is there a reason for this restriction? Is there a way to override this restriction?

I know it could raise locked file/corrupt DLL etc.. issues to sync actively used executables, but many utilities default to this share and do not redirect data work dirs to My Documents yet. It would be a huge help if there were a way around this.

Any ideas?
Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

iFolder in Program Files

> It appears that iFolder 3.2.x does not permit the creation of an iFolder
in C:\Program Files\* on the Windows platform.
>
> Is there a reason for this restriction? Is there a way to override this

restriction?
>
> I know it could raise locked file/corrupt DLL etc.. issues to sync

actively used executables, but many utilities default to this share and do
not redirect data work dirs to My Documents yet. It would be a huge help
if there were a way around this.
>
> Any ideas?


Sorry for the duplicate post. It appears GroupWise stopped working with
NNTP and I didn't realize the first submission had gotten through.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder in Program Files

Ryan,

You are correct in assuming that this is done to prevent locked
files/corruption etc... Currently the only way around this is to edit
the source and build your own client. This also prevents one from
creating an ifolder on a mapped drive for the same reasons.

Victor


RDKath@roushind.com wrote:
>>It appears that iFolder 3.2.x does not permit the creation of an iFolder

>
> in C:\Program Files\* on the Windows platform.
>
>>Is there a reason for this restriction? Is there a way to override this

>
> restriction?
>
>>I know it could raise locked file/corrupt DLL etc.. issues to sync

>
> actively used executables, but many utilities default to this share and do
> not redirect data work dirs to My Documents yet. It would be a huge help
> if there were a way around this.
>
>>Any ideas?

>
>
> Sorry for the duplicate post. It appears GroupWise stopped working with
> NNTP and I didn't realize the first submission had gotten through.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder in Program Files

Victor,

Thanks for the response. It appears that custom compiling cilents for this may be too much work. I will push foward advising users they may not do this. It is less work to compile the Linux clients, but WIndows and Mac OSX may be quite difficult.

Ryan

>>> Victor Billings<vbillings@novell.com> 02/21/06 04:41PM >>>

Ryan,

You are correct in assuming that this is done to prevent locked
files/corruption etc... Currently the only way around this is to edit
the source and build your own client. This also prevents one from
creating an ifolder on a mapped drive for the same reasons.

Victor


RDKath@roushind.com wrote:
>>It appears that iFolder 3.2.x does not permit the creation of an iFolder

>
> in C:\Program Files\* on the Windows platform.
>
>>Is there a reason for this restriction? Is there a way to override this

>
> restriction?
>
>>I know it could raise locked file/corrupt DLL etc.. issues to sync

>
> actively used executables, but many utilities default to this share and do
> not redirect data work dirs to My Documents yet. It would be a huge help
> if there were a way around this.
>
>>Any ideas?

>
>
> Sorry for the duplicate post. It appears GroupWise stopped working with
> NNTP and I didn't realize the first submission had gotten through.



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.