5 Aug
2003
5 Aug
'03
12:40 p.m.
Hi,
I need some help with Procomm. I've been trying to log onto an Intel
320 computer that runs iRMX. I have a terminal connected to the Intel and
I've been able run the diagnostics and to load the OS and boot up but
didn't have the correct account names or passwors to log into the system. I
searched the net last night and found some iRMX manuals. Read them and
found a couple of default account names and passwords. Today I tried them
on the 320. The Superuser password didn't work but one of the regular
account names and password did work so I was able to get into the system.
:-) But once it logged in it executed the user profile and that changed the
terminal setting so that all I got was garbage. :-( (I'll go back to
reading and see if there's a way to stop it from executing the user
profile.) I also tried using a PC with Procomm as a terminal. Procomm will
emulate a lot of terminals and I thought that maybe one of them would
display properly. But I could never get Procomm to work. It always said
"Off-line" and I could never get anything to display on the screen. Data
was going out to the computer and data was coming back from it but none of
it showed up on the screen or in the log file. Any ideas? I'm guessing
some kind of handshaking problem. I connected up my data display boxs with
about six LEDs connected to the most important signal lines and everything
looked fine so it must be one of the less common signals. I used the same
cable and connected it to a terminal and set it for the same baud rate, #
of data and stop bits, parity etc and it worked fine. Also tried another
cable and it worked for the terminal but not for the PC with Procomm. I
have used this same PC with Procomm and the same cable to successfully
connect to other older Intel boxs with no trouble. Anyone have any idea why
Procomm doesn't recognize this system?
Joe
5 Aug
5 Aug
2:26 p.m.
Under Options->System Options->Modem Connection...->Modem Connection
Properties...->Use Hardware Handshaking is the option for hardware
handshaking. Out of the box Procomm has hardware handshaking enabled, so
this could possibly be your problem. I usually leave the three checkboxes
unchecked, except in the rarest of cases.
I would also make sure you're connected to the com port, and not through a
modem connection (down in the status line at the bottom, 3rd box from the
left, you can click to select the com port. direct connect-Com1 is most
typical.
Sorry if any of this is obvious (like the com ports). I dunno what your
familiarity is with ProComm.
--John
P.S. Hyperterm sucks, Procomm rocks. We have some embedded products with
serial ports, and when our client tells us they're using Hyperterm, we tell
them we don't support it. It's too buggy.
On Tuesday 05 August 2003 13:34 pm, Joe wrote:
Hi,
I need some help with Procomm. I've been trying to log onto an Intel
320 computer that runs iRMX. I have a terminal connected to the Intel and
I've been able run the diagnostics and to load the OS and boot up but
didn't have the correct account names or passwors to log into the system. I
searched the net last night and found some iRMX manuals. Read them and
found a couple of default account names and passwords. Today I tried them
on the 320. The Superuser password didn't work but one of the regular
account names and password did work so I was able to get into the system.
:-) But once it logged in it executed the user profile and that changed the
terminal setting so that all I got was garbage. :-( (I'll go back to
reading and see if there's a way to stop it from executing the user
profile.) I also tried using a PC with Procomm as a terminal. Procomm will
emulate a lot of terminals and I thought that maybe one of them would
display properly. But I could never get Procomm to work. It always said
"Off-line" and I could never get anything to display on the screen. Data
was going out to the computer and data was coming back from it but none of
it showed up on the screen or in the log file. Any ideas? I'm guessing
some kind of handshaking problem. I connected up my data display boxs with
about six LEDs connected to the most important signal lines and everything
looked fine so it must be one of the less common signals. I used the same
cable and connected it to a terminal and set it for the same baud rate, #
of data and stop bits, parity etc and it worked fine. Also tried another
cable and it worked for the terminal but not for the PC with Procomm. I
have used this same PC with Procomm and the same cable to successfully
connect to other older Intel boxs with no trouble. Anyone have any idea why
Procomm doesn't recognize this system?
Joe
2:33 p.m.
On Tue, 5 Aug 2003, J.C. Wren wrote:
P.S. Hyperterm sucks, Procomm rocks. We have some
embedded products with
serial ports, and when our client tells us they're using Hyperterm, we tell
them we don't support it. It's too buggy.
Pff. I use Reflection for the
same reasons ;-)
(and get Telnet, SSH, X11 and LAT for free with it ;-)
--f
2:49 p.m.
At 07:23 PM 8/5/03 -0400, you wrote:
Under Options->System Options->Modem
Connection...->Modem Connection
Properties...->Use Hardware Handshaking is the option for hardware
handshaking. Out of the box Procomm has hardware handshaking enabled, so
this could possibly be your problem. I usually leave the three checkboxes
unchecked, except in the rarest of cases.
I would also make sure you're connected to the com port, and not through a
modem connection (down in the status line at the bottom, 3rd box from the
left, you can click to select the com port. direct connect-Com1 is most
typical.
Sorry if any of this is obvious (like the com ports). I dunno what your
familiarity is with ProComm.
Sounds like you have a newer version than mine. Mine is 1.1B IIRC. It has
boxs that say Yes or No or you can enter things like Half or Full in the
Duplex entry. It has two places for handshaking, one is for software
(XON/XOFF) and the other for hardware (CTS/DTR). You can turn each on or
off individually. I've tried every combination of Off and On but it doesn't
make a difference. I am connected to the corrrect port (2) if I switch it
to Comm 1 the various ready lights on the breakout box all go out.
Joe
4:16 p.m.
Mine is 4.8. I have a real copy, but I think there is (or was) a 30-day eval
version on their website. I only stick with it because it's what I'm used
to, and I have a number of macros.
The important thing about selecting a com program is not that it must be
ProComm, but that it must NOT be HyperTerm (or HyperDooDoo, as we refer to
it. I really don't understand what strangle hold those people have on MS. I
mean, OK, put aside one's hate for MS, it's the worst product they ship, and
not representative of the rest of Windows).
--John
On Tuesday 05 August 2003 15:47 pm, Joe wrote:
At 07:23 PM 8/5/03 -0400, you wrote:
Under Options->System Options->Modem
Connection...->Modem Connection
Properties...->Use Hardware Handshaking is the option for hardware
handshaking. Out of the box Procomm has hardware handshaking enabled, so
this could possibly be your problem. I usually leave the three checkboxes
unchecked, except in the rarest of cases.
I would also make sure you're connected to the com port, and not through
a modem connection (down in the status line at the bottom, 3rd box from
the left, you can click to select the com port. direct connect-Com1 is
most typical.
Sorry if any of this is obvious (like the com ports). I dunno what your
familiarity is with ProComm.
Sounds like you have a newer version than mine. Mine is 1.1B IIRC. It has
boxs that say Yes or No or you can enter things like Half or Full in the
Duplex entry. It has two places for handshaking, one is for software
(XON/XOFF) and the other for hardware (CTS/DTR). You can turn each on or
off individually. I've tried every combination of Off and On but it doesn't
make a difference. I am connected to the corrrect port (2) if I switch it
to Comm 1 the various ready lights on the breakout box all go out.
Joe
5:18 p.m.
At 09:13 PM 8/5/03 -0400, John wrote:
Mine is 4.8. I have a real copy, but I think there is
(or was) a 30-day
eval
version on their website. I only stick with it because
it's what I'm used
to, and I have a number of macros.
I have a real copy too. Just a real OLD copy! :-/
Joe>
6 Aug
6 Aug
5:49 a.m.
On Tue, 5 Aug 2003, Joe wrote:
At 09:13 PM 8/5/03 -0400, John wrote:
Does 1.0 for DOS or Procomm Plus 2.0 for DOS (which not long ago cost me
$5 boxed, at a second hand book sale) count? IMHO, Procomm Plus 2.0 for
DOS is perfect except that it does not have settings for baud rates higher
than 115200 (and how often do you need those anyway?)
-Toth
Mine is 4.8. I have a real copy, but I think
there is (or was) a
30-day eval version on their website. I only stick with it because
it's what I'm used to, and I have a number of macros.
I have a real copy too. Just a real OLD copy! :-/ 
5 Aug
5 Aug
5:40 p.m.
I've sucessfully used HyperTerminal to term into the controller boxes
for Brown and Sharpe MicroVal Coordinate Measuring Machines, and
Motorola Single Board Computers. It works quite well for me. Ages ago
I'd used ProComm and Telix. With all of the above, if it isn't working, you
probably don't have it set up correctly. Period.
At 09:13 PM 8/5/03 -0400, you wrote:
Mine is 4.8. I have a real copy, but I think
there is (or was) a
30-day eval
version on their website. I only stick with it because it's what I'm used
to, and I have a number of macros.
The important thing about selecting a com program is not that it
must be
ProComm, but that it must NOT be HyperTerm (or HyperDooDoo, as we refer to
it. I really don't understand what strangle hold those people have on MS. I
mean, OK, put aside one's hate for MS, it's the worst product they ship, and
not representative of the rest of Windows).
--John
On Tuesday 05 August 2003 15:47 pm, Joe wrote:
At 07:23 PM 8/5/03 -0400, you wrote:
> Under Options->System Options->Modem Connection...->Modem Connection
>Properties...->Use Hardware Handshaking is the option for hardware
>handshaking. Out of the box Procomm has hardware handshaking enabled, so
>this could possibly be your problem. I usually leave the three checkboxes
>unchecked, except in the rarest of cases.
>
> I would also make sure you're connected to the com port, and not
through
> a modem connection (down in the status line
at the bottom, 3rd box from
> the left, you can click to select the com port. direct connect-Com1 is
> most typical.
>
> Sorry if any of this is obvious (like the com ports). I dunno
what your
> >familiarity is with ProComm.
>
> Sounds like you have a newer version than mine. Mine is 1.1B IIRC. It has
> boxs that say Yes or No or you can enter things like Half or Full in the
> Duplex entry. It has two places for handshaking, one is for software
> (XON/XOFF) and the other for hardware (CTS/DTR). You can turn each on or
> off individually. I've tried every combination of Off and On but it doesn't
> make a difference. I am connected to the corrrect port (2) if I switch it
> to Comm 1 the various ready lights on the breakout box all go out.
>
> Joe
7606
days inactive
7607
days old
7 comments
5 participants
participants (5)
-
jcwren＠jcwren.com -
mail.list＠analog-and-digital-solutions.com -
rigdonj＠cfl.rr.com -
tothwolf＠concentric.net -
waltje＠pdp11.nl