| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3662.1 | | STRWRS::KOCH_P | It never hurts to ask... | Wed Jun 26 1996 22:50 | 15 |
|
Well, I've gotten a little farther, but I can't diagnose the problem.
Microsoft ODBC is already installed on my system from previous
requirements. However, when I try and start clearVISN Router Manager,
it won't start. The error is:
cannot initialize socket library error 11004 no data record available
and then
cannot initialize the instance of the networking window
I suspect that I don't have a variable defined or a path is incorrect
in one of the many .ini files. Does anyone know what may be causing
these errors?
|
| 3662.2 | step by step | VNASWS::ANDREAS | | Fri Jun 28 1996 14:07 | 16 |
|
>> cannot initialize socket library error 11004 no data record available
>> and then
>> cannot initialize the instance of the networking window
This is the same error I got if I install Multi-Chassis manager after I have
previously installed RM Autobahn V3.0 (from Diskettes, not from the CLvisn-
package).
Look again at the installation procedure and see what the changes are
for "btrieve" in the WIN.ini file if you only install MCM.
-Andy
|
| 3662.3 | Don't need RM to get TFTP Server | NETCAD::FORINO | | Tue Jul 09 1996 13:50 | 9 |
| You do not need to install Router Manager to get the TFTP Server. The
TFTP Server is part of the clearVISN Core that you get by default at
installation. These core files exist under the clearVISN Router icon.
You always get this icon at installation but you don't get Router
Manager or Router Configurator under it unless you install those
applications as well. If you don't install them you just get the
core files under that icon.
John
|
| 3662.4 | | STRWRS::KOCH_P | It never hurts to ask... | Tue Jul 09 1996 14:19 | 12 |
|
Yes, I understand this, however, I do disagree with the implementation.
The fact is that the TFTP server is tied to the router manager and you
have to read the documentation to figure out what to do. In my mind,
this makes it more difficult to use. If you had simply created an icon
labelled TFTP server, the problem would have been mitigated. Also, the
fact that a button wasn't added to the HUBloader screen which would
automatically start the TFTP server and make the starting of the TFTP
server a customer choice, it would have made things simpler.
I'm whining here, but I'm a field SE and customers do complain about
these types of things.
|
| 3662.5 | Implementation could have been more straight-forward... | NETCAD::BATTERSBY | Don't use time/words carelessly | Tue Jul 09 1996 15:58 | 7 |
| I'll have to side with Ted on this one. Making things "simple"
to understand goes a long ways toward helping customers get over
these obstacles, and maintaining their favor towards our products.
This seems to have been forgotten somehow in the method of
implementation chosen for the TFTP server startup.
Bob
|