Release Notes for MODEMID.EXE Introduction MODEMID.EXE is a software tool which generates a disk-based file (MODEMDET.TXT) containing unique modem ID strings for standard RS232 external and ISA slot type AT command modems. To provide portability and ease of use, MODEMID.EXE is designed to run under these operating environments: Windows 3.1, Windows for Workgroups, and all Chicago beta versions. Modem ID strings derived from use of this tool are subsequently embedded into standard Chicago modem INF files to provide automated modem detection, but should not be confused with true Plug and Play modem device ID strings which are used with many PCMCIA and PNP modems discussed elsewhere within Chicago beta documentation. Note that MODEMID.EXE and these release notes are provided under the terms of the nondisclosure agreement you or your company have entered into as part of the Chicago beta program. Please do not distribute these files outside of your company. Creating ID strings 1) Copy MODEMID.EXE to a hard drive or floppy of the computer which will be used for detection. In a large facility where many modems will be tested, a portable computer or easily transferrable floppy disk may be convenient. It is NOT necessary to run MODEMID.EXE from a Chicago beta machine. A Windows 3.1 or Windows for Workgroups machine is satisifactory. It is not necessary to copy MODEMID.EXE to a special subdirectory or disk location. 2) Install a modem to be tested into the computer. Be sure to consider possible COM port and IRQ conflicts during this step. It may be helpful to run the Windows Terminal program and transmit a few AT style commands to the modem to ensure proper configuration. 3) Run the MODEMID.EXE program using the Program Mangager, File Manager or other appropriate method to start the software tool. 4) Once the program has started, select the Menu Option "Create ID". 5) Select the appropriate COM port to which the modem is attached 6) A window will open named "Modem Being Detected" which prompts the user for an exact modem name. It is important that the name entered be a COMPLETE and ACCURATE description. Typically this should include the manufacturer name and common model designation from the facepanel of the modem. Examples of good and bad entries are shown below: Good Bad GreatModem PC288 VFC + FAX GreatModem 28.8 model GreatModem Scouter V.32bis FD GreatModem Scouter high speed GreatModem D/F V.34 FAX + ASD GreatModem Data Fax V.34 GreatModem 24/96 travel handy pocket GreatModem pocket GreatModem V.32bis Sportman FAX/DATA Great Modem Sportman 14400 Note! If you feel there is insufficient space to COMPLETELY and accurately describe the modem in the description box, use a sheet of paper or notepad file to document additional data which can be submitted to Microsoft with the detection file. 7) After completing this window and accepting entered data, MODEMID.EXE will interrogate the modem using a variety of AT commands. This should usually require under two minutes. The hourglass wait icon will remain until interrogation has been completed. On external modems you will see the modem lights flicker as interrogation proceeds. 8) An ASCII format file named MODEMDET.TXT will be written to disk in the Windows subdirectory (normally \WINDOWS on most systems). If you view this file you will see a list of AT interrogation commands and, near the end of that series, the detection ID string which has been derived. 9) As each subsequent modem is interrogated, test results are appended to the MODEMDET.TXT file which will gradually grow in size. 10) It is very important to interrogate as many modems within a product line as possible. Older modems are likewise important. Pay SPECIAL attention to modems which have been firmware upgraded through several versions despite retaining a primary product name. It is EXTREMELY important to generate detection ID strings for ALL variations of the same modem model. These variations are usually caused by manufactuer firmware chip upgrades/revisions over time while retaining the same product name. For example it may be possible to generate different ID strings for a modem of the name "Sportman V.32bis" manufactured in the years 1992, 1993 and 1994. All variations should be tested and listed if possible. 11) The final MODEMDET.TXT file (or several of these files) should be returned to Microsoft Chicago Modem Test and Development Group. ` The preferred return method is to separately e-mail modemdet.txt files to modemdet@microsoft.com. Or you may return detection files on floppy or email to: Jim Hood Email: A-JIMHO@Microsoft.Com MICROSOFT CORP, Building 5, ROOM 1037, ONE MICROSOFT WAY, REDMOND, WA 98052-6399 206/882-8020 X16573 Helpful suggestions: - Multiple laptop or desktop computers can be used for detection testing. Multiple MODEMID.TXT files can be submitted. - If you are aware of modems within your organziation at alternate sites you may distribute this document and copies of MODEMID.EXE to additional locations. -Do not alter the format of the MODEMID.TXT file. If you make a mistake, simply rerun the test and make a note of it when submitting the final file to Microsoft. -Submit a MODEMDET.TXT file for all of the modems you can obtain as soon as possible. If you have additional modems which are still under development, do NOT delay submission of the detection file. Microsoft can accept subsequent detection files in the future as Chicago development proceeds.