G
gus
Guest
when the executables are on a network drive, the code in them must be loaded over the network when the program is paged into the clinet machine's memory. depending on the network and the load on it, this may be noticeably slow at times. on a good network, with clients with sufficient memory, it may be perfectly fine. > On Oct 13, 2015, at 8:00 AM, Nigel Kneale wrote: > > Update from Progress Community [https://community.progress.com/] > > Nigel Kneale [https://community.progress.com/members/njk] > > Is there any reason why, instead of installing prowin32.exe through netsetup on to each desktop client, that each desktop could not simply map a network drive to prowin32.exe on the server? > > So in this setup prowin32.exe runs on the client desktop but resides on the server; the runtime files reside on the server, but run on the desktop client; the temporary files reside on the desktop client etc. > > View online [https://community.progress.com/community_groups/openedge_general/f/26/t/20726] > > You received this notification because you subscribed to the forum. To stop receiving updates from only this thread, go here [https://community.progress.com/community_groups/openedge_general/f/26/t/20726/mute]. > > Flag [https://community.progress.com/community_groups/openedge_general/f/26/t/20726?AbuseContentId=ac014b62-db09-4d95-a6ea-122f1a6156a7&AbuseContentTypeId=46448885-d0e6-4133-bbfb-f0cd7b0fd6f7&AbuseFlag=true] this post as spam/abuse.
Continue reading...
Continue reading...