Tillbaka till svenska Fidonet
English   Information   Debug  
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4786
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1123
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   3250
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13301
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/341
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2056
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4289
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   33431
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2065
DOS_INTERNET   0/196
duplikat   6002
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33946
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   24159
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12852
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4436
FN_SYSOP   41708
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13615
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16075
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22112
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   930
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
Möte OSDEBATE, 18996 texter
 lista första sista föregående nästa
Text 5432, 361 rader
Skriven 2005-06-26 11:54:04 av Rich (1:379/45)
   Kommentar till text 5429 av Geo (1:379/45)
Ärende: Re: An Army of Soulless 1's and 0's
===========================================
From: "Rich" <@>

This is a multi-part message in MIME format.

------=_NextPart_000_01A3_01C57A45.C0F793F0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Yes it does speak volumes about the real world.  Most people do not =
think like you are care about the thinks you care about regardless of = whether
or not you think they should.  Unfortunately, many are easily = tricked into
taking actions against their own interest.  That is what is = described in the
lead in to the article that triggered this thread.

Rich


  "Geo" <georger@nls.net> wrote in message news:42bef565@w3.nls.net...
  No I'm not giving up, just admitting that the latest versions don't =
suffer from the same UI flaws of previous versions. But the fact that so = many
people are still being fooled by this crap speaks volumes about the = real
world.

  Geo.
    "Rich" <@> wrote in message news:42bef4a3@w3.nls.net...
       Now you give up on making false claims about safe and unsafe =
attachments.  Are you incapable of admiting you are wrong?

       Are you trying to suggest that someone that downloads a ZIP file, =
opens that file, opens something from that file, and then still ignores = the
warning about it being unsafe should blame any unwanted consequences = on whom,
you?  How often do you infect yourself this way?

    Rich

      "Geo" <georger@nls.net> wrote in message =
news:42beee3d@w3.nls.net...
      not if it's in a zip file.
        "Rich" <@> wrote in message news:42beebc0@w3.nls.net...
           To try to fool the few people like you that ignore all the =
other signs.  When OE is configured to allow unsafe file types it = displays
the .scr extension even for the long path.  It also displays = the appropriate
icon which for the example you give is an application = icon not a JPEG icon. 
Outlook and OE still block it or warn about it = depending on settings. =20

        Rich

          "Geo" <georger@nls.net> wrote in message =
news:42bec43b$1@w3.nls.net...
          You don't believe the current UI with the way it displays an =
icon has had an effect?

          Why then do email virus use such long attachment names?

          Sheep.jpg                                                      =
                                       .scr

          explain that.

          Geo.
            "Rich" <@> wrote in message news:42be1eb8@w3.nls.net...
               The icons reflect the icons elsewhere in the UI.  I =
believe this makes sense and do not believe that this UI consistency = makes
users more likely to make bad choices.

               File extensions being hidden or not, and they are not on =
file attachments, is not the issue.  I realize that this is a topic you = like
to whine about because you believe that your preference is right = for
everyone.  Do you really believe the the clueless that ignore = warnings would
pay attention to this?  This is all moot given that = unsafe email attachments
are blocked and the article was describing = people downloading from the web
not opening an attachment.

               As for your claim to show a difference, this happens in a =
very obvious way.  Users are warned about dangerous files and not warned =
about safe ones.  The problem is that many ignore the warnings.  This is = the
topic discussed in the email to which you replied and one which you =
completely ignored in your reply.

            Rich

              "Geo" <georger@nls.net> wrote in message =
news:42be194e$1@w3.nls.net...
              The answer is very simple, instead of hiding dangerous =
attachments, show the users that these are somehow different from other =
attachments, something as simple as changing the icon to a skull and =
crossbones. To make it so that profession users can't open an attachment =
without an exchange server is just plain rude.

              The problem is MS has spent recent history trying to hide =
file extensions from the users, so now we have a bunch of clueless users = when
it comes to telling which file types are safe and which are not.

              Geo.
                "Rich" <@> wrote in message news:42be015f@w3.nls.net...
                   I don't see an easy answer.  The issue is not that =
users are warned when there is no reason too, it's that they got lucky.  = A
better analogy than a combination lock is Russian roulette.  It's = always
dangerous which is why there is a warning.  What would you do?

                   On a related note, how do you make a user that just =
wants things to "work" and clicks OK because it doesn't "work" if he = makes
another choice to care about such choices?  You can remove the = choice which
is the position taken with Outlook and dangerous = attachments.  There were
plenty that complained including folks here = when that happened.

                Rich

------=_NextPart_000_01A3_01C57A45.C0F793F0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2668" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Yes it does speak volumes =
about the=20
real world.&nbsp; Most people do not think like you are care about the =
thinks=20
you care about regardless of whether or not you think they should.&nbsp; =

Unfortunately, many are easily tricked into taking actions against their =
own=20
interest.&nbsp; That is what is described in the lead in to the article =
that=20
triggered this thread.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV>"Geo" &lt;<A =
href=3D"mailto:georger@nls.net">georger@nls.net</A>&gt; wrote=20
  in message <A=20
  =
href=3D"news:42bef565@w3.nls.net">news:42bef565@w3.nls.net</A>...</DIV>
  <DIV><FONT face=3DArial size=3D2>No I'm not giving up, just admitting =
that the=20
  latest versions don't suffer from the same UI flaws of previous =
versions. But=20
  the fact that so many people are still being fooled by this crap =
speaks=20
  volumes about the real world.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Geo.</FONT></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV>"Rich" &lt;@&gt; wrote in message <A=20
    =
href=3D"news:42bef4a3@w3.nls.net">news:42bef4a3@w3.nls.net</A>...</DIV>
    <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Now you give up on =
making false=20
    claims about safe and unsafe attachments.&nbsp; Are you incapable of =

    admiting you are wrong?</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Are you trying to =
suggest that=20
    someone that downloads a ZIP file, opens that file, opens something =
from=20
    that file, and then still ignores the warning about it being unsafe =
should=20
    blame any unwanted consequences on whom, you?&nbsp; How often do you =
infect=20
    yourself this way?</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV>"Geo" &lt;<A =
href=3D"mailto:georger@nls.net">georger@nls.net</A>&gt;=20
      wrote in message <A=20
      =
href=3D"news:42beee3d@w3.nls.net">news:42beee3d@w3.nls.net</A>...</DIV>
      <DIV><FONT face=3DArial size=3D2>not if it's in a zip =
file.</FONT></DIV>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
        <DIV>"Rich" &lt;@&gt; wrote in message <A=20
        =
href=3D"news:42beebc0@w3.nls.net">news:42beebc0@w3.nls.net</A>...</DIV>
        <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; To try to fool the =
few people=20
        like you that ignore all the other signs.&nbsp; When OE is =
configured to=20
        allow unsafe file types it displays the&nbsp;.scr&nbsp;extension =
even=20
        for the long path.&nbsp; It also displays the appropriate icon =
which for=20
        the example you give is an application icon not a JPEG =
icon.&nbsp;=20
        Outlook and OE still block it or warn about it depending on=20
        settings.&nbsp; </FONT></DIV>
        <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
        <DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
        <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
          <DIV>"Geo" &lt;<A=20
          href=3D"mailto:georger@nls.net">georger@nls.net</A>&gt; wrote =
in message=20
          <A=20
          =
href=3D"news:42bec43b$1@w3.nls.net">news:42bec43b$1@w3.nls.net</A>...</DI=
V>
          <DIV><FONT face=3DArial size=3D2>You don't believe the current =
UI with the=20
          way it displays an icon has had an effect?</FONT></DIV>
          <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2>Why then do email virus use =
such long=20
          attachment names?</FONT></DIV>
          <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial=20
          =
size=3D2>Sheep.jpg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
          .scr</FONT></DIV>
          <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2>explain that.</FONT></DIV>
          <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
          <DIV><FONT face=3DArial size=3D2>Geo.</FONT></DIV>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
            <DIV>"Rich" &lt;@&gt; wrote in message <A=20
            =
href=3D"news:42be1eb8@w3.nls.net">news:42be1eb8@w3.nls.net</A>...</DIV>
            <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; The icons =
reflect the=20
            icons elsewhere in the UI.&nbsp; I believe this makes sense =
and do=20
            not believe that this UI consistency makes users more likely =
to make=20
            bad choices.</FONT></DIV>
            <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
            <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; File =
extensions being=20
            hidden or not, and they are not on file attachments, is not =
the=20
            issue.&nbsp; I realize that this is a topic you like to =
whine about=20
            because you believe that your preference is right for=20
            everyone.&nbsp; Do you really believe the the clueless that =
ignore=20
            warnings would pay attention to this?&nbsp; This is all moot =
given=20
            that unsafe email attachments are blocked and the article =
was=20
            describing people downloading from the web not opening an=20
            attachment.</FONT></DIV>
            <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
            <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; As for your =
claim to show=20
            a difference, this happens in a very obvious way.&nbsp; =
Users are=20
            warned about dangerous files and not warned about safe =
ones.&nbsp;=20
            The problem is that many ignore the warnings.&nbsp; This is =
the=20
            topic discussed in the email to which you replied and one =
which you=20
            completely ignored in your reply.</FONT></DIV>
            <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
            <DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
            <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
            <BLOCKQUOTE dir=3Dltr=20
            style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
              <DIV>"Geo" &lt;<A=20
              href=3D"mailto:georger@nls.net">georger@nls.net</A>&gt; =
wrote in=20
              message <A=20
              =
href=3D"news:42be194e$1@w3.nls.net">news:42be194e$1@w3.nls.net</A>...</DI=
V>
              <DIV><FONT face=3DArial size=3D2>The answer is very =
simple, instead of=20
              hiding dangerous attachments, show the users that these =
are=20
              somehow different from other attachments, something as =
simple as=20
              changing the icon to a skull and crossbones. To make it so =
that=20
              profession users can't open an attachment without an =
exchange=20
              server is just plain rude.</FONT></DIV>
              <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
              <DIV><FONT face=3DArial size=3D2>The problem is MS has =
spent recent=20
              history trying to hide file&nbsp;extensions from the =
users, so now=20
              we have a bunch of clueless users when it comes to telling =
which=20
              file types are safe and which are not.</FONT></DIV>
              <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
              <DIV><FONT face=3DArial size=3D2>Geo.</FONT></DIV>
              <BLOCKQUOTE dir=3Dltr=20
              style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
                <DIV>"Rich" &lt;@&gt; wrote in message <A=20
                =
href=3D"news:42be015f@w3.nls.net">news:42be015f@w3.nls.net</A>...</DIV>
                <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; I don't =
see an easy=20
                answer.&nbsp;&nbsp;The issue is&nbsp;not that users are =
warned=20
                when&nbsp;there is no reason too, it's that they got=20
                lucky.&nbsp; A better analogy than a combination lock is =
Russian=20
                roulette.&nbsp; It's always dangerous which is why there =
is a=20
                warning.&nbsp; </FONT><FONT face=3DArial size=3D2>What =
would you=20
                do?</FONT></DIV>
                <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
                <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; On a =
related note, how=20
                do you make a user that just wants things to "work" and =
clicks=20
                OK because it doesn't "work" if he makes another choice =
to care=20
                about such choices?&nbsp; You can remove the choice =
which is the=20
                position taken with Outlook and dangerous =
attachments.&nbsp;=20
                There were plenty that complained including folks here =
when that=20
                happened.</FONT></DIV>
                <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
                <DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
                <DIV><FONT face=3DArial=20
            =
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>=


------=_NextPart_000_01A3_01C57A45.C0F793F0--

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)