| |
EB2DVY > PSK31 05.03.00 09:53l 166 Lines 7263 Bytes #-9638 (0) @ WW.SYD.NSW.
BID : 1026-EB2DVY
Read: OE1RRB GUEST
Subj: PSK31 Digest V1 #330
Path: OE1XAB<OE3XPR<OE6XAR<OE5XBL<DB0RGB<DB0SL<DB0FSG<IN3TRX<IN3TTI<IK5CKL<
IW5BFZ<IK1MVX<TK5KP<F6KOE<F5KBJ<F6KED<F5KPO<F5KAT<EA3D<EA3B<EA5VDR<
EA2BBS<EA2K<EA1URR<EA1URM<EA2RCF<EA2G<EA2URV
Sent: 000304/2154Z @:EA2URV.EABI.ESP.EU #:46175 [URV-ABRA Bilbao] $:1026-EB2DVY
From: EB2DVY@EA2URV.EABI.ESP.EU
To : PSK31@WW.SYD.NSW.AUS.OC
De: Psk31 Digest <owner-psk31@aintel.bi.ehu.es>
Para: <psk31-digest@bipt106.bi.ehu.es>
Asunto: Psk31 Digest V1 #330
Fecha: jueves 2 de marzo de 2000 4:26
Psk31 Digest Thursday, March 2 2000 Volume 01 : Number 330
In this issue:
[psk31] Re: [Hellschreiber] Ham (too much) spirit
[psk31] Winpsk 1.1 Info
See the end of the digest for information about psk31-digest
----------------------------------------------------------------------
Date: Tue, 29 Feb 2000 20:33:26 -0800
From: "Peter A. Klein" <pklein@2alpha.net>
Subject: [psk31] Re: [Hellschreiber] Ham (too much) spirit
>From: "Gary McDuffie, Sr." <mcduffie@scottsbluff.net>
>Referring to Pretty Park.exe trojan horse:
>...Problem is, I'm afraid the person who is responsible for
>getting it to the list probably didn't even know he was infected before
>it happened.
This is quite likely. One of the things this virus does is look through
your Internet address book and send itself to everybody in it, without your
knowledge. I believe it only affects Microsoft software like Outlook or
Exchange, but I'm not absolutely sure of this.
>Luckily, as I said in yesterday's post, I had just read a posting a day
>or two earlier about that virus and recognized it right away. The bad
>thing about this one is Norton Anti-Virus (5.0 and 2000) do NOT
>recognize it as a virus. They both report "no virus found". This, of
>course, leads to non-trust in NAV. I kept a copy on floppy to see if I
>can get out of Symantec why it didn't detect this thing and figure out
>how to be covered in the future.
I have Norton Anti-Virus. It detected the Pretty Park file that I received
yesterday. But I regularly connect to Symantec and download updated virus
signature files. There's a feature called "live update" in NAV that
automates most of this. If you don't update your program regularly, you
can't be protected against viruses that came out after your version of the
program was published.
Anti-Virus programs aren't very smart. All they do is detect a string of
bytes (characters) called a "signature" that identifies the virus. Then
they can disable that specific virus in an EXE file by deleting the virus
payload and changing the length of the file back to what it should have
been before the virus infected it. In the case of a DOC file, they can
disable the macro and/or "zero out" the infecting macro code. But the
Pretty Park worm actually turns its payload into a system file, and changes
some registry entries to point to it, so it's run every time you run any
other program. Fixing stuff like that needs to be done manually.
There are ways to turn on semi-smart behavior (called "heuristics") that
enable an anti-virus program to look for virus-like code in programs. The
problem with this approach is that it inevitably leads to so many false
alarms that you fail to trust the anti-virus program when you need it (as
in "The Boy Who Cried 'Wolf'"). So the best protection is regular updates
to a standard virus program.
Plus, don't run any macros in Word and Excel files unless you know exactly
where they came from and what they do. There's a setting in Word and Excel
that will always prompt you whenever a macro is encountered--it's called
"Macro Virus Protection" in Word 97, and it's in "Tools, Options, General."
And don't run program (such as EXE files) from unknown sources either.
>(www.symantec.com/avcenter/venc/data/prettypark.worm.html) didn't work,
>because, before we got those instructions, we let Norton try to clean it
>up. That failed miserably. We finally restored from a recent image and
>called it good.
Anti-virus programs can easily disinfect an individual .EXE file or disable
a virus macro in a word .DOC file, but I wouldn't trust any anti-virus
program to deal with registry entries and renaming of a Windows system
file. You have to do it manually. PrettyPark hooks into your system, so
it's not just a matter of one file.
The McAffee site has a more complex procedure for removing PrettyPark:
http://vil.mcafee.com/vil/vpe10175.asp
Hope this helps!
- --Peter, KD7MW
------------------------------
Date: Wed, 01 Mar 2000 08:02:58 -0800
From: "Robert G.Wagner" <n6dur@san.rr.com>
Subject: [psk31] Winpsk 1.1 Info
Hi Mr. Moe,
Just a note to compliment you again on the most recent WINPSK 1.1
Version; works great on my Sony Laptop with Icom 706 Mk II Mobile.
Some info worthy of knowing about this installation:
1. If you make a change to a Macro, i.e., your Brag File, and get a
Memory Allocation Error report the next time you bring up WinPSK 1.1, go
back to that Brag File and clean it up. You might have exceeded the
size limit. I made some changes to my mobile Brag File, then shutdown
for the day without bringing up Winpsk 1.1 to see if I had any
problems. The next morning on double-clicking the Winpsk Icon to bring
up the program, a box came up indicating a memory allocation error was
occurring; lucky for me I remembered the last thing I had done was work
on a brag file. I went back, reorganized the file and the report was
gone after a reload.
2. Another comment concerning how fast Winpsk 1.1 will lock on a PSK31
signal. I found my Laptop was not as responsive to AFC as my in-house
Desktop computer. I found removing Real Player and Real Player Jukebox
from the startup of the Laptop cleared this problem. AFC locks on
perfectly. I have found it is best not to have any unnecessary stuff
going. Also, most Laptops have various modes of operation settings to
reduce current drain and these can reduce mobile performance. I always
set my Laptop to Maximum Performance, since this makes the screen
brighter and is best for digging out the weak signals.
3. I set the ICom 706 Mk II for LSB and select LSB in Winpsk 1.1
SETTINGS-GENERAL SETUP. As most of us ICOM 706 users know, you can
trick the 706 into making a CW or RTTY filter available for SSB by, for
example, temporarily setting Fil 1 to FL-103, if you have FL-232 ( a
350 HZ) actually installed. Offset the shift to about 2 o'clock and
your in business. The DSP works fine also.
I optimized a 20 M Hamstick for 14070, a 10M Hamstick for 28120, and
found my 17M SSB Hamstick would also tune 18100, & have a Outbacker for
30M, so I'm set for several Psk31 bands. I've made several great
mobile contacts; no I'm not driving . . . . . . the xyl is or we're at
rest :))
Since I use a foot switch in the house with the big rig, this is not a
problem for me and lets me minimize the cables to the Laptop. KISS
73'S & HAPPY WARBLING TO ALL Hope to see you mobile de N6DUR/M Bob &
Marie
- --
ICQ# 2667720
WebMail: n6dur@netscape.net
Page me at:
http://wwp.mirabilis.com/2667720#pager
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
to unsuscribe from the list send to majordomo@aintel.bi.ehu.es a message
with a text line as follow: unsubscribe psk31 or unsubscribe psk31-digest
More instructions on PSK31 Webpage: http://aintel.bi.ehu.es/psk31.html
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
------------------------------
End of Psk31 Digest V1 #330
***************************
Read previous mail | Read next mail
| |
