I would have prefered it to work with Trinidad too :-) that would mean being in Trinidad ...
Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Riley, Steve Sent: Monday, February 07, 2005 6:31 PM To: 'salive@woodstone.nu' Subject: RE: [SA-list] New modem issue I changed the Country from US to Trinidad & Tobago then back, and now the modem is functioning. Thanks Dirk, as always, for brilliant support and responsiveness. Steve -----Original Message----- From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 11:45 AM To: Riley, Steve Subject: RE: [SA-list] New modem issue I think that the errormessage as defined within the TAPI subsystem are still "talking" about old stuff. I would suggest to look at the modem applet in the control panel and see if the international settings for it are correct and if they are, change them, apply and reset them back. Dirk. -----Original Message----- From: Riley, Steve [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 5:32 PM To: 'Dirk Bulinckx' Subject: RE: [SA-list] New modem issue Thanks Dirk. I think I would have understood better in Belgian! What does that mean to/for me? I checked the old machine and there is no such INI file, and I checked the new machine, and there are none there either. I have attached a list of all INI files from the old machine(NT 4.0 Server) and all the INI files on the new 2003 Server(2003INIS.TXT) Steve -----Original Message----- From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 9:08 AM To: salive@woodstone.nu Subject: RE: [SA-list] New modem issue About this: "Thursday, February 03, 2005 10:48:43 AM TAP ERROR: The values in the INI file are invalid. ( 26026)" This seems to point to a generic TAPI error with the name: LINEERR_INIFILECORRUPT And the info I found about this TAPI error (as it's reported back by the OS) "The telephon.ini file cannot be read or understood properly by TAPI because of internal inconsistencies or formatting problems. For example, the [Locations], [Cards], or [Countries] section of the telephon.ini file may be corrupted or inconsistent. " Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Thursday, February 03, 2005 6:33 PM To: salive@woodstone.nu Subject: RE: [SA-list] New modem issue Good question...never seen that before....let me do some research... Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Riley, Steve Sent: Thursday, February 03, 2005 5:00 PM To: 'salive@woodstone.nu' Subject: [SA-list] New modem issue I have just replaced some old hardware with something from this decade. I also upgrade from Windows NT 4.0 Server to Windows 2003 Server. I am running Standard 5.0.1680. The modem we used to use is not supported with Windows 2003(Practical Peripherals PM9600FXMT. The modem we have available is a Diamond SupraExpress 56e - PC V.90. The OS detects it and I can dial out using dial up networking. I have the comm settings at 8N1 and Baudrate at 9600. Protocol to use is TAP, and the SMSC number is the same as the old one. I had used Alpha Paging and SMS messaging. I tried 8N1, 7E1 and 7N1 When I try a test the log shows: Thursday, February 03, 2005 10:48:43 AM PAGING : Comm 0 Thursday, February 03, 2005 10:48:43 AM PAGING : RECIP 610912xxxx Thursday, February 03, 2005 10:48:43 AM PAGING : REQ F Thursday, February 03, 2005 10:48:43 AM PAGING : TEXT 1234567890 Thursday, February 03, 2005 10:48:43 AM PAGING : SMSC 1800250xxxx Thursday, February 03, 2005 10:48:43 AM PAGING : PROTO 1 Thursday, February 03, 2005 10:48:43 AM TAP DEBUG: Starting sending thread. ( 26400) Thursday, February 03, 2005 10:48:43 AM TAP DEBUG: Sending thread starting up. ( 26400) Thursday, February 03, 2005 10:48:43 AM TAP DEBUG: Logon procedure started. ( 26101) Thursday, February 03, 2005 10:48:43 AM TAP ERROR: The values in the INI file are invalid. ( 26026) Thursday, February 03, 2005 10:48:43 AM TAP remove #PHONE=610912xxxx#MESSAGE=1234567890#REDI=0#(#PHONE=610912xxxx#MESSAGE=12345 67890#REDI=0#) Thursday, February 03, 2005 10:48:43 AM TAP DEBUG: lineTranslateCaps unhandled error. ( 26400) Thursday, February 03, 2005 10:48:43 AM TAP DEBUG: Exception caught in SendThreadProc() ( 26400) Thursday, February 03, 2005 10:48:43 AM TAP DEBUG: Logon: failed. ( 26104) Thursday, February 03, 2005 10:48:43 AM TAP STATUS: Message sending failed. (ID: 13) ( 26315) Thursday, February 03, 2005 10:48:43 AM TAP STATUS: The transmission is completed. (ID: -1) ( 26313) Thursday, February 03, 2005 10:49:03 AM TAP wait (E- 26026)20 Thursday, February 03, 2005 10:49:03 AM TAP wait (E- 26026)20 Thursday, February 03, 2005 10:49:03 AM TAP wait (E- 26026)20 What is the INI file it is speaking of that has invalid values? Thanks Steve To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
