Re: XYWRITE digest 1388

[Patricia M Godfrey pmgodfrey@xxxxxxxx]

Jordan: Does your OS have anything akin to Windows' Control
Panel-->Resources listing? Because if this kind of thing were happening
in Win, I'd suspect a wrong driver causing a memory "conflict" for some
board. I use the quotes, because what usually happens is that the card
and the PCI or AGP slot are using the same memory--of course, because the
one is in the other, and they together constitute one subsystem--but
without the exact, correct driver (not a generic one for "cards using the
XYZ chipset), Windows thinks they're living in sin or something and
reports a conflict. Some techs say that since it's just a phantom
conflict (it doesn't always even cause a yellow question mark), it
doesn't matter, but I've found that apps that date back to DOS days (and
probably make calls direct to memory) will get confused by this setup and
crash.
	About XyWrite being a "Windows" application or not: The yo-yos at
Lexmark have short memories, and apparently have forgotten that there
once was something called Windows 3.x (AKA 16-bit Windows). Now it is
true that that was not a "real" OS, but rather an environment sitting
atop the OS, which was DOS in all its incarnations. XyWin is a real
(though atypical) 16-bit Win app; it is not a Windows 9.x (32-bit
Windows) app. But by their criteria, all 16-bit Win apps are simply "DOS
apps modified for Windows," and only 32-bit Win apps are "real" Windows
apps. It's a legitimate distinction, but a confusing way to use the
terminology.
Patricia