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

40
Dinkey Pro 7.6.1/Samples/C/MinGW/DinkeyChange/README.txt Normal file
View File

@@ -0,0 +1,40 @@
ChangeTest - sample code to call DinkeyChange in MinGW
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tested using minGW 3.4.2 and 4.8.1 and minGW-w64 4.8.1
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
libDinkeyChange.a Samples\c\import_libs contains the function definitions for DinkeyChange.dll
libDinkeyChangeDebug.a Samples\c\import_libs contains the function definitions for DinkeyChangeDebug.dll
libDinkeyChange64.a Samples\c\import_libs contains the function definitions for DinkeyChange64.dll
libDinkeyChangeDebug64.a Samples\c\import_libs contains the function definitions for DinkeyChangeDebug64.dll
changetest.rc Samples\c\Visual Studio 5\DinkeyChange resource for main dialog
(NB for compiling you will also need to compile the resources)
To compile for 32-bit:
gcc -m32 ..\..\changetest.c -L..\..\import_libs -lDinkeyChange -o ChangeTest.exe
To compile for 64-bit:
gcc -m64 ..\..\changetest.c -L..\..\import_libs -lDinkeyChange64 -o ChangeTest64.exe
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 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. So, you can use DinkeyChange.dll for your release build
and DinkeyChangeDebug.dll for your debug build.
Note - if you are interested in creating the libDinkeyChange.a import library yourself
then read the notes in the MinGW\Runtime\readme.txt file.