[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
RE:Xy3 with Novell Client 32--was keyboards/accents
- Subject: RE:Xy3 with Novell Client 32--was keyboards/accents
- From: Peter Brown pbrown@xxxxxxxx
- Date: Thu, 23 Mar 2000 08:58:13 -0500
Pam Upton writes:>
> Yes, the computer in question is on a Novell network, and we recently
> upgraded our
> net software, so I'm sure we're running the 32-bit version. Funny thing
> is, we have another person who works in 3+ on a Windows 95 machine (on the
> same network) and has no problems whatsoever. So in a way this probably IS
> connected to Win98 as well as the network software, or the way the two
> work together.
>
We have struggled with this same problem, and I reported it to the
List in mid-1998. I am now 99.9 percent certain it arises when (and only
when) Xy3 and Novell Client 32 reside on the same machine (there's been
some discussion about whether one or another version of Client 32 will lead
to different results, but I don't know that it's been resolved). I kept a
hard copy of the thread from the List: check out postings by Timothy Olson
(Dec. 2, 1998 and Aug. 10, 1998), Stephen Moore (Aug. 10, 1998), A. Fisher
(Nov. 1, 1998) et al.; Greg Reeves and Miriam Kleiger reported the problem
on Dec. 1, 1997. Sorry I don't seem to have saved the e-copies, but I could
fax the hard copies if anyone is desperate and can't get them from the UPenn
server (that may be the case; I think Carl or someone here said someone had
mistakenly dumped some of the older archive files???).
As Timothy Olson noted on 12/2/98, "what happens is that any
keystroke with more than one character or function m nemonic assigned to it
in the keyboard file gets "stuck"...until another keystroke bumps both of
them out." That would explain the accents problem originally reported by Pam
Upton.
Bottom line is: If you can persuade your MIS people to use a 16-bit
client, you can probably continue with Xy3. Xy4, I remember from an earlier
thread on the list, gives no such problem with Client 32.
Peter Brown
pbrown@xxxxxxxx
> On Tue, 21 Mar 2000, tom roche wrote:
>
> > Is this computer on a network? I had the same problem (I think) using
> > XyWrite 3+ on a Novell network. I couldn't type in special characters
> using
> > the numeric keyboard, and some functions calls would be delayed until I
> hit
> > another character. The deltas were delayed as well. My understanding is
> > that the problem was caused by t*he 32-bit networking software, although
> I'm
> > not really sure. Machines with the old software were able to run 3+
> without
> > any problems. I worked around the glitch for a while by hitting cursor
> keys
> > (up, down) whenever there was a delay, and by using a keyboard with a
> lot of
> > special characters mapped to keys. Then I got XyWrite 4, which worked
> fine.
> >
> > -----Original Message-----
>
> > >I have a query from a work colleague who has recently gotten a new
> > >computer and now finds herself plagued by a number of unusual problems
> > >when she tries to type many special characters in XyWrite. Her new
> setup:
> > >
> > >Computer: IBM 300 PL
> > >Keyboard: IBM Model #KB-7953
> > >Operating system: Windows 98
> > >XyWrite version: 3.56 (running in a DOS window off the Win98 desktop)
> > >
> > >The specific problems: (1) she cannot seem to type accents by pressing
> > >Ctrl-Alt (or Alt-Shift) plus the ASCII number--on either the number
> keypad
> > >or the top keyboard row. When she tries, she gets nothing. No weird
> > >characters, no spaces, nothing. As though there was no keyboard input
> at
> > >all. (2) When she tries to get the embedded code delimiters (≪ and ≫)
> on
> > >the command line, a regular Ctrl + < or > doesn't work. She has to
> press
> > >the relevant angle key twice, then hit backspace, and poof! the
> character
> > >pops up. This is, needless to say, annoying. (3) She has to hit F5
> twice
> > >rather than once to put the cursor on the command line. Other problems
> may
> > >surface, but these are the most apparent.
>
>