NAM serial connection to Windows XP

[bekcom]

Trying to hook up a laptop to the serial port on a nam but cannot get a connection. I have tried the setup in the FAQ but it is different in XP.

Thanks

Norm




Old ROLMan working on Norstars

 

[curlycord]

What part is different?

Which version NAM or you hooking up too?

 

[curlycord]

Also what is it you need to do? why are you trying to connect via serial?.

 

[bekcom]

Just trying to get some reports for a customer. Loks like when I do the FAQ setup I cannot get past the part were you assign it to a com port. Yhe screen says selected ports but there is nothing to select.


Old ROLMan working on Norstars

 

[lugerlover]

thought u could run reports via telset then just hook up printer to printer port???.Or use vm manager to do on screen...not sure if vm manager worked on xp???

 

[curlycord]

Yes you can do both, NVM requires NIC card and phantom modem file.

Sounds like your XP does not know you have a com port maybe.

Go to Control panel/System/Device Manager/PORTS and see what is listed.

 

[bekcom]

You are right, I am missing the nvmppp2.inf file. I will have to search to find a copy on the net somewere.

Thanks




Old ROLMan working on Norstars

 

[curlycord]

Another thread that might help:

http://www.tek-tips.com/viewthread.cfm?qid=1220064&page=1

Not sure if you will find it but do this....

Copy below to notepad then save as -select ALL FILES and name it nvmppp2.inf

Cheer


; NVMPPP2.INF
; Modified from example modem installation scripts

; Allow a win95 PC to use a direct dial up connection
; (i.e. installs a direct dial up device)

; Should already have installed Dial up networking with the
; TCP/IP protocol on your win95 PC

; steps
; 1) Copy this file to your Win 95 PC
;
; 2) Go to the control panel and double click the "Modems" icon.
; If a modem has previously been installed, click on the
; "ADD" button. If a modem has never been installed, a
; "Install New modem" dialog box is presented right away, without
; being prompted to press a button for "ADD", "Remove",
; or "Properties".
; 3) On the "Install New modem" dialog box, check
; "Don't detect my modem" box
; 4) Click the "Next>" button.
; 5) Click on "Have disk"
; 6) In the next dialog box enter the path to the file that
; you copied in step one
; 7) Click on "Direct Serial Connection"
; 8) Click on the "Next>" button.
; 9) Click on the port where you direct connection is going to be on
; this windows PC.
; (If you want to use the first serial port of your PC to
; communicate with the serial port on the NAM, choose
; COM1. Laptops commonly only have COM1).
; Then click on the "Next>" button. Quite often COM1.
; 10) Windows takes a few seconds to install this new device
; driver. After it is done, click the "Finish"
; button. The title of the modem, "Direct Serial connection"
; should appear in the next window.
; 11) Click "OK"
; 12) Go into dial up networking and make a new
; connection.
; 13) When the dialog box comes up select the Direct Serial
; Connection as your modem. GIve a name for this type of connection
; in the "Type a name for the computer you are dialing" field. An
; example name would be, "NAM Serial Port".and click configure.
; 14) Set the speed to 19200.
; 15) Choose the "Connection" tab, and remove the check for "Wait for
; dial tone befor dialing" and change the "Cancel the call if not
; connected within 60 secs" to be 0 seconds. Do NOT REMOVE THE
; check from the box! (If you remove the check, the connection will
; take literally FOREVER, and if you leave 60 seconds in the box,
; the connection will take about 1 minute to connect! Go figure!).
;
; 16) Press "OK" button.
; Then click on the "Next>" button.
; NOTE: It does _not_ matter what you put in for the phone number
; when you are prompted for one, because this device will NOT use it.
; Use some arbitrary value like "1".
; Click on the "Next>" button and then the "Finish" button.
;

; At this time it might be a good idea to go to dial up
; networking and choose the properties for
; this new connection that you have made. Choose "Server type".
; Although the Server Type must be PPP,
; and TCP/IP must be an allowed network protocol, the other
; settings such as "Log on to network", "Enable software compression",
; Require encrypted Password" do not seem to matter.
; For TCP/IP settings, ensure that "Server assigned IP address"
; and "Server assigned name server addresses" are all checked.
; Ensure that "Use IP header compression" and "Use default
; gateway on remote network" are also checked.


[Version]
Signature="$WINDOWS 95$"
Class=Modem
Provider=%Mfg%

[Manufacturer]
%Mfg%=Direct

[Direct]
%DSC% = Defn, UNIMODEM105DA558

[Defn]
AddReg=All, Common, Regular, EXTERNAL

[All]
HKR,,FriendlyDriver,,Unimodem.vxd
HKR,,DevLoader,,*VCOMM
HKR,,PortSubClass,1,02
HKR,,ConfigDialog,,modemui.dll
HKR,,EnumPropPages,,"modemui.dll,EnumPropPages"


[EXTERNAL]
HKR,, DeviceType, 1, 01

[Common]
; Hayes standard init/monitor/answer mechanisms.
; These can be redefined if different for a specific modem
; Perhaps these are not needed in a direct dial up connection, but
; I initially had strange errors reported by WIN95 when I tried to
; connect with all of these removed.
HKR, Init, 1,, "<cr>" ; do an "AT" to get autobaud correct (start other init strings with 2)
HKR, Monitor, 1,, ""
HKR, Monitor, 2,, ""
HKR, Answer, 1,, "None"
HKR, Hangup, 1,, ""
HKR,, Reset,, "None" ; slam in a reset before closing
HKR, Settings, Prefix,, ""
HKR, Settings, Terminator,, "<cr>"
HKR, Settings, DialPrefix,, "D"
HKR, Settings, DialSuffix,, ""
HKR, Settings, CallSetupFailTimer,, ""
HKR, Settings, InactivityTimeout,, ""
HKR, Settings, SpeakerVolume_Low,, "L0"
HKR, Settings, SpeakerVolume_Med,, "L2"
HKR, Settings, SpeakerVolume_High,, "L3"
HKR, Settings, SpeakerMode_Off,, "M0"
HKR, Settings, SpeakerMode_Dial,, "M1"
HKR, Settings, SpeakerMode_On,, "M2"
HKR, Settings, SpeakerMode_Setup,, "M3"
HKR, Settings, FlowControl_Off,, "&K0"
HKR, Settings, FlowControl_Hard,, "&K3"
HKR, Settings, FlowControl_Soft,, "&K4"
HKR, Settings, ErrorControl_Off,, "&Q6S36=3S48=128"
HKR, Settings, ErrorControl_On,, "&Q5S36=7S48=7"
HKR, Settings, ErrorControl_Forced,, "&Q5S36=4S48=7"
HKR, Settings, Compression_Off,, "S46=136"
HKR, Settings, Compression_On,, "S46=138"
HKR, Settings, Modulation_CCITT,, "B0"
HKR, Settings, Modulation_Bell,, "B1"
HKR, Settings, SpeedNegotiation_Off,, "N0"
HKR, Settings, SpeedNegotiation_On,, "N1"
HKR, Settings, Pulse,, "P"
HKR, Settings, Tone,, ""
HKR, Settings, Blind_Off,, "X4"
HKR, Settings, Blind_On,, "X3"

[Regular]
HKR, Init, 1,, "<cr>"
HKR, Init, 2,, "NoResponse"
HKR, Monitor, 1,, "Monitor"
HKR, Answer, 1,, "CLIENTSERVER"
HKR, Answer, 2,, "NoResponse"
HKR, Settings, DialPrefix,, ""
HKR,, Properties, 1, 80,01,00,00, ff,00,00,00, ff,00,00,00, 07,00,00,00, 0f,00,00,00, f7,03,00,00, 00,c2,01,00, 40,38,00,00
HKR, Responses, "<cr>", 1, 02, 00, 00, 00, 00, 00, 00,00,00,00 ; Client side - the server has acknowledged and the connection is completed

[Strings]
Mfg = "Norstar"
DSC = "Direct Serial Connection"

 

[RikRodgers]

I had the same trouble with xp. I tried to assign a new COM port, but it wouldn't take the direct connect settings.

I can't remember for sure, but for some reason, I had to put the nvmppp2 file on a floppy (the have disk prompt wouldn't allow me to select a file on my hard drive) and then use that as my driver.

Good luck.

 

[phoneguy427]

Will not work over win2000. Best result is win98(yeh right, we all have machines at win98). They came out with 4.1 so you can modify class of service through telset.