From: "Sammy Mitchell" 
>My first problem was that I was getting out of memory errors when I would
>try to invoke the editor multiple times.  The problem was sporadic.
>Eventually I solved it by changing the initial environment from Auto to
>1536.
I'm not sure what could be going on here.  Note that the editor itself does
not allocate any environment space.  I just checked, and on both of my
machines, I have the initial environment set to auto, and of course, I don't
experience the same problems!
>My next problem was in running one of my games.  I have created a
>demonstration program to analyze the problem.
>The first execution fails to restore the banner page.  The next time fails
>to restore the banner page and to restore 43 line mode.  The next time puts
>line 1 on line 2 and fails to erase line 25.  Then if I change the video
>mode back to 43 lines and try to switch to full screen I get the message
>"This program must be run in a Window, not in a full screen.  Your display
>does not support the screen size currently set by the program."  Then if I
>shell to DOS I can switch to full screen and restore the 43 line editor
>session.  I am able to create other video problems by experimenting with
the
>video commands in this way  but I think that this description is sufficient
>for isolating the problems.
>
>The demonstration program performs correctly under TSE 2.0.  From my
>experience, I recommend not maximizing the editor's Window and
experimenting
>with the restore settings on startup flag for best customization results.
Your macro runs fine here.  I've run it in 55x124 mode, 50x80, 43x80
and 25x80, all with the same results. Note that there are problems with the
win95 console video support.  I'm not sure whether the problems lie in win95
itself, or the drivers for specific video cards.  For instance, my work
machine rarely if ever experiences a glitch in the video output, however, on
my home machine, about one out of 50 executions of the editor, the cursor
disappears when I return back to the console prompt.  Also, sometimes the
screen is not hilighted correctly.
The other programmer here at SemWare runs WinNT, and the video seems to work
flawlessly there.  However, some one else running NT told me that every once
in a while the screen is not restored properly on termination.
Interesting note: The early beta versions of what was to become 2.6 failed
to update the screen properly many times, especially when changing the
number of rows
and columns.  We started inserting delays (sleeps, actually) into the code
just after many console output API calls, and the console output started
working better.  We inserted more delays, and it started working even
better.  Now, when the editor tries to change the number of rows and
columns,
he sleeps for up to 60 milliseconds, waiting for things to "settle".  I
don't know why it works, but it definitely seems to help.
Sammy
---
From: "Kevin A. Carr" 
First of all, I find it odd that you would have the HIMEM/EMM386/DOS=3D =
entries in your config.sys under Win95.  Normal installation of Win95 =
would REM out these lines.  Win95 automatically loads the memory drivers =
and there is no need to do this in config.sys.  This could be causing =
the problems you experience.  Try removing all but the SHELL command =
from your config.sys and see if you get better results.  In fact, I have =
a zero-byte config.sys file on my 95 machine.  I have two lines in my =
autoexec.bat that do a "SET DIRCMD=3D/ogen" and "DOSKEY /insert".  I =
have not had memory problems with any version of TSE.
----------
From:  Chris Shuffett[SMTP:CSHUFFET@providence-hospital.org]
Sent:  Tuesday, January 13, 1998 8:31 AM
To:  tsepro@semware.com
Subject:  TSE 2.8 Bugs
I recently switched PCs and installed TSE v2.80b.  I am running Win 95 =
and my config.sys file reads:
DEVICE=3DC:\WINDOWS\HIMEM.SYS
DEVICE=3DC:\WINDOWS\EMM386.EXE NOEMS
SHELL=3DC:\COMMAND.COM C:\ /P /E:1536
DOS=3DHIGH,UMB
BUFFERS=3D40,0
FILES=3D50
I created a MS-DOS program .pif file in the \TSE32 directory and created =
a shortcut for it in the desktop folder.  I invoke the editor from the =
Office toolbar.  I have set my screen resolution at 800 x 600 pixels.  I =
run in a normal window with both font types.  Initial font size is 5 x =
12 which allows two 80 column editor windows to fit side by side with =
minimal overlap.  Initial size 43 lines, usage window, restore settings =
on startup.
My first problem was that I was getting out of memory errors when I =
would try to invoke the editor multiple times.  The problem was =
sporadic.  Eventually I solved it by changing the initial environment =
from Auto to 1536.
My next problem was in running one of my games.  I have created a =
demonstration program to analyze the problem.
forward
proc banner()
forward
proc graphics_demo()
proc main()
    integer mode =3D Query(CurrVideoMode) // Save the video mode
    banner()
    // Save the banner page
    PopWinOpen(1, 1, Query(ScreenCols), Query(ScreenRows), 1, "", 0)
    if mode  _25_lines_
        Set(CurrVideoMode, _25_lines_)
    endif
    graphics_demo() // Display video demonstration
    if mode  _25_lines_
        Set(CurrVideoMode, mode) // Restore video mode
    endif
    PopWinClose() // Restore banner page
    delay(50)
    UpdateDisplay(_ALL_WINDOWS_REFRESH_) // Redraw the screen
end
proc banner() // Create wallpaper and title box
    integer sub1 =3D 1
           ,last_line =3D Query(ScreenRows)
    while not(sub1 > last_line)
        VGotoXY(1, sub1)
        Putstr(Format("" : 80 : "=A4"))
        sub1 =3D sub1 + 1
    endwhile
    sub1 =3D last_line / 2 - 1
    while not(sub1 > last_line / 2 + 4)
        VGotoXY(25, sub1)
        Putstr(Format("" : 30))
        sub1 =3D sub1 + 1
    endwhile
    VGotoXY(31, last_line / 2 + 1)
    Putstr("TSE 2.8 Video Test")
    delay(50)
end
proc graphics_demo()
    ClrScr() // Show first and last line
    VGotoXY(1, 1)
    Putstr("This is line 1")
    VGotoXY(1, 25)
    Putstr("This is line 25")
    delay(50)
    ClrScr() // All lines should be cleared
    VGotoXY(31, 13)
    Putstr("Screen Cleared")
    delay(50)
end
The first execution fails to restore the banner page.  The next time =
fails to restore the banner page and to restore 43 line mode.  The next =
time puts line 1 on line 2 and fails to erase line 25.  Then if I change =
the video mode back to 43 lines and try to switch to full screen I get =
the message "This program must be run in a Window, not in a full screen. =
 Your display does not support the screen size currently set by the =
program."  Then if I shell to DOS I can switch to full screen and =
restore the 43 line editor session.  I am able to create other video =
problems by experimenting with the video commands in this way  but I =
think that this description is sufficient for isolating the problems.
The demonstration program performs correctly under TSE 2.0.  From my =
experience, I recommend not maximizing the editor's Window and =
---
---------------