4.4 FAQ - Program Errors and Requests
- 4.4 FAQ - Program Errors and Requests
- 1. Where can I download the program?
- 2. Why is all the data in a database?
- 3. What is the best way to learn about the program?
- 4. The program displays an error or just stops working. What should I do?
- 5. The program gives an error opening the database. What should I do?
- 6. What can I do if the contest I want to participate in is not listed?
- 7. Errors and possible solutions <Obsolete>
- 8. CW stutters (using lpt or serial port keying) or Voice keying stutters
- 9. The radio locks up in transmit
- 10. Suddenly Function Key F2 is sending my CQ, instead of F1. Why?
1. Where can I download the program?
Full instructions for downloading and installing the software can be found here.
2. Why is all the data in a database?
Because that's how the program works. You can get log data into a spreadsheet program like Excel by generating your Cabrillo file and then loading it into Excel. The Cabrillo fields are fixed width, which makes it easy to get the data into the columns you want.
3. What is the best way to learn about the program?
- Read the Getting Started section of the manual. It takes you through the whole process from downloading the software to operating a first contest and generating your log file for submission. After that, you will probably want to known more about some areas. That's what the Digging Deeper section is for. You can look things up by window, or by the function you're interested in. Often, using the search function will give you what you need.
- Print out the ((Key Assignments (Keyboard Shortcuts)|Key Assignments)) or the Key Assignments Short List and keep it by your radio. Even long-time users will discover new keyboard shortcuts this way.
- Set up your next contest well in advance. That will give you a chance to iron out any wrinkles in the contest setup. Maker some dummy QSOs before the contest. When it's time to go, you can either create a new instance of the contest or clear out your dummy QSDOs before "Zero Hour".
- If you have problems and you can't find the answer, don;'t hesitate to ask on the N1MM Logger Plus reflector. That's what it is for. In addition to the N1MM Development Team, there are many experienced users there who will pitch in to get you going.
4. The program displays an error or just stops working. What should I do?
When the program displays an error or suddenly ends, this may be a bug in the program or a problem on your computer. Here are some hints on how to determine if it is a bug, what information to collect, and how to report it.
- Try to record step-by-step what you were doing when it happened. Record the exact error message, if any. If the program just failed, make note of when and under what circumstances
- Restart Windows, and then N1MM. Go back where you were when the problem happened. Particularly in cases where RFI is involved, Windows can easily become corrupted. If your problems with RFI are particularly severe, try a complete cold restart of your computer.
- After this, if you do the same thing again does it happen again?
- Do not immediately re-install the program; this rarely solves anything. Instead, rename your N1MM Logger.ini file (N1MM Logger.old, for example) and re-start the program. This will create another minimal .ini file, eliminating any user-selected options. Try the steps that caused the problem - does it still happen? Add back your radios, keying setup and other parts of your usual configuration, one by one.. Does the error recur? At what point?
- If the problem still exists, submit a bug report and fill in the form completely. A majority of the bug reports we currently receive are not program bugs at all, but problems with the user's understanding of the problem or in a particular set-up. Going through the steps above will help you know which your problem is, and filling out the form completely will help us help you without a lot of back-and-forth to fill in important details.
- If you need help with setup or how the program operates, you should refer to the manual, and if you don't find what you need, ask on the reflector. That's what it is for.
5. The program gives an error opening the database. What should I do?
This may mean that your database is corrupt. A first step is to try opening the program using another existing database (File >Open database). If the error only occurs with one database, then it is possible that the database has become corrupted.
There are two approaches you can take:
- Use N1MM Logger's File >Copy(and Compact) Database function to make a new database from your old one. This process opens the database, checks for many common errors, and fixes them.
- If you can't do it this way - if, for example, the database won't open - then you can try using one of many SQLite database tools available on the Internet. The N1MM Development Team uses a program called SQLite Expert. The "Pro" version (payment required) includes a "repair database" option. The standard version (free) does not include the repair function but many users report that they have been able to repair databases by simple opening the broken database with SQLite Expert (free) and re-indexing its files. Before using any utility like this, make a backup copy of the database. In extreme cases, we may be able to help you recover a database that just won't work, but not if you have lost it or damaged it further.
6. What can I do if the contest I want to participate in is not listed?
- First, double-check the supported contests listing. If you have just been looking at the short contest names in the Contest Setup dialog, you may have overlooked the one you want.
- NA3M has developed a User Defined Contest feature , and over 250 contest definitions have been created. They are stored here. Please note, though, that while NA3M will try to help with these contests, the definition files were developed mainly by other hams, and we lack the resources to support them.
- If you do not find the contest you want, you have two options:
- Use the UDC editor to develop your own definition file. The process may seem intimidating at first, but there is real satisfaction in adding another contest to the UDC roster, one that you programmed yourself. In the process, you'll learn a lot about what is involved in programming even the simplest contest so that all features of N1MM Logger operate correctly.
- Request that we add the contest to the roster of supported contests. If you do this, be sure to give us several months' lead-time for coding and debugging, and plan on being available yourself to help us test. Depending on the level of user interest, we may well suggest that you go the UDC route instead; there simply isn't enough time for everything people would like us to do.
7. Errors and possible solutions <Obsolete>
EntryWindow (Program_Initialize) - 3265 The database is corrupt. Select a new one or repair.
Run time error 32555 "Radio number error" Corrupt / bad entries in N1MM logger.ini, select a 'clean' version.
Run-time error - Automation error Windows 95 - This is mostly a problem with OLEAUT32.DLL. The version on the computer is to old for N1MM logger, replace it with a newer version. Use a version from Windows 98 or download VBRUN60SP6.EXE from the N1MM website ('Download | Other Files) or download it from the Microsoft Download center.
Windows 98 - This is mostly a problem with OLEAUT32.DLL. The version on the computer is to new for N1MM logger (probably a XP version).
1. Select Start -> Programs -> Accessories -> System Tools -> System Information
2. Select Tools / System File Checker from the System Information menu bar,
3. A dialog box appears, select "Extract one file from installation disk" and type OLEAUT32.DLL and click OK.
4. Insert your Microsoft Windows 98 installation disk, verify the default locations of Windows directory and CD drive are correct, and click OK.
5. The file will be replaced, and you will be prompted to restart the PC.
NB The same procedure works for Windows 95.
- Try using using a clean N1MM Logger.ini file. You will reset many of your configuration settings, but this often fixes the problem. Sometimes this has something to do with wrong configuration of ports.
When upgrading I get 'Error 429' The 429 error is usually caused by having the wrong version of CW IF.exe in the directory where the logging program is installed. All the files in the NewexeV.x.xx.exe have to be installed in the program directory.
Run Time error 339 - Component RICHTX32.OCX Install Richtx32.zip from the N1MM website ('Download | Other Files). Please read the instructions in the zip file.
Error message" DLPORTIO.DLL missing Download Port95nt.exe, this is a port driver. A link to this file can be found in the installation section. To install just run the exe as the administrator of your computer.
A Telnet Communications Error Occurred. Error: 10061 Connection is forcefully rejected The selected Telnet cluster declines your request to log in for some reason. Reasons could be:
- The maximum number of users are already connected.
- You are trying to telnet to the wrong port.
- The firewall on your pc (like ZoneAlarm) or in your router is blocking the program
- The DX cluster's software isn't working properly.
- The DX cluster has just rebooted and it not yet ready for users.
- bad dns from your router that is sending the requests to an internal machine that isn't set up for telnet.
Runtime error 339 - Component N1MMWave.ocx or one of its dependencies not correctly registered: a file is missing or invalid Win98 (as opposed to win98se) doesn't have the proper version of a couple dll's like mfc42.dl/msvcrt.dll etc.
A work around could be to install Internet Explorer 5, then upgrade to version 6, and maybe next to install Office 97 and if that doesn't fix it upgrade to Office 2000. One or the other of those would add those dll's as they are common ones used by most Microsoft products.
Runtime error 4 - Opening recording device - flagging Record QSOs Configurer - Audio Tab: Select a lower bitrate for your soundcard. 8 or 16 bits will probably always work, 24 is probably to high for the selected soundcard.
Err 3 - Format not supported. Use PCM. This error message occurs when trying to play a Wav recording that was made with some other sound recorder that saves the file in a non supported Wav recordingformat. Try to record with: Ctrl+Shift+Fx (Fx is a functionkey like F1)
429 - ActiveX component can't create object" and "91 - Object variable or With block variable not set" When running Windows Fundamentals for Legacy PCs (Windows FLP) you have to add and register "dao360.dll. This file does not exist at all on Windows FLP. See below in this FAQ how to fix this.
__When creating a new database the error below occurs:
HamTemp.mdb already exists, rename__ This happens because at some time in the past, something did happen during the create new database process that left a hamtemp.mdb file in the program directory. This is a temporary file needed during the database creation process but should be automatically removed when done. If it is already there, the database creation process fails.
The solution is to use Windows explorer to locate and delete hamtemp.mdb from the N1MM logger program directory. After that creating a database from inside N1MM will work again.
Err10 "playback fmt (format) not supported" The OCX used to play .wav files in N1MM only supports uncompressed, basic .wav recordings. There are a number of other CODECs out there that produce files it doesn't recognize which gives this error message. Try to record using N1MM logger or record using Windows Sound Recorder and its default CODEC.
8. CW stutters (using lpt or serial port keying) or Voice keying stutters
Mostly this means your pc is too busy handling other stuff during transmit or is underpowered. This could be outside N1MM logger. What to do? Some 'tricks'.
Try not to run other programs not needed for contesting.
Try filtering spots at your packet cluster node so as to reduce the traffic that must be handled by N1MM logger.
Set your telnet filters for the minimum number of spots consistent with your needs, particularly including only the current contest's mode and maybe only spots from areas near your own
Zoom the bandmap in so that it covers only a relatively small frequency range around your current frequency.
Limit the number of bands you try to cover with the Available Mults and Qs window's spot pane (for the band that the particular PC is on).
9. The radio locks up in transmit
This may result from an invalid PTT configuration.
Do not use more than one method of PTT control at the same time. Having two methods active, while it may look like a "belt and suspenders" approach, is less reliable than using only one method. The two methods can interfere with one another in such a way that the radio gets hung up in transmit when it receives two "switch to RX" commands simultaneously.
In particular, do not use "PTT via radio command" if you have another (hardware-based) PTT method working and active.
In digital modes, if you are able to do PTT from the main N1MM Logger program, do not also configure the digital engine (MMTTY or Fldigi) to do PTT; the only time you need to configure PTT in the digital engine is when you are not using any method of PTT control from N1MM Logger itself.
Another possibility is having a PTT keying line connected to a serial port control line (DTR or RTS) and having that control line set to "Always On"; this will result in the radio locking up in transmit whenever the Logger is started up.
10. Suddenly Function Key F2 is sending my CQ, instead of F1. Why?
N1MM Logger assigns messages to function keys based on their position in the table, not on how they are labeled. Hence, the first non-comment line (one that doesn't start with #)is Run F1, the 13th line is S&P F1, and so on. Moreover, you can insert comments in your function key file, and the program skips over them in deciding which message goes to which function key.
The label you put on the function key button (the part to the left of the comma in each line) is strictly for the buttons in the Entry Window - it does not control which message goes to which key.
Most likely you accidentally omitted a # or made some other typo in one of the lines in the file, causing the program to skip one. Try counting lines, or play safe by deleting all comment lines from your file. Also, make sure that each Fkey line has a comma before the start of the text to be sent.