Robert,
Thank you very much for your message. You're right: I have always a
solution for my problems. Anyhow, this is the whole story.
First, I discovered an error in my .bat file (editor /e4000 ansiup.int):
the comma was missing. But, after correcting the error (editor/e4000
,ansiup.int), if I run VA/NV $KB, the active keyboard when I start the
program is still Xy4.KBD instead of XY4ANSI.KBD (the specified one in my
ansiup.int). If I erase startup.int and continue attempting to load
ansiup.int, I receive an error message: startup.int not found. Solution:
to include a line in my .bat file, copying ansiup.int as startup.int
before running editor.exe. Then, ANSI keyboard, printer files, etc. were
loaded. Apparently, XyWrite refuses to load an alternate startup file
against the information included in the Manual (pages 2-33 and 2-34).
If, with the right files loaded, I shell to DOS, CHCP 1252 is not enough
to get an ANSI display in full screen mode (and after running CHCP 1252
in DOS session, 1252 code page is the active one, without any doubt).
Default XyWrite codepage is 850 after and before shelling to DOS. If I
suppress DF LA=850 or replace it with DF LA=437, I receive the following
message: "Customization file contains an unrecognized command" (I think
this is related to my U2 file, that requires 850 codepage). If I use a
minimalist startup.int (or even if I erase startup.int) for debugging
purposes, I don't get an ansi screen (with chcp 1252 before or after
running editor, via dos/nv, etc.). If I like to have an ANSI screen in
full screen mode, it's always necessary to use the VGA FONT CP1252.FNT
command. In windowed mode, CHCP works perfectly, together with the
Siebert's ANSI font or lucida console fonts (not with bitmap windows fonts).
Anyhow, after using VGA FONT CP1252.FNT (or, in windowed mode, with
Lucida console), I have a perfect ANSI display and I can manage and
produce ANSI files. As you know, I have been writing in XyWrite and
publishing in Ventura 5 for a very long time. The main purpose of my use
of ANSI XyWrite is to use Ventura 8 for desktop publishing and my first
tests are very positive (Ventura 8 "export on save" feature doesn't work
anymore with XyWrite format). Now I can edit ANSI files in XyWrite and
to have them again in Ventura 8 when I reopen the publication. Happy end.
Anyhow, it would be very useful for debugging purposes to have your ANSI
XyWrite configuration files (I am using the ones you sent me several
months ago in Manuel.zip). Maybe CHCP 1252 doesn't work as you have
stated because of my Spanish W2000 version. I don't know.
Best regards,
Manuel Castelao