AutoPatcher XP January/February 2005

By akaladis
in Software created by our members

 Share

Recommended Posts

Apprentice

Tekzel

Posted
Posted

Hello. In previous versions (4.x) I was able to set what i wanted selected by default, save it and burn it then I could just run it on several machines without changing the selections. I can not find a way to do this in this version, when i go through and select the options I want then exit it doesnt save the changes as the default. Is there any way to do this?

Rising Star

paratrupr

Posted
Posted
Look at the description, it says "This will install Sun's Java 1.4.2_05". So, is the description or the title wrong?

585373226[/snapback]

The description is wrong. 1.4.2_06 is the actual version installed.

post-46102-1106921143.gif

Rising Star

paratrupr

Posted
Posted
So if it is the correct version, then why Autopatcher did not detect it?

585373261[/snapback]

I assume you are referring to the detection of J2SE Runtime Environment 5.0? The module detection system is designed to look for programs that it has installed. Each module leaves a trace entry in the registry. When AP loads subsequent times, it will scan the registry for pre-defined entries. If it finds it, it considers it installed; unless you specify /noregcheck in the startup parameter. Since you or someone else installed the other version of Java, AP does not see it installed via it's detection method.

In this case, the "sunjava.amc" looks for the following info:

HKLM\Software\JavaSoft\Java Web Start\CurrentVersion

value="1.4.2_06"

If that key is present in your registry, AP will detect it as installed.

Veteran

EZRecovery

Posted
Posted
In this case, the "sunjava.amc" looks for the following info:

HKLM\Software\JavaSoft\Java Web Start\CurrentVersion

value="1.4.2_06"

If that key is present in your registry, AP will detect it as installed.

585373345[/snapback]

^like this?

post-40930-1106925913_thumb.jpg

Apprentice

Tekzel

Posted
Posted
Description is wrong, I'm afraid... I wonder why it didn't detect it...

Tekzel, you can change that using the module editor.

585373367[/snapback]

Oh wow, I totally missed that when playing around with it. So I would have to open each and every module and set them individually to either be default or not. Seems like a LOT of work :) Couldnt there be an easier way? Where it just pops up a list of all modules with checkboxes next to each one indicating their default state or not?

Grand Master

akaladis Veteran

Posted
  • Author
  • Veteran
Posted
Oh wow, I totally missed that when playing around with it.  So I would have to open each and every module and set them individually to either be default or not.  Seems like a LOT of work :)  Couldnt there be an easier way?  Where it just pops up a list of all modules with checkboxes next to each one indicating their default state or not?

585374389[/snapback]

It was actually made hard by design :) I wanted people to stick to official selections as much as possible. And if they choose to alter the modules or even their default status, it should become unofficial...

Neowinian

crider

Posted
Posted

G'day,

I love the idea of AutoPatcher, have been waiting for the SP2 Edition release before I tried it. I want to use it with the MS OEM Preinstallation Kit (MS-OEMPK), but need some help and advice.

How can I change the default component installation options? Turn On/Off options.

I can't run AutoPatcher via the network using \\machinename\sharename\AutoPatcher.exe I can't map a network drive using the MS-OEMPK to make the install.

I will also need to disable the reboot after installation so that the rest of the MS-OEMPK can finish the job.

Any ideas or workarounds?

Cheers

Grand Master

akaladis Veteran

Posted
  • Author
  • Veteran
Posted
G'day,

I love the idea of AutoPatcher, have been waiting for the SP2 Edition release before I tried it.  I want to use it with the MS OEM Preinstallation Kit (MS-OEMPK), but need some help and advice. 

How can I change the default component installation options?  Turn On/Off options.

I can't run AutoPatcher via the network using \\machinename\sharename\AutoPatcher.exe  I can't map a network drive using the MS-OEMPK to make the install.

I will also need to disable the reboot after installation so that the rest of the MS-OEMPK can finish the job.

Any ideas or workarounds?

Cheers

585377529[/snapback]

1. You will have to use the Module Editor to change the default property of the modules you wish.

2. AutoPatcher ran fine on my network: \\FRENZY\JunkDrive\AutoPatcher\AutoPatcher.exe

3. The newest main executable (which you can find in this forum a few posts up, supports the /noreboot switch, which supresses the reboot.

Enthusiast

new_duxie

Posted
Posted (edited)

Well APXP goes well, but if the dotnetframework hasn't already been installed and is installed by AP, straight after the SP1 framework gets installed the computer starts to restart itself, and APXP is forced to quit.

Any ideas on how to stop this restart?

Edited by new_duxie
Grand Master

akaladis Veteran

Posted
  • Author
  • Veteran
Posted
Well APXP goes well, but if the dotnetframework hasn't already been installed and is installed by AP, straight after the SP1 framework gets installed the computer starts to restart itself, and APXP is forced to quit.

Any ideas on how to stop this restart?

585385597[/snapback]

I'll look into that...

Rookie

iSix

Posted
Posted

nw_raptor - We (iSix) will be changing our download links later:

#12 (the ftp links) will no longer work

#13 the http links have changed to

http://download02.isix.net/autopatcher/Aut...an2005_Full.exe

and

http://download02.isix.net/autopatcher/Aut...an2005_Lite.exe

Thanks. :)

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.