We have implemented an application which utilizes the grayscale calls talked
about in the "Seeing Gray" papers. The application look absolutely GREAT on
the PalmPro, III, IIIx, and V that we have. Unfortunately, on our Handspring
Visor, the application is hardly usable. The entire screen is "washed out"
and streaky. I know of other software authors ( the developer of
ImageIII???), that have had to deal with the Visor hardware specifically in
order to get grayscale to work properly. Does anyone have any pointers on
problem? Does it have to do with the fact that the Visor is running 3.1 and
the other devices are at either 3.0x or 3.3? I would hate to have to back
out all of the software changes for grayscale and use patterns just so that
it works on the Visor.
Regards,
Bryan Nystrom
Natara Software, Inc. http://www.natara.com
ICQ: 2526059 (630) 579-0958
-----Original Message-----
From: Bryan Batchelder [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 14, 2000 11:53 AM
To: [EMAIL PROTECTED]
Subject: RE: TCP/IP vs. ping
I know on almost every server I admin, I shut down echo ports due to
security issues.
--B
> -----Original Message-----
> From: Scott Lopez [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 13, 2000 8:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: TCP/IP vs. ping
>
>
> I'd say this really depends on what you are trying to do.
> For security
> reasons, including windows, the SOCK_RAW parameter is not
> accepted, only in
> winsock2 was this changed and the only supported raw types
> are a limited
> version of ping and traceroute.
>
> My question is, are you trying to figure out if a system is
> alive? If the
> server supports ping, then open a connection to the ICMP
> "echo" port on the
> server, if you connect then you will know that the system is
> alive. Two way
> communication must occur for a socket to connect with TCP/IP.
> Ping or echo,
> simply receives data and regergitates it back out to the
> socket, connecting
> a socket performs almost all of these steps.
>
> Echo is supported on port 7 and both UDP and TCP are supported.
>
> BTW, the purpose of a raw socket is to allow the programmer
> to modify what
> is sent in the headers of the packet. Primarily to support
> new protocols
> over IP such as multicasting, etc.
>
> ----- Original Message -----
> From: "Bryan Waters" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, January 13, 2000 9:46 PM
> Subject: RE: TCP/IP vs. ping
>
>
> > Without the raw sockets support, it is NOT possible to
> perform a ping...at
> > least not short of writing your own TCPIP protocol...
> >
> > -bryanw
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, January 13, 2000 9:40 PM
> > To: [EMAIL PROTECTED]
> > Subject: TCP/IP vs. ping
> >
> >
> >
> >
> > I need to implement a "ping" function on the Palm.
> According to Article
> > 1141 in
> > the Palm Knowledge Base, "... PalmPilot supports the TCP and UDP
> > stream/datagram
> > layers of the internet. The raw socket interface is not
> supported. As a
> > result,
> > applications cannot implement a ping protocol." The
> article goes on to
> > describe
> > the Berkely Sockets API and the PalmPilot Net Library API.
> Can someone
> > clarify
> > for me whether it is, in fact, possible to perform a ping
> function in some
> > way?
> >
> > Thanks,
> > Barb
> >
> >
> >
> >
> >
>
>
