[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: Xy III & Faulty Memory?--original thread!
- Subject: Re: Xy III & Faulty Memory?--original thread!
- From: "..." yesss@xxxxxxxx
- Date: Sun, 1 Nov 1998 14:55:20 -0500 (EST)
≪ Another problem we have is caused by Win95 running
32bit Netware (it took two months to figure that one out).
Keyboard commands such as F5 have to be hit twice before
they'll execute. ≫ --Brian
≪ any keystroke with more than one character or function
mnemonic assigned to it in the keyboard file gets "stuck"
(at least in terms of display, probably also in terms of
processing) until another keystroke bumps both of them out.
[...] (theoretically, one could rewrite the "offending"
keyboard assignments into programs, replace their keyboard
file code with & and $ save/get function calls, then
load the programs individually onto those save/gets
in startup.int.[)...] ≫ --Timothy
I don't think so. If it could be done at all, one or two
&ldpms would probably fix all keys--
63=&ABC or
67=XC&Z or
68=&ACC&Z
--but if what stalls the system is a three-byte construct,
that would only exacerbate the prob by adding more. Even
if you wrote a different &ldpm for each func, you'd just
substitute one system-stalling three-byte construct for
another:
63=&B
67=&X
68=&C
Presumably NO and NI have failed as introductory funcs.
A few things besides big files simply have no internal
xyW3 workaround. Frustration at v3's inability to resolve
destructive ascii 26s drove me to write and integrate
into !xyWise a supplementary .EXE that generates xpl
code. 32bit Netware too may defeat xyW3. It's causing
three installations noted on the xylist (your two plus
the Kansas City Star) kbd headaches; how many other
businesses? A patch may be all that's needed. Or has
Novell already fixed the glitch? What of Stephen Moore's
≪ I suspect that your problem might be due to a
specific conflict between XyIII and the particular
revision of Client 32 you're using. (Have your MIS
people gotten the latest rev off the Novell website?) ≫ ?
When a business runs on xpl, porting a lot of xyW3
code to xyW4-nee-Signature is no casual consideration.
Till Novell delivers, double-striking FKeys may seem
preferable to that months-long, undocumented,
trial-and-error undertaking. ... Ciao. --a
======================================== adpFisher nyc
http://www.escape.com/%7Eyesss/_xypro.html ============================