On 11/28/2014 9:23 AM, Klaus Hartnegg wrote:> > Is there anything else that I could try, > or do I just have to stay on protocol NT1 > as long as we still use this old software? > > KlausTry in [global] acl allow execute always=true -- Regards -------------------------------------- Gerald Drouillard Technology Architect Drouillard & Associates, Inc. http://www.Drouillard.biz
On 01.12.2014 13:52, Gerald Drouillard wrote:> On 11/28/2014 9:23 AM, Klaus Hartnegg wrote: >> >> Is there anything else that I could try, >> or do I just have to stay on protocol NT1 >> as long as we still use this old software? >> > Try in [global] > acl allow execute always=trueThis issue would affect all clients, and usually all software that is being run from the server. But here only some old 16 bit programs are affected, not even all 16 bit programs. And they work fine on the few remaining WinXP machines, they only refuse to start in Win7. All clients have execute permission on all exe files. This must be some strange protocol incompatibility. Klaus
On 12/2/2014 11:04 AM, Klaus Hartnegg wrote:> On 01.12.2014 13:52, Gerald Drouillard wrote: >> On 11/28/2014 9:23 AM, Klaus Hartnegg wrote: >>> >>> Is there anything else that I could try, >>> or do I just have to stay on protocol NT1 >>> as long as we still use this old software? >>> >> Try in [global] >> acl allow execute always=true > > This issue would affect all clients, and usually all software that is > being run from the server. > > But here only some old 16 bit programs are affected, not even all 16 > bit programs. And they work fine on the few remaining WinXP machines, > they only refuse to start in Win7. > > All clients have execute permission on all exe files. This must be > some strange protocol incompatibility. > > KlausDid you try the "fix" I described above? I also had execute permissions on the files, but it didn't work. -- Regards -------------------------------------- Gerald Drouillard Technology Architect Drouillard & Associates, Inc. http://www.Drouillard.biz