TZUTC: 0200
CHRS: CP850 2
MSGID: 2:301/123 609f1193
REPLY: 2:240/77 609e501d

   Hello Kai!

14 May 21 12:20, you wrote to me:

 FS>> I'll probably end up using something similar. Thinking of
 FS>> publishing GoldEd as a Terminal Services remote app. Even on Mac,
 FS>> I could then just run the program via RDP, no need to connect to
 FS>> the whole desktop.
 KR> Interesting approach.

It's the "Windows style" of doing things. I've just moved my whole fido setup
to a new drive on my Windows terminal server, now everything is under f:/fido.
And I'm typing this on my Mac, but in GoldEd+/W64, published as a single
window via RDP. The client needed to connect is Microsoft's own "Microsoft
Remote Desktop" which is natively available on Mac.

 FS>> show stopper. This didn't happen before, but now I get this when
 FS>> I try to get out of an Area on GoldEd running remotely on my Mac:
 FS>> *****
 FS>>         Wait: /Volumes/bbs/msgbase/region30 is locked
 FS>> *****
 FS>> Not sure what that is all about?

 KR> I'm not sure if that's a filesystem message or a msgbase issue. Do you
 KR> have r/w access to the files? Does the username match? Some sharing
 KR> tools offer a usermap feature that tells the server that the remote
 KR> "mac" username is equal to the local "windows" username.

Yes, the names match, and I do have full access with my user. It's quite
strange, I also initally had this when using terminal services with the
"RemoteApp" version of GoldEd. Seems to be working now, though.

 KR> The msgbases are not multi access approved. If a tosser is active the
 KR> area should be locked to prevent the editor to mess up the tossing
 KR> run. I would look for other running sessions. How does the terminal
 KR> service remote app from above work? A service is running in background
 KR> all the time?

There shouldn't have been any other running sessions, at least I'm not aware
of any. Very curious, indeed. And I've had GoldEd open in the past few days on
my node system while new mail came in and the tosser (Fmail) went to work. So
you're suggesting I should prevent that from being possible by using semaphore
flags?

 KR> If all fails the last option would be a point installation on the mac
 KR> that connects to the node on windows via mailer.

Yes, also an option. But I'll try some more with this (terminal server
RemoteApp etc.) approach. "How hard can it be", as Mr Clarkson uses to say...
;-)


Regards
Fermin


... Other Taglines will follow...Keep only the ones you want...
--- GoldED+/W64-MSVC 1.1.5-b20180707
 * Origin: USS Ferminator - Unteraegeri, Switzerland (2:301/123)
SEEN-BY: 1/123 18/200 30/0 90/1 105/81 120/340 123/131 129/305 221/1
SEEN-BY: 221/6 226/30 227/114 229/101 424 426 452 664 700 1016 1017
SEEN-BY: 240/1120 5832 249/206 317 400 280/464 282/1038 292/854 301/0
SEEN-BY: 301/1 101 103 113 123 812 317/3 322/757 342/200 633/280 5058/104
PATH: 301/123 1 229/426