Any advice on how to link 3C to standard Laptop IR port?
>
It's not possible. The 3c/mx/siena only have the ability to communicate with
each other and IR printers.

Richard


"Martin" wrote in message
news:2I0sc.42$m36.36@newsfe2-win...
> Hi
>
>> Speeds comms formats etc
>
> TIA
>
> Kukri
>
>

"Middle aged" schreef in bericht
newsT%rc.22480$U1f1.20830@news04.bloor.is.net.cable.ro gers.com...
> Any advice on how to link 3C to standard Laptop IR port?
> >
> It's not possible. The 3c/mx/siena only have the ability to communicate
with
> each other and IR printers.

Can the laptop not tell to the Psion that it is really also a Psion?

"Boudewijn Dijkstra" wrote in message
news:40b24174$0$41753$5fc3050@dreader2.news.tiscal i.nl...
> "Middle aged" schreef in bericht
> newsT%rc.22480$U1f1.20830@news04.bloor.is.net.cable.ro gers.com...
> > Any advice on how to link 3C to standard Laptop IR port?
> > >
> > It's not possible. The 3c/mx/siena only have the ability to communicate
> with
> > each other and IR printers.
>
> Can the laptop not tell to the Psion that it is really also a Psion?

Huh? The IR protocols that the Series 3 uses are not the same as those used
by any version of Windows. As far as Windows is concerned, the Series 3
doesn't exist.

"JimC" schreef in bericht
news:4EBsc.9580$be.3078@newsread2.news.pas.earthli nk.net...
>
> "Boudewijn Dijkstra" wrote in message
> news:40b24174$0$41753$5fc3050@dreader2.news.tiscal i.nl...
> > "Middle aged" schreef in bericht
> > newsT%rc.22480$U1f1.20830@news04.bloor.is.net.cable.ro gers.com...
> > > Any advice on how to link 3C to standard Laptop IR port?
> > > >
> > > It's not possible. The 3c/mx/siena only have the ability to
communicate
> > with
> > > each other and IR printers.
> >
> > Can the laptop not tell to the Psion that it is really also a Psion?
>
> Huh? The IR protocols that the Series 3 uses are not the same as those
used
> by any version of Windows. As far as Windows is concerned, the Series 3
> doesn't exist.

Does this mean that, if a new IR protocol can be installed on a version of
Windows, my previous question can be answered with "yes, it can"?

> Does this mean that, if a new IR protocol can be installed on a version of
> Windows, my previous question can be answered with "yes, it can"?

If my memory is good, yes it can. The problem is that I don't remember how
exactly...
Let see what still live in my mind (not sure that it is good):

_ You need to install irCOM protocol on Windows. I don't have a link but I
know that it exists somewhere on the net a beta driver for this (beta but
it works great). I read a post here talking about it one month ago I think.

_ You need to enable the link connection of the Psion S3c/S3mx/Workabout and
select "Link Cable" (instead of "Psion IR"). The tips is that you have to
add in the "Extra parameters" field something like "-sTTY:I". This will
force the link software to use this device instead of TTY:A.

Sorry, I'm not sure about the parameter but I'm quite sure that it's
something like that.

Then, using Psiwin on the serial port created by the beta driver, you should
be able to connect transfer & synchronise you Psion with your laptop using
its ir port.

Note: only this port should be enable in Psiwin.


--
,,,
(._.)
/|\+\\
\|/ @u(==-

On Thursday, in article
<40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:

> Does this mean that, if a new IR protocol can be installed on a version of
> Windows, my previous question can be answered with "yes, it can"?

No. It means that the IR protocol implemented by the 3C is not a standard
implemented on Windows, and that PsiWIN doesn't recognise it, and never
will.
--
Raj Rijhwani | This is the voice of the Mysterons...
raj@rijhwani.org | ... We know that you can hear us Earthmen
http://www.rijhwani.org/raj/ | "Lieutenant Green: Launch all Angels!"

Raj Rijhwani wrote:
> On Thursday, in article
> <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
> usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
>
>
>>Does this mean that, if a new IR protocol can be installed on a version of
>>Windows, my previous question can be answered with "yes, it can"?
>
>
> No. It means that the IR protocol implemented by the 3C is not a standard
> implemented on Windows, and that PsiWIN doesn't recognise it, and never
> will.

Are you saying that it is NOT POSSIBLE to write code that runs on a
PC-compatible desktop computer under ANY operating system that can talk
to a 3C?
Or are you saying that your limited experience has never encountered
such code?
Or maybe you're just not reading the question.

I'm in a similar boat with an Osaris and would like to find a way to
get the terminal emulator to work over IR so I can talk to PIC
microcontroller projects.

--
Return address is VALID.
Bunch of stuff For Sale and Wanted at the link below.
Toshiba & Compaq LiIon Batteries, Test Equipment
Yaesu FTV901R Transverter, 30pS pulser
Tektronix Concept Books, spot welding head...
http://www.geocities.com/SiliconValley/Monitor/4710/

"mike" wrote in message news:40B7D0A8.3040104@juno.com...
> Raj Rijhwani wrote:
> > On Thursday, in article
> > <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
> > usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
> >
> >
> >>Does this mean that, if a new IR protocol can be installed on a version
of
> >>Windows, my previous question can be answered with "yes, it can"?
> >
> >
> > No. It means that the IR protocol implemented by the 3C is not a
standard
> > implemented on Windows, and that PsiWIN doesn't recognise it, and never
> > will.
>
> Are you saying that it is NOT POSSIBLE to write code that runs on a
> PC-compatible desktop computer under ANY operating system that can talk
> to a 3C?
> Or are you saying that your limited experience has never encountered
> such code?
> Or maybe you're just not reading the question.


The text seems pretty clear, try reading it again.
And who would develop an application for a dead machine now?- it would have
been done when they were being sold if at all. Look through the software
sites for software that was produced ....... Good luck. Check the newsgroup
archives, there was something for the 5 series, but I'm not sure about the
others.

__________________________________________________ _____________
eg
IrTran-P OPM

History
IrTran-P Version HistoryVersionDateDescription
0.0.12001-07-20Alpha release

Description
IrTran-P is a protocol that allows digital cameras to send and receive
photos
via infra-red. This is my initial implementation of an IrTran-P OPL module.
I'm releasing this to gauge the level of interest in such a library, and to
find
out how well the library works in spite of all the development short-cuts I
did
in implementing it.
Please email me your comments, even if it works perfectly, but especially if
it
doesn't.
If it doesn't work, please attach the "IrTranP.log" file that should be in
the
same directory as "foo.jpg".
Please note that I have only tested using my Casio QV-3000EX/Ir camera. When
you
email me, please tell me what camera and EPOC handheld you're using.
Download
Download the following and unzip onto your EPOC handheld. There are two
files:
"IrTranP.opo" (the IrTran-P library), and "IrTranPtest.opo" (a test harness
for
the library). Make sure they're both in the same directory, get your camera
ready to send, then run "IrTranPtest.opo". Wait for the prompt, then start
your
camera sending. Hopefully, the transfer should start and you'll end up with
a
JPEG called "foo.jpg" in the root directory of the current drive (or where
ever
OPL files end up by default).
irtranp.zip ( 4k) IrTran-P OPM test files
You'll also need to download and install the SCOMMS.OPX from Symbian:
scomms.zip ( 117k) Scomms.OPX

Last updated: 2001-07-21
__________________________________________________ __________________
also
SCOMMS.OPX
==========
This OPX allows EPOC OPL developers to make use of the IrDA IRCOMM protocol.
This is the protocol used by IrDA equipped mobile phones with data modems.

The previous IrDA functions in SYSTEM.OPX gave TinyTP functionality, which
limited it's use to other EPOC devices and IrDA printers.

This release includes an update of the IrDA stack for increased reliability.

Copyright
---------
SComms.opx is Copyright (c) 1997-1999 Symbian Ltd. All rights reserved. It
forms part of the OPL SDK and is subject to the License contained therein.

Distribution
------------
SComms OPX should only be distributed to end users in one of the SIS files
included in this release. This ensures that older versions will not be
installed over newer versions without warning.

The best way to do this is to include the SComms SIS within your
applications
SIS. This means you can distribute your application as a single SIS file,
and
be sure that SComms and the IrDA update will only be upgraded if necessary.

For MARM distributions use this line in your PKG file:
@"SComms.SIS",(0x100038F2)

For WINS distributions use this line:
@"SCommsW.SIS",(0x100038F2)

TSCOMMS.OPL
-----------
This program tests and demos much of the functionality of SCOMMS OPX. Use
it
against another S5 running Comms (or the emulator if you have an IrDA
adapter
for the PC which runs from COM1.)

Ensure the remote link is switched off on both machines, and set-up Comms to
run with "InfraRed" rather than "Serial port 0". Make sure you have the
IrDA
update on both machines.

Contents of ZIP
---------------
The ZIP file contains the following files

readme.txt - This file
tscomms.tpl - OPL test and demo program (text format)
e32err.tph - Lists the error codes that E32 sets status words to when using
asynchronous functions (text format)
scomms.txh - OPX header file (text format)
scomms.sis - SIS file containing scomms.opx and IrDA update (MARM)
scommsw.sis - SIS file containing scomms.opx and IrDA update (WINS)

AlanS espoused:
>
> "mike" wrote in message news:40B7D0A8.3040104@juno.com...
>> Raj Rijhwani wrote:
>> > On Thursday, in article
>> > <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
>> > usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
>> >
>> >
>> >>Does this mean that, if a new IR protocol can be installed on a version
> of
>> >>Windows, my previous question can be answered with "yes, it can"?
>> >
>> >
>> > No. It means that the IR protocol implemented by the 3C is not a
> standard
>> > implemented on Windows, and that PsiWIN doesn't recognise it, and never
>> > will.
>>
>> Are you saying that it is NOT POSSIBLE to write code that runs on a
>> PC-compatible desktop computer under ANY operating system that can talk
>> to a 3C?
>> Or are you saying that your limited experience has never encountered
>> such code?
>> Or maybe you're just not reading the question.
>
>
> The text seems pretty clear, try reading it again.

Not sure that the text is clear, but this might be interesting
to the OP?

http://www.geocities.com/SiliconValley/Lakes/3947/



--
| Mark Kent -- mark at ellandroad dot demon dot co dot uk |
People who have what they want are very fond of telling people who haven't
what they want that they don't want it.
-- Ogden Nash

"Mark Kent" wrote in message
news:11gq9c.mfe.ln@ellandroad.demon.co.uk...
> AlanS espoused:
> >
> > "mike" wrote in message
news:40B7D0A8.3040104@juno.com...
> >> Raj Rijhwani wrote:
> >> > On Thursday, in article
> >> > <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
> >> > usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
> >> >
> >> >
> >> >>Does this mean that, if a new IR protocol can be installed on a
version
> > of
> >> >>Windows, my previous question can be answered with "yes, it can"?
> >> >
> >> >
> >> > No. It means that the IR protocol implemented by the 3C is not a
> > standard
> >> > implemented on Windows, and that PsiWIN doesn't recognise it, and
never
> >> > will.
> >>
> >> Are you saying that it is NOT POSSIBLE to write code that runs on a
> >> PC-compatible desktop computer under ANY operating system that can talk
> >> to a 3C?
> >> Or are you saying that your limited experience has never encountered
> >> such code?
> >> Or maybe you're just not reading the question.
> >
> >
> > The text seems pretty clear, try reading it again.
>
> Not sure that the text is clear, but this might be interesting
> to the OP?
>
> http://www.geocities.com/SiliconValley/Lakes/3947/
>
>

What's not clear?
-No. It means that the IR protocol implemented by the 3C is not a standard
implemented on Windows, and that PsiWIN doesn't recognise it, and never
will.

AlanS wrote:
> "Mark Kent" wrote in message
> news:11gq9c.mfe.ln@ellandroad.demon.co.uk...
>
>>AlanS espoused:
>>
>>>"mike" wrote in message
>>
> news:40B7D0A8.3040104@juno.com...
>
>>>>Raj Rijhwani wrote:
>>>>
>>>>>On Thursday, in article
>>>>> <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
>>>>> usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Does this mean that, if a new IR protocol can be installed on a
>>>>>
> version
>
>>>of
>>>
>>>>>>Windows, my previous question can be answered with "yes, it can"?
>>>>>
>>>>>
>>>>>No. It means that the IR protocol implemented by the 3C is not a
>>>>
>>>standard
>>>
>>>>>implemented on Windows, and that PsiWIN doesn't recognise it, and
>>>>
> never
>
>>>>>will.
>>>>
>>>>Are you saying that it is NOT POSSIBLE to write code that runs on a
>>>>PC-compatible desktop computer under ANY operating system that can talk
>>>>to a 3C?
>>>>Or are you saying that your limited experience has never encountered
>>>>such code?
>>>>Or maybe you're just not reading the question.
>>>
>>>
>>>The text seems pretty clear, try reading it again.
>>
>>Not sure that the text is clear, but this might be interesting
>>to the OP?
>>
>>http://www.geocities.com/SiliconValley/Lakes/3947/
>>
>>
>
>
> What's not clear?
> -No. It means that the IR protocol implemented by the 3C is not a standard
> implemented on Windows, and that PsiWIN doesn't recognise it, and never
> will.
>
Ok, let's get really clear by quoting the original request.
start quote
Any advice on how to link 3C to standard Laptop IR port?
Speeds comms formats etc
end quote

I don't see any restrictions on software. The guy wants a way to do it,
as do I.
Repeat!!! no mention of PSIwin or any standard protocol or any specific
application on either end of the transfer. I'm CERTAIN
that a protocol exists and that it's quite possible to do the transfer.
All we need to know is if anyone else has done it and how.
Darn, it's possible to write hex assembler on both ends and do it.
We could rewrite the OS on both ends.
We're looking for a somewhat easier way. Telling us it can't be done
or that your favorite program won't do it is not helpful.
Thank you!!
mike


--
Return address is VALID.
Bunch of stuff For Sale and Wanted at the link below.
Toshiba & Compaq LiIon Batteries, Test Equipment
Yaesu FTV901R Transverter, 30pS pulser
Tektronix Concept Books, spot welding head...
http://www.geocities.com/SiliconValley/Monitor/4710/

My previous post:

<<

> Does this mean that, if a new IR protocol can be installed on a version of
> Windows, my previous question can be answered with "yes, it can"?

If my memory is good, yes it can. The problem is that I don't remember how
exactly...
Let see what still live in my mind (not sure that it is good):

_ You need to install irCOM protocol on Windows. I don't have a link but I
know that it exists somewhere on the net a beta driver for this (beta but
it works great). I read a post here talking about it one month ago I think.

_ You need to enable the link connection of the Psion S3c/S3mx/Workabout and
select "Link Cable" (instead of "Psion IR"). The tips is that you have to
add in the "Extra parameters" field something like "-sTTY:I". This will
force the link software to use this device instead of TTY:A.

Sorry, I'm not sure about the parameter but I'm quite sure that it's
something like that.

Then, using Psiwin on the serial port created by the beta driver, you should
be able to connect transfer & synchronise you Psion with your laptop using
its ir port.

Note: only this port should be enable in Psiwin.

>>

irCOM is a standard ir protocol mimicing serial port. Windows has drop it
since Windows 2000 for an unknow reason and reduced its driver size (you
know... when you don't know how to do something properly...).
Most phones using infrarouge and modem using infrarouge have to add their
own driver to have the irCOM protocol back.

--
,,,
(._.)
/|\+\\
\|/ @u(==-

On Friday, in article <40C15B7B.6000607@juno.com>
spamme0@juno.com "mike" wrote:

> AlanS wrote:
> > "Mark Kent" wrote in message
> > news:11gq9c.mfe.ln@ellandroad.demon.co.uk...
> >
> >>AlanS espoused:
> >>
> >>>"mike" wrote in message
> >>
> > news:40B7D0A8.3040104@juno.com...
> >
> >>>>Raj Rijhwani wrote:
> >>>>
> >>>>>On Thursday, in article
> >>>>> <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
> >>>>> usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Does this mean that, if a new IR protocol can be installed on a
> >>>>>
> > version
> >
> >>>of
> >>>
> >>>>>>Windows, my previous question can be answered with "yes, it can"?
> >>>>>
> >>>>>
> >>>>>No. It means that the IR protocol implemented by the 3C is not a
> >>>>
> >>>standard
> >>>
> >>>>>implemented on Windows, and that PsiWIN doesn't recognise it, and
> >>>>
> > never
> >
> >>>>>will.
> >>>>
> >>>>Are you saying that it is NOT POSSIBLE to write code that runs on a
> >>>>PC-compatible desktop computer under ANY operating system that can talk
> >>>>to a 3C?
> >>>>Or are you saying that your limited experience has never encountered
> >>>>such code?
> >>>>Or maybe you're just not reading the question.
> >>>
> >>>
> >>>The text seems pretty clear, try reading it again.
> >>
> >>Not sure that the text is clear, but this might be interesting
> >>to the OP?
> >>
> >>http://www.geocities.com/SiliconValley/Lakes/3947/
> >>
> >>
> >
> >
> > What's not clear?
> > -No. It means that the IR protocol implemented by the 3C is not a standard
> > implemented on Windows, and that PsiWIN doesn't recognise it, and never
> > will.
> >
> Ok, let's get really clear by quoting the original request.
> start quote
> Any advice on how to link 3C to standard Laptop IR port?
> Speeds comms formats etc
> end quote
>
> I don't see any restrictions on software. The guy wants a way to do it,
> as do I.
> Repeat!!! no mention of PSIwin or any standard protocol or any specific
> application on either end of the transfer. I'm CERTAIN
> that a protocol exists and that it's quite possible to do the transfer.

Even if the HARDWARE-SUPPORTED protocols are incompatible?

If you're so damned certain it can be done, why don't you read up on it
and do it?
--
Raj Rijhwani | This is the voice of the Mysterons...
raj@rijhwani.org | ... We know that you can hear us Earthmen
http://www.rijhwani.org/raj/ | "Lieutenant Green: Launch all Angels!"

"mike" wrote in message news:40C15B7B.6000607@juno.com...
> AlanS wrote:
> > "Mark Kent" wrote in message
> > news:11gq9c.mfe.ln@ellandroad.demon.co.uk...
> >
> >>AlanS espoused:
> >>
> >>>"mike" wrote in message
> >>
> > news:40B7D0A8.3040104@juno.com...
> >
> >>>>Raj Rijhwani wrote:
> >>>>
> >>>>>On Thursday, in article
> >>>>> <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
> >>>>> usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Does this mean that, if a new IR protocol can be installed on a
> >>>>>
> > version
> >
> >>>of
> >>>
> >>>>>>Windows, my previous question can be answered with "yes, it can"?
> >>>>>
> >>>>>
> >>>>>No. It means that the IR protocol implemented by the 3C is not a
> >>>>
> >>>standard
> >>>
> >>>>>implemented on Windows, and that PsiWIN doesn't recognise it, and
> >>>>
> > never
> >
> >>>>>will.
> >>>>
> >>>>Are you saying that it is NOT POSSIBLE to write code that runs on a
> >>>>PC-compatible desktop computer under ANY operating system that can
talk
> >>>>to a 3C?
> >>>>Or are you saying that your limited experience has never encountered
> >>>>such code?
> >>>>Or maybe you're just not reading the question.
> >>>
> >>>
> >>>The text seems pretty clear, try reading it again.
> >>
> >>Not sure that the text is clear, but this might be interesting
> >>to the OP?
> >>
> >>http://www.geocities.com/SiliconValley/Lakes/3947/
> >>
> >>
> >
> >
> > What's not clear?
> > -No. It means that the IR protocol implemented by the 3C is not a
standard
> > implemented on Windows, and that PsiWIN doesn't recognise it, and never
> > will.
> >
> Ok, let's get really clear by quoting the original request.
> start quote
> Any advice on how to link 3C to standard Laptop IR port?
> Speeds comms formats etc
> end quote
>
> I don't see any restrictions on software. The guy wants a way to do it,
> as do I.
> Repeat!!! no mention of PSIwin or any standard protocol or any specific
> application on either end of the transfer. I'm CERTAIN
> that a protocol exists and that it's quite possible to do the transfer.
> All we need to know is if anyone else has done it and how.
> Darn, it's possible to write hex assembler on both ends and do it.
> We could rewrite the OS on both ends.
> We're looking for a somewhat easier way. Telling us it can't be done
> or that your favorite program won't do it is not helpful.
> Thank you!!
> mike
>
>

You are ignoring any advice or help people are trying to give.

You are so sure it can be done- go and do it, then report back.

Raj Rijhwani espoused:
> On Friday, in article <40C15B7B.6000607@juno.com>
> spamme0@juno.com "mike" wrote:
>
>> AlanS wrote:
>> > "Mark Kent" wrote in message
>> > news:11gq9c.mfe.ln@ellandroad.demon.co.uk...
>> >
>> >>AlanS espoused:
>> >>
>> >>>"mike" wrote in message
>> >>
>> > news:40B7D0A8.3040104@juno.com...
>> >
>> >>>>Raj Rijhwani wrote:
>> >>>>
>> >>>>>On Thursday, in article
>> >>>>> <40b5b168$0$41746$5fc3050@dreader2.news.tiscali.nl>
>> >>>>> usenet@bdijkstra.tmfweb.nl "Boudewijn Dijkstra" wrote:
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>>Does this mean that, if a new IR protocol can be installed on a
>> >>>>>
>> > version
>> >
>> >>>of
>> >>>
>> >>>>>>Windows, my previous question can be answered with "yes, it can"?
>> >>>>>
>> >>>>>
>> >>>>>No. It means that the IR protocol implemented by the 3C is not a
>> >>>>
>> >>>standard
>> >>>
>> >>>>>implemented on Windows, and that PsiWIN doesn't recognise it, and
>> >>>>
>> > never
>> >
>> >>>>>will.
>> >>>>
>> >>>>Are you saying that it is NOT POSSIBLE to write code that runs on a
>> >>>>PC-compatible desktop computer under ANY operating system that can talk
>> >>>>to a 3C?
>> >>>>Or are you saying that your limited experience has never encountered
>> >>>>such code?
>> >>>>Or maybe you're just not reading the question.
>> >>>
>> >>>
>> >>>The text seems pretty clear, try reading it again.
>> >>
>> >>Not sure that the text is clear, but this might be interesting
>> >>to the OP?
>> >>
>> >>http://www.geocities.com/SiliconValley/Lakes/3947/
>> >>
>> >>
>> >
>> >
>> > What's not clear?
>> > -No. It means that the IR protocol implemented by the 3C is not a standard
>> > implemented on Windows, and that PsiWIN doesn't recognise it, and never
>> > will.
>> >
>> Ok, let's get really clear by quoting the original request.
>> start quote
>> Any advice on how to link 3C to standard Laptop IR port?
>> Speeds comms formats etc
>> end quote
>>
>> I don't see any restrictions on software. The guy wants a way to do it,
>> as do I.
>> Repeat!!! no mention of PSIwin or any standard protocol or any specific
>> application on either end of the transfer. I'm CERTAIN
>> that a protocol exists and that it's quite possible to do the transfer.
>
> Even if the HARDWARE-SUPPORTED protocols are incompatible?
>
> If you're so damned certain it can be done, why don't you read up on it
> and do it?

IrComm is certainly available for Win. It's a port of the Linux IrDa
stack, and I use it to connect a Win2k machine to a Psion 5mx (which
is also said to be 'impossible' or some other such nonsense.

I'm not sure what you mean by a 'hardware supported' protocol, are you
in possession of some design details of the Psion3C which are useful
and/or important for writing IR software?

The link I provided has software which can use the Psion3C's ir port
to transfer files to and from a Windows PC, which would rather suggest
that you don't know what you're talking about.

--
| Mark Kent -- mark at ellandroad dot demon dot co dot uk |
Isn't air travel wonderful? Breakfast in London, dinner in New York,
luggage in Brazil.

On Sunday, in article <5scu9c.pj3.ln@ellandroad.demon.co.uk>
mark.kent@demon.co.uk "Mark Kent" wrote:

> The link I provided has software which can use the Psion3C's ir port
> to transfer files to and from a Windows PC, which would rather suggest
> that you don't know what you're talking about.

In this instance it would seem so. I was under the misapprehension that
the 3C was not IrDA compliant - hence none of the standard protocols
(IrCOMM, IrTTY, etc...) would mean a thing. I was clearly misinformed,
or misunderstood the conversation.
--
Raj Rijhwani | This is the voice of the Mysterons...
raj@rijhwani.org | ... We know that you can hear us Earthmen
http://www.rijhwani.org/raj/ | "Lieutenant Green: Launch all Angels!"

Am 06.06.2004 19:47 hub Raj Rijhwani aber zu reden an und sprach:

>>Mark Kent" wrote:
>
>> The link I provided has software which can use the Psion3C's ir port
>> to transfer files to and from a Windows PC, which would rather suggest
>> that you don't know what you're talking about.
>
> In this instance it would seem so. I was under the misapprehension that
> the 3C was not IrDA compliant - hence none of the standard protocols
> (IrCOMM, IrTTY, etc...) would mean a thing. I was clearly misinformed,
> or misunderstood the conversation.

No, you were right. The 3c does *not* speak standard IrDA, and the software
mentioned mimics the special 3c infrared protocol to transfer files.

This is why a 3c and a 5 (mx/pro) cannot "talk" to each other via infrared.
The 5 series talks standard IrDA.

My $0.02

R/\LF

On Sunday, in article
Ralf@Eichler.com
"Ralf Eichler" wrote:

> No, you were right. The 3c does *not* speak standard IrDA, and the software
> mentioned mimics the special 3c infrared protocol to transfer files.

OK, so I was half right. But I was under the impression (false, clearly)
that the 3c Ir hardware was not even IrDA compatible, never mind the comms
protocol. If there's software that can fudge it, there must be some
degree of compatibility in the hardware.

> The 5 series talks standard IrDA.

Yes, I know that. I've used it many a time to talk to printers, mobile
phones, laptops, etc.
--
Raj Rijhwani | This is the voice of the Mysterons...
raj@rijhwani.org | ... We know that you can hear us Earthmen
http://www.rijhwani.org/raj/ | "Lieutenant Green: Launch all Angels!"

Am 07.06.2004 01:12 hub Raj Rijhwani aber zu reden an und sprach:

> ... I was under the impression (false, clearly)
> that the 3c Ir hardware was not even IrDA compatible, never mind the comms
> protocol.

There is a chance that someone with enough knowledge of the 3c interiors
may be able to write a true IrDA driver for it, because the _hardware_ (IR
transmitter and receiver) are interoperable. But I doubt that it will be
able to transfer at high speed - because all IrDA protocol would have to be
done by software - and not by hardware, as in all newer machines.

R/\LF