Unlikely DodUpdate is not a unpacker but only a renamer utility.
I monitored the Update Steps and see this evironment:
When IDE start the update, download the PKG from the net then unpack IT during the download.
Infact the progress bar of the update status indicate:
Download IDE Help File Package....
Unpack IDE Help Package...
Download IDE main files package....
Unpack IDE main package...
At this stage, if you see in the temp folder you can see
In addings to two PKG files a very large numbers (334 files exactly) named:
ProtonIDE.0000 to ProtonIDE.0333
and one file named: ProtonIDEIndex.0000
So to finalize the update the IDE updater launch the utility dupupdate with this commandline text:
C:\TEMP\ProtonIDEIndex.0000
Opening this file (ProtonIdeIndex.0000) you can see these lines:
334
C:\Temp\ProtonIDE.0193
C:\Programmi\ProtonIDE\MCLoader\LoaderHEX\16F87_04.hex
C:\Temp\ProtonIDE.0194
C:\Programmi\ProtonIDE\MCLoader\LoaderHEX\16F87_20.hex
C:\Temp\ProtonIDE.0174
C:\Programmi\ProtonIDE\MCLoader\LoaderHEX\16F870_04.hex
....... ecc ecc
The list is long as all 334 filename, and the utility i think rename all these files, then copy it in the proper application folder, but unlikely is already unpacked during the update stages.
I think that the dupMgr.dll unpack it with proper DLL entry. I think you need to use a DLL checker to see all the entry of the DLL to chek if there are an antry for a unpack.
If you open with a winhex the dll you can see inside the text LZH hoffman ecc ecc. I think it uses this kind of compression. Dunno if ciphered.
I tried to replace during download the PKG with the beta PKG to see if the original updater unpack IT, but is impossible to replace on the fly the file, because is in use. I unlocked it during download and replaced, but the downloader tell that the file is corrupted.
Also hexediting the IDE exe I found another download urls:
www.mecanique.co.uk/updates/proton/ProtonMessage.pkgwww.mecanique.co.uk/updates/proton/ProtonMessageBETA.pkgThe url is valid and the files is present. Dunno what is it.
I have no more time, due to real work, but I think that faking more the dupMgr.dll you can modify it to use a filename DupUpdate.pkg.0000 as download file, but another filename for unpacking filename (like xxxx.pkg). So if you put in the temp dir the beta package with the proper filename (xxxx.pkg), you can download the non beta package, but decompress the beta.
Finally I think that operating more on the DLL is possible to decompress the BETA.
Bye
bye