Standalone issue with Windows network file server

[Ken Ray]

On Tue, 1 May 2007 07:49:32 -0400, Paul Gries wrote:

> On 30 Apr 2007, at 11:59 PM, Ken Ray wrote:
> 
>> On Mon, 30 Apr 2007 15:14:22 -0400, Paul Gries wrote:
>> 
>>> On 30 Apr 2007, at 3:02 PM, Ken Ray wrote:
>>> 
>>>> On Mon, 30 Apr 2007 13:30:44 -0400, Paul Gries wrote:
>>>> 
>>>>> Hi all,
>>>>> 
>>> That is a standalone saving a data stack.  (I used the splash-screen
>>> approach to building the standalone, using Rev. version 2.7.4.291, in
>>> case it matters.)  There is the standalone splash screen stack, the
>>> primary stack ("BlueMain", with a Save button), and three substacks
>>> of BlueMain.  Saving either BlueMain or one of the substacks causes
>>> the freeze.
>> 
>> Is the standalone running from the network as well, or is it running on
>> a local machine?
> 
> It's running from the network as well.  I make the standalone and 
> then copy the folder named "Windows" to the network drive.

A long time ago I had issues related to UNC pathnames that Rev was 
unable to resolve which caused problems in accessing files on network 
servers. It's possible that when saving, Rev is getting the "filename" 
property of the stack and trying to write the data back to that 
location. One thing to check would be to put in some debug code that 
did "put the fileName of stack 'BlueMain'" and see what it is. If the 
network drive isn't mapped, perhaps mapping it to a drive letter and 
then setting the filename of the stack to a path that includes the 
drive letter will help.

Ken Ray
Sons of Thunder Software, Inc.
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/