Invalid serial port spec

[1/9] from: greggirwin:mindspring at: 5-Nov-2001 13:46

Quick question, I want to open a serial port under Win2K. system/ports/serial contains: [com1 com2] My modem uses com3. I think it's one of those kitchen-sink modem cards that does sound and other stuff too. I get an "invalid port spec" error when I try to open port3 (also tried open join serial:// ['com3]). Any ideas, or do I have to use Windows Comm functions to access ports not listed by REBOL? As a twist, I need an open ended solution (i.e. not just for com3) as the machine will have a modem *pool* I'll need to access. (com16...calling com16...come in...) Thanks! --Gregg

[2/9] from: ryanc:iesco-dms at: 5-Nov-2001 12:59

This is because the serial port scheme expects com1 to be called port1 in this case. I heard somewhere that rebol cant garantee that com1 is going to be port1, but it has seemed to hold true on all implementations I have experimented with so far. Here is an open spec for the serial port that I was using to test something with this morning... sp: open/binary/direct serial://port1/2400/8/none/1 --Ryan Gregg Irwin wrote:

[3/9] from: ryanc:iesco-dms at: 5-Nov-2001 13:21

<SNIP> > Any ideas, or do I have to use Windows Comm functions to access ports not

<<quoted lines omitted: 3>>

> Thanks! > --Gregg

</SNIP> Also know that support for more than 4 serial ports has been historically sketchy for many programs. I would be a little cautious until I found out for sure that REBOL can indeed talk to these higher ports. I would like to think that such legacy architecture issues have been long put to rest, but... --Ryan

[4/9] from: holger:rebol at: 5-Nov-2001 13:28

On Mon, Nov 05, 2001 at 01:46:36PM -0700, Gregg Irwin wrote:

> Quick question, > > I want to open a serial port under Win2K. > > system/ports/serial contains: [com1 com2] > > My modem uses com3. I think it's one of those kitchen-sink modem cards that > does sound and other stuff too.

At the beginning of your script, or in your user.r set system/ports/serial: [com1 com2 com3] Then open your serial port with port3. Same technique for higher-numbered ports. -- Holger Kruse [holger--rebol--com]

[5/9] from: holger::rebol::com at: 5-Nov-2001 13:29

On Mon, Nov 05, 2001 at 12:59:03PM -0800, Ryan Cole wrote:

> This is because the serial port scheme expects com1 to be called port1 in this > case. I heard somewhere that rebol cant garantee that com1 is going to be > port1, but it has seemed to hold true on all implementations I have experimented > with so far.

REBOL maps port1 to whatever is defined in system/ports/serial. REBOL sets that block to reasonable defaults, but it can be changed by the the user. -- Holger Kruse [holger--rebol--com]

[6/9] from: greggirwin:mindspring at: 5-Nov-2001 14:43

Thanks Holger!!! I didn't even think about trying to override it. DOH! --Gregg

[7/9] from: greggirwin:mindspring at: 5-Nov-2001 14:44

Hi Ryan, << Also know that support for more than 4 serial ports has been historically sketchy for many programs. I would be a little cautious until I found out for sure that REBOL can indeed talk to these higher ports. I would like to think that such legacy architecture issues have been long put to rest, but... >> The other hope is that the modem pooling device will handle the details and I'd just need to have a single port to deal with. --Gregg

[8/9] from: amicom:sonic at: 6-Nov-2001 6:33

I've had success with serial ports up to and including COM6 when writing a dumb terminal emulator using REBOL/View. -Bo

[9/9] from: greggirwin:mindspring at: 6-Nov-2001 10:58

Hi Bo, << I've had success with serial ports up to and including COM6 when writing a dumb terminal emulator using REBOL/View. >> Good to know. Thanks! --Gregg

Notes

Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted