From: sinip@hamhq.yfnet.org.yu (SINISA PAVLOVIC)
Reply-To: sinip@hamhq.yfnet.org.yu (SINISA PAVLOVIC)
Organization: HAM HQ BBS, Doboj, RS, 074/24-360

    
From: Jonathan de Boyne Pollard   SP> Since I just came in, would you mind to post filename again, if it
is
JD >  SP> about a program that will set numlock ON for all OS/2 sessions?
JD >
JD > Why can you not set your echo pointers back and read the preceding
message

Well, having in mind part of text that goes after this, you do have short
fuse, don't you? :-)

JD > This isn't Usenet where there is so much "noise" message traffic that all 
b
JD > the very largest sites are forced by the sheer volume to expire
newsgroups
JD > every 2 or 3 days.  In Fidonet, nodes tend to keep messages for weeks, if 
n

In a way, from my point of view, it is Usenet (it IS Fido, obviously).
Actually, I get OS/2 conferences in a way of UUCP/USENET format.

JD > months, before expiring them.  Jack's original message in this thread is
da
JD > a mere 7 days ago and is almost certainly still in your local bossnode's
JD > messagebase.

The problem is, that, being a Sysop of this local BBS, I have asked a
friend in Belgrade to start OS/2 conefernces feed to the BBS, which
started just day before the message about Numlock which I saw appeared.
So, there wasn't a way to anticipate what I'm going to get when it is
about messages, and moreover, no (easy) way to "reset pointers" or do
something like that in UUCP way of exchange between PCBoard and Unix
system.

JD > you link to them -- '&' instead of '+' for some robots -- so that you
don't
JD > into this situation in the first place.  You can also use the standard
%RES
JD > directive.  Send %HELP to your bossnode's area fixing robot for details.)

See above about how the mail goes in and out of this BBS, and you'll see
that none of that is applicable.

Anyhow, nobody opened fire on me like you did since 1995. Though, at that
time it was live ammo. :-))

JD > As for numlock, there are three ways of going about things:
JD >
JD >         1.  If you have a recent OS/2 Warp 4 fixpack, first try the
/NUMON
JD > command-line option to IBMKBD.SYS.

FP9 here, tried, no success.

JD >         2.  If you use JP Software's 4OS2 and Take Command for OS/2
command
JD > interpreters, put
JD >
JD >                 if %_shell% EQ 0 .and. %_ptype% EQ FS keybd /n1
JD >
JD >         in your 4START.BTM, and create a TCOS2 program object in your
deskt
JD > Startup folder that has "/c keybd /n1" in the parameters field.

Somehow, I wouldn't like to switch to 4OS2 just because of Numlock
problem.

JD >         3.  If both of the above do not apply, download one of the many
nat
JD > OS/2 command-line utilities that can change the keyboard lock state, such 
a
JD > for example, KEYLOCKS.EXE from the OS/2 Command Line Utilities version
1.0
JD > (OS2CLU01.ZIP/OS2CLU01.ARJ on any good files site).

I'll try that, thanks.

Regards from Doboj, Republic of Srpska.

---
 * JABBER v1.1 * GODISNOWHERE



--- FIDOGATE 4.3.5
114/477
143/1