Looking for suggestions..

OK, I've got Bink 260 X7 version for NT able to open on this test box with WIN-XP latest and critical packs fixed. At this point the POTS version using the executable that was in the \NT subdirectory of the oarchive will run, and will poll via a controller based modem, connect with another of my POTS Bink sites on OS/2 and so on. It will also exit to MAX 3.01 and seems to work there.

But .. the visual screen for the Bink operation has the header up at the top just fine, but a humongous bunch of black space empty lines in the log file display screen until you get way down hundreds of lines later to the bottom of whatever. At that point all the log display is visible. In fact, if you Alt X
and get out of Bink, when it is over, there on the screen will be all those log
lines which were missing from the visual part of the Bink user screen.

I'm not a WIN oriented person. Been OS/2 for years. What am I doing wrong with the BINKLEY.CFG file or the video in the WIN-XP box which is causing this issue?

Thanks..

Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)

Hi Mike,

I'm not a WIN oriented person. Been OS/2 for years.
What am I doing wrong with the BINKLEY.CFG file or the
video in the WIN-XP box which is causing this issue?

You know me, I am not a WIN person either, however are you using any of the MODE commands to set screen width/height? Maybe there is a missmatch with that or possibly the scrollback buffer for that session?

Cheers............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Mike Luther (1:117/3001) wrote to All at 17:25 on 12 Jul 2004:

OK, I've got Bink 260 X7 version for NT able to open on this test
box with WIN-XP latest and critical packs fixed. At this point the
POTS version using the executable that was in the \NT subdirectory
of the oarchive will run, and will poll via a controller based
modem, connect with another of my POTS Bink sites on OS/2 and so
on. It will also exit to MAX 3.01 and seems to work there.

But .. the visual screen for the Bink operation has the header up
at the top just fine, but a humongous bunch of black space empty
lines in the log file display screen until you get way down
hundreds of lines later to the bottom of whatever. At that point
all the log display is visible. In fact, if you Alt X and get out
of Bink, when it is over, there on the screen will be all those log
lines which were missing from the visual part of the Bink user
screen.

I'm not a WIN oriented person. Been OS/2 for years. What am I
doing wrong with the BINKLEY.CFG file or the video in the WIN-XP
box which is causing this issue?

Mike,

Try right clicking on the program bar, the bar with the program name on the left and the three Windows buttons on the right--if you've done that right, you'll see c:\windows\system32\ntvdm.exe. Then click on "Properties" and in "options" set your viewing screen as "window" and in "layout" set Screen buffer
size and Window size at width 80 and height 25.

This should work as I used this to clean up a similar problem I had with Irex's
screen.

Take care,

Steven Horn (stefhorn@yknet.ca)
Moderator, ALASKA_CHAT
--- timEd/386 1.10.y2k+
* Origin: Yukon Mail (northof60.tzo.com), Whitehorse,Canada (1:17/67)

Thanks Steven ..

Mike,

Try right clicking on the program bar, the bar with
the program name on the left and the three Windows
buttons on the right--if you've done that right,
you'll see c:\windows\system32\ntvdm.exe. Then click
on "Properties" and in "options" set your viewing
screen as "window" and in "layout" set Screen buffer
size and Window size at width 80 and height 25.

This should work as I used this to clean up a similar
problem I had with Irex's screen.

Take care,

Steven Horn (stefhorn@yknet.ca)

OK .. I set BT32.EXE up to the WIN/NT version and put the .DLL in the directory. If I use a controller based modem the POTS version of this is now running even without loading WINFOSSIL. If I use COM/IP with no provision for the FOSSIL loaded as part of COM/IP .. and neither is WINFOSSIL here, then this
is running on WIN-XP as well.

In each case doing exactly what you suggest as to playing with the Window size for height and saving that to the shortcut that runs these cleans up the screen
print format deal as far as I can tell. I just got both the POTS and the TELNET version to handle message traffic both ways to the test box.

Took me a heck of a lot longer to download and add the five new critical patch updates that were released today for the WIN world than it did to do all this, chortle. But things are now working at a basic level for me to continue the research.

Thanks again!

And to you too, Peter for your thoughts...

Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)

Mike Luther (1:117/3001) wrote to Steven Horn at 23:02 on 14 Jul 2004:

In each case doing exactly what you suggest as to playing with the
Window size for height and saving that to the shortcut that runs
these cleans up the screen print format deal as far as I can tell.
I just got both the POTS and the TELNET version to handle message
traffic both ways to the test box.

Note that you can increase the window size if you increase the font size.

Took me a heck of a lot longer to download and add the five new
critical patch updates that were released today for the WIN world
than it did to do all this, chortle. But things are now working at
a basic level for me to continue the research.

I had seven patches for Windows 2000. Fortunately I have ADSL.

Thanks again!

De Nada. I'm off on holidays.

Take care,

Steven Horn (stefhorn@yknet.ca)
Moderator, ALASKA_CHAT
--- timEd/386 1.10.y2k+
* Origin: Yukon Mail (northof60.tzo.com), Whitehorse,Canada (1:17/67)