|
Moderator H/PC Vanguard Posts: | 2,832 |
Location: | Choking on the stench of ambition in Washington DC | Status: | |
| Is it possible, through the registry, to create a RAW IR port (COM 4)?
Jake |
|
|
|
Administrator H/PC Oracle Posts: | 18,011 |
Location: | United Kingdom | Status: | |
| I would make for an interesting experiment.
Let's have a go.
HKLM\Drivers\BuiltIn\IrDA
Schema: <Name> <type> <Value>
Tsp String Unimodem.dll
DeviceArrayIndex DWord 2
Prefix String COM
Dll String Serial.Dll
Order DWord 1
Index DWord 4
DeviceType DWord 2
FriendlyName String Raw Infrared COM4
All it's doing is hooking the hayes modem and serial driver, both of which CE2 have. |
|
|
|
Moderator H/PC Vanguard Posts: | 2,832 |
Location: | Choking on the stench of ambition in Washington DC | Status: | |
| Okay, I'll play with this and see what I get.
A couple of questions before I start:
1) I already have HKLM\Drivers\BuiltIn\IrDA that sets up "Infrared port on Com5:" Are you suggesting that I modify this section? Or should I start a new key? If I do hack the existing key, what do I lose by abandoning "Infrared port on Com5:" ?
2) What you suggest as a test for IR Raw to see if it actually works? I have an IR port on my laptop. Would Hypterterminal be of assistance here? Or some other program?
This is intriguing,
Jake |
|
|
|
Administrator H/PC Oracle Posts: | 18,011 |
Location: | United Kingdom | Status: | |
| If there is already a COM5 port setup then it could mean that COM4 is being used. When you setup a new connection, what is the COM5 doing, is it already a raw port, what drivers is it using?
Pass I'm afraid, I have never had a need of using this before, you use IrCOMM for all other connections that I've used, using the Infrared Data Association Protocol. The RAW connection is literally used to bypass the protocol and flash the LED. Hence why I've never thought to try this. |
|
|
|
Moderator H/PC Vanguard Posts: | 2,832 |
Location: | Choking on the stench of ambition in Washington DC | Status: | |
| "Infrared port on Com5:" is using "Serial.Dll"
In Remote Networking, I have options for "Generic Infrared Modem on COM3:" and the same heading continues thru COM6
Internal Modem is COM4
However, in the COM5 specs in the reg, I do not have a Tsp String Unimodem.dll
Is it still worth hacking, do you think?
Jake |
|
|
|
Administrator H/PC Oracle Posts: | 18,011 |
Location: | United Kingdom | Status: | |
| I would say that your deivce has COM5 setup as the RAW port.
Sounds like you have the Combi GenIrDA driver installed too. I would take it off and use the specific one for your system's needs. You don't want to introduce a comflict in the port manager.
Can you pate up the entire set of registry information for the COM5 port? |
|
|
|
Moderator H/PC Vanguard Posts: | 2,832 |
Location: | Choking on the stench of ambition in Washington DC | Status: | |
| Hi, Chris,
Here's the reg info:
Devconfig: 10 00 00 00 05 00 00 00 10 01 00 00 00 4B 00 00
00 00 08 00 00 00 00 00 00
Friendlyname: Infrared port on COM5:
Order: 3
Index: 5
Dll: Serial.Dll
Prefix: COM
DeviceArrayIndex: 2
What do you think?
Jake |
|
|
|
Administrator H/PC Oracle Posts: | 18,011 |
Location: | United Kingdom | Status: | |
| I would suggest that out aim here is to make it appear in the ports list in make new connection.
If you want the device to be available as a Direct Cable Connection, set the DeviceType to 6.
If you want the device to be available as a Dial-up Connection, set the DeviceType to 2
Obviously if you want to use it as a dial-up connection you will need to add the Telephony Service Provider (TSP) unimodem.dll line. |
|
|
|
Moderator H/PC Vanguard Posts: | 2,832 |
Location: | Choking on the stench of ambition in Washington DC | Status: | |
| Hi, Chris,
If I do get an IR Raw port working, what's the easiest way to test it?
Jake |
|
|