| View previous topic :: View next topic |
| Author |
Message |
BoBo Guest
|
Posted: Wed Jun 21, 2006 9:38 am Post subject: Decode/Encode Dll's [Dll] |
|
|
| Quote: | General Information:
-------------------
Many decoders are available but many require you to know the file
type in advance. With the DLLs included, you don't have to know
or care what format is used, the software will determine that.
The test programs provided will demonstrate that. The test
programs and shareware DLLs can be used by individuals free of
charge but businesses wishing to license the software should
contact us at the addresses provided below for pricing
information.
The Decode/Encode DLLs can be called from any Windows programming
language (such as VB, Visual C, Powerbuilder, etc.). It allows you
to automatically detect if a given file is UUENCODED, Base64(MIME),
XXENCODED, BinHex or encoded with a user-supplied table. The DLL
can then decode the file(s) either in the current directory or in
one specified by the user. Binary files can also be encoded for
transmission over the Internet.
New in version 1.2-2.5:
- Added handling for Base64 text to GetMessageText function.
- Function to return system date (local or GMT) when passed a
message header date
- Message Header parameter for Routing Headers
- Improved Decode/Encode in memory.
- The decoding routines now assume Content-Transfer-Encoding: 7bit
if the Content-Transfer-Encoding header is not specified.
- HTML messages are now returned when calling GetMessageText.
- Chinese 'Big5' subject headers and attachment names are now
handled.
- Function for saving the decoded message text to a file.
- Functions for retrieving the message header information (From, To,
Subject, etc).
- Functions for encoding/decoding to/from memory buffers.
- Extended characters (over ASCII 127) in the file name are decoded
properly.
- Improved VB test programs
- Boundary can now be passed in to the encoding routine.
- Handling of non-standard rich text attachments, those containing
HTML tags or invalid symbols (such as and < indentations) in
MIME attachments
- quoted-printable encoding is now provided
- 7bit (unencoded text files) and quoted-printable files are now
also decoded.
- Files encoded UUENCODED and containing "BEGIN -- Cut Here -- cut
here" before the encoded part are now decoded using the correct
file name.
- Utility functions for Resolving name collisions, Splitting and
Concatenating files are available.
- BinHex and XXENCODED files can now be produced (encoded). |
Decode/Encode DLL's v2.5 (UUE,Mime64...)
463009 Kb
2006-05-25 12:53:39
[Download] |
|
| Back to top |
|
 |
Larry
Joined: 03 Mar 2005 Posts: 20
|
Posted: Mon Feb 04, 2008 5:42 am Post subject: Can't get DllCall of DecExt.dll to work..... |
|
|
I've spent about 4 hours trying to get the Funduc DecExt.dll to Decode an "EML" type file without success. The test.eml file can be decoded ok using the Shell Extension that calls DecExt.dll.
Here is my code:
#F12::
result := DllCall("decext.dll", str, "I:\Send\test.eml")
if not result
{
MsgBox Errorlevel = %Errorlevel%
return
}
return
The MsgBox command executes and shows the following:
Errorlevel = -4
According to AutoHotKey Help, an ErrorLevel of -4 means
"The specified function could not be found inside the DLL"
Is there anyway to find out the name of the "Decode" function in the DLL file?
Although I'm not a newbie to AutoHotKey, I'm not an accomplished programmer either, and I'm not all that knowledgeable about DLL files.
Perhaps there is a way to get AutoHotKey to call the Shell Extension.
Does anyone know how to go about doing that?
If anyone knows where I'm going wrong or knows a different way to get AutoHotKey to Call the Decode function in the Funduc DecExt.dll file, I would be very appreciative.
Thanks,
Larry |
|
| Back to top |
|
 |
majkinetor
Joined: 24 May 2006 Posts: 3615 Location: Belgrade
|
Posted: Mon Feb 04, 2008 10:52 am Post subject: |
|
|
| Quote: | | Perhaps there is a way to get AutoHotKey to call the Shell Extension. |
You have to use COM. Function is not exported but accessed via COM interface so there is no way you can use DllCall the regular way. _________________
 |
|
| Back to top |
|
 |
Larry
Joined: 03 Mar 2005 Posts: 20
|
Posted: Tue Feb 05, 2008 8:41 am Post subject: |
|
|
Thanks for the input majkinetor. I'm not a programmer and clueless about how to use the information you provided though. I will see what I can find out about "COM" (whatever it is), and see if I can figure out how to use it to accomplish the desired task. Thanks again for sharing your knowledge....
Larry |
|
| Back to top |
|
 |
majkinetor
Joined: 24 May 2006 Posts: 3615 Location: Belgrade
|
Posted: Tue Feb 05, 2008 11:43 am Post subject: |
|
|
If you are not programmer, I suggest you stop ASAP.
COM is hard even to programmers and in AHK it has special aroma
Try to find some normal dll, instead. _________________
 |
|
| Back to top |
|
 |
|