Msg: Re: vdosplus "set" command anomalies?

Hi John,

I just returned home and tried this, but I have not able to reproduced this. Actually during vDosPlus's development I used the /SET option myself quite often, but until now I have yet to seen this problem. Perhaps it is related to some other Windows application or setting(s) on your system?

Wengier

From: "John Paines" (Redacted sender "vf200" for DMARC)
To: "xywrite@xxxxxxxx"
Date: Tue, 21 Feb 2017 16:43:04 +0000 (UTC)

Wengier,

I tried running the "vdosplus set" command from Windows. The same anomaly
previously reported -- the displayed text turned from black to white italics --
occurred. I did note other issues related to xpl execution or keyboard macros
with vdos sessions initiated with the set command, but didn't explore at the
time....

In any event, not really an impediment....

On Tuesday, February 21, 2017 11:50 AM, Wengier Wu wrote:

Hi John,

The SETCFG command is for setting *non-port* config options. Please use instead the SETPORT command for setting COMx/LPTx (x=1..9) ports. Its syntax is equivalent to the SETCFG command, except that it will change the port options like LPT1 as you mentioned:

SETPORT LPT1="PDFtoPrinter.exe" #LPT1.PDF

Please note that there are only 4 config options (out of 60+ config options) not supported by the SETCFG/SETPORT commands: CONFWARN, COLORS, LOW and XMEM. The COLORS config option can be changed by the separate SETCOLOR command, so in fact there are only 3 config options not supported by the "SET" commands. Hope this helps.

Wengier

On Feb 21, 2017, at 11:27 AM, John Paines (Redacted sender "vf200" for DMARC) mailto:dmarc-noreply@xxxxxxxx wrote:

Wengier,

It's my understanding that some commands, such as "LPT1 =", can't be set with SETCFG. So, for example, if in the course of work you wanted to send PCL print jobs to an actual printer instead of the screen, "vdosplus /set "LPT1 = "PDFtoPrinter.exe" #LPT1.PDF" allows you do so without editing the config.txt file or exiting vdos and running the command at launch.

Anyway, that's my rationale for running the "set" command inside an existing vdos session, but it sounds like this use was not what you intended.

From: Wengier Wu mailto:dmarc-noreply@xxxxxxxx
To: xywrite@xxxxxxxx
Sent: Tuesday, February 21, 2017 11:05 AM
Subject: Re: vdosplus "set" command anomalies?

Hi John,

You meant that you commanded "vDosPlus /set ..." inside an existing vDosPlus window? I am not quite sure why you want to do this. The "/set" option is for initializing the settings when you launch vDosPlus from Windows, and if vDosPlus is already running you can change the setting of the current vDosPlus session using the SETCFG command (rather than using "vDosPlus /set ..."). Hope this helps.

Wengier

On Feb 21, 2017, at 10:23 AM, John Paines (Redacted sender "vf200" for DMARC) mailto:dmarc-noreply@xxxxxxxx wrote:

Wengier,

When the "set" command is executed, another vdos window opens -- and it's in that window where the change initiated by the set command takes effect. So now there are two versions of vdos running.

I assume this is normal behavior(?) Thanks.

From: Wengier Wu mailto:dmarc-noreply@xxxxxxxx
To: xywrite@xxxxxxxx
Sent: Tuesday, February 21, 2017 10:08 AM
Subject: Re: vdosplus "set" command anomalies?

Hi John,

May I ask what is the "new vdos(plus?) window" you are referring to? Thanks.

Wengier

On Feb 20, 2017, at 4:14 PM, John Paines (Redacted sender "vf200" for DMARC) mailto:dmarc-noreply@xxxxxxxx wrote:

The vdosplus "set" command, for example

Vdosplus /set LPT1 = "PDFtoPrinter.exe" #LPT1.PDF

or

Vdosplus /set font = consola

leads to a variety of odd xy3 behaviors in the new vdos window which the command opens.

The example in front of me is a simple xy3 macro which loads an HP printer driver. Perform it in the primary vdos window and it works as expected. Invoke it in the window loaded after the "set" command above, and it turns normally displayed black text into white italic text.

Not a pressing matter, but anyone else?