home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Elite Hackers Toolkit
/
TheEliteHackersToolkitVolume1_1998.rar
/
HACKERS.BIN
/
appcraks
/
P_PVEXE2.ZIP
/
PEPPER.NFO
< prev
Wrap
Text File
|
1990-01-01
|
3KB
|
75 lines
+----------------------------------------------------------------+
| ...nothing important - just a small Pepper's work... 03-11-98 |
+----------------------------------------------------------------+
| subject: PrivateEXE v 2.0a |
| url: http://www.midstream.com |
+----------------------------------------------------------------+
Info on the Prog's limits
-------------------------
PrivateEXE Demo's limit is that a protected Prog still can be
started by Alt-B. Also sometimes an extra "Override" button is
shown when starting a protected Prog. Click on it and the Prog
also will start without the password. Besides that there is a
an extra nag, showing a "Trial period over" after a certain time.
The "trial nag" only appears if the protected Prog is a 32-bit
application.
Solution
--------
Attached are the files 006.DLL and 007.DLL which should be used
instead of the originals. The original DLLs are copied to the
Window\System directory when PrivateEXE is installed. Depending
on the OS (Win 3.x, Win95, WinNT) the directory maybe different.
So a search for 006.DLL and 007.DLL maybe necessary.
Replacing the DLLs will make
- no more Alt-B function possible to overrun a protection
- no more "Override button"
- no more time nag when starting a protected Prog
- no "Evaluation Copy" text in a protected Progs Window title
To understand the crack and limitations here some infos.
A protected Prog is slightly modified and calls one of the
DLLs when started:
006.DLL is called by 16-bit Progs
007.DLL is called by 32-bit Progs
That means without having the DLLs on your system a protected
prog cannot be started. So you cannot transfer a protected Prog
to another computer without the required DLL. It is said that
a special version exists working without DLLs (the protection
is fully packed to the protected Prog). For sure the better
kind of protection - but unfortunately that version is not
distributed as Shareware.
Known Problems with PrivateEXE v 2.0a
-------------------------------------
The following problems / bugs were observed with the original
PrivateEXE and are NOT RELATED TO ANY CRACK OR PATCH:
- It CAN BE impossible to remove a protection from a 16-bit Prog
(only observed in NT 4.0 - in Win 95 there was no problem)
- VisualBasic 3 Progs cannot be protected.
The second problem seems to be known because a message says that
such kind of software cannot be protected with the actual version.
The first problem seems to be a bug but not a serious one because
always a backup of the unprotected Prog is made.
Finally:
"PrivateEXE Demo" itself shows some typical "Shareware" effects:
- "Evaluation Copy" message
- Timeout message after 12 months
Anyway it works fully functional - so no patch was made for it.
Pepper