Page 3 of 20

PostPosted: Mon Jun 18, 2012 5:48 pm
by TwoJ
Updated to 2012-06-18

PostPosted: Thu Jul 12, 2012 3:09 pm
by TwoJ
Verified to 2012-07-12

PostPosted: Sat Aug 25, 2012 2:37 pm
by TwoJ
Updated to 2012-08-25

PostPosted: Fri Sep 28, 2012 4:37 pm
by TwoJ
Verified to 2012-09-28

PostPosted: Thu Oct 11, 2012 3:38 pm
by TwoJ
Updated to 2012-10-11

PostPosted: Mon Nov 26, 2012 9:43 pm
by TwoJ
Updated to 2012-11-26

PostPosted: Sat Dec 01, 2012 10:21 pm
by ChiefZeke
Visio Viewer 2013 32/64 has been posted.

PostPosted: Sun Dec 02, 2012 11:20 am
by TwoJ
Thanks Chief!
I probably will only update it on the next cycle of updates but thanks for the info! Amazing that visio viewer is 2013 now and Word viewer is 2003!

PostPosted: Sun Dec 02, 2012 2:25 pm
by benners
TwoJ wrote:Thanks Chief!
I probably will only update it on the next cycle of updates but thanks for the info! Amazing that visio viewer is 2013 now and Word viewer is 2003!


Viewers are a ball ache, especially word

All other viewers are excelviewer, visioviewer, and powerpointviewer.exe
word viewer is wordview_en-us.exe, language specific

Now with Visio 2013 there's 32bit and 64bit, so even less naming constancy.

The word installer exe version is 12, the extracted msi version is 11.
Word updates are version 11

None of the viewers have a description (apart from showing the file name) or internal name or product name and some report wrong versions i.e 6.0 instead of 11

Makes checking the file for processing a nightmare. :mad:

Stupid Microsoft continuity

PostPosted: Sun Dec 02, 2012 6:18 pm
by dziubek
benners wrote:I have started rewriting the OI. this will be version 2.0. Slow going at the mo but nibbling away at it.


TwoJ wrote:Hi Benners

Was just packaging up the updates for the XP release and i noticed a small issue, actually maybe 2 - the first i noticed some time ago, that the OI is only displaying the 6 digits of the old hotfix numbers (ie KB9xxxxx) and not the new 7 digit numbers (ie KB2xxxxxx).

benners wrote:This seems to have led to a secondary issue that it added a hotfix KB2289169 to the obsolete folder, in the display it is shown as KB228916 (as noted above as the 1st issue), but then it also copies KB2289162 as well to the obsolete folder, even though it does integrate it into the hotpack. I suspect it just copies any kb228916* which catches the KB2289169 (obsolete) and KB2289162 (needed) into the obsolete folder.


benners wrote:A little bug correction to add :-)
Yep. saw this new naming and thought that's gonna break something. Same as mentioned by r2d2 and PDL707. I am going to have to make some time soon and fix a few things sooner than planned.


@benners
Do you plan to release update Office Integrator v1.1?