I recently installed JRed on a Windows ME notebook and discovered that Windows ME and Windows 2000 have changed the API for accessing infrared ports. The good news is that the new API is socket-based, and is pretty easy to develop with. The bad news is that by default, Microsoft hogs up the OBEX services, which means JRed's OBEX implementation won't work.
It's easy to disable Windows file transfer, which I hoped would free up the OBEX service. Unfortunately, there appears to be no way in ME to add new services. The API is there but it returns an error saying the option is not available.
If anybody has a clue about IR programming in the new Windows API, I'd appreciate any info you can provide.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I recently installed JRed on a Windows ME notebook and discovered that Windows ME and Windows 2000 have changed the API for accessing infrared ports. The good news is that the new API is socket-based, and is pretty easy to develop with. The bad news is that by default, Microsoft hogs up the OBEX services, which means JRed's OBEX implementation won't work.
It's easy to disable Windows file transfer, which I hoped would free up the OBEX service. Unfortunately, there appears to be no way in ME to add new services. The API is there but it returns an error saying the option is not available.
If anybody has a clue about IR programming in the new Windows API, I'd appreciate any info you can provide.
Try irCOM2k
http://www.wintotal.de/Software/index.php?rb=8&id=426
creates a virtual COM-Port for the infra-red-port