Path: csiph.com!aioe.org!BHGTVyTGRwF2ntnqLVfpDg.user.46.165.242.75.POSTED!not-for-mail
From: "R.Wieser" <address@not.available>
Newsgroups: microsoft.public.scripting.vbscript
Subject: Re: System wide memory-only storage?
Date: Tue, 8 Feb 2022 20:31:07 +0100
Organization: Aioe.org NNTP Server
Lines: 22
Message-ID: <stuhlt$6if$1@gioia.aioe.org>
References: <1mfe1tm8sv3bn.1od9m321kpijg$.dlg@40tude.net>
Injection-Info: gioia.aioe.org; logging-data="6735"; posting-host="BHGTVyTGRwF2ntnqLVfpDg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-Priority: 3
X-Notice: Filtered by postfilter v. 0.9.2
Xref: csiph.com microsoft.public.scripting.vbscript:12404

JJ,

> Anyone know any system wide memory-only storage? To serve as a media
> for communication between scripts.

Ha!  My chance to return a favour. :-)

You could take a look at

https://docs.microsoft.com/en-us/windows/win32/memory/creating-named-shared-memory

Ofcourse, it would need a small program (an invisible service one ?) to 
create and keep it alive.  By putting it into the "startup" folder its ready 
for use whenever someone logs on.

By the way: have you also thought about using a named pipe ?  Might even be 
easier to manage (no handshaking).

Regards,
Rudy Wieser