B12-01   Why do my RF codes not work?

First, be sure that you’ve set the IDs on the receiver and in ProntoEdit so they both match.

Next, when aliasing codes, the RF setting must be configured on the device that contains the source code, not just the device that contains the alias. So, if the RF device "television" has a button that aliases to the IR device "VCR", then the aliased code will still be transmitted in IR, even though the button is under an RF device. The source code’s transmission preference is always maintained.

If you create a CCF file (such as a gallery) that is too large to fit into the Pronto - or more technically accurate, bigger than the maximum size specified in the pronto.ini file - you will not be able to save the file. Instead, ProntoEdit will return with the message "Error saving file.ccf, configuration is xx% too big to fit in Pronto". Unless you are using ProntoEdit v4.0.3 or newer, whatever you do, don't exit ProntoEdit!

Since ProntoEdit starts saving the file before checking how big it will be, the file you tried to save over has already been deleted (and is 0 bytes in length). That means that the ONLY available copy of your work is the one currently open in ProntoEdit. Now, it is possible to get around this problem by changing the SIZE= value in the pronto.ini file (see earlier in the FAQ for specific directions on how to do this for the creation of a large gallery file), but ProntoEdit must be restarted before such changes take effect. If you do that, you will completely lose that file.

No matter what, some of your work is going to be lost. What you must now do is delete enough panels or devices from the current open configuration until ProntoEdit successfully saves the file. After that, if you still want to create a larger file, you may exit the software and modify the configuration file. Note that even if you do this the Pronto itself will not be able to hold a configuration larger than the original value for your model - don't try. To be safe, always return the pronto.ini file back to its original settings before working on a file that will be sent to your remote.

In Windows NT/2000/XP it is possible to disable "8.3 filenames". 8.3 filenames are a holdback from the old MS-DOS days, where filenames couldn't be longer than 8 characters, plus a 3 character extension. With the advent of long filenames ("My Accounts for 2001.xls"), there is no longer any reason to keep filenames short. Which is why some users decide to disable the old-fashioned 8.3 filename compatibility mode.

However, while ProntoEdit will work fine with long filenames, ProntoEdit's emulator cannot. For example, the filename

My Pronto Configuration.ccf

would need to look like

mypron~1.ccf

to the emulator. However, if you disable short filenames, the file looks like

My Pront.ccf

...which does not exist. To solve this problem you must either re-enable 8.3 filenames, or keep your filenames shorter than 8 characters in length, with no spaces.

It has been found that the appearance of strange symbols under only the alias list is caused by a bug in one of the library files installed by Microsoft Internet Explorer 5.0 and 5.5. The solution for 5.0 users is to upgrade to version 5.01, which you may download from Microsoft's Windows Update web site. IE5.5 users cannot easily fix this problem, though installing an older version of comctl32.dll may work.

This has been fixed in ProntoEdit v4.0 and newer.

Another font problem may occur under Windows XP, 2000 or NT -- after installing ProntoEdit no symbols will appear correctly on any screen. The solution is to reboot your computer, which will finalize installation.

Other font issues may be caused by a corrupt or missing font file. If you can access a font named "Pronto" from your word processor -- and it looks like the Pronto's text -- everything should be working in ProntoEdit. If it is instead missing from both your word processor and the Windows Font Manager you may need to reinstall ProntoEdit, or manually install the font file (pronto.ttf) which should be located in c:\windows\fonts\.

The self-installing ProntoEdit download (earlier than version 4.0) does not have any internal CRC checking – thus if you had a corruption problem while downloading, the package will still merrily install invalid files, causing the program to run incorrectly. The solution to this problem is simple: download the file again. Also, ensure the file saved to your hard drive is of appropriate size.

This is a known condition in most installations of Windows XP, Windows 2000 or Windows NT 4.0. Some systems may be able to learn codes successfully (particularly under Windows XP), however for the rest there are no known fixes. The best solution is to download your unpopulated CCF file to the remote, and then learn all IR codes on it. When finished, upload the file back to the computer.

If you receive the error "PRONTOEDIT.EXE is linked to missing export MFC42.DLL:6880" then one of two things is wrong.

First, you must make sure that all programs are closed. Hit <CTRL> <ALT> <DEL> all at once and END TASK each item on the list except for Explorer and Systray.

Next, go to a DOS Prompt (Command Prompt) and type:

• cd\windows\system (press ENTER)
• ren mfc42.dll mfc42_orig.dll (press ENTER)
• exit (press ENTER)

  If this does not work you must "Restart in MS-DOS mode" and perform the above steps.

  Now, reinstall ProntoEdit.

  The problem should now be corrected, however if it is not then you may have multiple copies of the MFC42.DLL file. Use the Start Menu's "Find - Files or Folders" options to search and obtain a list of all MFC42.DLL files. Rename them one by one using the above method (substituting the correct directory/folder) until the error with ProntoEdit stops.
  

In ProntoEdit v2.0, you can't edit, copy or paste IR hex codes - the window is grayed out. To fix that you must edit the c:\windows\pronto.ini file with a text editor, such as Notepad (or for an automated method download Pronto.ini Workshop). Then, under the [version] section, add this line:

developer=1

Save, and restart ProntoEdit. You will now be able to copy, paste and otherwise massage IR hex codes in whatever way you like. You'll also notice that this adds a fourth button, "Advanced", which allows you to create RC5/6 codes, plus the device name right-click menu option "needs programming". If you find this screen too large on your system - it doesn't fit vertically - you must either switch to a higher resolution screen, or change from "Large Fonts" (125%) down to "Small Fonts" (100%) under your system display properties.

This has been fixed in ProntoEdit 3.0 and newer.

This is a known issue with ProntoEdit 2.0 and many recent versions of the software. All IR code labels cannot be changed - attempting to do so may result in no label at all. In turn, having no label may also result in the Emulator crashing when working with that page, however the actual remote will not have such a problem. Note that this does not affect button labels - just the internal infrared code labels.

Although some versions appear to let you change labels, it does in fact not work.

This has been fixed in ProntoEdit 4.0.3 and newer.

This error is caused by having a previous version of ProntoEdit or RC5000 Setup installed on your system and installing ProntoEdit v2.0. During the ProntoEdit installation process, instead of replacing or modifying an existing copy of the pronto.ini file with a single new configuration line, the program does nothing - and thus crashes when you try to load up the software.

To fix, you must edit the c:\windows\pronto.ini file with a text editor, such as Notepad (or for an automated method download Pronto.ini Workshop). Then, under the [ccf] section, add this line:

universal_size=960

Keep the "size=380" line as is. While you're in there, I strongly suggest making the change described just further up this page in FAQ section B11-08. Save your changes and you'll now be able to use ProntoEdit v2.0. If you have a problem with the pronto.ini file being "read only", then you may have installed Marantz Touch Screen Setup, which does strange things to your pronto.ini file. The Pronto.ini Workshop utility linked to earlier will correct that issue.

This is no longer a problem with ProntoEdit v3.0 and newer.