Path: csiph.com!aioe.org!BHGTVyTGRwF2ntnqLVfpDg.user.46.165.242.75.POSTED!not-for-mail From: "R.Wieser" Newsgroups: microsoft.public.scripting.vbscript Subject: Re: System wide memory-only storage? Date: Wed, 9 Feb 2022 13:05:49 +0100 Organization: Aioe.org NNTP Server Lines: 22 Message-ID: References: <1mfe1tm8sv3bn.1od9m321kpijg$.dlg@40tude.net> <1hm50ti2564b5$.1rkccix2jdsx8$.dlg@40tude.net> Injection-Info: gioia.aioe.org; logging-data="64353"; posting-host="BHGTVyTGRwF2ntnqLVfpDg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org"; X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-MSMail-Priority: Normal X-Notice: Filtered by postfilter v. 0.9.2 X-Priority: 3 Xref: csiph.com microsoft.public.scripting.vbscript:12407 JJ, > Sorry, but I need to use/borrow existing built in Windows > applications' functionality. Not creating a custom application. Than I think you're out of luck. Although a (vb)script can access a named pipe or a mailslot* when one exists, it doesn't seem to be able to create one themselves. *which nowerdays is normally disabled on ones 'puter. A question though : why the "memory-only" requirement ? Without it you could just use one (or two in case of handshaking). A quick search for IPC returned this one : https://stackoverflow.com/questions/10943464/inter-process-communication-using-vbscript Regards, Rudy Wieser