on Fri, 29 Aug 2003
14:01:08 PDT7
> I'd like to know why if anyone can give you an answer.
Well your examples worked. Mine did not. The answer is the type of file
system on the vdisk. All of your examples had file names 8 characters or less.
What I did was use a four characters followed by 5 '?' which generates a 9
character file name which is invalid on a FAT drive. I don't know whether to
call it a bug or a feature but I did expect the SysTempFileName to return a
file name not null. If it had returned a file name the subsequent file open
would have had an open error which would have pointed out the problem.
=====================================================
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".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 29 |
August |
2003 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
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.
