Paul wrote:
Stan Brown wrote:
On Sat, 14 Apr 2018 20:55:34 -0400, Paul wrote:
OK, I'll take a long-shot on this, and tell you to use
the Compatibility interface to an EXE and change the
runtime compatibility to some older OS. There's an example
of the dialog around 40% of the way down this page.
Thanks for replying, Paul. It _was_ a long shot. I said to myself,
"self, if the program works okay in Windows 8 why would it need a
compatibility setting for Windows 7? But Paul's smart guy, so it's
worth trying."
Unfortunately, when I set the program to be compatible with Vista (XP
wasn't available), exactly the same thing happened as before. Thanks
anyway, for trying.
If the source is available, you could work on it.
When the program makes a call, there's got to be
a returned status code somewhere that indicates
the program is not happy.
Paul
ftp://ftp.vim.org/pub/vim/pc/vim72src.zip
hardcopy.c ???
It seems to have the ability to deliver error messages.
EMSG(_("E673: Incompatible multi-byte encoding and character set."));
********** message.txt on FTP site **********
-- older versions --
8953966 gvim72.exe V7.2 complete self-installing package
7194365 vim72rt.zip V7.2 runtime files
1399386 vim72lang.zip V7.2 language files
980100 gvim72.zip V7.2 GUI bin for Windows 95/NT and later
1051406 gvim72ole.zip V7.2 GUI bin with OLE and VisVim
949997 gvim72_s.zip V7.2 GUI bin for Windows 3.1 with Win32s
879774 vim72w32.zip V7.2 bin Windows NT/XP console
969187 vim72d32.zip V7.2 bin 32 bit MS-DOS prot. mode
2460134 vim72src.zip V7.2 sources packed for MS-DOS
1844224 gvim72.pdb debugging info for gvim72ole.zip
3279872 gvim72ole.pdb debugging info for gvim72w32.zip
2780160 vim72w32.pdb debugging info for gvim72.zip
There is no 16 bit binary for Vim 7.2 and later
********** message.txt on FTP site **********
If you can't see the error messages while in gvim72,
maybe you could try the console version ?
If VIM doesn't throw an error message, that means the printing
subsystem gave an "OK" status to VIM, then the printing
or spooler portion of Windows burped. Check your print spooler
status, for evidence of burping.
Paul