SCOUG-Programming Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 28 Aug 2003 18:51:58 PDT7
From:	Sheridan George <s-geo@usa.net >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: REXX SysTempFileName function

Content Type: text/plain

The problem could be long file names. One of the reasons I went to
RamDisk from vdisk was the format system. vdisk seems to be FAT and
does not accept long file names. RamDisk does accept long names plus it
will resize itself where vdisk won't.

Sheridan

PS One not so good thing about RamDisk is its refusal to accept a read
only file.

blairra@tstonramp.com wrote:

>I just ran a program that uses SysTempFileName to assign file names for work
>files. It works properly if the work files are on a real disk but fails if
>they are on a vdisk. SysTempFileName returns a null if the target disk is a
>vdisk.
>
>I am using eCS v1.0, don't know if that makes a difference or not.
>
>Anyone know if it should work on a vdisk? I expected it to.
>
>=====================================================
>
>To unsubscribe from this list, send an email message
>to "steward@scoug.com". In the body of the message,
>put the command "unsubscribe scoug-programming".
>
>For problems, contact the list owner at
>"rollin@scoug.com".
>
>=====================================================
>
>
>
>
>
>
>

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 28 | August | 2003 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.