Jarno Mikkola Posted March 13, 2009 Posted March 13, 2009 As the title says, why is the Weidu.exe(setup-widescreen.exe) inside the widescreen-v2.1.exe so large, as it's about 8 times bigger than the usual, as the normal is 508Kb and this one is 3,909Kb, and as far as I can tell, it doesn't do anything differently, as the mod can be installed with using the normal WeiDU.exe(v210) renamed as setup-widescreen.exe. Was it just a mistake of packing the source coded .exe and not the binary one? The reason why I ask is the space and that I have seen this actually giving few hitches to the WeiDU.exe's auto updating.
the bigg Posted March 13, 2009 Posted March 13, 2009 Wow, fun. It appears that, my upload script compresses the executable after creating the local copy rather than before (meaning that the copy I use for uploading mods was bloated). I've fixed the problem in my script; since I have stuff in WSM that require W211, I'll wait before uploading WSM 2.2 though.
Leomar Posted April 16, 2009 Posted April 16, 2009 Wow, fun. It appears that, my upload script compresses the executable after creating the local copy rather than before (meaning that the copy I use for uploading mods was bloated). I've fixed the problem in my script; since I have stuff in WSM that require W211, I'll wait before uploading WSM 2.2 though. Only to let you know, that we have gamer reports about the WeiDU.exe's auto updating problem, which Jarno mentioned. The 4MB setup-widescreen.exe causes problems by all auto updating processes, which the Widescreen mod is included. Greetings Leomar
Jarno Mikkola Posted April 16, 2009 Author Posted April 16, 2009 And it might be a cause for this... at least according to my tests, and few other players with the BWP installer.
the bigg Posted April 16, 2009 Posted April 16, 2009 Sigh. Please nag me every week until I release WSM 2.2 and WeiDU 211.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.