Rescue for 4D - Documentation

RESCUE FOR 4D DOCUMENTATION - Doctor

DOCTOR

Doctor
Only Check (Only Log)
Checking and manual correction
Checking and automatic correction
Further Information
Save a Log
Print a Log

Doctor :

Doctor checks the coherence of internal resources of a file with a 4th Dimension™ structure.

Doctor opens structures :

Compiled and Not Compiled - Version 5.1 minimum - Mac and PC

4D First - Version 5 - 68xxx and PPC

According to options selected in the Preferences, Doctor checks :

Resource size (Resource Size) : compared to the headers and the File size.
Resource position (Resource Position) : coherence of resource position.
Resource number (Resource Duplicate ID) : several resources without the same ID.
Warning Size : gives you a warning when a resource size exceeds the fixed parameter (minimum 10,000 bytes)
Resource header (Resource Headers) : coherence of resource headers.
References between resources (Resource Crossing).
Resource Fork of a file (Macintosh Resources) : state of Fork Resource of a file (PICT, str#, TEXT, NFNT,...).

According to option chosen in the pop-up menu of the Check zone, Doctor :

will not make corrections (Only Log option )
allows you to make corrections manually (Manual option )
or corrects automatically (Auto option...).

Only Check (Only Log):

Run the checking

Click on the button to start the checking

Stop the checking
To cancel the checking operation, Enter one time Command-Shift-Period.

Doctor messages:
Doctor messages:

The header :

Saturday 9 November 1996	The date of checking

Start Log on 'Escapade'	The operation type and the name of the file structure analyzed
Compiled On v3 Macintosh. With 4D Compiler 2.5.2c d3 Pro for all Macintosh. For Processor(s) : 680xx + 6888x - 68040LC PPC Intel. Compiled with packages: - ACI_Pack.4DX - File Toolkit for 4D F-1.2.1 - MENUTOOL.4DX - SuperReport Pro.ext - System7Pack - WINTOOLS.4DX	The computer where the database must be used. If the structure is compiled: The version of compilator used. The list of correct names of all externals for which the compiled database is waiting (very useful, if we change the name of packages into the folder Mac4DX...).
File Size 8876494 bytes	The size of the structure file in bytes
Check Resources : Size, Position, Duplicate ID, Headers, Crossing, Macintosh, Types.	Checks made according to the setting of preferences.

Checking on the table of resource types

Resource Types Table Checking:	Begin work on the resource types.
38 Resource Types.	Number of resource types
Type Table Size 120,210 bytes OK.	Size of the Type table (Double Checking).
Type Table Position OK.	The table position seems correct.
All Necessary Types Found OK.	The forced types are presents.
Duplicate Type OK.	There is no duplication of Types.
Resource Types Check OK.	The Type table is correct.

Checking of resources

Resource Table checking :	Begin working on the resources.
5,999 Resources.	Number of resources in the database.
Resources Size 8,492,662 Bytes OK.	Checking of resources validity. Displays their Real size.
Duplicate Resource ID OK.	No resource ID duplicated.
Resource Check OK.	The resource table is correct.

Other possible Messages with the settings of Doctor preferences :

Possible Messages with Resource Size checked. This option checks for negative size resources. These occur frequently if the computer crashes while you are working in a structure.
Invalid Size Error : Type : 'CC4D' ID : 5,092 Size : -8 -> Resource Type : Procedures / Methods / Scripts / Formula. No Method Name (Possible as Not A Method). Advice : Correct It	The resource size is bad. This resource can crash 4D. If it is not an essential resource, you must delete it.
Possible Messages with Resource Crossing checked. The Crossing checks all the relations between resources (internal resources). This option informs you of the missing and/or unused resources.
Resource Crossing : BA4D Resource Not Found. Type : 'MEN4' ID : 11594 -> Resource Type : Menu Definitions. Parent No Found. Advice : Correct It	The resource 'MEN4' of ID 11594 is not used by a 'BA4D'.
Resource Crossing : List Resource Not Found. Type : 'LE4D' ID : 0 -> List Name : "Wordings of notes" Advice : Don't Correct	The 'List' resource isn't found when it's used in the 'LE4D' by the enumeration "Wording of notes".
Possible Messages with Position checked. The resource position is important because it may be out of file (4D message "Try to read beyond end of file") or it points to the next resource (Bomb).
Resource Out Of File : Type : 'EN4D' ID : 0 Size : 1891631096 -> Resource Type : Enumeration Contents (v5). Parent No Found. Advice : Correct It	The resource doesn't entirely enter the file. This problem occurs when it is recorded by 4D. This resource can crash 4D. If it is not an essential resource, you must delete it.
Possible Messages with Duplicate ID checked. Several resources with the same ID are not managed well by 4D. This doesn't seem to be a problem. If this occurs, you can delete without worrying about the specified resource because 4D doesn't use it.
Duplicate Resource ID Error : Type : 'EN4D' ID : 0 Size : 1891631096 -> Resource Type : Enumeration Contents (v5). Parent No Found. Advice : Correct It	Two resources have the same ID. 4D will never see the second ; you can delete it without worrying.
Possible Messages with Headers checked. A Header is a small tag that 4D puts at the beginning of each of its resources. A header tells 4D that the resource it is about to load is the resource for which it was waiting. This checking catches +/- 30% of resource problems.
Resource Header Error : Type : 'FO4D' ID : 2562 Size : 310 -> Resource Type : Layout Contents. Table Name : [Key_words] - Form Name : "List" Advice : Correct It	The resource FO4D (format [Key_Words]List) is damaged. This resource can crash 4D. If it's not an essential resource, you must delete it.
Possible Messages with Size Warning checked. This option allows two things. First, what resources have a size greater than x. And, second, it can be used to find resources of a particular size which too important to risk damaging.
Resource Size Warning : Type : 'FO4D' ID : 27862 Size : 106144 -> Resource Type : Layout Contents. Table Name : [xInterface] - Form Name : "DialParamGPAO" Advice : Don't Correct	The resource FO4D (format [ParamGPAO]Input) has a superior size compared with the one listed in preferences.

Checking of Macintosh resources

Macintosh Resource Table Checking :	Begin work on Macintosh resources.
306 Resources.	Total Number of resources.
Resources Size 426822 Bytes Ok.	Size of resources.
Macintosh Resources Check Ok.	The Macintosh resource Fork is correct.

Warning : if the database is being migrated from Windows without being translated by the 4D Transporter, the following warning will appear :

"Impossible To Check Macintosh Resource Fork.
Use Macintosh Resource Editor To Do That.
Macintosh Resource Check Found Problem(s)."

This does not signify that there is a problem ; only that there is no Resource Fork for this file. On the Macintosh, there must be a resource fork for a 4D structure.

Manual Correction :

The manual correction Option is possible only on not compiled Structures.

For each error detected, a dialogue appears.

This dialogue indicates :

The problem found : problem zone,
Information about the resource which has a problem : Resource details zone
If you don't obtain this information, it is because the resource is too damaged to recover it,
The cause of the problem and will render an explanation should you choose to correct the problem : advice zone,
and the advice of Doctor, here Don't Correct.
The default option will be the one which appears as the most judicious to Rescue for 4D.
IT'S REALLY NOT ADVISABLE TO DELETE ESSENTIAL RESOURCES ('FI4D','LE4D','LIBA','PA4D','PR4D','TF4D','TP4D','WN4D'). Notice that Rescue for 4D will display three types of warning messages :
- be careful in deleting it
- don't delete the resource. ,
- No problem, Delete
  
  As always, the final decision belongs to you. (Warning)

The Stop Check button allows you to cancel the Doctor action.

Checking and automatic correction :

The Automatic correction Option is possible only on not compiled Structures.

If you have selected the option Auto... in the pop-up menu of the Check zone, Doctor corrects automatically the errors.

We strongly advise you to use the Only Log option. (Warning)

Further information :

To avoid bad information, Rescue for 4D does not use the trash table of 4D. It allows the correction of some problems such as overlapping resources. However, after having used Rescue for 4D and having deleted some resources, you should compact with 4D Utils. The last one will again update the trash table. (Warning)
Some errors types, such as the Headers errors, must be corrected ONLY WITH Rescue for 4D. In fact, this error type is, in general, a sign that the resource isn't where 4D was looking for it. A correction with 4D (deleting a procedure, for example) can cause damage to one, or more, other resources. Rescue for 4D corrects this type of problem without introducing new problems because it doesn't manage the Trash Table. (Warning)
If essential resources are absent, you must --- IMPERATIVELY --- save again.

Save a log:
Save a log:
: You can Save a log by selecting the item Save from the File menu.
You can open it with a simple text editor.
Print a log:
Print a log:

You can Print a log by selecting the item Print from the File menu.