Regarding the backup and patching process     (Moderator: Hell Raiser) Previous Topic | Next Topic
Page 1 of 1
 Author 
 Post 
Post 02-Jun-2006 20:31        

Instead of making a backup of the exe, then patching, then restoring the backup, why not just copy jk.exe to say, jk_ext.exe and apply the patch to jk_ext.exe?

The patcher could run jk_ext.exe to play with the cogext.dll loaded, and just run traditional jk.exe if the user wants to play vanilla JK. This way, patching only occurs if jk_ext.exe isn't present, and there isn't copying/moving/deleting going on, other than the initial duplication of jk.exe if jk_ext.exe doesn't exist.

QM
Post 03-Jun-2006 01:21        

I think it has to do with the VB paradigm. HR would know.
Hell Raiser
Site Developer
Post 03-Jun-2006 19:18        

It's because I wanted it that way. Razz (I was under the influance, what can I say?)

The 2nd release of JK Patcher, if I ever get around to it, will do exactly that: Copy jk.exe then patch the copies, so there's no more moving/copying/patching/restoring stuff.
*** Post commands are unavailable for guests. ***