Connecting the device via IR?

For simply transfering files via IrDA, could you not use Total Commander and copy them back and forth that way? (obviously that's not transfering via ActiveSync though)
Also, you haven't mentioned what CPU architecture your box is, that can be helpful for trying to assist when you ask for help

I tried IR to try connecting my units to my computers and i couldnt get it to work. I have the unit still and i have a XP computer im working on building (kinda waiting for parts and twiddling my thumbs).

Can you try dissecting these cabs? They were USB irda drivers for x86 CE 5.0 Maybe they can help?

If i recall correctly some have an IrDA utility

https://www.hpcfactor.com/downloads/details.asp?r={B6286A96-9CDF-4BB8-97BC-39FBE1C4174C}&highlight=MCS7780_WinCE.zip
https://www.hpcfactor.com/downloads/details.asp?r={9784C3E6-300D-446F-9E14-0B66D5D11076}

If the cabs don't install, use this to extract the cab on desktop windows

https://www.hpcfactor.com/scl/2052/Unknown_or_not_specified/MSCEInf/version_2.6

I tried IR to try connecting my units to my computers and i couldnt get it to work. I have the unit still and i have a XP computer im working on building (kinda waiting for parts and twiddling my thumbs).

The MosChip is actually device I'm using on my host PC I wish I could duplicate the device

I feel like this is a separate topic, do you think you could make a separate thread?

Lemmi try finding it. I am still waiting on parts for the XP computer, so it may work with the XP machine. But i tried Windows 7/8/10/11 and different versions of Mac OS and had zero luck. It may work perfectly with an XP machine ? I have no idea. Ill dig up the unit i have and let ya know once the parts im waiting on for the XP computer come this week. :-)

I got MANY projects all going on haha.

Although quite lightweight, the IrDA subsystem in Windows is now an optional component as 99% of users will not require it. To enable it, so that you can develop with InTheHand.Net.IrDA, or to use the built-in file transfer functionality, you'll need to follow these steps:-

Open Settings
Open Apps
Select "Optional features"
Select "+ Add a feature"
Select the checkbox next to "IrDA Infrared"
Click "Install"
These steps are almost identical for Windows 11, although some of the screens will look different.

Once you install this feature, and you have a supported IrDA adapter, the OS will automatically handling incoming Object Push requests. It will pop up a dialog to save an incoming file. If you want to use the ObexListener instead you must stop the "irmon" Windows Service. This can be done either through the administration tools in Windows or programmatically using ServiceManager, but the latter requires your app to run with administrative permissions (showing a UAC prompt).

If the IR port is acting as a keyboard input device then either it is wired in directly as a human interface device, in which case that identity will be part of the chip on its USB controller and you are not going to be able to change it.

If however it is a serial FIR port and there is a driver DLL performing the conversion into ASCII, then in theory, you might be able to change the driver to re-use the COM port with ActiveSync. You are going to have to look through the HKLM driver sections and look at the device COM port availability to ascertain what my be what. If it is a standard serial port then in theory you could take the registry and (if needed) driver from another CE device, import it and is might work.