| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 471.1 | Part of the answer.. | LANDO::CUMMINS | | Fri Feb 07 1997 09:18 | 3 |
| The 4100 does indeed have EISA slots. Five PCI slots and three
additional slots that can be consumed with EISA/ISA options or
PCI options.
|
| 471.2 | built-in | MOVMON::DAVIS | | Fri Feb 07 1997 09:45 | 11 |
| The KCRCM is not supported on the 4100 because this functionality
is built into the combo module.
The prototype systems did not have the combo module, the KCRCM
was used to debug the functionality, but all revenue systems have a
combo board.
What do you need that isn't already there?
Todd
|
| 471.3 | | POBOXB::BAK | | Fri Feb 07 1997 09:47 | 7 |
| Hi,
No need to order a KCRCM.....it's already built into the base system drawer.
Refer to Users Guide for commands.
Dennis
|
| 471.4 | All there - thanks | BIS1::DOOSJE::HERTA | For something fulfilled this hour, loved, or endured | Fri Feb 07 1997 11:47 | 5 |
| Great! I clearly did not look into all the details.
Thanks for your quick responses.
Herta
|
| 471.5 | connect to RCM without hitting ^] ? | DOOSJE::HERTA | For something fulfilled this hour, loved, or endured | Mon Feb 10 1997 04:14 | 6 |
| We attached serial port 1 to a DECserver and connect to the console via a telnet
listener. This works fine for most of the console operations, but evidently not
for RCM commands: to enter RCM you need to type ^]^]rcm, and the first control
happily kicks you out of telnet. Is there a way to bypass this?
Herta
|
| 471.6 | | LANDO::CUMMINS | | Mon Feb 10 1997 10:01 | 8 |
| Yes, connect a serial line to COM1/RCM. Now type the escape sequence to
drop into RCM firmware.. ^]^]RCM.
When at the RCM> prompt, modify the escape sequence to something else
using the RCM>setesc command. An RCM>status command will display
current firmware status, including the escape sequence.
BC
|
| 471.7 | which modem? | DOOSJE::HERTA | For something fulfilled this hour, loved, or endured | Wed Feb 12 1997 05:02 | 14 |
| Our telecom department recently replaced most of the Digital internal modems with
U.S. Robotics modems, and we had to get similar modem cards for our portables due to
incompatibilities with Multitechs. To avoid further compatibility problems, the
U.S. Robotics Sportster DATA/FAX Modem would be our choice to connect to the 4100.
When our secretary wanted to order one, she was given a list of three modems
that answer the description:
1. Sportster V.34 External Fax/Data Modem (BE)
2. Sportster V.34 External Fax/Data Modem (BE) + Netlink
3. Sportster V.34 External Fax/Data Modem (CCITT)
Will any of these do? Any preference?
Herta
|
| 471.8 | Sportster modem no longer supplied | DOOSJE::HERTA | For something fulfilled this hour, loved, or endured | Mon Feb 17 1997 04:11 | 13 |
| In absence of a reply, I contacted our supplier to try and get more info on the
modems. They say the Sportster modems have been replaced by
1. U.S. Robotics Voice 33.6 V34+ Modem - External
2. U.S. Robotics Voice 33.6 V34+ Modem - External (CCITT)
What makes a given modem supported? The fact that it has been tested? Should I
select the CCITT compliant modem, or the other one?
If there is a more appropriate place to ask this, or a person I might contact,
please let me know. The system must be shipped March 3, which does not leave me
much time.
Herta
|
| 471.9 | | SERIES::CIAFFI | | Tue Feb 18 1997 09:45 | 16 |
| The only thing that makes a modem supported is if we've tried it and it
works. There wasn't much of a procedure in place for testing modems when
the kcrcm was developed.
The basic idea is to set up the modem for no-echo (e0), verbose mode off (v0),
factory config (&f0), minimal response (x0) and auto answer off (s0=0).
So when you go to set your modem init string from the SRM console the string
you use would look something like this: at&f0e0v0x0s0=0. Some modems require
slightly different switches to give the same results so you'll have to try
it a few times.
Personally I haven't had good luck with the US Robotics modems.
hope this helps,
Marco
|