[Date Prev][Date Next][Subject Prev][Subject Next][
Re: No more XP lag with Tamedos
- Subject: Re: No more XP lag with Tamedos
- From: "Robert Holmgren" holmgren@xxxxxxxx
- Date: Sun, 26 Dec 2004 21:33:38 -0500
** Reply to message from Michael Norman on Sun, 26 Dec
2004 13:50:55 -0500
> Changed this to EG=0, forcing a 25-line
> configuration, which I want, and this allowed me to eliminate the sl=26
> default from startup.int.
Why would you want SL=26 -- if you want 25-line screen (22 lines of text)? If
you want a 28-line screen (25 lines of text), you'd use SL=28. But not SL=26.
> I ... added *df dr=c:\xy* for lack of something better.
DR is the directory where overflow files are created. It is VERY important!
And you've got a bad spec there; it should be "DF DR=C:\XY\" with a terminal
Maybe Tame is interacting with some other problems; but you have a lot of
errors strewn in these files -- who knows how many more; and I'm using Tame
v4.5D, and I don't see _any_ of these anomalies. I come up in window 1, no
Numlock, no double cursor (I'm still not sure what "double cursor" means --
cannot visualize it). Tame is working very effectively, & cursor does NOT
crawl at all. Indeed, cursor goes so fast I had to scale back on MODE CON rate
spec (which was 31, which is tops).
When you say you come up in Window 2, where is the DIR display that you created
-- Window 1 or Window 2? If you want to solve this, you have to work backward
in STARTUP, and insert an at the beginning of lines, and work your way
upward in the file. Keep relaunching XyWrite, until it comes to rest in window
1. Then move down one line and confirm that yes, that one line causes it
to start in window 2. That's how you get to the bottom of these kinds of
behaviors... It's the same debugging procedure I outlined the other day, only
in reverse. Although... you might start by simply renaming STARTUP.INT, so
that it doesn't load. With zero configuration, which window do you come up in?
If window 2, then you maybe can point the finger at Tame (although doesn't
happen to me). If window 1, then the problem is created further down in
STARTUP, and not by Tame. These are very simple diagnostic procedures... The
goal here is to isoate the one line, and then the one instruction, that causes
the window toggle.