Direct X Addon
Whatacrock
10 Mar 2010
Hey Cristiano, Started a new fresh autopatcher directory on my machine and downloaded the new apup 1.31.
Downloaded the XP enu plus java and direct x. When I finished ran autopatcher and noticed that the direct x selection now reads as March 2009 instead of Feb 2010. Is this an error in naming ? The file was 103 Mb in downloading.
I have a log file.
Cheers
Bruce
Edited by Whatacrock, 10 March 2010 - 07:14 AM.
Downloaded the XP enu plus java and direct x. When I finished ran autopatcher and noticed that the direct x selection now reads as March 2009 instead of Feb 2010. Is this an error in naming ? The file was 103 Mb in downloading.
I have a log file.
Cheers
Bruce
Edited by Whatacrock, 10 March 2010 - 07:14 AM.
_def_x_
10 Mar 2010
Indeed, the wrong DirectX script is being used:
When I was with the team I had recommended moving the old scripts to a backup folder in the same directory to prevent this
kind of confusion - DirectX\backup, or at least add the date to the script -> autopatcher_directx_feb2010.script
The reason this makes me mad is I just ran APUP on my Addons release and this stupid blunder deleted Feb2010, and began to
download Mar2009. I'm on freakin' dialup and now I have to download another 100+ megs because of this unnecessary mistake,
the date in APUP wont make you aware of the mixup. I only ran APUP to get v1.3 added to my Addons release - jeez feakin' louise!
Spoiler
When I was with the team I had recommended moving the old scripts to a backup folder in the same directory to prevent this
kind of confusion - DirectX\backup, or at least add the date to the script -> autopatcher_directx_feb2010.script
The reason this makes me mad is I just ran APUP on my Addons release and this stupid blunder deleted Feb2010, and began to
download Mar2009. I'm on freakin' dialup and now I have to download another 100+ megs because of this unnecessary mistake,
the date in APUP wont make you aware of the mixup. I only ran APUP to get v1.3 added to my Addons release - jeez feakin' louise!
Cristiano
10 Mar 2010
damm... i've edited the right file, but have uploaded the wrong one
that will be fixed asap
mike, sorry for the issue
[]s
that will be fixed asap
mike, sorry for the issue
[]s
Cristiano
10 Mar 2010
done. the right script is at our server, but i had to re-do the module, the 104MB from the update and hide it from our corporate firewall. i don't have the rti tool in here, so probably this module will be unofficial until tonight
[]s
[]s
_def_x_
10 Mar 2010
To try and lend a hand I took the liberty to update the DirectX script, I downloaded the executable from a friends home, everything
is here, and needed -> updated script, .rti (signed Cristiano Portela), and an updated .apm (added Feb2010 to the Title).
Your choice
is here, and needed -> updated script, .rti (signed Cristiano Portela), and an updated .apm (added Feb2010 to the Title).
Your choice
_def_x_
10 Mar 2010
Checked the script and all is good at my end, but APUP (1.3.0.1) did do something strange...
I made sure Updater, Engine, and DirectX were checked - clicked Next - and immediately APUP disappeared, didn't minimize,
closed - no Finish tab, no errors visibly or in the log. There wasn't anything to download I was only checking the script.
I ran APUP again with no problems - go figure
I made sure Updater, Engine, and DirectX were checked - clicked Next - and immediately APUP disappeared, didn't minimize,
closed - no Finish tab, no errors visibly or in the log. There wasn't anything to download I was only checking the script.
I ran APUP again with no problems - go figure
Cristiano
11 Mar 2010
weird. well, today my day was lost. i've arrive at home and i'm without my dsl... and i have to match the local updates to be able to sign... oh well...
[]s
[]s
_def_x_
11 Mar 2010
Update:
I looked at my DirectX folder (the one where the latest had been deleted) and I noticed an old .md5 from a past DirectX
left behind -> md5_checksum_for_DirectX_Aug_2009_Redistr.md5, and that there was no .md5 for Feb2010, I also
forgot to add one so, I updated the script and provided an .md5 for Feb2010.
This is what I did, use the updated script and new .md5 (or not)
Info:
If everything seems OK, update the script and add the md5.7z to -> /releases/directx/ with the directx.rti file.
BTW, I provided the same .apm and .rti as before in the directx_files_updated.7z (this time in a folder), the updated
script and new md5.7z are all that need to be uploaded.
I looked at my DirectX folder (the one where the latest had been deleted) and I noticed an old .md5 from a past DirectX
left behind -> md5_checksum_for_DirectX_Aug_2009_Redistr.md5, and that there was no .md5 for Feb2010, I also
forgot to add one so, I updated the script and provided an .md5 for Feb2010.
This is what I did, use the updated script and new .md5 (or not)
Info:
Spoiler
If everything seems OK, update the script and add the md5.7z to -> /releases/directx/ with the directx.rti file.
BTW, I provided the same .apm and .rti as before in the directx_files_updated.7z (this time in a folder), the updated
script and new md5.7z are all that need to be uploaded.
