9Appendix D: Loading/Unloading Override
PTBurn now allows an external program to override disc load/unload functionality. This is useful if you want to do some external processing of the disc, either before recording or after recording. This also allows the ability to load discs into the drive so an external program can read information from the drive (without performing any recording). An example of one use of this functionality is detailed below.
NOTE: If you do not need burning capabilities, then you may want to consider using the PTRobot DLL for moving discs around instead of using the PTBurn SDK.
PTBurn SDK Load/Unload Override example:
The user wants to run their own “special” verification procedure on the disc. They want this procedure to run prior to unloading the disc to the printer and want to be able to control whether the disc passes or fails based on their verification.
-
User submits a Recording/Printing job with LoadUnloadOverride = YES.
-
Once the disc is loaded, PTBurn will set the following values in the Job specific status section:
[JobXYZ]
LoadDiscState0 = 1
LoadDiscDrive0 = F
-
This notifies the client that the disc is loaded in drive F: and in a hold state until the client releases the hold state. The user could do some special procedure on the disc at this point if they desire.
-
The user releases the hold state by sending the “Process Disc” message. For this example the message file must be called JobXYZ.ptm and the contents are shown below. The DiscID is the value of X from the LoadDiscStateX in the status file.
Message= PROCESS_DISC
DiscID=0
-
Once PTBurn processes the “Process Disc” message the .ptm file is deleted and the Job specific status section is updated as follows:
[JobXYZ]
LoadDiscState0 = 2
LoadDiscDrive0 = F
-
At this point PTBurn will process the recording portion of the job as it was specified in the .JRQ file. If no recording is specified in the JRQ file, the PTBurn will skip over the recording phase.
-
Once completed, PTBurn will enter a hold state with the job status section as follows:
[JobXYZ]
LoadDiscState0 = 3
LoadDiscDrive0 = F
-
At this point, the client can perform his “special” verification procedure on the disc.
-
If the user’s special verification procedure fails, the client can send the “Reject Disc” message as detailed below. This will cause the hold state to end, and the disc will fail and be rejected appropriately. The contents of JobXYZ.ptm would be:
Message= REJECT_DISC
DiscID=0
-
However, if the user’s special verification passes, the client can send the “Unload Disc” message as detailed below. This will cause the hold state to end. The job will continue with printing if the JRQ file specifies that the disc be printed on. Otherwise, the disc will be unloaded to the output. Here are the contents of JobXYZ.ptm:
Message= UNLOAD_DISC
DiscID=0
3/06/17 - document version 3.2.5
-
Added 4200 and SE-3 Robot types to status output
-
Added new cartridge type for the Lotus cartridge
9/20/11 – document version 3.24
-
Added a Clean Cartridges .PTM command in section 4.16
4/6/11 – document version 3.23
-
Added Job Error 40 in Appendix C
-
Added 4100 XRP Robot Type in Section 3.1.3.2
-
Added JobState in Section 3.2.4.12
2/4/11 – document version 3.22
-
Updated ink level information for 4-Cartridge robots (sections 3.1.3.8 & 3.1.3.9 & 3.2.5.20 & 3.2.5.21)
-
Added new RobotType to section 3.1.3.2
-
Added ISRC capability for Audio discs (section 2.1.5)
-
Added CD-Text capability for Audio discs (Sections 2.1.43 to 2.1.48)
-
Added missing documentation for CurrentStatusState in section 3.2.4.20
-
Updated information for ReadDataFormat (2.1.20) and CreateSubFolders (2.1.21)
-
Moved Section 2.3 and consolidated with 5.1. Updated section 5.2
-
Updated Section 1 to notify the existence of both Unicode and MBCS versions of PTBurn
9/16/10 – document version 3.2.1
-
Updated options for JobStartup
8/10/10 – document version 3.2.0
-
Added new keys to PTSetup.in in 5.0
-
DrivesToUse
-
KioskMode
-
LIghtState
-
Added best practices section.
2/17/10 – document version 3.1.0
-
PathTo, PathFrom and DPI keys were incorrect in 4.11 and 4.12. Added Burn Engine Error Code Table in Appendix C.
11/12/09 – document version 3.0.9
9/21/09 – document version 3.0.8
-
Added Section 2.1.42 for PrintReject Key.
4/24/09 – document version 3.0.7
-
Added Section 2.1.41 for key RobotName. The functionality already existed for specifying a particular robot, but the key had not been documented.
12/31/08 – document version 3.0.6
-
Updated Section 2.1.33 to note the need for the DiscType key when doing pre-mastering of a DVD.
11/7/08 – document version 3.0.5
-
Updated Appendix C to define more system and job/disc errors
6/20/08 – document version 3.0.4
-
Updated Section 2.1.3 to note that the Importance key now allows values up to 400.
-
Updated Section 2.1.41 to clarify how merging works with SureThing
-
Updated Section 3.1.2.9 with CartridgeType values
-
Updated Section 3.2.3.18 for LoadDiscState
-
Added Section 3.2.4.21 DriveLetter to get the drive letter for the recorder.
-
Updated several of the Status file sections to clarify.
-
Added UDF250 & UDF260 options to DataImageType.
1/28/08 – document version 3.0.3
-
Added Section 3.1.3
-
Added Set/Clear Kisok mode message (4.15) and corresponding status (3.1.2.11)
-
Changed “Error” key to “SysErrorNumber” (3.1.2.5)
-
Added Server Tick Count (3.1.3.1)
-
Added StatusFrequency key to PTSetup.INI in case the developer wants to change how often the status is updated. (Appendix A)
9/20/07 - document version 3.0.2
-
Updated Appendix 6 to reflect the changes in installing the service versus the old PTBurn application.
-
Removed the CDText Keys. They will not be supported in the first version of PTBurn 3.0 and will be added in a future release.
9/13/07 - document version 3.0.1
-
Updated section 2.1.5 to show the new feature of copying source files/folders while changing the destination file and/or folder names.
-
Added section 2.1.47 MergeField to document how a user can specify Surething merge fields within the JRQ file.
Dostları ilə paylaş: |
