j.foucher/PS_Dinkey
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Original SDK

Browse Source
This commit is contained in:
j.foucher
2026-05-06 07:47:36 +02:00
parent 2915e04380
commit 0ed627517a
674 changed files with 89334 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
Dinkey Pro 7.6.1/Samples/C/C++Builder XE3/DinkeyChange/README.txt Normal file
View File

@@ -0,0 +1,50 @@
ChangeTest - sample code to call DinkeyChange.dll in C++ Builder XE3 (and more recent)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This project is written in C++ Builder XE3 but will work in more recent
versions (they will upgrade the Project to the latest version). For earlier versions
you should use the project in the C++Builder folder.
The source files in the project are:
File name Folder Description
changetest.c Samples\c main source code file for C
changetest.h Samples\c contains some useful constants
DinkeyChange_borland.lib Samples\c\import_libs contains the function definitions for DinkeyChange.dll
DinkeyChange64_borland.a Samples\c\import_libs contains the function definitions for DinkeyChange64.dll
changetest_imports.c Samples\c\C++Builder XE3\DinkeyChange contains code to link the correct import library
changetest.rc Samples\c\C++Builder\DinkeyChange resource for main dialog
resource.h Samples\c\C++Builder\DinkeyChange header file for resource
Note that the source paths are structured to minimise files. If you want to
move this project the references to these files will probably be no longer valid.
The project can compile to both 32-bit and 64-bit platforms and will link the appropriate
import library. For 32-bit you will call DinkeyChange.dll and for 64-bit you will call
DinkeyChange64.dll.
The sample code contains 7 functions. Just use which ever functions are most
appropriate and customise in your own way. The sample code is just a guide.
As none of the parameters are sensitive then there is no need to implement
strong security in calling DinkeyChange.
Note - you will not be able to debug your program after DinkeyChange has been called.
Our strong anti-debug code will cause the debugger to throw an exception. However,
if you do need to debug your code you can use our debug module for DinkeyChange:
DinkeyChangeDebug.dll (or 64-bit version). So, you can use DinkeyChange.dll
for your release build and DinkeyChangeDebug.dll for your debug build.
Note - the 32-bit DinkeyChange_borland.lib was created using Borland's IMPLIB tool. If there is a problem
with the file we provide you can create your own by running (for example):
c:\program files\CodeGear\Rad Studio 5.0\bin\implib import_libs\DinkeyChange_borland.lib DinkeyChange.dll
(This assumes that the current directory is the Samples\C directory).
Note - the 64-bit DinkeyChange64_borland.a was created using Borland's MKEXP tool. If there is a problem
with the file we provide you can create your own by running (for example):
(from a RAD Studio Command Prompt)
mklib import_libs\DinkeyChange64_borland.a DinkeyChange64.dll
(This assumes that the current directory is the Samples\C directory).