- Joined
- May 26, 2007
- Messages
- 5,545
- Reaction score
- 1,315
For reasons of copyleft I am posting this updater server maker
It was created with the informations in this thread and some additional help from Gregoo and Moons.
It's purpose is to create the file structure that you host on your web server if you want to redirect the official update programs (psupdate.exe) to your server so you can roll out updates the way they do.
LunarPT where keen to do that, and had already made the necessary modifications to psupdate.exe, but couldn't quite get the right formatting for the files server side... most importantly the setfile.lst file.
In order to use this tool, you will need
This isn't production quality. It has a number of flaws, and I'm not releasing the source till everything works as it's supposed to. Right now, the option to choose your input and output directories doesn't work at all, and I notice some of the "/" parameters are playing up again. But you can consider it a functional beta. Core functionality works, some options perform in unexpected ways and extended functionality is designed but not yet implemented.
As it stands, it will take an installation from the the present working directory, and produce the directory structure you need on your web server in a new "updates" folder in the parent of the present wording directory. The term "present working directory" refers to what ever comes before the ">" on the command prompt. So if the prompt is "C:\PT\MyClientFiles>" then "C:\PT\MyClientFiles" is the present working directory. Windows will always pass a "present working directory" to any program it runs, but it's difficult to tell, until you run the program, if it's going to pass the folder the executable you are running is located in or the %SystemRoot% path. The old Windows .pif files used to let you manually set it, but this isn't a DOS tool... it's a Win32 command line program, so it gets a .lnk not a .pif.
There is a maximum file count of 20013 files... this is enforced in MakeUps.exe, and I'm sure you can hack it out, but the reason it's there is that the psupdate.exe I tried would crash horribly if you try to include more files in the updater than that. (they don't allocate enough memory to hold the indexes of more files)
You can use it's output to start working on patching up your own updater, since I understand Lunar have no intention of releasing theirs, and I see no reason why they should. Their changes are very specific for their server and you are as well off working directly from an original... if you can.tt1:
More important for me is that this updater is mine. (With all due credit to RaGEZONE and especially Gregoo, Moons) I worked hard on it and wrote it up developing and learning as I went. If anybody releases something similar from here on out, it's probably based on my work.
The date stamp on this post is my proof that on this date, I had created a workable (if beta) solution for this issue. I didn't work it all out myself without help... I had help. But I pulled it all together and made something that does the job.
Once bugs are ironed out I will release the source... but as LunarPT are the initiators they will get advance copies of each improvement to use as they choose. But by and by I will update this release for everyone.
You must be registered to see links
.It was created with the informations in this thread and some additional help from Gregoo and Moons.
It's purpose is to create the file structure that you host on your web server if you want to redirect the official update programs (psupdate.exe) to your server so you can roll out updates the way they do.
LunarPT where keen to do that, and had already made the necessary modifications to psupdate.exe, but couldn't quite get the right formatting for the files server side... most importantly the setfile.lst file.
In order to use this tool, you will need
You must be registered to see links
(known as LhA on the Amiga where it really took off, or LZH on DOS)... you should have it installed in some location in your system search path. What does that mean? Start a command line and enter "path" you will see the response "PATH=" and a long list of fully qualified directories separated by semi-colons (";") any one of those will do for you, but I would recommend whatever your equivalent of C:\Windows is... to be sure, from the same command line, you can enter "Echo %SystemRoot%" and it will tell you. You can also type "%SystemRoot%" in the address bar of any explorer browser window for it to change to that directory, and then you can just drop Lha.exe there.This isn't production quality. It has a number of flaws, and I'm not releasing the source till everything works as it's supposed to. Right now, the option to choose your input and output directories doesn't work at all, and I notice some of the "/" parameters are playing up again. But you can consider it a functional beta. Core functionality works, some options perform in unexpected ways and extended functionality is designed but not yet implemented.
As it stands, it will take an installation from the the present working directory, and produce the directory structure you need on your web server in a new "updates" folder in the parent of the present wording directory. The term "present working directory" refers to what ever comes before the ">" on the command prompt. So if the prompt is "C:\PT\MyClientFiles>" then "C:\PT\MyClientFiles" is the present working directory. Windows will always pass a "present working directory" to any program it runs, but it's difficult to tell, until you run the program, if it's going to pass the folder the executable you are running is located in or the %SystemRoot% path. The old Windows .pif files used to let you manually set it, but this isn't a DOS tool... it's a Win32 command line program, so it gets a .lnk not a .pif.
There is a maximum file count of 20013 files... this is enforced in MakeUps.exe, and I'm sure you can hack it out, but the reason it's there is that the psupdate.exe I tried would crash horribly if you try to include more files in the updater than that. (they don't allocate enough memory to hold the indexes of more files)
You can use it's output to start working on patching up your own updater, since I understand Lunar have no intention of releasing theirs, and I see no reason why they should. Their changes are very specific for their server and you are as well off working directly from an original... if you can.tt1:
More important for me is that this updater is mine. (With all due credit to RaGEZONE and especially Gregoo, Moons) I worked hard on it and wrote it up developing and learning as I went. If anybody releases something similar from here on out, it's probably based on my work.
The date stamp on this post is my proof that on this date, I had created a workable (if beta) solution for this issue. I didn't work it all out myself without help... I had help. But I pulled it all together and made something that does the job.
Once bugs are ironed out I will release the source... but as LunarPT are the initiators they will get advance copies of each improvement to use as they choose. But by and by I will update this release for everyone.
Attachments
You must be registered for see attachments list
Last edited: