
                  Bulletin Boards under OS/2       (Fidonet)

                 Saturday, 27-Nov-1999 to Friday, 03-Dec-1999

+----------------------------------------------------------------------------+

From: Alan Ianson                                       26-Nov-99 13:12:18
  To: Troy-williams                                     28-Nov-99 06:32:23
Subj: Lord IGM's

 AI> * Original Area: MUFFIN
 AI> * Original To  : All (1:153/757)

 T>     HEY YOU ARROGANT DUMBASSWHOLE:

Your trying to flatter me, aren't you.. ;)

 T>             
 T>          Send your cross-posted spam somewhere else!!!!

What spam? Where else? I posted a question about a problem I'm having with
OS/s and some LORD IGM's in the Maximus Support Echo, and the OS/2 BBS help
echo. What's the problem with that.

 Ttyl :-),
         Al

--- Maximus/2 3.01
 * Origin: The Rusty MailBox - Vancouver, B.C. Canada (1:153/757)
201/505
911

+----------------------------------------------------------------------------+

From: Stephen Monteith                                  28-Nov-99 06:02:05
  To: Alan Ianson                                       28-Nov-99 15:26:22
Subj: Lord IGM's

Hello Alan!

Replying to a message of Alan Ianson of 1:153/757 on 1999/11/24, 16:14:19 said 
to All at 1:167/133:

 AI>         I'm having a problem with some LORD IGM's. I'm running
 AI> Maximus/2 3.01 with SIO 1.60D. Lord runs fine, and about 1/2 of my
 AI> IGM's are also fine, but the rest don't seem to work. The user
 AI> see's ***Hold On*** and that's the last thing they see on their
 AI> screen. The IGM does see the carrier I think, since it just sits
 AI> there waiting for input and doesn't say "Carrier Lost" and
 AI> dropping back to lord. Anyone know what's going on here, or what I
 AI> can do to fix it?

What IGMs are you running?  I may be using them and can pass on my settings,
or at least I may have an explaination.  I'm also running Max/2 3.01 and SIO
1.60D.  A sample of your SIO line in the config.sys may help too.

Stephen Monteith

1988 Jeep YJ with 30" tires and RE 4" lift
The Operating System/2 Version is 4.00 Rev. 9.033 
There are 52 Processes with 259 Threads.
This machine's uptime is 1d 23h 58m 36s 328ms.

--- FleetStreet 1.25.1
 * Origin: Juxtaposition BBS, telnet: juxtaposition.dynip.com (1:167/133)

+----------------------------------------------------------------------------+

From: Stephen Monteith                                  28-Nov-99 06:03:26
  To: Alan Ianson                                       28-Nov-99 15:26:22
Subj: Lord IGM's

Hello Alan!

Replying to a message of Alan Ianson of 1:153/757 on 1999/11/26, 13:12:18 said 
to Troy-williams at 1:167/133:

 AI>> * Original Area: MUFFIN
 AI>> * Original To  : All (1:153/757)

 T>>     HEY YOU ARROGANT DUMBASSWHOLE:

 AI> Your trying to flatter me, aren't you.. ;)

If he could only spell Asshole correctly though.  :)

 T>>          Send your cross-posted spam somewhere else!!!!

 AI> What spam? Where else? I posted a question about a problem I'm
 AI> having with OS/s and some LORD IGM's in the Maximus Support Echo,
 AI> and the OS/2 BBS help echo. What's the problem with that.

Some people just don't know what spam is.  Probably didn't get any turkey and
only get Spam instead.. ya that's it.  :)

Stephen Monteith

1988 Jeep YJ with 30" tires and RE 4" lift
The Operating System/2 Version is 4.00 Rev. 9.033 
There are 54 Processes with 256 Threads.
This machine's uptime is 2d 0h 0m 44s 257ms.

--- FleetStreet 1.25.1
 * Origin: Juxtaposition BBS, telnet: juxtaposition.dynip.com (1:167/133)

+----------------------------------------------------------------------------+

From: Francois Massonneau                               27-Nov-99 20:19:24
  To: All                                               29-Nov-99 03:33:21
Subj: nlmaint

Hello !

I'm looking for someone who is using NLMAINT for OS/2 to maintain his nodelist 
/or nodelist segment.
I don't know how to make NLMAINT to accept the new flags like X2C, X2S,

Bye, Francois!


Email: fmas@celtes.com
Web  : http://www.worldnet.net/~island/

---
 * Origin: Island's BBS, a Node in the Atlantic Ocean (2:326/2)
396/1

+----------------------------------------------------------------------------+

From: Peter Knapper                                     29-Nov-99 21:25:29
  To: Francois Massonneau                               29-Nov-99 08:06:00
Subj: nlmaint

Hello Francois,

 FM> I'm looking for someone who is using NLMAINT for OS/2 
 FM> to maintain his nodelist /or nodelist segment.
 FM> I don't know how to make NLMAINT to accept the new flags like X2C, X2S,

Yep, using NLMAINT for a Region segment fine here. One thing you need to be
aware of, is that any FLAGS you wish to ADD into your output segment, must
also be added to the Nodelist generation run by whoever processes YOUR output
segment as input. Also be aware that it is not obvious that the lcoation of
the additional file is critical. I have assumed that you are using a directory 
naming scheme that matches the examples provided with NLMAINT.

You can add the following 2 LINES to your NLMAINT control file as follows
(examples shown for my Region) -
============================================
; Flags       R57flag.Ctl
Uflags      R57Uflag.Ctl
============================================
The first line defines a file that lists the extra flags approved by the
IC/ZCC. In this case there are no extra network wide flags approved so I dont
use this file, it is commented out.

The second line defines a file that lists the extra flags approved by YOUR ZC
for use within YOUR Zone. Please note that in the above case, the file
R57UFLAG.CTL is placed in the MASTER directory along with the NETnnn segments
I use as the basis for my regional run.

And the file R57Uflag.Ctl contains -
============================================
IBN
IFC
ITN
IVM
IP
IMI
ISE
ITX
IUC
IEM
============================================
This adds several Internet based flags to the Region 57 segment I submit to
the Z3C.

I hope this helps...............pk.


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

+----------------------------------------------------------------------------+

From: Jean-Michel Dossogne                              28-Nov-99 08:24:05
  To: All                                               29-Nov-99 11:45:20
Subj: os/2 & pionneer drm1804x

Hello All.


extract of my config.sys :
=====
basedev=7870.add  dated 08/04/99, for the aha2940uw (hd's, cd-rw, jaz)
basedev=aha152x.add /L /V    for the aha1505 (scanner, drm1804x), lun scan
BASEDEV=OS2SCSI.DMD
BASEDEV=OS2CDROM.DMD
IFS=CDFS.IFS
basedev=os2aspi.dmd /all
=====

the aha2940uw works just fine as usual, nothing special to report
the aha1505 reports the 2 lun of the pionneer - yes it has only 2 for 18 cd's! 
- and... nothing further!  under Dos, the Dos pionneer driver attributes a
drive letter to each cd... nothing such here, in Warp 4 (fp10, latest in
french version), I have only 1 drive letter and of course no access to it.
any further idea/tip/proposal/solution (better! :) is most than welcome!

btw, if anyone ever got that cd-changer working under warp on an ibm ps/2 with 
ibm scsi controller, that's also good, I have and use such a pc for homework,
it could go to the bbs if required :)

btw, the Diamond A90 (savage4) works great in 1024x768x16m@75hz on my 17"
screen. Nice to have such great drivers for a quite fast card!

Jean-Michel

--- GoldED 3.00.Beta2+
 # Origin: Doggy's BBS - Philippeville Belgium +3271666292 V34+ (8:7620/1)
 * Origin: The TALKING HUB * Alexandria, VA * (703) 549-5612 (1:109/11)

+----------------------------------------------------------------------------+

From: Rich Wonneberger                                  29-Nov-99 19:46:00
  To: Jean-Michel Dossogne                              30-Nov-99 21:01:14
Subj: os/2 & pionneer drm1804x

*** Quoting Jean-Michel Dossogne to All dated 11-28-99 ***
> basedev=7870.add  dated 08/04/99, for the aha2940uw (hd's, cd-rw, jaz)
> basedev=aha152x.add /L /V    for the aha1505 (scanner, drm1804x), lun 

Try adding /ET to the .add driver lines.
It worked for my 1542b & c cards.
BASEDEV=AHA152X.ADD /L /V /ET

Hope it helps
Rich
I-Net   turtil@frontiernet.net


... Watch out! There's a tagline pirate about!
---
 * Origin: Turtil's Pond BBS. Monroe NY 914-783-2106 (1:2625/50)
120

+----------------------------------------------------------------------------+

From: Francois Massonneau                               01-Dec-99 19:53:10
  To: Peter Knapper                                     03-Dec-99 01:12:01
Subj: nlmaint

Hello Peter!

Replying to a message of Peter Knapper to Francois Massonneau:

 PK> You can add the following 2 LINES to your NLMAINT control file as
 PK> follows (examples shown for my Region) -
 PK> ============================================ ; Flags      
 PK> R57flag.Ctl Uflags      R57Uflag.Ctl
 PK> ============================================ The first line defines a
 PK> file that lists the extra flags approved by the IC/ZCC. In this case
 PK> there are no extra network wide flags approved so I dont use this
 PK> file, it is commented out.

Yes, I knew that, and mine looks like that :
PRIvate Ok
; REDUNdant
FLAGS flags.txt
UFLAGS uflags.txt
COPyright  cpyright.txt
PROlog     prolog.txt
EPIlog     epilog.txt

But the problem is with what I read in the doc file :
------------------------
     are not strictly ``free-form'' and must conform to certain rules. For
     example, a flag cannot commence with the letter 'U' under any conditions
     (this prefix is reserved for the first user flag specified in a nodelist
     entry), the letter 'G' is reserved for gateways, and the letter 'X' is
     reserved for file request capability. Attempting to define flags, or even
     user flags, with these prefixes will cause them to be ignored ('X' is the
     exception, where two-character flags will be allowed for when a new file
     request capability is added).
------------------------

As he said "the letter X is reserved for file request capability,...." how can 
I make NLMAINT to accept the new flags X2C and X2S.
If I add those two flags in the UFLAGS.TXT file, they will be reject, no ??
I saw in the nodelist that those flags are always put _before_ the ",U,"
flags.
So do I have to add them in the UFLAGS.TXT or FLAGS.TXT files ? Or do I have
to ignore those flags in those two files, and let the submitters to send me
their segment with those flags in ??

Bye, Francois!

P.S. I would be interested about what flags I have to put in my FLAGS.TXT and
UFLAGS.TXT files. I guess I made many mistakes, as I put in my flags.txt for
example those flags :
ALLFIX,FID2INT,FIDS,INTIREX,MI,SEAT,V34+  (one per line of course).
and in my UFLAGS.TXT I have :
3COMX2C,3COMX2S,EMA,EVY,FAX,IBN,IFC,IFT,ITN,IVM,IP,IMI,ISE,ITX,IUC,IEM,PN,RDN,S
DN,SDS,TTf,TUF,V90C,V90S,V110H,V110L,Z19,

Thank you in advance.

Email: fmas@celtes.com
Web  : http://www.worldnet.net/~island/

---
 * Origin: Island's BBS, a Node in the Atlantic Ocean (2:326/2)
170/400
260/10

+----------------------------------------------------------------------------+

From: Peter Knapper                                     03-Dec-99 20:32:18
  To: Francois Massonneau                               03-Dec-99 09:11:02
Subj: nlmaint

Hi Francois,

 FM> As he said "the letter X is reserved for file request 
 FM> capability,...." how can I make NLMAINT to accept the 
 FM> new flags X2C and X2S.

You would have to use the FLAGS or UFLAGS files to allow them to be included,
however the person that processes the segment you output must also be
configured to process those flags otherwise your segment will be rejected.

The only flags that YOU can "create" are U flags for the USER defined ones,
however please note that anyone above you in the nodelist generation chain
must also be configured to allow them to be processed. The only valid values
you can include in the non-U section are flags approved by your ZC/the IC.

Note: Flags you define in the UFLAGS file do not need the U prefx in that
file, that is automatically added in front of the FIRST User flag by NLMAINT
when it outputs a new nodelist segment.

 FM> I saw in the nodelist that those flags are always put 
 FM> _before_ the ",U," flags.

That is because they are not USER flags and can only be approved for use by
your ZC, which means that if NLMAINT does not currently allow them to be
included, you need to define them in your FLAGS file.

 FM> P.S. I would be interested about what flags I have to 
 FM> put in my FLAGS.TXT and UFLAGS.TXT files. I guess I 
 FM> made many mistakes, as I put in my flags.txt for example those flags :
 FM> ALLFIX,FID2INT,FIDS,INTIREX,MI,SEAT,V34+  (one per line of course).

This would only work if your ZC had approved the use of these flags and anyone 
in the nodelist generation chain above you had their segment compiler
configured in a similar manner.

 FM> and in my UFLAGS.TXT I have :
 FM> 3COMX2C,3COMX2S,EMA,EVY,FAX,IBN,IFC,IFT,ITN,IVM,IP,IMI,I
 FM> E,ITX,IUC,IEM,PN,RDN,SDN,SDS,TTf,TUF,V90C,V90S,V110H,V110L,Z19,

Similar with these. For example, for Region 57 in Zone 3 I am not using a
FLAGS file, however my UFLAGS file is -
==================================================================
IBN
IFC
ITN
IVM
IP
IMI
ISE
ITX
IUC
IEM
==================================================================
and this seems to work fine.

I hope some of this helps...............pk.


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

+----------------------------------------------------------------------------+

From: Sean Dennis                                       02-Dec-99 16:25:24
  To: Alan Ianson                                       03-Dec-99 13:20:23
Subj: Lord IGM's

Hello, Alan.

-=> Replying to a message of Alan Ianson to All:

 AI>         I'm having a problem with some LORD IGM's. I'm running
 AI> Maximus/2 3.01 with SIO 1.60D. Lord runs fine, and about 1/2 of my
 AI> IGM's are also fine, but the rest don't seem to work. The user see's
 AI> ***Hold On*** and that's the last thing they see on their screen. The
 AI> IGM does see the carrier I think, since it just sits there waiting
 AI> for input and doesn't say "Carrier Lost" and dropping back to lord.
 AI> Anyone know what's going on here, or what I can do to fix it?

Hmmm... I'd assume you have the - parameter set in SIO else you wouldn't be
able to run DOS doors over the com handle... uhm... try running PMLM in a
window while someone's online and using one of the faulty IGMs to see if
everything is truly getting passed to the IGM correctly.  Unfortuatly, I don't 
use IGMs with my LORD setup, so this is kinda like a shot in the dark for me.  
Any other ideas?

Duh-is this on dialup or on a telnet connect?  Are all of your ports locked
and if so, are all the doors and everything locked on the same speed?

Later,
Sean

. o O ( Happy holidays from the staff at AfterHours/2 BBS! )

--- FleetStreet 1.25
 * Origin: It's a different party afterhours. .oO{ AH/2 }Oo. (1:395/610)
170/400
260/10

+----------------------------------------------------------------------------+

+============================================================================+
