home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Beijing Paradise BBS Backup
/
PARADISE.ISO
/
software
/
BBSDOORW
/
NODELIST.286
< prev
next >
Wrap
Text File
|
1976-11-24
|
19KB
|
391 lines
;A Zone Nodelist for Friday, October 13, 1995 -- Day number 286 : 06108
;A
;S A listing of all the systems within Region 65 of Fidonet
;S
;A Copyright 1995, Fidonet Region 65, by Roy Luo --- All rights reserved.
;S
;S Specific authority is hereby granted to Fidonet Coordinators to process
;S this list in any manner necessary to its inclusion in the Fidonet Nodelist,
;S provided only that it continues to be protected by a compilation copyright
;S in all composite lists.
;S
;S
;A
;
Zone,6,ASIA,JAPAN,Kazuyoshi_Shinada,81-3-3355-4395,9600,XA,CM,V32B,V42B,ZYX
;
Region,65,Fido_Mainland_China,Beijing,Roy_Luo,86-10-251-5423,9600,CM,V32B,V42B,VFC,V34
;
Host,650,Beijing_Net,Beijing,Jerry_Meng,86-10-427-3892,9600,MO,V32B,V42B,VFC,V34
,1,Beijing_Great_Wall_BBS,Beijing,Roy_Luo,86-10-251-5423,9600,CM,V32B,V42B,VFC,V34
Pvt,101,USR_Support_CHN,Beijing,Roy_Luo,-Unpublished-,9600,MO,V32B,V42B
Pvt,102,Sunspot_Computer_Club,Beijing,Sam_King,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
Pvt,103,Flying-Fish,Jining,Eel_Smile,-Unpublished-,9600,MO,V32B,V42B
Pvt,108,City_Folk,Beijing,Simon_Peng,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
Hold,4,Beijing_Ham_Radio_BBS,Beijing,Jerry_Meng,86-10-427-3892,9600,CM,V32B,V42B,VFC,V34
Hub,14,Easy_Express,Beijing,Jimmy_Zhao,86-10-601-6728,9600,V32B,V42B,VFC,V34,CM
Pvt,143,POINT_3,Beijing,Blacker_Sun,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
Pvt,1497,POINT_97,Beijing,Gao_Bo,-Unpublished-,9600,MO,V32B
Pvt,18,China_Primitive_Men,Beijing,Aaron_Zhang,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
,19,Aquarius_&_Mel,Beijing,Chen_Chun,86-10-218-5699,9600,CM,V32b,V42b,VFC,V34
Pvt,1901,POINT_1,Beijing,Chen_Chun,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
Pvt,1902,POINT_2,Beijing,Daniel_Lei,-Unpublished-,9600,MO,V32B
Pvt,1903,POINT_3,Beijing,Yin_Long,-Unpublished-,9600,MO,V42B,V32B
Pvt,1904,POINT_4,Beijing,Gang_Moming,-Unpublished-,9600,MO,V42B,V32B
Pvt,1905,POINT_5,Beijing,Dave_Xie,-Unpublished-,9600,MO,V42B,V32B
Pvt,1906,POINT_6,Beijing,Zhang_Fenghu,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
Pvt,1907,POINT_7,Beijing,Ren_Jianhua,-Unpublished-,9600,MO,V32B
Pvt,1908,POINT_8,Beijing,Jerry_Meng,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
Pvt,404,Bubble_Dragon's_Ship,Beijing,Wang_Gang,-Unpublished-,9600,MO,V32B
Pvt,405,Zenith_Star,Beijing,Daniel_Zhang,-Unpublished-,9600,MO,V42B,V32B,VFC,V34
Pvt,418,Dr._Windows'_Labs,Beijing,Peter_Fang,-Unpublished-,9600,MO,V32B,V42B,VFC,V34
;
Host,653,EastChina_Net,Nanjing,Minghao_Bao,86-25-341-3254,9600,CM,XA,V32B,V42B
,21,Longmen_Town_BBS,Jinan,Zou_Xiaodong,86-531-696-4282,9600,CM,XA,V34,V32B,V42B
,1000,JoyRide_BBS,Nanjing,Feng_Ni,86-25-322-5921,9600,XA,V32B,V42B,V34
Pvt,501,POINT_1,Nanjing,Feng_Ni,-Unpublished-,9600,MO,V42B
Pvt,502,Star_War,Nanjing,John_Yuan,-Unpublished-,2400,MO,V42B
Pvt,507,POINT_7,GuanNan,Pan_Jianmin,-Unpublished-,9600,MO,V42B
,1001,1001_NIGHTS_BBS,Nanjing,Minghao_Bao,86-25-341-3254,9600,CM,XA,V32B,V42B
Pvt,602,ADEN_BBS,Nanjing,Kennethe,-Unpublished-,2400,MO,V42B
,1008,DreamYouth,Nanjing,MaoRong_Chen,86-25-341-5915,9600,MO,V42B
;
Host,655,SouthChina_Net,Shenzhen,Chen_Hai-qing,86-755-542-3139,9600,CM,XA,V32B,H16,V32T,VFC,V34
Hub,1,SHENZHEN-HUB,SHENZHEN,Chen_Hai-qing,86-755-542-3139,9600,CM,XA,V32B,HST,V32T,VFC,V34
Pvt,2,SZ-Doctor_Bear,Shenzhen,Chen_Haiqing,-Unpublished-,9600,MO,XA,V32B,V42B
,3,Electron,Shenzhen,Zhou_Gao-xiang,86-755-227-2211,9600,MO,XA,V32B,V42B
,5,New-moon_BBS,Guangzhou,Andy_Yuan,86-20-3847074,9600,CM,XA,V32B,V34
Pvt,100,Echomail_N655,Shenzhen,Pony_Ma,-Unpublished-,9600,MO,XA,V32B,VFC,V34
,101,Pony_soft_BBS,Shenzhen,Pony_Ma,86-755-559-9961,9600,CM,XA,V32B,V32T,V42B
,102,Data-Fast_BBS,Shenzhen,Chen_Hai-qing,86-755-542-3139,9600,CM,XA,V32B,HST,V32T,VFC,V34
,201,PC_User_Group_BBS,Shanto_Guangdong,Huang_Yaohao,86-754-846-9169,9600,CM,XA,V.32B,V.34
;
Host,656,SouthwestChina_Net,Chengdu,Rene_Ren,86-28-554-5031,9600,CM,V32b,V42b,XA
,1,CDWM_BBS,Chengdu,Rene_Ren,86-28-554-5031,9600,CM,V32B,V42B,XA
,2,MegaStar,Chengdu,Rene_Ren,86-28-774-5862,9600,MO,V32B
,3,New_World,Chengdu,Li_H.y,86-28-662-4093,9600,CM,V32B,XA
,4,New_humanity,Chengdu,Vide_Chen,86-28-521-1376,9600,CM,V32B
,5,Devir_BBS,Chengdu,Yang_Gang,86-28-555-5830,9600,MO,V32B
;S
;S
;S The following flags define special operating conditions:
;S
;S Flag Meaning
;S
;S CM Node accepts mail 24 hours a day
;S MO Node does not accept human callers
;S
;S
;S The following flags define modem protocols supported:
;S
;S Flag Meaning
;S
;S V21 ITU-T V21 300 bps full duplex
;S V22 ITU-T V22 1200 bps full duplex
;S V29 ITU-T V29 9600 bps half duplex
;S V32 ITU-T V32 9600 bps full duplex
;S V32b ITU-T V32bis 14400 bps full duplex
;S V33 ITU-T V33
;S V34 ITU-T V34 28800 bps full duplex
;S V42 ITU-T V42 ARQ error control
;S V42b ITU-T V42bis Compression Protocol
;S H96 Hayes V9600
;S HST USR HST up to 9600 BPS
;S H14 USR HST up to 14400 BPS
;S H16 USR HST up to 16800 BPS
;S MAX Microcom AX/96xx series
;S MNP Microcom Networking Protocol error correction
;S PEP Packet Ensemble Protocol
;S CSP Compucom Speedmodem
;S ZYX ZyXEL up to 14400 BPS
;S Z19 ZyXEL up to 19200 BPS
;S V32t AT&T/Phylon's "V.32terbo"
;S VFC Hayes/Rockwell's "V.Fast Class"
;S
;S NOTE: Many V22 modems also support Bell 212A.
;S
;S If no modem flag is given, Bell 212A is assumed for 1200 bps
;S systems, CCITT V22bis is assumed for 2400 bps systems.
;S
;S A separate modem capability flag should not be used when it can be
;S determined by the modem flag. For instance, a modem flag of HST
;S implies MNP. V32b implies V32 and V42b implies V42. HST,MNP and
;S H14,MNP and H16,MNP and V32,V32b and V42,V42b flag pairs are
;S unnecessary. H14 implies HST, H16 implies H14 and V42.Bis and Z19
;S implies ZYX as well as V.42Bis.
;S
;S The following flags define the type(s) of compression of mail
;S packets supported.
;S
;S Flag Meaning
;S
;S MN No compression supported
;S
;S NOTE: The only compression method standard in
;S FidoNet is archiving, using the standard SEA ARC
;S format, with archive names defined by the
;S specification for ARCMail 0.6. The absence of the
;S MN flag indicates that ARCMail 0.6 compression is
;S supported by this node.
;S
;S
;S The following flags indicate the types of file/update requests
;S supported.
;S
;S The following flags indicate the types of file/update requests
;S supported.
;S
;S |----------------------------------------------------------|
;S | | Bark | WaZOO |
;S | |-------------------------|-------------------------|
;S | | File | Update | File | Update |
;S | Flag | Requests | Requests | Requests | Requests |
;S |------|------------|------------|------------|------------|
;S | XA | Yes | Yes | Yes | Yes |
;S | XB | Yes | Yes | Yes | No |
;S | XC | Yes | No | Yes | Yes |
;S | XP | Yes | Yes | No | No |
;S | XR | Yes | No | Yes | No |
;S | XX | No | No | Yes | Yes |
;S |----------------------------------------------------------|
;S
;S The following software is qualified to use the specified
;S file request flag:
;S
;S |---------------------------------------|
;S | File Req Flag Software Package |
;S |---------------------------------------|
;S | XA Frontdoor <1.99b |
;S | Frontdoor 2.02+ |
;S | Dutchie 2.90c |
;S | Binkleyterm >2.1 |
;S | D'Bridge <1.3 |
;S | TIMS |
;S |---------------------------------------|
;S | XB Binkleyterm 2.0 |
;S | Dutchie 2.90b |
;S |---------------------------------------|
;S | XC Opus >1.03 |
;S |---------------------------------------|
;S | XP Seadog |
;S |---------------------------------------|
;S | XR Opus 1.03 |
;S |---------------------------------------|
;S | XX D'Bridge 1.30 |
;S | Frontdoor 1.99b |
;S |---------------------------------------|
;S | None QMM |
;S |---------------------------------------|
;S ,2,ENDA-MAGHRED,Rabat,Muriel_Elbarkauoi,212-7-756412,9600,CM,V32b,V42b
;S
;S The following flags define special operating conditions:
;S
;S Flag Meaning
;S
;S CM Node accepts mail 24 hours a day
;S MO Node does not accept human callers
;S LO Node accepts calls Only from Listed
;S FidoNet addresses
;S
;S The following flags define modem protocols supported:
;S
;S Flag Meaning
;S
;S V21 ITU-T V21 300 bps full duplex
;S V22 ITU-T V22 1200 bps full duplex
;S V29 ITU-T V29 9600 bps half duplex
;S V32 ITU-T V32 9600 bps full duplex
;S V32B ITU-T V32bis 14400 bps full duplex
;S V33 ITU-T V33
;S V34 ITU-T V34 28800 bps full duplex
;S V42 LAP-M error correction w/fallback to MNP 1-4
;S V42B LAP-M error correction w/fallback to MNP 1-5
;S MNP Microcom Networking Protocol error correction
;S H96 Hayes V9600
;S HST USR Courier HST
;S H14 USR Courier HST up to 14.4Kbps
;S H16 USR Courier HST up to 16.8Kbps
;S MAX Microcom AX/96xx series
;S PEP Packet Ensemble Protocol
;S CSP Compucom Speedmodem
;S ZYX Zyxel (implies V.32Bis & V.42Bis)
;S
;S NOTE: Many V22 modems also support Bell 212A.
;S
;S If no modem flag is given, Bell 212A is assumed for 1200 bps
;S systems, CCITT V22bis is assumed for 2400 bps systems.
;S
;S
;S A separate modem capability flag should not be used when it can be
;S determined by the modem flag. For instance, a modem flag of HST
;S implies MNP. V32b implies V32 and V42b implies V42. MNP,HST and
;S H14,MNP and H16,MNP and V32,V32b and V42,V42b flag pairs are
;S unnecessary. H14 implies HST, H16 implies H14 and V42.Bis and Z19
;S implies ZYX as well as V.42Bis.
;S
;S The following flags define the type(s) of compression of mail
;S packets supported.
;S
;S Flag Meaning
;S
;S MN No compression supported
;S
;S NOTE: The only compression method standard in
;S FidoNet is archiving, using the standard SEA ARC
;S format, with archive names defined by the
;S specification for ARCMail 0.6. The absence of the
;S MN flag indicates that ARCMail 0.6 compression is
;S supported by this node.
;S
;S The following flags indicate the types of file/update requests
;S supported.
;S
;S The following flags indicate the types of file/update requests
;S supported.
;S
;S |----------------------------------------------------------|
;S | | Bark | WaZOO |
;S | |-------------------------|-------------------------|
;S | | File | Update | File | Update |
;S | Flag | Requests | Requests | Requests | Requests |
;S |------|------------|------------|------------|------------|
;S | XA | Yes | Yes | Yes | Yes |
;S | XB | Yes | Yes | Yes | No |
;S | XC | Yes | No | Yes | Yes |
;S | XP | Yes | Yes | No | No |
;S | XR | Yes | No | Yes | No |
;S | XW | No | No | Yes | No |
;S | XX | No | No | Yes | Yes |
;S |----------------------------------------------------------|
;S
;S The following software is qualified to use the specified
;S file request flag:
;S
;S |---------------------------------------|
;S | File Req Flag Software Package |
;S |---------------------------------------|
;S | XA Frontdoor <1.99b |
;S | Frontdoor 2.02+ |
;S | Dutchie 2.90c |
;S | Binkleyterm >2.1 |
;S | D'Bridge <1.3 |
;S | TIMS |
;S |---------------------------------------|
;S | XB Binkleyterm 2.0 |
;S | Dutchie 2.90b |
;S |---------------------------------------|
;S | XC Opus >1.03 |
;S |---------------------------------------|
;S | XP Seadog |
;S |---------------------------------------|
;S | XR Opus 1.03 |
;S |---------------------------------------|
;S | XW Fido >12M |
;S | Tabby |
;S |---------------------------------------|
;S | XX D'Bridge 1.30 |
;S | Frontdoor 1.99b |
;S |---------------------------------------|
;S | None QMM |
;S |---------------------------------------|
;S
;S The following flag defines gateways to other domains (networks).
;S
;S Flag Meaning
;S
;S Gx..x Gateway to domain 'x..x', where 'x..x` is a string
;S of alphanumeric characters. Valid values for 'x..x'
;S are assigned by the FidoNet International
;S Coordinator. This flag is not authorized for use by
;S any node unless specifically authorized by the IC or
;S FidoNet Inter-Network Coordinator. Registered
;S domain gateways include:
;S uucp to be used only by nodes in a list of
;S authorized fidonet.org sites available at
;S 1:1/31.
;S
;S
;S The following flags define the dedicated mail periods supported.
;S They have the form "#nn" or !nn where nn is the UTC hour the mail
;S period begins, # indicates Bell 212A compatibility, and !
;S indicates incompatibility with Bell 212A.
;S
;S Flag Meaning
;S
;S #01 Zone 5 mail hour (01:00 - 02:00 UTC)
;S #02 Zone 2 mail hour (02:30 - 03:30 UTC)
;S #08 Zone 4 mail hour (08:00 - 09:00 UTC)
;S #09 Zone 1 mail hour (09:00 - 10:00 UTC)
;S #18 Zone 3 mail hour (18:00 - 19:00 UTC)
;S #20 Zone 6 mail hour (20:00 - 21:00 UTC)
;S
;S NOTE: When applicable, the mail period flags may
;S be strung together with no intervening commas, eg.
;S "#02#09". Only mail hours other than that standard
;S within a node's zone should be given. Since
;S observance of mail hour within one's zone is
;S mandatory, it should not be indicated.
;S
;S
;S There is also a user flag which defines user-specific values. If
;S present, this flag MUST be the last flag present in a nodelist entry.
;S For further technical details about this flag, consult FidoNet
;S Technical Standard document FTS-0005 which is available for file
;S request under that magic name from 6:6/0 and 6:720/303 outside of the
;S Zone Mail Hour (+/- 2 hours).
;S
;S Zone 6 authorised 'user' flags:-
;S
;S Modem capability flags
;S
;S V32T V.32 Terbo mode
;S VFC Rockwell's V.Fast Class
;S Z19 ZyXEL up to 19200 BPS
;S
;S NetMail Coordination when (NC not= Host)
;S
;S NC Network Coordinator. This flag is ONLY to be used by
;S the Network Coordinator of a net which has split the
;S duties of NC and Host and the NC does NOT occupy the
;S Net/0 position in the nodelist.
;S
;S EchoMail Coordination:
;S
;S ZEC Zone EchoMail Coordinator. Not more than one entry
;S in the zone 6 segment may carry this flag and that must
;S be the current Zone EchoMail Coordinator.
;S
;S REC Regional EchoMail Coordinator. Not more than one
;S entry in any region may carry this flag and that must
;S be the current Regional EchoMail Coordinator.
;S
;S NEC Network EchoMail coordinator. Not more than one entry
;S in any net may carry this flag and that must be the
;S current Network EchoMail Coordinator of that Net. This
;S flag will be authorised by the relevant Regional EchoMail
;S Coordinator.
;S
;S Note: Redundant AKAs used to indicate EchoMail
;S Coordination functions are no longer permitted.
;S
;S System open hours:
;S
;S Txx In accordance with the recommendations in FSC-0062
;S and the reference table reproduced below:
;S
;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+
;S |Letter|Time| |Letter|Time| |Letter|Time| |Letter|Time| |Letter|Time|
;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+
;S | A |0000| | F |0500| | K |1000| | P |1500| | U |2000|
;S | a |0030| | f |0530| | k |1030| | p |1530| | u |2030|
;S | B |0100| | G |0600| | L |1100| | Q |1600| | V |2100|
;S | b |0130| | g |0630| | l |1130| | q |1630| | v |2130|
;S | C |0200| | H |0700| | M |1200| | R |1700| | W |2200|
;S | c |0230| | h |0730| | m |1230| | r |1730| | w |2230|
;S | D |0300| | I |0800| | N |1300| | S |1800| | X |2300|
;S | d |0330| | i |0830| | n |1330| | s |1830| | x |2330|
;S | E |0400| | J |0900| | O |1400| | T |1900| | | |
;S | e |0430| | j |0930| | o |1430| | t |1930| | | |
;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+
;S