[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: Xy under WIN on a laptop, redux {was Re: WinXP/ME}
- Subject: Re: Xy under WIN on a laptop, redux {was Re: WinXP/ME}
- From: Mimi Gauthier LeBien mgnola@xxxxxxxx
- Date: Sun, 28 Oct 2001 17:12:18 -0600
Jordan, if you don't mind letting me know if you end up having success
with this. I am in the same predicament - xy4dos on a Thinkpad with
Windows 2000. This is the first time I am using Win2000 OS. I
am ready to fdisk the whole c: drive and start from scratch. I
wouldn't mind doing this, but I will lose all of the other default
programs that come with the computer - which I wouldn't mind losing
either, but I'm worried about driver issues, etc. Any suggestions
from anyone? Sounds like I'm in pretty bad shape, huh?
--mimi
Mimi Gauthier LeBien
mgnola@xxxxxxxx
"You got to
be a spirit, not a ghost!"
Bullworth
At 01:31 PM 10/28/2001 -0800, you wrote:
Timothy Olson wrote:
I know this has come up several times here, and I will go back through
the message base to research what was said. Last week, I had
occasion to try getting Xy3+ running for someone, under Win-2K
Professional on a Thinkpad. Couldn't get past a strictly **
1/2 ** page display, and
even that with squashed aspect ratio and ugly character display.
O.K., that's the display issue, and I recall some workarounds were
discussed here. (Hope I don't have to track down the UltraVision
utility, assuming it is still available somewhere. I know the
developer used to have a
Forum sub-section on Compuserve.) More distressing than that was
the fact that the keyboard was non-functional, starting with basic cursor
movement. Nothing seemed to move anywhere, even when trying to type
plain alpha characters. The only way to get cursor movement was
via
ALT+arrow key, which did move a space in the indicated direction.
I deactivated just about every line in STARTUP.INT that might have been
relevant, which had no effect. More than likely, using Xy4DOS would
have made no difference. My suspicions are leaning towards some big
KBD file issues. But I didn't have time to troubleshoot it this
trip --
maybe next month when I get back there again. Any suggestions would
be welcome.
Jordan