[Date Prev][Date Next][Subject Prev][Subject Next][ Date Index][ Subject Index]

Re: XPL failures in current vdos-lfn



Yes, SPEAKER=OFF restores the former execution speed.  Thanks again.



From: Wengier W
To: "xywrite@xxxxxxxx"
Sent: Thursday, May 26, 2016 11:53 AM
Subject: Re: XPL failures in current vdos-lfn

Hi John,

So it is now clear that the error is not specific to vDos-lfn at all. I also want to let you know that the speed is probably caused by the PC-speaker sound support in current vDos-lfn as mentioned in my previous email. Since by default it will beep when the error message is displayed, it will take more time for the error message to stay on the screen. But as I pointed out earlier you can turn off sound support easily by setting "SPEAER=OFF" in config.txt if you want.

Wengiers


On Thursday, May 26, 2016 11:41 AM, John Paines wrote:


Wengier,


You're right!  What happened was, that program runs much more slowly in current vdos-lfn than in vdosxy3, so I saw those error messages (which appear to be false alarms) for the first time.  The replace functions do get performed, despite the error messages.



From: Wengier W
To: "xywrite@xxxxxxxx"
Sent: Thursday, May 26, 2016 11:34 AM
Subject: Re: XPL failures in current vdos-lfn

Hi John,

I have tried to run your 333 file. Yes, I can see the "missing separator" error message, but it happens in vDosXy and original vDos too, not just vDos-lfn. I have tested several times to confirm this, so it is not specific to the current vDos-lfn. The only difference I found is that the current vDos-lfn has sound support through PC speaker, so it will beep when the error message is displayed. On the other hand, it will be silent when the error message is displayed in vDosXy and original vDos. Sound support is a feature of recent vDos-lfn versions, though you can turn it off by setting "SPEAKER=OFF" in config.txt.

Wengier


On Thursday, May 26, 2016 10:49 AM, John Paines wrote:


Wengier, I wanted to isolate the problem.  I've attached a file of 3 global replacement routines -- because these instructions employ xywrite wildcards, I can't just transcribe them here -- which produce the "missing separator" error message.  That error message would normally indicate that a global replacement operation isn't properly formatted.     


Open any document and run the file as a program, and you should see the error.  You'll also see a "not found" error message, but that one is to be expected, since it's unlikely any document you create will have these unique text strings.



From: Wengier Wu
To: xywrite@xxxxxxxx
Sent: Thursday, May 26, 2016 9:40 AM
Subject: Re: XPL failures in current vdos-lfn

At the moment there is not yet a response from John and I am not able to reproduce the problem with my own XPL files. If anyone else is able to reproduce the problem please let me know too. Thanks!

Wengier

On May 25, 2016, at 4:38 PM, Wengier W (Redacted sender "wengierwu" for DMARC) mailto:dmarc-noreply@xxxxxxxx wrote:

Hi John,

Could you please send me the macro you mentioned so that I can test it on my system? Thanks.

Wengier


On Wednesday, May 25, 2016 3:32 PM, John Paines mailto:dmarc-noreply@xxxxxxxx wrote:


Wengier,


I use a xywrite macro (written in xywrite's xpl language) to reformat documents.  That macro encounters errors when running in the current version of vdos-lfn  -- I'm seeing "missing separator" error messages on several global replace operations with which the macro begins, which indicates it's not performing these instructions.


The same macro performs without error in vdosxy3 (and previously, in DOS and Windows XP).  It also performs without error in an April 25th version of vdos-lfn, the only older version of vdos-lfn I have on hand.