I have a refurbished nortel applications module (NAM) v 4.1 that runs my voicemail.
I have the nortel software to interface with it via tcp/ip, but i am unable to connect. the ethernet interface does light up and have activity when plugged in. I have been having a lot of trouble finding information about how to check the tcp/ip config on the nam - i have hooked up a monitor and keyboard to it and can tell that it runs OS/2 3.1 and that the ethernet interface is enabled in the bios.
i cannot seem to get to the command line - right after boot up, i see the c:\ prompt, but the os continues to load os2you 3.2 "limited host interface...". It says use ctrl + break to exit, but those keys do nothing....
Any ideas would be great...this older nortel stuff has been a real bear...
There are two function key combinations that can be activated while the white blob appears on the screen followed by the word OS/2. These are alt-F1 which will interrupt the boot process and take you to a recovery menu, and alt-F2 which will continue the boot while displaying the name of each device driver as it is loaded.
The recovery menu that comes up when you press alt-F1 contains a number of options to help you in getting your system to start although in some cases your system may not be recovered by these as well as you might like. Options contained in this menu include:
ESC to continue with the normal boot process F2 to boot to a command line without starting the graphical interface. From here you can run MAKEINI to rebuild your desktop or use TEDIT (a small command line editor) to fix corrupted files. F3 to reset the video mode back to VGA, bypassing the installed graphics driver. A useful option if your video driver gets corrupted or you set it up incorrectly. F4 to restart the system with a maintenance desktop. From here you can use the selective reinstall option to rebuild the corrupted part of your system. F5 enables FULL hardware detection. F6 disables hardware detection. This is useful if you have problems with plug and play adapters. 0 recovers from the original archive of your system setup that was taken when your system was first installed. 1, 2, or 3 to restart from one of the last three archives that you created. Any other custom configurations that you have created and added to the menu by updating the ALTF1BOT.SCR file. Using alt-F2 to display the drivers as they are loaded will help you to identify the driver giving the problems if your system hangs part way through the boot process.
Found out that I had to do a Feature 915 (in my case F922) to make the nam capable of being managed locally - some sort of monitor package installed.
I used tcpcfg to set an ip - restarted and double checked - can not ping address or loopback (when enabled).
I have used mpts to check the installed NICs - just shows "ibm parallel port" with 0-ibm os/2 netbios 0-ibm tcp/ip i switched the 0 on tcp/ip to 1, rebooted, and seems that I can ping the loopback and my address just fine. But i can't ping anything else, and PCs can't ping the nam. I thought that the parallel port thing was perhaps normal - the nic is on an all-in-one IBM 586VE single board computer.
Am wondering if I should install another NIC, but I am unsure of which one to use - I can't open the thing since it has warranty stickers on it. I am assuming that these things only use a couple of nics - but i am unsure about configuring it manually, and I DO NOT want to crash this thing...
Would F5 (full hardware detection) detect and install the NIC and perhaps save the day? Or does this really screw with settings and should be avoided?
Read the following : http://www.tek-tips.com/viewthread.cfm?qid=1362190&page=1 Here you will find a total explanation about installing the nortel nam Also is written that only some nic are possible to use and it has to be isa Furthermore I quote:I can't open the thing since it has warranty stickers on it When installing configuring etc with os/2 you sometimes have to open the case becasue a lot of hardware is not supported. If still you cant get this to work can you give me the specification about the hardware you are using
