PRB: Copying Files to the Remote Device Fails

ID: Q185214

The information in this article applies to:

Microsoft Windows CE Toolkit for Visual Basic 6.0
Microsoft Windows CE Toolkit for Visual Basic 5.0

SYMPTOMS

The following error message might appear when you are developing Windows CE Toolkit for Visual Basic (VBCE) applications:

Copying required files to the remote device failed.

There are several reasons why this message might occur. This article addresses some of these reasons and how to resolve them.

MORE INFORMATION

Common scenarios for this error message include, but may not be limited to the following:

Scenario 1

Cause

An invalid remote or local path is entered in the Project Properties dialog box, or alternately, an non-existent directory structure exists on the remote device or emulator.

Solution

Ensure that both the local and remote paths contain valid path locations.

Scenario 2

Cause

The remote device is not connected to the desktop machine.

Solution

Ensure that the device is physically connected to the desktop and that you have entered valid login parameters.

Scenario 3

Cause

A project with the same name is already running on the remote device.

Solution

End the application that is running on the remote device or change the local and remote path information to reflect a different project name.

Scenario 4

Cause

VBCE run-time and remote debugging files are in ROM on the remote device, but do not match those that ship with VBCE. This is currently a known issue with the Sharp Mobilon HC4100 and HC4500.

Solution

For VBCE5:

Copy the files that shipped with VBCE down to the remote device manually. You need to copy the following files:

<path to vbce>\vbce\bin\mips41xx\RunTime\pvb.exe
<path to vbce>\vbce\bin\mips41xx\RunTime\pvbrt.dll
<path to vbce>\vbce\bin\mips41xx\RunTime\vbscript.dll
<path to vbce>\vbce\bin\mips41xx\RunTime\vbsen.dll
<path to vbce>\vbce\bin\mips41xx\Tools\pdm.dll
<path to vbce>\vbce\bin\mips41xx\Tools\vbrmon.dll

Note that these files are processor specific and that the last two are required for remote debugging.

For VBCE6:

Copy the files that shipped with VBCE down to the remote device manually. You need to copy the following files:

<path to vbce>\vbce\bin\mips41xx\RunTime\pvbdecl.dll
<path to vbce>\vbce\bin\mips41xx\RunTime\pvbform2.dll
<path to vbce>\vbce\bin\mips41xx\RunTime\pvbhost2.dll
<path to vbce>\vbce\bin\mips41xx\RunTime\pvbload.exe
<path to vbce>\vbce\bin\mips41xx\RunTime\vbscript.dll
<path to vbce>\vbce\bin\mips41xx\RunTime\vbsen.dll
<path to vbce>\vbce\bin\mips41xx\Tools\pdm.dll
<path to vbce>\vbce\bin\mips41xx\Tools\pvbctrl.exe
<path to vbce>\vbce\bin\mips41xx\Tools\vbrmon.dll

Note that these files are processor specific and that the last three are required for remote debugging.

Scenario 5

Cause

The VBCE application is being developed on a machine running Windows 95 or Windows 98. This only applies to VBCE 5.0.

Solution

VBCE requires Windows NT 4.0 with Service Pack 3. The main reason for this requirement is that the Windows CE operating system is Unicode based, and only Windows NT 4.0 provides complete emulation capabilities. There are currently no plans to make VBCE operable under Windows 95 or Windows 98. For additional information, please see the following article in the Microsoft Knowledge Base:

Q184851 INFO: VBCE Does Not Run on Windows 95 or Windows 98

NOTE: This only applies to VBCE 5.0.

Scenario 6

Cause

Connection to the device was lost and reconnected during the same Visual Basic session.

Solution

Close and reopen Visual Basic.

Scenario 7

Cause

The message may appear under unknown circumstances.

Solution

There are a couple of things that can be done in an attempt to remedy the situation. First, try exiting Visual Basic and re-launching it. Second, try closing the Emulation window and re-launching it via the Windows Start menu, selecting Programs, then Windows CE Platform SDK, then Desktop Handheld PC Emulation.

Additional query words: vbce vbce5 vbce6

Keywords : kbToolkit kbVBp500 kbWinCE100 kbGrpVB
Version : WINDOWS:
Platform : WINDOWS
Issue type : kbprb