----------------------------------------------------- Please notice that in China and Taiwan there began the Chinese New Year's celebration which will last until 02/02/98. So many people will celebrate with their families or will be out of office to have a vacation. Also ZyXEL Comm. Corp. will be closed in the coming week. You won't receive any feedback and replies to your support request if you sent them to ZyXEL Taiwan. *** I want to wish a "Happy New Year" to all my friends in Taiwan *** 2.) FAQ continued for "MDMZYXnn.INF" driver file for Windows9x/NT4 ------------------------------------------------------------------ In the last two days I received many eMails from customers who reported their problems or sucess in installing the new INF drivers for Windows9x or WindowsNT 4.0 Now I want to forward some of these reports to all of you. I think this might help you to understand what's going on. Indeed I didn't think that the simplified INF files will cause so many questions now: Q: After the installation of your new "MDMZYXEI.INF" under Windows95 the operating system recognizes a new hardware device (modem found) and is asking for a "serial wave device driver" - But I couldn't find this driver. Where can I get it from and how should I install it ? A: If you are running Windows95 with updated UNIMODEM/V (for voice modems) or the Windows95 OSR 2.x (OEM Service Release is a newer version of Windows95 which already includes the UNIMODEM/V) then it will prompt for a serial wave device driver: You will find the "ZyXEL Elite 2864I ISDN Modem Serial Wave Device" driver as the "SWVZYXEI.INF" file which is included in the "MDMZYXEI.ZIP" compressed ZIP file. Windows95 will install it as additional audia device then. You will be able to work with TAPI for voice modems. But note: this voice mode is still under BETATEST and will not (!) work with Windows95 correctly so far. It is already prepared for some new voice sampling methods which will be available with Windows98 and next generation of WindowsNT. Q: When I try to call to an analog (MODEM) destination, your new INF file works fine, but when the other site ist digital (ISDN) I got a CONNECT but there are no characters e.g in the HyperTerminal. I installed already the new bug fixed file. (= MDMZYXEI.INF 01/22/98). A: As I wrote in the "MDMZYXEI.TXT" the default B-channel protocol is set to PPP now. If you want to work with HyperTerminal (eg: with X.75 or V.120) you must remove the "ATB40" in the modems extra settings. The "mouse click path" is as follows: START | Settings | Control Panel | Modems | Properties | Connection | Advanced | Extra Settings | Then you should use the ZyICM v2.4 to select the B-channel protocol to either X.75 or V.120. (In the future this will become much more simplier - we are working on some improvements in the firmware.... Currently we don't have any release date scheduled yet.) Q: Is it possible to have the old system of your INF file with different modem entries for V.34, V.110, V120, X.75? A: Microsoft asked us to simplify the INF files as much as possible. This is the reason why only one modem entry will occure with the new INF files now. For the B-channel protocol selection for outgoing calls you will have to use ZyXEL's ISDN Configuration Manager v2.4. It will be an advantage especially for those who are working with RAS (Remote Access Service) under WindowsNT 4.0 - because there it is not possible to assign several modem entries for one and the same COM port. (This is a feature which is available under Windows9x only) With previous INF files the RAS user had to change the modem entries if he wanted to select X.75 or V.120 or PPP - and then he had to reconfigure the RAS, which caused a reboot of the WindowsNT 4.0 system. Q: I had the same problem with my Elite 2864 after updating from "MDMZYXLG.INF" (rel. 38) to "MDMZYXLG.INF" (rel. 53). I use Windows95 OSR 2 and before updating I looked for OEMx.INF files, but couldn't find any. After I ran into trouble, I looked at the "external connection" of my Provider and discovered that though "Modems" only contained one entry when I looked at the pull-down menu of "connect through". I could select from two different modems. I also looked at my INF-directory and removed all "MDMZyXxxx.INF" files including one called "Zyxel Comm. Corp.MDMZYXLG.INF" which was located in "c:\windows\INF\OTHER\". After that I reinstalled "MDMZYXLG.INF" and everything worked OK. A: First, thank you for your feedback. Yes, indeed, the Windows95 OSR 2 and also Windows98 Beta will install new INF files into that \WINDOWS\INF\OTHER\ directory, if you selected "Have Disk" while installing new INFs. In previous version of Windows95 the INFs were renamed to "OEMxx.INF" and were located in the \WINDOWS\INF\ directory only. Microsoft has changed this INF installation routine since Windows95 OSR 2.x Q: Concerning the "omni.net": I experienced the same problem with my "omni.net" after upgrading to the new firmware v1.20 and after installing the new *.inf file. I dont know which of the following that remedied the problem but it is gone now, I havent tried to duplicate it yet.. I did a hardware factory default reset......a couple of times. I installed the old InternetConfigurationManager .inf since it wasnt in the new *.inf anymore. I removed and reinstalled the TA through ->Control Panel->Modem.... twice. Restarted Windows a couple of times.. I dont know in which order or which one helped.. Now I have another problem. Windows keeps finding new hardware "Found Omni.net v1.20..", and keeps installing it, and I keep removing it since I dont know which .inf file it uses for it (It installs it as "ZyXEL omni.net, PlugnPlay"). I use Windows95 v4.00.950a, with all patches. A: If you remove or rename all the old existing 'MDMZYX*.INF' files you have to remove also all the modem entries from the modem's properties! Please check also the "Windows9x Device Manager" for any installed old modem entry: click with the second (normally right) mouse button on the "My Computer" icon on the Desktop and select "Properties | Device Manager | Modem" -> if you will see there any existing old ZyXEL modem, select it and click on the "Remove" button. Check the directories \WINDOWS\INF\ and \WINDOWS\INF\OTHER\ if there are any old "MDMZYXnn.INF" files -> remove or rename them. Then you can begin with the installation of the new INF files again. Q: Under WindowsNT 4.0 I first installed your "MDMZYXEI.INF" (01/20/98) and two days later your newer version (01/22/98) of that same file. In the release notes - as well as in your announcement on the mailing list - you told us that the problem of the 1 second in the "CallSetupTimout" is fixed with the new file. Indeed, if I look into the modem's properties, there the value is set to 60 seconds now. However, when I want dial to my ISP the modem still disconnects after one second - and also in the logfile "\WINNT\SYSTEM32\MODEMLOG.TXT" you can clearly see that S7=1 (instead of S7=60). What is the mistake and how can I fix this now ? A: WindowsNT works with compiled versions of the INF file. If you forgot to delete the old "MDMZYXEI.PNF" (compiled INF) then WindowsNT will still use that old file - even if you copied the newer INF file into the \WINNT\INF\ directory. As long as WindowsNT dedects a PNF file with the same name, it won't recompile it. So this is the reason why it still sets the CallSetupTimout to 1 second (because it's in the registry). You have to remove the old modem's entries from registry, delete the MDMZYXEI.PNF file in the \WINNT\INF\ directory and reinstall the modem. It now will use the new version of the MDMZYXEI.INF and will automatically compile it to MDMZYXEI.PNF -> it's contents will be used for the Registry. note: this is for more experianced users: ----------------------------------------- You can check also the Registry by yourself with the "REGEDIT.EXE" tool: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ Class\{4D36E96D-E325-11CE-BFC1-08002BE10318}\0000\Settings\Init\1\ --> there you can set the ATS7=60..... and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ Class\{4D36E96D-E325-11CE-BFC1-08002BE10318}\0000\Default\ --> there you can set the first byte from value 0x01 to 0x3c (60 --> seconds) and now there comes a little bit longer support request eMail which is lso worth to include it to these FAQs - I hope that I don't bother you with t: Q: I live in the Netherlands and own a Zyxel 2864I modem which was purchased in Holland through Nijhoff Automatisering which is our Dutch distributor since June 1996. With the new firmware (and .INF's) for this modem (v2.11) there seems to be support for voice modems, which I like to investigate. The Plug & Play facility of Windows 95b (OSR 2.x) identifies my modem as a modem without Voice capabilities however. This is correct behaviour according to the INF file, for my modem yields plug & play info "ZYX02FF" (ATI9 output confirms this). When one studies the INF file, "ZYX02FF" seems to key to a USA-model, and here I'm a bit puzzled. Do I really own a Elite 2864I targetted at the USA-market instead of the European (Dutch) market ? It does have a "CE" sticker attached at the backside however, which suggest otherwise. Everything seems to work just fine. I'm flashing the DSS1 (European) type firmware in my modem and has performed outstanding for several years here (and still does!). This plug & play info generated by my modem, is this correct behaviour for the Dutch situation? Is this perhaps configurable in some way in order to get these voice capabilities. Only DSS1/ITR6 is supported for VOICE according to the latest INF-files. But with plug and play key "ZYX02FF" this is a no go. I can modify the inf file myself but this is not wise to do so of course. Is this plug & play key hardcoded and not to be changed in order to reflect the correct hardware configuration ? Is perhaps my modem too old ? I've contacted a friend of mine, who purchased an ISDN-upgradeboard for his Zyxel 2864 only a few months ago and his plug and play info yields also the "ZYX02FF" mark, so perhaps this is indeed correct in the Dutch situation. However I'm at a loss. Below are some output's from my modem to be found: ati0 : 28642 ati1 : Elite 2864I DSS1 : V2.11 Internal fax/modem : V1.16f DFCC ati9: (CTRL-0)$ZYX02FF\0000DFCC\MODEM\\ Elite 2864I DSS1 : V2.11 EA) Serial number is S632003842 Hope you can shed some light on this for I'm really puzzled and confused here, Kind regards, Eric Sluyter A: Thank you, Eric, for your excellent feedback and support request. I love such long questions. First of all, "DON'T PANIC !" - you have indeed an European model of the Elite 2864I with the correct firmware for EuroISDN. Well, indeed, there is a little difference - compared to other models that were purchased in other European countries: the ISDN country code ! Although the EuroISDN is well specified by ETSI (European Telecomm. Standards Institute) there exists many different ISDN supplementary services with many different optional parameters - still all are standardized. But it is country depended which of these optional parameters are offered by your telecom company in your country. So the only way to cover these different behaviours of the ISDN supplementary service is to use special country codes. This is controlled by the firmware: the ISDN country code will be already set in the ZyXEL factory before the products will be shipped to your local distributor. Now, your problem is that ZyXEL implemented the existance of the ISDN country code since firmware v2.04 when we added the feature of the metering pulses on the POTS port of Elite 2864I. And if you already had your ZyXEL Elite 2864I BEFORE that firmware - the country code couldn't be set in the factory at that time, of course. So it default's to the value 255 (0xFF) - which because the ISDN country code for USA. Also persons who upgrade the Elite 2864 MODEM to an Elite 2864I ISDN TA will run into the same problem as you described. Because in the analog MODEM there is no ISDN country code included, so again it will default to the value 0xFF after the hardware upgrade. In all these cases please contact the support hotline of your local distributor - you probably will have to send your unit to him so that he can set the correct ISDN country code according to your country. Note: that we don't supply country codes for all countries. In such cases only the local distributor will know which ISDN country code will work best with your country depended implementation of the ISDN supplementary services. The ISDN country code could be displayed either with the command 'AT#h' or in the response to the Windows9x Plug&Play ID of command 'ATi9': in "ZYXmmcc' the cc means the hex value of the ISDN country code. Please don't experiment on the ISDN country code - it could affect some "strange" behaviours in with your ISDN switches in your country if you'd selected the wrong code. So check that situation with your distributor ! 3.) FAQ continued for SYMANTEC/DELRINA WinFax Pro 8.02 with Talkworks --- FD 2.20c.mL - Fastecho 1.46 * Origin: <=-Pulse BBS-=> +31-79-3437581 24 hours a Day (2:281/614) --------------- FIDO MESSAGE AREA==> TOPIC: 116 ZYXEL MODEMS Ref: F1V00002 Date: 01/22/98 From: STEVEN LEEMAN Time: 08:53pm \/To: DEREK STEEL (Read 0 times) Subj: 56k and Zyxel Friday January 16 1998 03:17, Derek Steel wrote to Tom Freeman: DS> The Zyxel has had things like callerID, voice, and fax in memory, DS> distinctive ring, and a lot of others long before anyone else.. software never got finished for voice also flashcode never got 100% never got 33k6...blaming zyxel 2864 doesn't contain a second generation chip :( o zwaai, zwaai, )/\,[_) Steven Leeman `T7 ]=[ Sysop SkyNET Bbs ... think I'll crash. --- SkyNetMail * Origin: SkyNet Bbs 32-(0)16-580862 (2:292/624) --------------- FIDO MESSAGE AREA==> TOPIC: 116 ZYXEL MODEMS Ref: F1V00003 Date: 01/23/98 From: STEVEN LEEMAN Time: 09:43am \/To: JOE SCHWEIER (Read 0 times) Subj: 56k and Zyxel Friday January 16 1998 12:28, Joe Schweier wrote to Tom Freeman: JS> I've use a ZyXEL modem as a sysop and a small business owner and have JS> always like the modem over any other product. you see now more stuff coming for their omni model... and on their website it's COMET that rulez...they have it in every modem :( also 56k! o zwaai, zwaai, )/\,[_) Steven Leeman `T7 ]=[ Sysop SkyNET Bbs ... Bugsbugsbugsbugsbugsbugsbugsbugsbugsbugsbugs --- SkyNetMail * Origin: SkyNet Bbs 32-(0)16-580862 (2:292/624) --------------- FIDO MESSAGE AREA==> TOPIC: 116 ZYXEL MODEMS Ref: F1W00000 Date: 01/25/98 From: DIMITRI VAN HOVEN Time: 05:59pm \/To: ALL (Read 0 times) Subj: 2 ZyXEL NEWS 3 ---------------------------------------------------------------------- I also receiced some more questions concerning the WinFax 8.02 and Talkworks. I think this might be also very interresting for many of our customers .... Q: Thanks very much for this information. Yes, indeed, I that's the problems with WinFax Pro v8.0x and ZyXEL modems all the time. With the old version Winfax 7.x at least there I had no problems. My question after I read all the news and after updating to firmware v2.10: please tell me the correct way how to set the ZyXEL Elite 2864I into fax receiving mode when the computer is not working ? What is the right led ? Is it right that I must give before ending my computer work the following commands: AT&F AT+fclass=2 AT+FZF=3 AT&N32 AT&D3&W0Z0 I think that my question not alone my individual questions. A: yes, indeed, I am asked very often how to do this - and I mentioned it in the applictions notes for using WinFax 7.0 and WinFax 8.02 Please check these applications notes, you can download them from our FTP server: ftp://ftp.zyxel.co.at/public/software/WinFax70/zyxwfx70.zip ftp://ftp.zyxel.co.at/public/software/WinFax802/zyxwfx82.zip The commands which your wrote in the lines above are nearly correct: it your be "AT+FCLASS=Z" ("zet" instead of the digit "two") You can enter all these lines into the WinFax FAX Modem settings, but you should use WinFax Pro in COM-port mode, not in TAPI-mode, otherwise these commands won't be sent to the modem. More detailed information how and where exactly you should enter these init strings are documented in my application notes on the FTP server. Q: I also had the problems with Winfax 8.02 patch and Talkwork together with my Zyxel Elite 2864i that you described in your e-Mail. It turned out, that not the files are missing but the codec is not registered correctly. The solution to this is to add the following keys in the registry (this is for Windows NT): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ drivers.desc dcczyl32.acm="Symantec Zyxel Audio Codec" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ Drivers32 MSACM.dcczyxl="dcczyl32.acm" For Windows 95 it should be sufficient to add the following entry to the system.ini file: [drivers32] MSACM.dcczyxl=dcczyl32.acm After these modifications you don't get any error messages from Winfax anymore. A: thank you very much for your feedback - I am sure that Symantec/Delrina support will add it to their knowledgebase too ! Q: Nevertheless I still have a problem with using talkworks as an answering machine: Talkworks answers incoming phonecalls correctly and starts recording the incoming message. When the caller goes off hook though the transmission from the ZyXEL ISDN Terminal Adapter is also ended at once even though it is not completly done. This means at the end of every recorded message there are a few seconds missing. My Elite 2864i is equipped with 2 MB of memory. Do you know a solution to this problem? Symantec customer service couldn't help me on this. A: I could duplicate your problem with the ZyXEL Elite 2864I, but it does not have these problems if using the ZyXEL Elite 2864 (analog MODEM). Currently I don't have any solution for that question either but I am sure that ZyXEL R&D and Symantec/Delrina Talkworks R&D will check this and will search where we can improve that behaviour in voice mode. -------------------------------------------------------------- PS: This eMail is distributed by the "zyxel-info@zyxel.co.at" mailing list. If you ever want to remove yourself from this list,you can send mail to "majordomo@zyxel.co.at" with the following command in the body of your email message: unsubscribe zyxel-info end -------------------------------------------------------------- electronic greetings from Vienna/Austria Manfred Recla ********************************************************** ZyXEL European File Distribution - Coordination Center E-Mail: support@zyxel.co.at FTP: ftp://ftp.zyxel.co.at/public/ WWW: http://www.zyxel.co.at ********************************************************** === Cut === Ter info! Best Regards, -=*Dimitri*=- diho@wxs.nl dvanhoven@biochem.nl ... "I believe he can create miracles..." - Dana Scully on God -+- GoldED 2.50+ + Origin: ZyXEL -=More Than A Modem=- (2:281/614) ============================================================================= Hello All! Best Regards, -=*Dimitri*=- diho@wxs.nl dvanhoven@biochem.nl ... "Guess I'm not dead." - Mulder to Scully (Apocrypha) --- FD 2.20c.mL - Fastecho 1.46 * Origin: <=-Pulse BBS-=> +31-79-3437581 24 hours a Day (2:281/614) --------------- FIDO MESSAGE AREA==> TOPIC: 116 ZYXEL MODEMS Ref: F1W00001 Date: 01/25/98 From: DIMITRI VAN HOVEN Time: 05:59pm \/To: ALL (Read 0 times) Subj: ZyXEL NEWS 2 ============================================================================= * Forwarded by Dimitri van Hoven (2:281/614) * Area : ZYXEL.028 (ZyXEL modems en aanverwante software NL) * From : Dimitri van Hoven, 2:281/614@fidonet (Sunday January 25 1998 17:50) * To : All * Subj : ZyXEL NEWS 2 ============================================================================= Dear ZyXEL customer, Vienna, 01/20/98 Some days ago, ZyXEL has released new firmware versions for all ZyXEL ISDN terminal adapters for the EuroISDN (DSS1) and the national German (1TR6) ISDN switches. The current versions are now: ZyXEL Elite 2864I v2.11 ZyXEL Omni TA128 v2.07 ZyXEL omni.net v1.20 ZyXEL omni.net D v1.01 ZyXEL omni.net PLUS v4.02 All these updated firmware files can be downloaded from our Web and FTP sites, eg: http://www.zyxel.co.at - or from any other European mirror site. Please don't get confused about the models "omni.net" and "omni.net D". The "omni.net D" is a new model without POTS (a/b-adapter) ports. This is the reasons why there is a different firmware file for that model. You can't flash the firmware of "omni.net" into an "omni.net D" and vice versa. The same situation applies to "Omni TA128" and "omni.net PLUS" models (there exists different hardware with different features although all the ISDN terminal adapters of the "omni" family look very similiar !) note: we already received some feedbacks that users have problems with the firmware v2.07 for Omni TA128 if the files were downloaded from our US site (http://www.zyxel.com) - we will fix this soon. We also released new versions of the INF driver files for Windows9x and WindowsNT 4.0 (and NT 5.0 Beta 1). These driver files can be downloaded from following URL: ftp://ftp.zyxel.co.at/public/software/Windows95/ the file names are as follows: mdmzyxei.zip -> for Elite 2864I mdmzyxot.zip -> for Omni TA128 mdmzyxon.zip -> for omni.net mdmzyxod.zip -> for omni.net D mdmzyxop.zip -> for omni.net PLUS please read the corresponding txt (ASCII text) files for further information, how to install them and what has been changed... We also recommend to use the updated version of ZyXEL's ISDN Configuration Manager (also known as "ZyICM"), version 2.4 (01/17/98) ftp://ftp.zyxel.co.at/public/software/zyicm/zyicm24.zip