| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | File sharing problem with JAM |
[ 20 Jul 07 09:48, Michiel van der Vlist wrote to Michael Kleefeld ]
MK>> SHAREMODE (yes)
MV> Wonder what is meant by mode#.
Possibly these:
Open Access
open_access_ReadOnly = $0000; { ---- ---- ---- -000 }
open_access_WriteOnly = $0001; { ---- ---- ---- -001 }
open_access_ReadWrite = $0002; { ---- ---- ---- -010 }
Open share rights
open_share_DenyReadWrite = $0010; { ---- ---- -001 ---- }
open_share_DenyWrite = $0020; { ---- ---- -010 ---- }
open_share_DenyRead = $0030; { ---- ---- -011 ---- }
open_share_DenyNone = $0040; { ---- ---- -100 ---- }
The default is
FileMode := open_access_ReadWrite OR open_share_DenyNone; // $42
I don't remember if these are the same modes that apply to region/record
locking as they do to (whole) file locking - one program using file locking
will always conflict with another using record locking.
-- Scott Little [fidonet#3:712/848 / sysgod{at}sysgod.org]
--- GoldED+/W32-MINGW 1.1.5-b20070503
* Origin: Cyberia: Come get some. (3:712/848)SEEN-BY: 261/38 633/104 260 262 267 285 712/0 256 313 848 800/432 @PATH: 712/848 633/260 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.