WinRVM FAQ

Table of ContentsManual Mode | Unattended Mode | Interactive Mode | Reimagine Mode | Options | Version history | FAQ

Click here for Pocket WinRVM FAQ.


If you're having a problem with WinRVM, first make sure you're running the latest version.

Installation issues:

The setup program displays "Setup fatal error: unable to generate installation log file"

How do you copy the WinRVM settings from one PC to another?

On startup WinRVM is displayed briefly then disappears

On startup WinRVM is not displayed, but is listed in the Windows Task Manager.

When running WinRVM for the first time it displays "run-time error 430: class does not support automation or does not support expected interface".

When running WinRVM for the first time it displays an error message that a required .dll or .ocx file is missing such as mscomct2.ocx, msvcrt.dll, scrrun.dll, wshom.ocx.

On startup WinRVM displays "Run-time error 9: subscript of out range" and WinRVM will exit (leaving WinRVM in memory). 

The "Host | Check for WinRVM update" feature says an update is available but the update fails for "Error in FTPDownloadFile(): 75: Path/File access error".

The "Host | Check for WinRVM update" feature says an update is available but it will not install or download, the log displays "Host didn't have a file for us".

The "connect via" setting in the Host options will not list any dial-up connections in the drop-down list, only "LAN" is listed.

When entering Unattended Mode, "RVM configuration lists different site names or site IDs for RVM 1!" is displayed.

The "Host" menu is unavailable (grayed-out).

The WinZip command line program won't install.

A command-line window displays "Thank you for trying winzip...press any key to continue".

After installing WinRVM and rebooting, Windows displays "Explorer has performed an illegal operation (page fault)" and you're unable to continue using Windows.

The WinRVM setup program displays "Setup cannot continue because some system files are out of date on your system" after rebooting and running setup a second time

Unable to upgrade to a newer version of WinRVM, a "Permission denied" error is logged.


Modem/host issues:

The modem stays connected for hours.

No data is received from the site, even tho the logs indicate it will successful in sending a file.

Get "ISP name phone book entry not found" when trying to dial.

WinRVM can connect to the ISP but it can't connect to the FTP server and logs "Unable to connect to host Envipco".

When sending data to the host, WinRVM locks up displaying the FTP window with 0 bytes sent/received.

WinRVM displays the error message "Error in FTPDownloadFile(): 75: Path/File access error" when trying to update the WinRVM documentation via the Host menu.

WinRVM can't connect to the FTP server when using a proxy.

When connecting to dial-up, WinRVM says it's instantly connected, following by "Dial-up: no existing connection"

When connecting to dial-up, WinRVM says it's instantly connected, following by "Unable to connect to host Envipco"

WinRVM sends a file into the host every few minutes

After remotely receiving a new version of WinRVM, WinRVM exits but doesn't restart WinRVM. When WinRVM is restarted, the old version of WinRVM would run.

WinRVM logs "error 550 access is denied" when logging into the FTP server

A dial-up error 692 "Hardware Failure in the Modem" occurs

A dial-up error 623 "System could not find the phone book entry for this connection" occurs

The Dial-Up Networking Password Is Not Saved

Various dial-up errors occur

A "run-time error 53: file not found" occurs when attempting to send data to the host.

The modem won't answer a call.

When uploading a file from WinRVM via MUSTATUS's "view remote file" feature, the file is garbled except in the beginning. 

WinRVM won't let me select the modem's COM port in the Unattended Mode Options.

The modem doesn't disconnect after WinRVM is done communicating with the host.

WinRVM displays "unable to connect to host" and doesn't display the dial-up window.

When attempting to dial the host, a "no dial tone" error message is displayed.

WinRVM displays a message such as "Upload file not found: c:\bb\999999_03-05-03_112826.zip" when attempting to transmit a file to the host.

WinRVM logs "No zip file to send" when performing a scheduled call.

WinRVM isn't sending an email when an error occurs

How do you test sending an email for an RVM error?

When sending a file WinRVM logs "Error 12031 connection to the server was reset. File transfer terminated."

WinRVM can't unzip a file received from host.


RVM Communications issues:

WinRVM is unable to communicate with any RVMs.

WinRVM displays "Communications difficulty: nnnn parity/break/framing/overrun/overflow errors".

WinRVM displays various communications problems such as "REQ n" and "NAK n".

WinRVM is unable to load software to an RVM but other RVM communications works.

The error message "No response from RVM, waiting for C_STOP" occurs at the beginning of an RVM software update.

The COM port number for my USB to serial adapter is COM10 or higher and WinRVM doesn't recognize it.

After replacing the USB RS485 adapter, WinRVM displays "Invalid RVM COM port"

WinRVM displays the error message "Port already open"

After changing the current RVM address/port, WinRVM displays "run-time error 35600, index out of bounds". This error would then occur each time WinRVM was run.

How do you configure WinRVM to use "no parity"?

An RVM isn't communicating and the serial number is wrong (after moving netbook from one store to another)

Also see the Pocket WinRVM RVM communications FAQ.

Also see Communications Problems (Site Controller/WinRVM)... 


General issues:

The menu item "Host | Check for WinRVM program update" fails with a message about unable to change folders.

When sending barcodes to the RVM the error message “Parameter SUPPLEMNTMODE not recognized by RVM” occurs.

A 3-way RVM's Q file indicates all 3 readings are glass (the HT lines are "HGF")

A Q file's meter reading is missing after the "HM" line in the Q file.

WinRVM displays the error message "unexpected End-Of-File, probably no data" when sending a voucher file to the RVM.

Storing images in a Hecon or Swecoin printer doesn't work

When configured for PC-DAS, when applying barcode updates to the RVM, WinRVM would log "Received file: cf1500a.tbl" but would not send the files to the RVM(s) nor display "Processing received files [timer]".

How do you configure WinRVM for a POS system?

After sending a voucher to a Hecon printer, the voucher no longer prints.
After clicking , WinRVM displays "RVM serial number [nnnnnn] not found!"

WinRVM displays "unknown error" for a certain RVM error.

On startup WinRVM unexpectedly enters Unattended Mode and displays "Can't enter Unattended Mode - you haven't entered the RVM configuration info! Would you like to enter the RVM configuration info now?"

WinRVM prompts me to "select the maxpay amount" when sending a parameter table to an RVM. How do I turn this off?

WinRVM sends/prompts the wrong file after updated the RVM software or performing a board swap procedure and then moving to a different RVM.

How do you automatically send a specific barcode file to a stand-alone RVM?

How do you send a new version of WinRVM to a WinRVM site running in Unattended Mode?

Barcodes are not sent to the RVMs after barcodes are sent by the host to a PC in Unattended Mode.

Q files aren't being sent to the server, but the site is calling in.

A "Run time error 13: type mismatch" occurs when attempting to send barcodes to an RVM.

Whenever a barcode table is sent to an RVM, the barcode file's time/date stamp gets changed to the current time.

When one RVM is placed into service mode, WinRVM isn't putting the other RVMs into service mode.

WinRVM would lock up (display "not responding") after attempting to enter the Options dialog box.

The RVM is out of service for "WAITING FOR STARTUP".

After selecting "File | create generic RVM parameter tables" the DOS box remains on the screen.

On startup WinRVM beeps but no window appears.

On startup WinRVM displays "Run-time error 7: out of memory"

On startup WinRVM displays "Run-time error" 13 or 35600

On startup WinRVM displays "run-time error 53: file not found", it will not respond to any mouse clicks and the mode button is labeled "in [specific] mode".

A "Run-time error 5: invalid procedure or argument call" occurs and the computer runs very slowly.

When running WinRVM, the program stays minimized in the task bar or fails for a run-time error.

What cables are needed to connect a remote display?

The remote display's "Send test message" button in Unattended Mode Options doesn't work after changing the COM port.

The remote display was accidentally unplugged and plugged back in but it no longer reports errors.

When sending a new RVM program (IMG file), the following warning message is displayed "W659; CRC Error Sent xxxx, Rcvd yyyy"

The message "Insufficient system resources exist to complete the requested service" pops up when zipping a file to send to the host


The menu item "Host | Check for WinRVM program update" fails with a message about unable to change folders.
[added 5/5/15]  Give user write access to the folder "c:\Program Files (x86)\WinRVM". Otherwise, the "Host | Check for WinRVM program update" will not work.
Open "Computer" (Windows Explorer) and browse to "c:\Program Files (x86)", right-click the "WinRVM" folder and select "Properties". Click the "Security" tab. Click "Edit". In the "Group or user names" section, click "Users (...)" then in the "Permissions for Users" section, scroll down and and put a check-mark by "Write" in the "Allow" column. Click OK twice.


 

When sending barcodes to the RVM the error message “Parameter SUPPLEMNTMODE not recognized by RVM” occurs.
[added 8/29/13]  Solution: update to the latest version of the file supplemental.opt in \cf1500 which doesn't reference the SUPPLEMNTMODE parameter (you can also simply put a ";" in front of this line). This only occurs when using 2/8/12 or later RVM software and "Enable supplemental barcodes in RVM when sending barcodes" is enabled in WinRVM.

A 3-way RVM's Q file indicates all 3 readings are glass (the HT lines are "HGF")
[added 5/17/12]  The technician needs to make sure “Support 3-way enhanced capacity glass” is unchecked in WinRVM’s Barcode Options. When this is enabled it treats a tri RVM as a 3-way glass RVM, which when downloading, causes all the machine type header lines in Q file to show up as glass. This setting is currently only used in Iowa and Hawaii.

A Q file's meter reading is missing after the "HM" line in the Q file.
[added 12/11/15]
Make sure the following setting is NOT enabled in WinRVM’s General Options:
“Don’t prompt for meter reading for any RVMs”. If this has a check mark, this will result in a blank “HM “ line being written to the Q file.

WinRVM displays the error message "unexpected End-Of-File, probably no data" when sending a voucher file to the RVM.
[added 4/24/12]  Disable "Automatically center store info on vouchers" in WinRVM's general options and try again. Make sure the file you are sending is valid.

When sending a new RVM program (IMG file), the following warning message is displayed "W659; RVM memory CRC error, RVM controller may be bad! Sent xxxx, Rcvd xxxx"
[updated 9/4/13]  This error message indicates the RVM memory is defective and the RVM controller needs to be replaced.

Whenever this message is displayed WinRVM aborts the IMG loading process and prompts "Error, retry?". I recommend the techs click retry which will force WinRVM to resend the IMG file to the RVM. If the same message is displayed the RVM controller should be swapped. If you click "No" to the retry the RVM is left in a state where it has no tables loaded into memory.
You may be able to get the RVM running by manually reloading all the tables but I would not trust the RVM, as it is known to be defective. If just one memory location is defective the RVM may run fine until it tries to run the piece of code that corresponds to the defective memory location at which point the RVM will do something unpredictable such as locking up. It could do anything such as corrupting all the barcode counts, turning on all the motors, etc. Basically anything could happen, so it is unsafe to use an RVM with a known memory problem. Perhaps the bad memory location is somewhere that will never be accessed under normal use (relating to a feature/parameter that is disabled), but there is no way to determine this, so the controller should be replaced.

Another possible solution:
- Turn off the RVM and remove these 2 RAM chips (U26,U27) for at least 10 seconds, then plug them back in, swapping the position of chips U26 and U27, then power up the RVM.
- Set the proper RVM communications mode (Hold the '#' key on the keypad. Turn the RVM on.)
- From WinRVM, select "Advanced | Install RVM program" but don't select "Yes". Turn the RVM off and back on then immediately select "Yes" to  load the RVM program.

The message "Insufficient system resources exist to complete the requested service" pops up when zipping a file to send to the host
[added 1/10/18]  This is a low-memory warning from Windows, not a WinRVM error message. 

See this page for some things to try: https://www.drivethelife.com/windows-10/insufficient-system-resources-exist-to-complete-the-requested-service-windows-10.html

 I also discovered in my googling:

Configuring WinRVM to reboot the PC at least once a day may help prevent this if it’s not already configured to do so.

Storing images in a Hecon or Swecoin printer doesn't work
[added 3/24/09]  A bug in WinRVM versions prior to 1.9.6 caused the last image not to be sent to the RVM. Workaround: add a blank line at the end of the .PIL file.

When configured for PC-DAS, when applying barcode updates to the RVM, WinRVM would log "Received file: cf1500a.tbl" but would not send the files to the RVM(s) nor display "Processing received files [timer]".
[added 4/11/06]  This is a bug in WinRVM versions 1.5.4-1.5.6. Load the latest version or version 1.5.3.

After sending a voucher to a Hecon printer, the voucher no longer prints.
[added 4/11/06]  You must disable the "Automatically center store info on vouchers" in the General Options, otherwise the voucher template will be corrupted.

After clicking , WinRVM displays "RVM serial number [nnnnnn] not found!"
[added 10/11/05]  If you are not in the NorthEast U.S., you should disable "use recmod extraction" in the barcode options.
If you normally use recmod extraction, then the serial number may be programmed into the RVM incorrectly or the RVM machine type is incorrectly set (for example: configured as a glass machine instead of a PET machine). Click to verify/change the RVM configuration info. If the RVM is configured properly then perhaps the recmod serial number file is out of date or incorrect...obtain a new copy of the file.

When connecting to dial-up, WinRVM says it's instantly connected, following by "Dial-up: no existing connection"
[added 5/23/14]  Use WinRVM 3.6.7 or later and enable "Use RasDial to dial ISP with:" in the Host Options.
If that doesn't fix, delete the dial-up connection and add a new one.

When connecting to dial-up, WinRVM says it's instantly connected, following by "Unable to connect to host Envipco"
[updated 10/9/17]  Here is a log snippet:
<409999> 05/25/16 13:02:22 -- Dialing Dial-up Connection
<409999> 05/25/16 13:02:23 -- using RasDial, ISP username=winrvm01@earthlink.net
<409999> 05/25/16 13:02:23 -- Dial-up connection to Dial-up Connection established
<409999> 05/25/16 13:02:25 -- Unable to connect to host Envipco (ftp.envipcotech.com)
<409999> 05/25/16 13:02:25 -- Dial-up connection terminated

Use WinRVM 3.6.7 or later and enable "Use RasDial to dial ISP with:" in the Host Options.
Make sure the dial-up name doesn't contain a space (unless using WinRVM 4.0.4 or later).
Delete the dial-up connection and add a new one.

Get "ISP name phone book entry not found" when trying to dial.
[added 3/9/15]  Restart WinRVM. In WinRVM's Host Options, click the "Connect via" drop-down box and select the correct ISP name.

No data is received from the site, even tho the logs indicate it will successful in sending a file
[added 10/3/19] 
1. Click “File | Options | Host | Edit FTP Server Configurations | Reset to defaults”. Click Save and retry and then call me to see if the file shows up.
2. If that doesn’t work, click “Reset ALL settings to default values” in the general options, then reconfigure the site ID and any other custom settings and try again.
3. If that doesn’t work, uninstall WinRVM, and install the latest WinRVM version via the setup program and try again (make sure I’m standing by to look for an incoming file).
4. If that doesn’t work, change the “Host server” in the Host Options to “Envipco FTP” and try again.

The modem stays connected for hours.
[added 9/9/15]  1. Use the latest version of WinRVM (ver 3.7.3 and later retry terminating the dialup connection a few times if unsuccessful the first time. If it still can’t terminate the dialup it will reboot the PC which should terminate the connection).

2. Set the modem’s internal “Disconnect Inactivity Timer” to 60 seconds (the modem will hang up if no data is sent or received within this timeframe).
Run Device Manager: from WinRVM’s “RVM Comm” Options, click the “Run Windows Device Manager” button (or click “Start”, type in “device” then click “Device manager” in the list.)
Expand the “Modem” section, and double-click “USB Modem” or “Conexant USB ... Modem”.
Click the “Advanced” tab.
Under “Extra initialization commands”, enter “ATS30=6” (without quotes!).

Don’t click OK yet…

3. Perhaps there is an updated Windows modem driver that solves this issue.
Click the “Driver” tab in the Device Manager and note the driver date.

Click OK.

Zoom’s driver update page indicates the latest Windows 7 32-bit driver is 2/9/11, the latest Windows 8 driver is 12/21/12.
If the installed driver date is earlier than the latest version you should update the driver by downloading the appropriate driver such as 3095_Win7-32bit_v20220.exe for 32-bit Windows 7 and run it with the modem still plugged in and follow the instructions.
After installing, verify the driver date.
I recommend downloading to a USB stick before heading to the store to save time downloading over dialup.

4. When using dialup, Windows update should be disabled (perhaps Windows sees the internet is connected then starts downloading some huge update).
Click “Start”, type in “windows update” and click the “windows update” icon in the list.
Click “Change settings” on the left.
Under “Important updates”, change setting to “Never check for updates (not recommended)”.

Click OK.

5. If none of the above solve the problem, install and run MBAM free to ensure there’s no malware.
I recommend downloading to a USB stick before heading to the store to save time downloading over dialup.

WinRVM can connect to the ISP but it can't connect to the FTP server and logs "Unable to connect to host Envipco".
[added 3/6/15]  If using dialup, try installing a Clip On Noise Suppressor to see if that helps. Also rerouting the phone cable away from any device that may be causing interference may help.
Also try:
Temporarily enable the "even more" debugging messages in the General Options.
Enable the "RasDial" feature in WinRVM’s Host Options (requires WinRVM 3.6.7 or later). This works with 32 and 64-bit Windows.
Try that a few times, if that still doesn’t work, email me the WinRVM log file.
Disable the "even more" debugging messages in the General Options.

WinRVM sends a file into the host every few minutes
[updated 10/13/14]  In WinRVM's Host Options, make sure "Contact host every x minutes" is set to 0 and "also every x minutes" is set to 0 in the "send data to host" section. If that doesn't fix the issue then it's most likely an RVM error that is being repeatedly sent by the RVM for some reason. Try sending the correct ERRLIST file to the site, as the version on site may be incorrect (set to call for any error such as bin full).
Either resolve the RVM issue or edit the errlist file so that the particular error being sent doesn't generate a call, but just log the error message. For example, if W490 is being constantly sent by the RVM, change
0490 W C N RVM returned to service
to
0490 W L N RVM returned to service
then restart WinRVM.

WinRVM displays the error message "Error in FTPDownloadFile(): 75: Path/File access error" when trying to update the WinRVM documentation via the Host menu.
[added 1/19/12]  Disable User Account Control in Windows as explained in the WinRVM installation instructions then rerun WinRVM.

WinRVM can't connect to the FTP server when using a proxy.
[added 3/25/16]  In, the Host Options, click "Edit FTP server configuration".
Change the "Address" field from "ftp.envipcotech.com" to the proxy hostname.
Change the "user name" field from "winrvm" to "winrvm@ftp.envipcotech.com".

After remotely receiving a new version of WinRVM, WinRVM exits but doesn't restart WinRVM. When WinRVM is restarted, the old version of WinRVM would run.
[updated 2/24/09]  This was fixed in update.bat by increasing the delay to wait for WinRVM to close from 3 to 9 seconds on 4/3/08.
To fix:
- On site: use "Host | Check for WinRVM documentation update" which will download the latest version of update.bat to C:\Program Files\WinRVM\WinRVM_docs.
- Remotely: use SiteZipCopier to send UpdateBatchFile.zip to the site.

WinRVM logs "error 550 access is denied" when logging into the FTP server.
[added 8/4/05]  Make sure the user name and password are correct in the Edit FTP server configurations window; they are case-sensitive.

A dial-up error 692 "Hardware Failure in the Modem" occurs.
[added 4/10/14]  Turn off the PC. Unplug the USB modem. Turn on PC. Exit WinRVM. Plug modem page in. Run WinRVM and retry. If it still doesn't work, delete the dial-up connection and reenter the info, restart WinRVM. If that doesn't work, try a different modem.

A dial-up error 623 "System could not find the phone book entry for this connection" occurs
[added 7/13/18]  Close and reopen WinRVM. Go to the Host Options, under "Connect via", select the drop-down list and select the correct dialup name. Click OK and retry.

Various dial-up errors occur
[added 4/22/14]  Check the phone cable and make sure it's not passing near something that could give off interference such as an electric motor, power supply, etc. Try routing the cable differently or try using a different phone cable. If the cable is long (more than 10') add a clip-on ferrite core noise suppressor/filter.

WinRVM displays "unknown error" for a certain RVM error.
[updated 12/15/14]  Make sure you have the latest ERRLIST file (available in the RVM data files) in c:\cf1500. If you copy a new version to c:\cf1500 you must restart WinRVM if it is running.
If it displays "Unknown error 0", the above instructions won't help. This simply means the RVM is in sleep mode. Once WinRVM wakes up the RVM it will operate normally.

On startup WinRVM unexpectedly enters Unattended Mode and displays "Can't enter Unattended Mode - you haven't entered the RVM configuration info! Would you like to enter the RVM configuration info now?"
[added 7/1/05]  WinRVM's registry settings got corrupted somehow. To fix:

WinRVM prompts me to "select the maxpay amount" when sending a parameter table to an RVM. How do I turn this off?
[added 6/30/05]  Click the new "Edit custom parameter prompts" button in the Manual Mode Options ( to the right of the "parameter table" check box) to edit the file c:\cf1500\prompt.ini. Put a ";" in front of the line:
Select maxpay amount,MAXPAY,$2.55,$5.00,$5.15,$6.00,$7.50,$9.95,$10.00,$12.00,unlimited (0)
then save the file. Alternatively you could rename or delete prompt.ini.

WinRVM sends/prompts the wrong file after updated the RVM software or performing a board swap procedure and then moving to a different RVM.
[added 6/20/05] This is a bug in WinRVM versions prior to 1.3.8 (and Pocket WinRVM 1.0.9). Upgrade to the latest version. 
As a workaround: go to the "Advanced | Set/modify RVM info" and click cancel after performing a software update.

How do you automatically send a specific barcode file to a stand-alone RVM?
[added 3/18/05] Copy your specific barcode filename (such as "Buy 4 less abar.tbl") to multiple files whose filename starts with the RVM serial number to receive this file. For example, if you have 3 can RVMs with serial numbers 111111, 222222, 333333 that you want to load a "Buy 4 less abar.tbl" to, copy "Buy 4 less abar.tbl" to these filenames: 
111111abarcode.tbl
222222abarcode.tbl
333333abarcode.tbl

 
Copy these 3 files to \cf1500 on the pocket pc. When you send barcodes (or any file for that matter) to the RVM, WinRVM first looks to see if ssssssFILENAME.TBL exists and will send it. Note: ssssss=RVM serial number and FILENAME.TBL is the default filename such as abarcode.tbl when sending a can barcode table. 
This is a good method because the technician just selects "send barcodes" and the correct file will automatically be sent to the RVM without him having to choose the file. The downside is that every time the "Buy 4 less abar.tbl" changes, you have to create a new set of individual barcode files such as 111111abarcode.tbl. However, you could easily create a batch file to do this automatically each time "Buy 4 less abar.tbl" is created. 

How do you send a new version of WinRVM to a WinRVM site running in Unattended Mode?
[added 2/23/05] Zip the new version of WinRVM.exe and CURRENT_WINRVM_VERSION.TXT into the corresponding siteid.zip such as 123456.zip. When the site contacts the host and retrieves the siteid.zip file, it will install the new version of WinRVM. Note: under certain circumstances, such as if a new DLL is required, the new version of WinRVM may require a full installation. In this case, WinRVM will not attempt to install the new version.
Required WinRVM ver 1.0.7 or later.

Note: for pocket WinRVM, zip PocketWinRVM.exe and CurrentPocketWinRVMVersion.txt into the corresponding siteid.zip instead.
Required Pocket WinRVM ver 1.0.5 or later.

The Dial-Up Networking Password Is Not Saved
[added 2/17/05] See http://support.microsoft.com/?kbid=148925

When sending data to the host WinRVM locks up displaying the FTP window with 0 bytes sent/received.
[updated 3/29/12] The Windows firewall might be blocking WinRVM. For Windows 7: Click start, type in “firewall” then choose “allow a program through windows firewall”. If “Communicates with CF1500 RVMs” is listed, make sure private and public check boxes are checked (for all instances of WinRVM). If it’s not listed, click  “Allow another program” then select WinRVM from the list, click “Network location types”, then enable both private and public networks, press OK then click “Add”.

Use WinRVM 3.3.5 or later and enable "Passive connection" in the Host Options in the FTP section, especially if using a wireless modem.

This can be caused by anti-virus software that is attempting to update it's database. eTrust Antivirus must be configured to not prompt the user before dialing.

When sending data to the host, you get various error messages like "Connection to server reset"
Use WinRVM 3.3.5 or later and enable "Passive connection" in the Host Options in the FTP section.

Barcodes are not sent to the RVMs after barcodes are sent by the host to a PC in Unattended Mode.
[updated 7/23/18] In WinRVM's General Options, make sure that "Use eDAS 2007 barcode format" is disabled and make sure the barcode file naming convention is set correctly (usually "siteidX.tbl"). To fix remotely: send Use_SC_Barcode_Naming_Convention.zip to the site with SiteZipCopier.

Q files aren't being sent to the server, but the site is calling in.
[added 7/23/18] In WinRVM's General Options, make sure “Report RVM status only (No Q file)” is NOT enabled. To fix remotely: send EnableQFileSending.zip to the site with SiteZipCopier.

A "Run time error 13: type mismatch" occurs when attempting to send barcodes to an RVM.
[added 6/22/04] There is probably a formatting problem with the barcode file. Load the file into the Barcode Converter program which will display where the problem is.

Whenever a barcode table is sent to an RVM, the barcode file's time/date stamp gets changed to the current time.
[added 4/23/04] This is normal, it occurs because WinRVM sorts the barcode table before sending it to the RVM.

The modem won't answer a call.
[added 4/23/04] Make sure WinRVM version 1.2.9 or later is installed.
If using an external modem the modem cable must support the following hardware handshake line: RI.

When uploading a file from WinRVM via MUSTATUS's "view remote file" feature, the file is garbled except in the beginning. 
[added 4/23/04] If using an external modem the modem cable must support the following hardware handshake lines: RTS, CTS.
Make sure WinRVM version 1.2.9 or later is installed.

WinRVM won't let me select the modem's COM port in the Unattended Mode Options.
[added 4/16/04] First, verify which COM port the modem is on via the Window's device manager (click button in the RVM Comm options). Double-click Modems, then double-click the installed modem. Click the "modem" tab, the Port number will be listed at the top. Keep the device manager windows open.
From WinRVM's Unattended Mode Options, click the drop-down arrow by the Modem section. If WinRVM doesn't list the COM port that the modem is attached to, exit WinRVM then return to the device manage window and click the "advanced" tab in the modem window, then click the "Advanced port settings" button. Click the "Com port number" and change it to the next available Com port number that is not in use. Reboot the PC. WinRVM's Unattended Mode Options should now list the COM port of the modem - select it and click OK.

On startup WinRVM displays "Run-time error 7: out of memory"
[added 5/12/04]One of the WinRVM registry settings may be corrupt due to running a beta VB.NET version of WinRVM. Erase the WinRVM registry settings as described here.

On startup WinRVM displays "Run-time error" 13 or 35600
[added 4/16/04]One of the WinRVM registry settings may be corrupt, erase the WinRVM registry settings as described here.

On startup WinRVM beeps but no window appears.
[added 4/14/04]Make sure another copy of WinRVM isn't already running (run the task manager and look for WinRVM). 
On Windows XP, try renaming the file c:\program files\WinRVM\WinRVM.exe.manifest to something else and rerunning WinRVM.
Upgrade to the latest version of WinRVM. Reboot your PC. If all else fails, erase the WinRVM registry settings as described here.

How do you copy the WinRVM settings from one PC to another?
[updated 8/4/09]
1. From the master PC, click "start | run" enter "regedit" and hit Enter.
2. Browse to registry key "HKEY_CURRENT_USER\Software\VB and VBA Program Settings\WinRVM"
3. Click "WinRVM" to select it. Click the "File" menu (Windows XP) or "Registry" menu (Windows 2000) and select "Export". Enter a filename such as "WinRVM settings July 28 2009.reg". Make sure "export range" is set to "selected branch" then click "Save".
4. Close Regedit.
5. Copy the ".reg" file created in step 3 to your destination PC. Make sure WinRVM is NOT running then double click the .reg file and click "yes" when asked "Are you sure you want to add the information in [filename.reg] to the registry?"
You can perform this step before or after installing WinRVM, it doesn't matter.

On startup WinRVM is displayed briefly then disappears
[added 12/5/07] Terminate winrvm.exe from the Task Manager (press ctrl-alt-delete, select task manager, then "processes").
Create a file named WinRVMfilestamps.txt in c:\cf1500. To create: run notepad, type a space then click "file | save as".
Re-run WinRVM.
This bug was fixed in WinRVM versions 1.8.3 and later.

On startup WinRVM is not displayed, but is listed in the Windows Task Manager.
[added 8/22/07] Terminate winrvm.exe from the Task Manager (press ctrl-alt-delete, select task manager, then "processes").
Re-run WinRVM but hold down the shift key while launching WinRVM. WinRVM should prompt if you want to reset the registry settings. Select "yes".
If this still doesn't fix the problem, re-install WinRVM from the setup file, but if Windows warns you that it is installing older versions of certain files, select the option to overwrite these files (such as system32\wshom.ocx, system32\msvcrt.dll, system32\scrrun.dll) with the older files from the WinRVM installation, with the exception of system32\quartz.dll.

When running WinRVM for the first time it displays "run-time error 430: class does not support automation or does not support expected interface".
[updated 4/19/10] Install a codec pack as explained in the WinRVM setup instructions.
This can also happen when installing on Windows 98. To fix, run an older WinRVM setup program such as ver 1.6.2 first, then install the latest WinRVM version without uninstalling the old version.

When running WinRVM for the first time it displays an error message that a required .dll or .ocx file is missing such as mscomct2.ocx, msvcrt.dll, scrrun.dll, wshom.ocx.
[added 8/30/07]  Install WinRVM ver. 1.6.1 from the setup file, then reinstall the latest version of WinRVM.

On startup WinRVM displays "Run-time error 9: subscript of out range" and WinRVM will exit (leaving WinRVM in memory). 
[updated 11/23/05] This happens if you run version 1.4.5 (or later) of WinRVM, then you run a previous version of WinRVM. If you really need to run an old version, you can hold the shift key down when running the old version of WinRVM and select "yes" to the prompt about resetting WinRVM's registry settings. You only need to do this once (unless you run WinRVM ver 1.4.5 or later).

The "Host | Check for WinRVM update" feature says an update is available but the update fails for "Error in FTPDownloadFile(): 75: Path/File access error".
[updated 9/9/15]See the section on "Write access" to resolve.

The "Host | Check for WinRVM update" feature says an update is available but it will not install or download, the log displays "Host didn't have a file for us".
[updated 3/31/04]This seems to be an intermittent problem, but has been fixed in WinRVM version 1.2.8. 
As a workaround, run Windows Explorer, browse to c:\program files\WinRVM and run WinRVM.exe from here and try again. Make sure WinRVM.exe is spelled with the proper case. If you still can't get it to work, call Randy to temporarily rename WinRVM.zip to WINRVM.zip on the host server.

The "connect via" setting in the Host options will not list any dial-up connections in the drop-down list, only "LAN" is listed.
[added 1/23/04]This bug is in WinRVM version 1.1.9-1.2.1. As a workaround, exit WinRVM, run regedit and change
HKEY_CURRENT_USER\Software\VB and VBA Program Settings\WinRVM\settings\InternetConnectionName
to the dial-up connection name such as "Earthlink". The next time you run WinRVM the "connect via" should be set to "Earthlink".

When one RVM is placed into service mode, WinRVM isn't putting the other RVMs into service mode.
[added 12/3/03]Edit PARMS.TBL and set SC_ATTACHED=1. Click "File | Created individual RVM parameter files" then send the parameter files to all RVMs.

WinRVM would lock up (display "not responding") after attempting to enter the Options dialog box.
[added 12/1/03]This bug occurred in WinRVM versions 1.1.2-1.1.8 if no dial-up connections were defined in Windows. There are two solutions:
1. Create a dial-up connection in Windows, even a bogus one.
2. Update to WinRVM version 1.1.9 or later.

How do you configure WinRVM to use "no parity"?
[updated 6/30/05] For Fuji RVMs only: WinRVM does not have a way to change the parity directly. However, you can use 'no parity' by running 'regedit' and changing the registry key:
HKEY_CURRENT_USER\Software\VB and VBA Program Settings\WinRVM\settings\CommPortSettings
from "19200,o,8,1" to "19200,n,8,1" then re-running WinRVM. The RVM's MONitor ROM must be set to 'no parity' also (hold '#' while powering up the RVM, then select '0' to change communications options which requires a MON ROM version 2/15/00 or later).

An RVM isn't communicating and the serial number is wrong (after moving netbook from one store to another)
[added 10/19/16] This was fixed in WinRVM 3.7.7: clicking the "Clear list" button in the RVM configuration list now also clears the list of previous RVM serial numbers.
As a workaround for previous versions of WinRVM, exit WinRVM, delete registry key "HKEY_CURRENT_USER\Software\VB and VBA Program Settings\WinRVM\PreviousSerialNos and SerialNos" then restart WinRVM.

No RVM error messages are reported.
[added 10/13/11] In WinRVM's RVM Communications Options, set Hardware handshaking to "On". Also make sure SC_ATTACHED=2 in the RVM.

When entering Unattended Mode, "RVM configuration lists different site names or site IDs for RVM 1!" is displayed.
[added 11/6/03] When initially installing a new WinRVM PC in the field, after selecting "fill list by asking RVMs" in the RVM configuration list, I recommend manually deleting all site ID and site name entries for all ports except port 0. Then click "Update only (all RVMs)" so that the site ID and site name from port 0 will be sent to all other RVMs. In the future WinRVM will be changed to make this smoother.

The "Host" menu is unavailable (grayed-out).
[added 10/20/03] You must fill in all information in the Host Options to enable the host menu.

The modem doesn't disconnect after WinRVM is done communicating with the host.
[updated 10/14/03]WinRVM versions 1.12 and later should immediately disconnect. For WinRVM versions prior to 1.1.2 it is normal for the modem to stay online for 1 minute after WinRVM is done communicating. If the modem stays online for more than 2 minutes, check the following:
1. disable any "modem on hold" application running in the background. Click here for info.
2. verify the dial-up connection is set to disconnect after 1 minute of idle time:
- click "start | connect to" and click on your ISP name such as "Earthlink"
- click "properties" in the connect window that just popped up
- click the Options tab.
- change "idle time before hanging up" to 1 minute
- click OK
- click cancel in the connect window

WinRVM displays "unable to connect to host" and doesn't display the dial-up window.
[added 10/7/03] For Windows XP: click "start | control panel | network and internet connections | Internet Options" and verify the following settings:
- click the "Connections" tab.
- under the "dial-up and VPN settings", verify the correct ISP name has "(default)" after the name such as "Earthlink (default)".
- click the "Always dial my default connection" button.
- click OK

If WinRVM still displays "unable to connect to host", exit and rerun WinRVM and try again.
Use WinRVM 3.6.7 or later and enable "Use RasDial to dial ISP with:" in the Host Options.

When attempting to dial the host, a "no dial tone" error message is displayed.
[added 10/7/03] Make sure the phone line is plugged into the correct phone jack on the modem. There are typically two phone jacks on modems - connect the phone line to the one labeled "line" (or it may have a phone jack icon). Do not plug into the jack labeled "phone" (or may have a phone icon).

A command-line window displays "Thank you for trying winzip...press any key to continue".
[added 10/7/03] You must enter the registration code into Winzip to avoid this.

The WinZip command line program won't install.
[added 10/7/03] Install Winzip first.

The COM port number for my USB to serial adapter is COM10 or higher and WinRVM doesn't recognize it.
[added 5/4/10] WinRVM versions prior to 3.0.0 only support COM port numbers from 1 to 9. So either upgrade to the latest WinRVM version, or change the COM port settings as follows:
in WinRVM, click "File | Options | RVM Comm".
Click the "Run Windows Device Manager" button.
Click "+" next to "Ports (COM & LPT)" to list your current COM devices.
Right-click on your USB-to-serial adapter's COM port and choose "properties".
Click the "Port Settings" tab, then "Advanced".
Click the drop-down box next to "Port number" and change the COM port number to less than 10. If using a desktop PC, don't use COM1 or COM2 as this may conflict with a physical COM port. Choose a COM port number such as COM5 to COM9. Choose a port number that isn't labeled "in use". If all COM port numbers are listed as "in use", select a port anyways and ignore the warning given.
Click OK. Click OK. Close Device Manager.
If you had to select a port labeled as "in use" you must now reboot your PC.
Rerun WinRVM and set the RVM Com port to the port number you selected above.

After replacing the USB RS485 adapter, WinRVM displays "Invalid RVM COM port"
[added 10/2/03] Replacing an existing USB RS485 adapter will cause Windows to place the adapter at the next unused COM port (for example, if the old USB adapter was using COM4, replacing the adapter will cause Windows to put the new adapter at COM5). 
To determine which COM port is the RS485 adapter:
for Win XP: click " start | control panel | performance and maintenance | system | hardware | device manager". Then double-click " ports".
for Win 95/98: click " start | settings | control panel | system | hardware | device manager | ports
You may need to reboot the PC before WinRVM will display the new COM port in the drop-down list in the RVM Communication Options.

After selecting "File | create generic RVM parameter tables" the DOS box remains on the screen.
[added 3/12/03] Upgrade to WinRVM software 1.3.1 or later to fix this problem. 
For older versions of WinRVM:
Close the window. To automatically close the window, copy the scsetmas.pif from the cf1500 installation disk to c:\cf1500. Or, from Windows Explorer, right-click on c:\cf1500\scsetmas.bat and select Properties, then click "close on exit" (may not be available in Win XP).
This can occur if the "RVM tables" folder is changed in the general options after WinRVM is installed.

On startup WinRVM displays "run-time error 53: file not found", it will not respond to any mouse clicks and the mode button is labeled "in [specific] mode".
[added 5/23/03] Make sure the Windows shortcut to WinRVM is configured to start in a folder containing at least one file. Also, exiting the program would not terminate it from memory (use Windows task manager to terminate it).
This bug was fixed in WinRVM ver 1.0.8.

A "Run-time error 5: invalid procedure or argument call" occurs and the computer runs very slowly.
[added 4/26/07] This can occur when running on and old PC. Boot into the CMOS settings and change the "system boot speed" from low to high.

A "run-time error 53: file not found" occurs when attempting to send data to the host.
[added 8/13/04] The last line on the display is something like: "Compressing files to c:\bb\999997_08-16-04_151243.zip". To fix, enable "log to file" in the General Options. This was fixed in WinRVM ver. 1.3.2.

What cables are needed to connect a remote display?
[added 3/2/11]

1.      #303760 USB to RS232 serial adapter (I’m using a different USB to RS232 serial in the photo, these are pretty standard, so any should work)
If you have a free physical serial port (COM1 or COM2) use can use a plain RS232 cable instead of the USB to RS232 adapter.

2.      Null-modem modtap adapter (DB9 female connector).

3.      Standard CAT5 LAN cable

The remote display's "Send test message" button in Unattended Mode Options doesn't work after changing the COM port.
[added 5/22/03] After changing the COM port you must click 'OK' and return to Unattended Mode Options before sending a test message

The remote display was accidentally unplugged and plugged back in but it no longer reports errors.
[added 2/15/06] Push the button on the remote display. If that doesn't work, restart WinRVM.

When running WinRVM, the program stays minimized in the task bar or fails for a run-time error.
[updated 4/29/04] Right-click WinRVM in the taskbar and choose "maximize". If you are unable to resize the WinRVM window, leave WinRVM maximized and restart the PC. If that doesn't work:

if using WinRVM ver 1.3.1 or later:
 
Hold the shift key down and start WinRVM.
WinRVM displays the following prompt: 
     Are you sure you want to reset ALL of WinRVM's
    registry settings to the default values?
    You will have to manually reconfigure all the Option windows!

Choose "yes". This should fix the problem but you must now reconfigure your WinRVM configuration options.

if using an older version of WinRVM:
Right-click WinRVM in the taskbar and choose "close". Press ctrl-alt-del and select "task manager", click "Processes". If "winrvm.exe" is listed, click winrvm.exe to highlight then click "End process". Delete all WinRVM registry keys by running regedit and deleting HKEY_CURRENT_USER\Software\VB and VBA Program Settings\WinRVM. Rerun WinRVM and reconfigure your WinRVM configuration options.

Note: this can occur if WinRVM is closed while it is minimized. WinRVM versions 1.1.0 and later do not have this problem.

After changing the current RVM address/port, WinRVM displays "run-time error 35600, index out of bounds". This error would then occur each time WinRVM was run.
[added 3/6/03] To fix: exit WinRVM, run regedit and set HKEY_CURRENT_USER\Software\VB and VBA Program Settings\WinRVM\settings\RS485Address=0.
This bug was fixed in WinRVM ver 1.04.

WinRVM displays a message such as "Upload file not found: c:\bb\999999_03-05-03_112826.zip" when attempting to transmit a file to the host.
[added 3/5/03] For installations to be run in Unattended Mode under Windows 2000 or Windows XP, you must install the Winzip command line programs and change the the Host Options settings for zip program (wzzip.exe), unzip program (wzunzip.exe), and both in folder (c:\program files\winzip).
If running under Windows 95, 98, Me, check the Host Options settings for zip program, unzip program, and both in folder, they should reference the default values (pkzip.exe, pkunzip.exe, c:\program files\winrvm). Check that pkzip.exe and pkunzip.exe are installed in the WinRVM program folder. If not, download the latest version of WinRVM and install.

[updated 3/7/03]This problem can also be caused on Windows 2000 or Windows XP systems if the user's security privileges prevent writing to c:\program files. This problem was fixed in WinRVM ver 1.04.

WinRVM isn't sending an email when an error occurs.
[updated 10/8/14]
There are several things that can cause this:
- Make sure “Minutes between email retries” is not 0 in the Misc Options.
- Column 8 of the errlist file isn't configured to send an email for the errors that are occurring.
- In WinRVM's Host Options, "Errlist col 8 override character for all errors" is set to not send an email for all errors  (normally this field is blank so that the ERRLIST file determines which errors send an email).
- The email settings aren’t configured properly (wrong email address/password/server/etc).
- sendemail.exe is missing from C:\Program Files\WinRVM. Check the WinRVM log to verify if this is the case.
- sendemail.exe is corrupted in C:\Program Files\WinRVM. Make sure the file size is 1497K.
- The RVM is in service mode.
- The RVM isn't communicating.
- You’re using a version of WinRVM prior to 3.3.5 that only supports sending emails from/to envipco.com addresses and you're trying to use a non envipco.com address.
- Some WinRVM versions prior to 3.4.4 had a bug that prevented error emails from being sent.

If you use WinRVM 3.5.3 or later you can use the "Send test email" button to verify the email is working.

How do you test sending an email for an RVM error?
[updated 7/1/13]
The easiest way is to use WinRVM 3.5.3 or later and simply click the "Send test email" button.
If you're using an older version, then use this complicated procedure instead:
1. In WinRVM’s Host Options, set the “Errlist col 8 override character for all errors” to “T” to send an email for ALL RVM errors.
2. In WinRVM's Reimagine Options (even if machine is not a Reimagine unit), configure the email settings. If using SSL, specify the mail server port in the server field by adding ":portnumber" to the server such as "smtp.gmail.com:587". Note: SSL requires WinRVM 3.3.5 or later.
3. Put WinRVM into Interactive mode (or Unattended Mode if you want to see the live log info, but this mode doesn’t play videos)
4. Create an RVM error such as:
- pulling the paper out of the printer
- blocking the bin full beam with some tape
- turning the motor overload switch (below maintenance key) to 0
5. Close cabinet door. WinRVM should immediately log the error and send an email.
6. Check the WinRVM log to see if the email was sent by exiting Interactive/Reimagine mode then clicking the notepad icon in the WinRVM toolbar.
You should see something like:
<E0039A> 07/09/12 10:44:54 -- Sending email '[Thirsty Camel Parap] E448: Glass Bin Full' to errors-nt@envirobank.com.au
<E0039A> 07/09/12 10:44:55 -- email sent
If you see the error "c:\Program Files\WinRVM\sendemail.exe not found, downloading file from host" make sure this file exists in your "tosite" folder on the hosts FTP server as described in WinRVM 3.3.5 so that WinRVM will automatically download this file. You can also manually copy sendemail.exe to c:\Program Files\WinRVM to fix the problem.

When sending a file WinRVM logs "Error 12031 connection to the server was reset. File transfer terminated."
[added 5/3/16]
This can happen if the FTP server is full, have the system administrator check.

WinRVM can't unzip a file received from host.
[added 10/19/17]
Verify the "Compression Options" settings in WinRVM’s Host Options, specifically the  “Unzip cmd line”. Generally, clicking the "Use 7-Zip" button will fix this problem.

WinRVM logs "No zip file to send" when performing a scheduled call.
[updated 6/27/13] Check the zip command-line arguments in the host options. Click the "Use Info-zip" button to use the default settings.

Note: 64-bit operating systems require a different zip/unzip program as follows:
Perform a full install of WinRVM ver 3.5.6 or later and click "Use 7-zip" in the Host Options.
If using an earlier WinRVM version perform these steps:
1. Download the free 7-zip compression program 7za920.zip (or latest "Command Line" version from this page).
2. Unzip the file 7za.exe to C:\Program Files (x86)\WinRVM
3. Run WinRVM (2.0.7 or later), go to the Host Options:
- change the zip AND the unzip program to 7za.exe
- "both in folder" should be "C:\Program Files (x86)\WinRVM"
- change "zip cmd line" to " a" (note there is a space before the 'a')
- change "unzip cmd line" to " e -y" (note there is a space before the 'e')
- click OK at the bottom

WinRVM displays the error message "Port already open"
[added 12/6/02] This indicates some other program is using the specified com port. Close the other program then rerun WinRVM. Do not run two instances of WinRVM at the same time! Perhaps "hot sync" software for use with a PDA is running (see taskbar icons). This can also occur if a DOS box is running and DOS software such as PCRVM was run. You must close the DOS box before running WinRVM. 
If this is the first time WinRVM is run it will default to COM1 - select the correct COM port in the RVM Communication Options

After installing WinRVM and rebooting, Windows displays "Explorer has performed an illegal operation (page fault)" and you're unable to continue using Windows.
[added 2/13/03] This is caused by an incompatible version of the file WININET.DLL that is copied to c:\windows\system during the installation process. This problem has occurred on Toshiba laptops running Windows 98.
To fix: reboot to a DOS command-line prompt by pressing F8 when you boot your PC, or boot from a boot floppy. 
Copy an appropriate version of the file WININET.DLL (click to download the 4/23/99 version) which is for Windows 98) to c:\windows\system, then reboot your PC, the problem should be fixed. 
Don't install WinRVM without first downloading the latest version off the web site, as this problem has been fixed (or just follow the directions below regarding changing SETUP.LST to skip WININET.DLL).
Note: all versions of the WinRVM installation zip files on the web site (including previous versions) were changed on 2/13/03 to avoid this problem.

The setup program displays "Setup fatal error: unable to generate installation log file"
[added 8/24/09] You don't have administrative rights to install software. Ask your network administrator to give you permission. Try to create a folder under "c:\Program Files", if you can't then you will be unable to install WinRVM.

The WinRVM setup program displays "Setup cannot continue because some system files are out of date on your system" after rebooting and running setup a second time.
[updated 10/2/17]  Installing WinRVM 4.0.3 or later should resolve this. Otherwise:
Move the error message window so you can see the window underneath. It should indicate which file is causing the conflict such as WININET.DLL, HID.DLL, SETUPAPI.DLL. Extract the files from the WinRVM setup program using Winzip/7zip, edit SETUP.LST and find the line that corresponds to the conflicting file, for example:

...
File33=@scrrun.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/26/01 4:39:42 PM,151601,5.6.0.6626
File34=@WININET.DLL,$(WinSysPath),,$(Shared),8/29/02 12:00:00 AM,585728,6.0.2800.1106
File35=@WinRVM.exe,$(AppPath),,,12/17/02 4:50:48 PM,565248,0.9.0.9
...

Put a semi-colon in front of the offending line (the installer will skip this file) and renumber subsequent "FileNN" lines to maintain the proper numerical sequence like so:
...
File33=@scrrun.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/26/01 4:39:42 PM,151601,5.6.0.6626
;File34=@WININET.DLL,$(WinSysPath),,$(Shared),8/29/02 12:00:00 AM,585728,6.0.2800.1106
File34=@WinRVM.exe,$(AppPath),,,12/17/02 4:50:48 PM,565248,0.9.0.9
...

Rerun the setup program and it should not display any more error messages. If you still get the same error message, read the Microsoft Knowledge Base Article 191096 "Multiple "System Files Are Out of Date" Errors" as it provides additional tips to solve this problem such as running the setup program in safe mode (press F8 when booting PC).

If WinRVM installs correctly but when you run WinRVM it's still running an old version: extract WinRVM.exe from WinRVM.cab to c:\program files\winrvm.

Unable to upgrade to a newer version of WinRVM, a "Permission denied" error is logged.
[added 11/23/15] [Windows 8, 10] Give user write access to the folder "c:\Program Files (x86)\WinRVM" as described here. This can't be done remotely.

WinRVM displays "Communications difficulty: nnnn parity/break/framing/overrun/overflow errors".
[updated 6/1/17] If you're using a USB to serial adapter, make sure you're using the very latest Windows driver, especially if you're using Windows 7.
Disable USB power management from the device manager for the USB to serial adapter (Uncheck "Allow the computer to turn off this device to save power" ).
We recommend using the following USB to serial adapters: SABRENT Model SBT-FTDI 6 ft. USB 2.0 to Serial (9-pin) DB-9 RS-232 Adapter Cable 6ft Cable (FTDI Chipset) or FTDI US232R-100-BULK. We no longer recommend the IOGear GUC232A if used under Windows 7 or later due to communications issues.
Verify cabling.
Replace the RS232 to RS485 adapter and other cables with known good cables.
In WinRVM's RVM Communications Options, try all 3 values for "hardware handshaking", if that doesn't work, set it back to "driver default".
As a last resort, try with a different PC, swap the RVM controller.

WinRVM displays various communications problems such as "REQ n" and "NAK n"
[Added 10/3/16] This usually means the USB to serial adapter is the problem. See solutions listed under A reprint voucher is occasionally printed after a normal voucher is printed.

WinRVM is unable to load software to an RVM but other RVM communications works.
[updated 6/10/10]Check the RVM Comm Options screen and make sure the "reboot delay" setting is set to 2000.

The error message "No response from RVM, waiting for C_STOP" occurs at the beginning of an RVM software update.
[added 2/6/03]
There may be a problem with the RS232 cable, specifically one of the handshake lines. Replace with a known good cable.

The RVM is out of service for "WAITING FOR STARTUP".
[added 11/5/03] This can occur if the RVM is in the MONITOR mode (like after a power up) when WinRVM polls it, WinRVM puts the RVM into "waiting for startup" mode but doesn't bring it out of that mode. This bug was fixed in WinRVM version 1.1.5.
To fix a "waiting for startup" problem: enter Manual Mode, click the affected RVM in the status window and click the "show status of current RVM" button (the balloon-text with an "I" button). Simply powering the RVM off and on or restarting WinRVM will not fix the problem.