 |
|
|
|
|
VB RezQ
Error and Warning Messages
|
|
This page provides information about the error and warning messages that may occur:-
(a) when using VB RezQ.
(b) when opening a project recovered by VB RezQ in the VB IDE.
VB RezQ Error and Warning Messages
This section details the error and warning messages that may be
produced by VB RezQ and gives guidance on what action you
should take.
Not a VB file. (EXE file signature MZ not found.)
Not a VB file. (Not a Windows EXE file.)
Not a VB file. (Windows file signature NE/PE not found.)
This is a Visual Basic version x file. 16bit versions of VB are not
supported by VB RezQ.
On opening a file VB RezQ first checks that the file is
truly a 32-bit Visual Basic file. If not, then a message box will
appear with one of the above messages. No further processing of this
file is possible.
Visual Basic Runtime references can not be found.
As above. This message may also appear when a VB file has been modified by
a protection scheme, a compression/packing utility or possibly a virus.
No further processing of this file is possible.
VBP data signature could not be located.
In attempting to rebuild the Project information (.vbp), if
VB RezQ is unable to find an expected data structure then this
message appears in the Progress Log. Maybe the executable file has
been compressed or modified in some way (e.g. might be infected with
a virus). No further processing of this file is possible.
This file contains additional resources.
This message appears in the Progress Log to indicate that the
source Project File (.vbp) has an entry of ResFile32="Res32.res".
Prior to version V2.6a, VB RezQ created a Res32.txt file
as a script that could be used to drive a freeware tool called
Resource Hacker
to regenerate the resource file Res32.res. From V2.6a,
VB RezQ will now create the Res32.res file when
the Res32.txt file is saved.
Warning: VB RezQ has saved information that will allow
a more accurate recovery of native code.
Close this file with File, Close then
select File, Open to recover again.
This message may appear following an attempted disassembly of a native
code executable file. VB RezQ has discovered additional
information which can only be used by re-running the recovery.
Warning: Unknown OCX foo.ocx - Add Object={ line to MoreOCXs.txt
This message appears in the Progress Log to indicate that the
executable file uses a custom control (foo.ocx) for which VB RezQ
has no information. This means the recovered files will not have the
necessary references to this control.
Copy the Object={... definition line for this control from
another project file (.vbp) and paste it into the MoreOCXs.txt
file (in the same folder as VB RezQ). This file is read at start up by
VB RezQ and will enable it to create recovered files with the correct
references to additional controls.
Foo.FRM form object rebuild stopped at &Hxxxx. Typemark &Hyy
Foo.FRM form object rebuild stalled at &Hxxxx. Unknown Typemark &Hyy
Foo.FRM form object rebuild stalled. Unknown TypeIndex &Hyy
These messages may appear in the Progress Log to indicate that
VB RezQ encountered difficulty in recovering the graphical part
of a form, property page, user control, user document or designer.
Please help to improve VB RezQ by providing details to us.
** WARNING xxxx - This file not fully understood by VBRezQ. Refer to Help.
This message may appear in the Progress Log if VB RezQ has
detected a problem which suggests that the executable file contains
features which are not understood.
Please help to improve VB RezQ by providing details to us.
There may not be enough memory. VBRezQ will attempt to continue.
This message may appear in a message box when VB RezQ v2.3b is
creating child windows to display the recovered files from a very large
project (typically one with over 130 source files).
Improvements made in v2.3d mean that very large projects can be
handled successfully and that this situation can no longer occur. See
the Support page regarding version history and updates to the latest version.
VB IDE Error and Warning Messages
This section considers the error and warning messages that may be
produced by the VB IDE when opening a project recovered by VB RezQ.
Custom controls are by far the most common cause of error messages when opening
a recovered project. Typically the VB IDE creates a Formxx.log file containing
messages like these :-
Line nn: Cannot load control Foo2; license not found.
The VB IDE cannot find the design-time licence for this control.
Line nn: Cannot load control Foo2.
The VB IDE cannot find the .OCX file for the control.
First of all you should ensure that :-
1) any necessary Object={... definition lines have been added
to the MoreOCXs.txt file before using VB RezQ to recover the project,
2) all referenced .OCX files are present on your system and visible
from the VB IDE Project Components dialog,
3) you have design-time licences for those controls that need them.
With any luck this will clear all error messages. However, you may sometimes
see messages like these :-
Line nn: Cannot load control Foo2.
Line nn: Class Xxx.Yyy of control Foo2 was not a loaded control class.
Line nn: The property name Bindings in Foo2 is invalid.
Most controls will accept a Form file with missing properties (which will be
the case for all custom controls except those that are fully recovered by
VB RezQ), but a few controls will refuse to load unless certain
properties are set. These seem in the main to be controls that store some
or all of their properties (seen in the IDE) in an OleObjectBlob property
(seen in the form file). The VB IDE will delete the control from the form
and you will have to add it back manually.
Line nn: Cannot load control DBGrid1.
Line nn: Property OleObjectBlob in DBGrid1 could not be set.
Line nn: Property Bindings in DBGrid1 could not be set.
The DBGrid control (DBGRID32.OCX) stores all of its properties in a binary
OleObjectBlob. The design-time OleObjectBlob differs in places from the
version in the compiled file and VB RezQ attempts to fix up the recovered
OleObjectBlob to suit. In a small number of cases this strategy fails and
the control will not load. The VB IDE will delete the control from the form
and you will have to add it back manually.
|
|
|
|
Buy Now