Subj : Files on LAN.
To   : Gerald Miller
From : mark lewis
Date : Fri Jul 09 2004 11:45 pm

 GM>>> G:\AE04F89B.000 appears to be a randomly generated file
 GM>>> name....  Every time I try to run the FrontDoor BTM (when
 GM>>> SHARE is loaded via config.sys), the BTM halts and the file
 GM>>> name is always different.  It is almost as if SHARE doesn't
 GM>>> agree with / like the 4DOS TEE command. ???

 ML>> nah, i think that Dan Egli hit the nail on the head and that it is
 ML>> 4DOS' swapfile...

 GM> === Cut Begin: 4DOS.INI ===
 GM> Environment=1536
 GM> EnvFree=128
 GM> Swapping=EMS, XMS, g:\
 GM>   ;I will change the above line to the following...
 GM> ;     Swapping=EMS, XMS, None

i only have XMS in this line...

 GM>   ;I have the following line commented out.  What is your
 GM> recommendation?
 GM> ; SwapReopen=YES
 GM>   ;[NO] Reopen swap file if it is closed; Set to `Yes' to
 GM> enable reopening
 GM>   ;of the 4DOS swap file if it is closed by another program
 GM> (Novell Netware
 GM>   ;drives). If an application or network generates
 GM> reproducible errors
 GM>   ;related to the 4DOS swap file (for example "Swap file seek
 GM> failed" or
 GM>   ;similar errors).

never seen the swapreopen but after reading the text, i can understand why it 
may be needed... should not be needed unless you are swapping to a network 
drive that may "disappear" on you...

 GM> UniqueSwapName=YES
 GM>   ;I will change the above line to the following...

this one should be yes... well, at least that's what i have... possibly not 
needed if one isn't swapping to disk...

 GM> ;     UniqueSwapName=NO
 GM> [Secondary]
 GM>   ;Set secondaries shell directives
 GM> Swapping=XMS, EMS, None
 GM> === Cut End:   4DOS.INI ===

i don't have a secondary section in my ini file...

 [ ...snip... ]

 ML>> i feel that that's not the problem... i'm more inclined to look to
 ML>> your 4DOS ini file and see the swapping settings in there as well as
 ML>> what uniqueswapname is set to...

 GM> I made the modifications to the 4DOS.INI file, and I will put

 GM>     Install=C:\Dos\SHARE.EXE /f:4096 /l:25

 GM> back in the config.sys file, reboot and see how FrontDoor does
 GM> with these changes.

ok...

 GM> But, if SHARE is not really needed for WfW 3.11 (because it is
 GM> loading "device=vshare.386"), then, what's the point in putting
 GM> SHARE in the config file?  To see if my FrontDoor BTM file hangs
 GM> the system, again?

for one thing, yes... note also that some things require share capabilities... 
the JAM message bases required it at one point... not sure how that was taken 
care of... its been so long but i likely still have the messages concerning it 
in the beta area(s)... i mention JAM only because FD supports it in FM and i 
don't know if you use it or not...

also note that that vshare stuff is only in effect /while/ running windows...

 GM>>> Do you know if SHARE will handle pipes (as in "|")?

 ML>> yes, it has not problems with them at all... as long as
 ML>> they are not open in a restricted mode ;)

 GM> I can't see that echoing a command to the screen _AND_
 GM> piping it to a log file would be a restricted mode...
 GM> Why would jpsoft do that when they know that some clients
 GM> would use SHARE?

who knows... its likely not being done so don't worry about it ;)

)\/(ark

 
* Origin: (1:3634/12)

.