Download Overnet v0.44 Patcher (StoneFisk 2003 v0.01)

Binary attached, @ only 6kb it should not be a problem to vast readership of 
this list. Contents of attached zip : "sf-overnet", binary and source for 
overnet version 0.44 *crack* by stonefisk.

Rant... Overnet v0.44 may or may-not be patched by hex editing in the same way 
as previous cracks that I have posted. I don't know, don't care, I haven't & 
will not bother to look. Some  people have said the *magic* string wasn't in 
version v.42, but it was there, just slightly different and in a different 
location, some people just want spoon feeding.

I have not used overnet for awhile, but yesterday wanted some juicy releases, so 
I grabbed the latest version of Overnet (v0.44) and gave it a spin. Cool, no 
more .NET .

Just for shits and giggles, I looked at memory patching the upload / download 
values. Overnet coders still use the same old dumb methods, grabbing values out 
of the edit boxes and using them to set the transfer rates. If the values are 
manually set in the GUI and 'OK' button is pressed, then the values are (when 
required) adjsuted as per ratio restrictions. But if the values are *adjusted* 
in memory, we bypass any ratio based value adjustment. So we could set upload 
rate to = 1 & download rate to = 0 (0 being machine max dl rate) and it would 
work quite happy. But if you then viewed the network options GUI and press 'OK' 
button the ratio adjustment calculation woudl kick back in. BUT... we can deal 
with that easily too. If the memory patcher repeatedly patches the values in 
memory (say every 1/2 sec) we effectively superglue our values in memory.

I have tested the method and happy it's cool (wouldn't of posted if I didn't). 
Not sure but it seems you must allow some upload traffic, else everything grinds 
to a halt. In my testing I set the max upload value to 1, and everything was 
cool. Setting it to 0.1, things seemed to grind to a halt after a short while, 
never tested this much... probably a requirement of the overnet serverless 
protocol.

So how to patch the memory ? Find the correct memory offsets and adsust the 
values as per your requirements. Plenty of tools out there to do this manually, 
and a few that could semi-automate the process. Plenty of coding examples in 
many languages how to patch memory, could make your own tool.

Well okay, you don't care about anything I said above you just want a overnet 
crack ? That's why I coded my own and attached it to this post. Binary and 
source. Coded in win32 assembly.

Features/Instructions : Sets Max upload value to 1.	  (Allow a small amount 
of traffic) Sets Max Download Value to 0.  (0 being the setting for machine 
limit)

Place the sf-overnet.exe in the same folder as overnet.exe.

When ever you want to run overnet, run the crack/exe instead. Hit the start 
button on sf-overnet.exe GUI and Overnet will be launched and the mem patch 
applied. The sf-overnet.exe will ensure the values are constantly fixed in 
memory, so nether user  adjustment via gui or adjustment by the overnet process 
itself will have any effect on the values. When overnet is closed down then the 
sf-overnet.exe safely exits also.

Tested and developed under WINXP PRO SP1 & WIN2K SP3 ONLY. errm or in other 
words this won't work on non NT boxen (make your own)

stonefisk <>< (feb2003)

Binary attached, @ only 6kb it should not be a problem to vast readership of 
this list. Contents of attached zip : "sf-overnet", binary and source for 
overnet version 0.44 *crack* by stonefisk.

Rant... Overnet v0.44 may or may-not be patched by hex editing in the same way 
as previous cracks that I have posted. I don't know, don't care, I haven't & 
will not bother to look. Some  people have said the *magic* string wasn't in 
version v.42, but it was there, just slightly different and in a different 
location, some people just want spoon feeding.

I have not used overnet for awhile, but yesterday wanted some juicy releases, so 
I grabbed the latest version of Overnet (v0.44) and gave it a spin. Cool, no 
more .NET .

Just for shits and giggles, I looked at memory patching the upload / download 
values. Overnet coders still use the same old dumb methods, grabbing values out 
of the edit boxes and using them to set the transfer rates. If the values are 
manually set in the GUI and 'OK' button is pressed, then the values are (when 
required) adjsuted as per ratio restrictions. But if the values are *adjusted* 
in memory, we bypass any ratio based value adjustment. So we could set upload 
rate to = 1 & download rate to = 0 (0 being machine max dl rate) and it would 
work quite happy. But if you then viewed the network options GUI and press 'OK' 
button the ratio adjustment calculation woudl kick back in. BUT... we can deal 
with that easily too. If the memory patcher repeatedly patches the values in 
memory (say every 1/2 sec) we effectively superglue our values in memory.

I have tested the method and happy it's cool (wouldn't of posted if I didn't). 
Not sure but it seems you must allow some upload traffic, else everything grinds 
to a halt. In my testing I set the max upload value to 1, and everything was 
cool. Setting it to 0.1, things seemed to grind to a halt after a short while, 
never tested this much... probably a requirement of the overnet serverless 
protocol.

So how to patch the memory ? Find the correct memory offsets and adsust the 
values as per your requirements. Plenty of tools out there to do this manually, 
and a few that could semi-automate the process. Plenty of coding examples in 
many languages how to patch memory, could make your own tool.

Well okay, you don't care about anything I said above you just want a overnet 
crack ? That's why I coded my own and attached it to this post. Binary and 
source. Coded in win32 assembly.

Features/Instructions : Sets Max upload value to 1.	  (Allow a small amount 
of traffic) Sets Max Download Value to 0.  (0 being the setting for machine 
limit)

Place the sf-overnet.exe in the same folder as overnet.exe.

When ever you want to run overnet, run the crack/exe instead. Hit the start 
button on sf-overnet.exe GUI and Overnet will be launched and the mem patch 
applied. The sf-overnet.exe will ensure the values are constantly fixed in 
memory, so nether user  adjustment via gui or adjustment by the overnet process 
itself will have any effect on the values. When overnet is closed down then the 
sf-overnet.exe safely exits also.

Tested and developed under WINXP PRO SP1 & WIN2K SP3 ONLY. errm or in other 
words this won't work on non NT boxen (make your own)

stonefisk <>< (feb2003)