54 replies to this topic

[ViroMan]

AP Todo List:

• Add MS Office detections
  
• Fix ability to register DLL's

Apup Todo:

• Fix APUP 1.4.14 chokes big time when attempting to run a local script
  
• Fix GUI hides when it shouldn't
  
• Fix ability to register DLL's
  
• Hide background information when in download mode
  
• Fix folder rename not working

Edited by ViroMan, 01 April 2013 - 04:53 AM.

[click-click]

Hi VM,

I did notice a minor nit on APUP. While downloading, the screen keeps flashing in a pulsating way and I keep
seeing the Welcome text and Releases Available header from the first menu during some of the flashes.

Edited by click-click, 20 March 2013 - 10:47 AM.

[Black Ghost]

 ViroMan, on 20 March 2013 - 08:36 AM, said:

AP Todo List:

• Fix .NET 4.5 bug <-- apup too?
  
• Add MS Office detections

So this will now detect Office 2010 and 2013 versions of Office now?

[ViroMan]

Well I can get the office 2010 in there if I can get some good intel from DJ when I get with him. IF someone has office 2013 I can get with them and we can figure out the detections for it.

Quote

While downloading, the screen keeps flashing in a pulsating way and I keep seeing the Welcome text and Releases Available header from the first menu during some of the flashes.

Well I have an idea what your talking about even though I don't experience it. When it goes into "download mode" It just pops up another screen on top of the information already there. The pulsing your seeing is probably from the rapid refreshes to the screen and check for user input I am forcing to keep things smooth and lock free. What I can do to fix this(seeing the old data not the pulses) is force the background items to be hidden when the download screen pops up. Its a very easy change.

Edited by ViroMan, 21 March 2013 - 08:32 AM.

[DesertJerry]

ViroMan, on 21 March 2013 - 08:25 AM, said:

Well I can get the office 2010 in there if I can get some good intel from DJ when I get with him. IF someone has office 2013 I can get with them and we can figure out the detections for it.

Was the info I posted in #8 here helpful? http://www.autopatch...bad-detections/

[ViroMan]

I downloaded it. It does look helpful. I haven't gotten any code work done yet though since they have me working the whole damn weekend.

[DesertJerry]

ViroMan, on 24 March 2013 - 08:06 AM, said:

I downloaded it. It does look helpful. I haven't gotten any code work done yet though since they have me working the whole damn weekend.

Oh well, being retired has its advantages!!! Anyway, as I mentioned - i have Office 2010 Pro installed with the Win7 operating systems and Office 2010 Home and Student with the XP operating systems; figured I'd mention it though I don't really think there would be much of a difference in detecting either one.

I thought you might be interested in the following information I copied from recent AutoPatcher log files:

Spoiler

Autopatcher v5.7.31 Has Started at 23-Mar-13 20:29:43
AutoPatcher Has Finished Loading The Filesystem.
Parsing Detected Commandline Arguments...
Obtaining list of all supported by Autopatcher and installed on this machine...
Detected
English (1033) Windows 7 Ultimate 64-bit
System Components:
Internet Explorer: 10.0.9200.16521
Windows Media Player: 12.0.7601.17514
.NET Framework: 2.0.50727.5420|2.0SP2|3.0.30729.5420.5420|3.0SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 5.0.7601.17514
DirectX: 4.09.00.0904
MSN/Live Messenger:
Office Components:
** NONE **

Spoiler

Autopatcher v5.7.31 Has Started at 24-Mar-13 12:58:46
AutoPatcher Has Finished Loading The Filesystem.
Parsing Detected Commandline Arguments...
Obtaining list of all supported by Autopatcher and installed on this machine...
Detected
English (1033) Windows XP Professional Service Pack 3
System Components:
Internet Explorer: 8.0.6001.19403
Windows Media Player: 11.0.5721.5280
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 4.5.6001.22159
DirectX: 4.09.00.0904
MSN/Live Messenger:
Office Components:
Microsoft Word: 14.0.6129.5000
Microsoft Excel: 14.0.6126.5003
Microsoft PowerPoint: 14.0.6009.1000
Microsoft OneNote: 14.0.6134.5000

Notice that AutoPatcher's detection did not show Win7 was updated with Service Pack 1 but did detect that Office 2010 was installed in XP Pro - how does that happen?

Later with XP Pro x64 - notice Office 2010 was detected:

Spoiler

Autopatcher v5.7.31 Has Started at 24-Mar-13 14:50:56
AutoPatcher Has Finished Loading The Filesystem.
Parsing Detected Commandline Arguments...
Obtaining list of all supported by Autopatcher and installed on this machine...
Detected
English (1033) Windows XP Professional x64 Service Pack 2
System Components:
Internet Explorer: 8.0.6001.23471
Windows Media Player: 11.0.5721.5280
.NET Framework: 2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 4.5.6001.22159
DirectX: 4.09.00.0904
MSN/Live Messenger:
Office Components:
Microsoft Word: 14.0.6129.5000
Microsoft Excel: 14.0.6126.5003
Microsoft PowerPoint: 14.0.6009.1000
Microsoft OneNote: 14.0.6134.5000

Edited by Whatacrock, 16 April 2013 - 01:47 AM.

[DesertJerry]

Odd - no Edit button, anyway - next is Win7 Ultimate 32bit w/SP1 - showss Office 2010 detected:

Spoiler

Autopatcher v5.7.31 Has Started at 24-Mar-13 15:23:18
AutoPatcher Has Finished Loading The Filesystem.
Parsing Detected Commandline Arguments...
Obtaining list of all supported by Autopatcher and installed on this machine...
Detected
English (1033) Windows 7 Ultimate 32-bit
System Components:
Internet Explorer: 10.0.9200.16521
Windows Media Player: 12.0.7601.17514
.NET Framework: 2.0.50727.5420|2.0SP2|3.0.30729.5420.5420|3.0SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 5.0.7601.17514
DirectX: 4.09.00.0904
MSN/Live Messenger:
Office Components:
Microsoft Word: 14.0.6129.5000
Microsoft Excel: 14.0.6126.5003
Microsoft PowerPoint: 14.0.6009.1000
Microsoft Outlook: 14.0.6131.5000
Microsoft Access: 14.0.6024.1000
Microsoft Publisher: 14.0.6026.1000
Microsoft OneNote: 14.0.6134.5000

Edited by Whatacrock, 16 April 2013 - 01:48 AM.

[ViroMan]

Not sure why the SP didn't detect. Also the fact that it detects office in most of the OS's but not the one x64 is weird. When I get the time I will investigate.

[RileyM3]

Just out of curiosity, how is OS/Office/Service Pack level info gathered? Javascript? VB? Registry Keys? WMI?
It is my understanding that adding a new OS or Office requires modifying the code for AP and releasing a new version.
Also, it seems tougher to add new OS / Office versions if few people have them (because they haven't been widely adopted yet)
Is it easier to add detection for new things as they come out, or to look at an updated detection method that might make things easier?

Just curious...sometimes I wish I would have chosen the programmer route instead of the MCSE route =P

[ViroMan]

Currently its gathered by registry keys. With AP2 you will be able to add detections via a detection script. You provide the name you want something to be classified as and then how to detect it (whether by registry and/or by file). This will enable Autopatcher2 to grow in detection without needing a programmer to add support for things. Each item to be installed will be listed in an APM file as it currently is but, the structure of the file will be radically different. The APM structure will allow for listing of multiple files and multiple download locations per update(a download for each OS type or IE type). No longer will we need 3-5 apms for one update. Maintenance will be so much easier on our end. Especially if I can get the new APM editor completed at the same time.

Edited by ViroMan, 31 March 2013 - 08:10 AM.

[ViroMan]

Hey guys... I had a thought. Would any of you be adverse to having the language versions color coded? English would remain with a white background and others would get other colored backgrounds. Nothing too dark. It would just make it easier to find your language. If you would like to see it, I would of course want your opinions on colors.

[ViroMan]

So I have been trying to get autopatcher to remove that old nasty dll file. Seems the MS VB code that needs the dll auto loads the damn thing into memory before any code(non auto-generated code) executes. So when I tell it to delete the silly old dll file it gives permission denied because its currently in use. I will see if I have more success with having apup delete the damn thing since it doesn't need it and therefore might be able to remove it. Thing is... when it runs the remove command(if it finds the old dll) it will ALWAYS pop up a box saying unregister successful since I have to use the windows service to unregister. You should only see this pop up box once if you have the old dll... hopefully.

Edit: What a huge pain in the butt but, I got it to work though.

Edited by ViroMan, 08 April 2013 - 01:55 PM.

[Whatacrock]

Any chance of generating an error log for autopatcher ... that is to say to report any installation problems of updates.

Thought about this for a while but refreshed the idea dealing with the update problem DesertJerry has with a Windows XP x64 update.

Your thoughts

[ViroMan]

I will have to look into it but, initial reply is no. AP can't at the moment hook into updates for progress reports and I don't know if they have error-level upon process finish and even if they do... what a doozy to try and create that many strings. Are you looking for just a simple update kbxxx failed with errorcode 12345?


edit:
So I did a little test of one of the older updates I have on me. They do report errorcodes on exit... so having a simple report in the log is possible.

Edited by ViroMan, 16 April 2013 - 03:21 AM.