I just joined a group about it. It is called SCAMP. It is a new protocol
they are developing. The Yahoo group for it is:
http://groups.yahoo.com/group/SCAMPprotocol/

Here is what they told me after I joined and asked about it:
---------
Cut/paste
---------
Yes,  This is very neet protocal.

Cuurntely the software needs  pretty much a robust link for it to work
well. 
We are all pretty much  excitely awaiting new software from Rick
Muething, 
KN6KB.
We also understand Barry Sanderson KB9VAK is looking at creating another
new 
and more robust protocal based on the new DRM method of broadcasting
that 
may eventually be used.


When you joined the group.  You should have been sent some doccuments
that 
explain Scamp and what it is.
You can find the install requirements in the Paclink SCD Install.doc.

If you did not receive these documents.  You can downaload them from 
ftp://winlink.org/scamp/.

You may also want to check out some of the sceen captures located in the

groups file section, such as.

acceptp2pinbound.jpg

telnet setup.gif


You can go to this link and downaload the documents and beta test
procedure 
and software..

ftp://winlink.org/scamp/

Paclink Postoffice 1.0.8.zip
Paclink SCD 0.3.8.zip

SCAMP Overview.doc

Paclink SCD Install.doc
KN6KB DCC2004.doc
Paclink SCD QuickStart Guide.doc
SCAMP beta.doc


Paclink SCD Revision History.txt
SCAMP  Alpha Testing Commences.doc

You can find the install requirements in the Paclink SCD Install.doc;


Paclink SCD
Microsoft .NET Framework (if not already installed on your computer)

Microsoft Direct X Sound card Controls (if not already installed on your

computer)

In addition, you will need to have a standard E-mail client such as
Outlook 
or Outlook Express available for testing and operation. Initially, this 
should be on the same computer as Paclink SCD but once installation is 
complete other E-mail clients (compatible with standard POP3 and SMTP 
servers) can be used on other computers networked to the Paclink SCD 
computer. Outlook Express is normally included with all Windows
operating 
systems and is part of MS Internet Explorer 6.0. You can also operate 
Paclink SCD from other mail clients like Netscape, Mozzila, or Eudora
but 
these programs may have some restrictions on multiple accounts. Windows
2000 
Professional or Windows XP (Pro or Home) is required for Paclink SCD.

Computer Requirements:

Paclink SCD runs as a .NET application and will require the installation
of 
the .NET Framework version 1.1 (or later). The table below is the 
requirements as suggested by Microsoft but reports suggest instabilities

using with Win98/se and Win ME. At this time Paclink SCD has NOT been
tested 
with Win 98 or ME and only installations with Windows 2000 or Windows XP
and 
a minimum of 256 Meg of RAM are recommended. Paclink SCD also uses 
considerable CPU resources in computing the FFT and encoding and
decoding of 
data to/from the sound card. It is currently recommended for processors
of 
1000 MHz Celeron or higher capability with 256 Meg or more of RAM. The
Beta 
test program will accumulate statistics on operation with various
processors 
and allow a more expanded recommendation.

      Minimum Requirements

      Processor
     .1 Client (a computer not working in a server capacity):
90-megahertz 
(MHz) Intel Pentium-class processor

      .2 Server (a computer working in a server capacity): 133-MHz Intel

Pentium-class processor

      Operating System
     The .NET Framework 1.1 Redistributable is supported on the
following 
platforms:

      .1 Microsoft WindowsR Server 2003* (.NET Framework 1.1 is
installed as 
part of the operating system)

      .2 Windows XP Professional*

      .3 Windows XP Home Edition

      .4 Windows 2000*

      .5 Windows Millennium Edition (Windows Me)

      .6 Windows 98

      .7 Microsoft Windows NTR 4.0 Service Pack 6a

      Notes: ASP.NET Web applications and XML Web services can only be 
hosted on Windows XP Professional, Windows 2000, and Windows Server 2003

      The .NET Framework 1.1 Redistributable cannot be installed on
64-bit 
computers; Windows NT 4.0 Terminal Server is not supported

      Memory
     .1 Client: 32 megabytes (MB) of RAM, 96 MB recommended

      .2 Server: 128 MB of RAM, 256 MB recommended

      Hard Disk
     110 MB of hard disk space required, 40 MB additional hard disk
space 
required for installation (150 MB total)

      Display
     800 x 600 or higher-resolution display with 256 colors

      Input Device
     Microsoft mouse or compatible pointing device

      Other
     .1 Microsoft Internet Explorer 5.01 or later is required .

      .2 Microsoft Data Access Components 2.6 is required for data 
scenarios. (not required for Paclink)

      .3 Install the latest Windows service packs and critical updates
from 
the Windows Update site.

      .4 Installation of the .NET Framework 1.1 is split into two parts:
the 
core and language packs. The core contains everything you need to run
.NET 
Framework applications; all dialog boxes and error messages will be in 
English. If you want dialog boxes and error messages in another
language, 
you must also install the corresponding language pack. For more
information, 
see the .NET Framework Downloads page.


Radio Interface Requirements:

Paclink SCD requires an isolated audio interface from the computer sound

card to the transceiver for operation. This can be any of the commonly 
available sound card interfaces. The following have been used
successfully: 
Rig Blaster, Tigertronics signal-link, Rascal, Saratoga. Serial PTT 
operation is preferred but VOX will work provided sensitivity is set
high 
enough and there the transceiver has minimal VOX delay.

The Beta version does NOT currently support the RigExpert interface. It
is 
recommended that the computer, sound card interface and transceiver 
operation be verified with another sound card mode and software before 
trying to use SCAMP.
----
----

Hope that helps.

7&3 fer nw,
Bob
KE5CTY (old calls WB5ZQU - WY5L)
FP#-1141
http://www.qsl.net/ke5cty/
Code may be taking a back seat for now, but the pioneering spirit that
put the code there in the first place is out front of it all.




-----Original Message-----
From: Repeater-Builder@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Coy Hilton
Sent: Thursday, June 16, 2005 6:56 PM
To: Repeater-Builder@yahoogroups.com
Subject: [Repeater-Builder] Email from a repeater


I have been hearing rumbelings about programs to allow retreeving 
emails from or through repeaters. Does anyone know of it and can you 
tell me where I can get it.
73
AC0Y  






 
Yahoo! Groups Links



 








 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/Repeater-Builder/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to