home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hacks & Cracks
/
Hacks_and_Cracks.iso
/
vol1
/
axmfs210.zip
/
ZuLu.nfo
< prev
Wrap
Text File
|
1997-08-06
|
2KB
|
40 lines
AxMan File Splitter v2.10 *Patcher*
Eliminates the 30 day expiration
Does NOT eliminates the nag
by ZuLu
Where: http://www.wwnet.com/~dfend/axman.html
Instructions: Unzip NOexpire.EXE into your AxMan directory
(where you installed the program).
Then just double click on it.
Patches AXMAN.EXE. When you're done, you may
delete the patch files: Noexpire.exe
Do NOT attempt to patch a copy of Axman.exe
that's already patched. You HAVE to use a
fresh/virgin/new/unpatched/original file.
NOTES: The first patcher apparently caused faults for some
people. I'm giving up trying to patch nag screens
for Visual Basics programs. First of all, it's
tricky. Secondly, I don't really give a shit about
nag screens. One non-delaying nag screen on startup
or on exit.....big frickin' deal. And between using
Buzof and RTVreco, there's RARELY a nag screen that
can't be taken care of automatically. Changing a
program's coding is always risky. Why do it for
something a wimpy as a nag screen?
This patcher basically just truncates the path statement
that the program uses to find the "Install Date" in the
Windows Registry. Since the program can no longer find
the number, it can't compute how long it's been on your
system. The result is that the program NEVER expires.
Be aware that you'll probably see some funky numbers in
the AxMan nag screen "days remaining" box. Mine pretty
much stays at -45 now (yes, that's negative). I ran the
program 27 times in a bunch of different situations and
I couldn't get it to fault. I think it's safe