Brian May schrieb:
Tomasz Chmielewski wrote:
* When using offline mode, logon delay window was displayed longer than
necessary on certain hardware setups (VMware, certain network cards
etc.)- should be fixed now, but please double check, as it was tested on
a limited set of hardware.
I
Tomasz Chmielewski wrote:
That would be unfortunate :(
Can you make sure when you find some free time?
What specs do these machines have, is it old or modern hardware in terms
of speed (CPU, HDD, etc.)?
Disconnected operation, with no access to server.
On a Compaq nc4200 laptop: 5-10
Mumble, mumble... or this apply only to 'always'?
Sorry, i'm really an idiot. ;(
Clearly the 'upgrade' clause have no mean for an 'always' execution
type, but for 'once' _have_ mean. ;(
I've added a 'upgrade' clause to my recipe (equal to the install one)
and now settings are correctly
Mandi! Marco Gaiarin
In chel di` si favelave...
Yes, seems to work.
Forced an immediate reboot, tomorrow i will test with an
REBOOT=ReallySuppress.
I confirm that works. The recipe i use to update WPKG is:
package
id=wpkg
name=WPKG
revision=1211
Marco Gaiarin schrieb:
(...)
I've also noted a strange thing: i also use this recipe:
package
id=wpkg-settings
name=WPKG Settings
revision=10
priority=5
reboot=false
execute=once
depends package-id=wpkg/
install
Mandi! Tomasz Chmielewski
In chel di` si favelave...
Is %WPKGROOT% a password-protected share?
No, guest access, file mode 664.
(seems no a file access problem, on new install the settings file are
correctly loaded...)
--
dott. Marco Gaiarin GNUPG Key ID:
Marco Gaiarin wrote:
I've also noted a strange thing: i also use this recipe:
package
id=wpkg-settings
name=WPKG Settings
revision=10
priority=5
reboot=false
execute=once
depends package-id=wpkg/
install
Tomasz Chmielewski wrote:
Did you have it scheduled at startup or at shutdown?
I have the same problem; scheduled at startup for me.
Brian May
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
Tomasz Chmielewski wrote:
* When using offline mode, logon delay window was displayed longer than
necessary on certain hardware setups (VMware, certain network cards
etc.)- should be fixed now, but please double check, as it was tested on
a limited set of hardware.
I *think* I still have
I think it should also upgrade if you have Windows Installer 3.1, but I
didn't test it personally.
Yes, seems to work.
Forced an immediate reboot, tomorrow i will test with an
REBOOT=ReallySuppress.
Cool! ;)
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
I forgot to say.
Please, build a WPKGClient .msi installer that are able to upgrade
itself as soon as possible, i think this is the real priority now,
new features will come. ;)
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia''
Marco Gaiarin schrieb:
I forgot to say.
Please, build a WPKGClient .msi installer that are able to upgrade
itself as soon as possible, i think this is the real priority now,
new features will come. ;)
It should be able to upgrade itself, provided you have Windows Installer
3.1 installed.
Marco Gaiarin schrieb:
Mandi! Tomasz Chmielewski
In chel di` si favelave...
It should be able to upgrade itself, provided you have Windows Installer
3.1 installed.
Doesn't it work for you?
I meant: release please a fixed 1.2.X version, or release 1.4.0 without
loosing too much time
Hi,
Does it (or Event Log) say failed to stop the service?
Or it just take (veeery) long to stop?
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and even
after wpkg was done with everything I cannot
Jens Geile schrieb:
Hi,
Does it (or Event Log) say failed to stop the service?
Or it just take (veeery) long to stop?
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and even
after wpkg was done
Mandi! Tomasz Chmielewski
In chel di` si favelave...
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and
even after wpkg was done with everything I cannot start the service again
for like 2
Mandi! Tomasz Chmielewski
In chel di` si favelave...
I think it should also upgrade if you have Windows Installer 3.1, but I
didn't test it personally.
You are saying that 1.2.X just works?
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La
Hi,
Does it (or Event Log) say failed to stop the service?
Or it just take (veeery) long to stop?
I can confirm that it takes (veeery) long to stop the service. During my
testing I started the service manually using net start wpkgservice and
even after wpkg was done with everything
Marco Gaiarin schrieb:
Mandi! Tomasz Chmielewski
In chel di` si favelave...
Please, explain a bit how it works... please...
Hmm, what works?
It schedules either on startup or shutdown.
Right now, you can't schedule the service to execute the sequence both
on startup and or shutdown.
Yes, it works without a execute before script !
(Even if there is an eventlog error saying Starting WPKG on shutdown)
I had as well a script running execute before, which was just
updating the wpkg-settings. (%PROGRAMFILES%\WPKG\wpkginst.exe
--SETTINGSFILE=\\server\share\settings.xml)
After
Tomasz Chmielewski schrieb:
Tomasz Chmielewski schrieb:
Gerd Ott schrieb:
Hallo,
Scheduling the execution on system shutdown works fine on a XP-System
here. Thanks for your investment!
On a win2000 testbox (SP4, all windows-updates, installer 3.1)
execution does not start on shutdown, no
Berge Schwebs Bjørlo schrieb:
On Fri, Jun 13, 2008 at 05:15:52PM +0200, Marco Gaiarin wrote:
I've done it:
C:\WINDOWS\system32msiexec /qb /i
\\media\software\shareware\Utility\WPKG\WPKG Client 1.3.2.msi
SETTINGSFILE=\\file\wpkg\settings.xml ALLUSERS=1
C:\WINDOWS\system32echo
On Sat, Jun 14, 2008 at 10:46:04PM +0200, Tomasz Chmielewski wrote:
Berge Schwebs Bjørlo schrieb:
FWIW: Running msiexec witn /qn instead of /qb will not install WPKG Client
1.3.2 - Windows will complain about wpkglogon.dll being in use in the
event log and refuse to install the package.
Hallo,
Scheduling the execution on system shutdown works fine on a XP-System
here. Thanks for your investment!
On a win2000 testbox (SP4, all windows-updates, installer 3.1)
execution does not start on shutdown, no errors in eventlog. Perhaps
it's even not possible with this OS-version?
Mandi! Tomasz Chmielewski
In chel di` si favelave...
Windows Installer 3.1 has to be installed. With it, it is able to
upgrade MSI packages where there are files in use.
Ok, windows installer 3.1 are OK. Windows XP SP2 with all updates
applied.
At least it works that way when double
Marco Gaiarin schrieb:
2) effectively the install goes well, after reboot the service works
and all was at the right place. But... the question about rebooting
now or later WAS DISPLAYED also if 've used /qb.
So you have made an installer non-silent for a silent installation
system. ;)
It
Mandi! Tomasz Chmielewski
In chel di` si favelave...
It should not display a question if you use a /noreboot flag to msiexec:
msiexec /norestart ...
?! msiexec does not have such a switch...
http://support.microsoft.com/?scid=kb%3Ben-us%3B227091x=7y=16
Tipo evento:
Marco Gaiarin schrieb:
Mandi! Tomasz Chmielewski
In chel di` si favelave...
It should not display a question if you use a /noreboot flag to msiexec:
msiexec /norestart ...
?! msiexec does not have such a switch...
Tomasz Chmielewski schrieb:
Gerd Ott schrieb:
Hallo,
Scheduling the execution on system shutdown works fine on a XP-System
here. Thanks for your investment!
On a win2000 testbox (SP4, all windows-updates, installer 3.1)
execution does not start on shutdown, no errors in eventlog. Perhaps
On Fri, Jun 13, 2008 at 05:15:52PM +0200, Marco Gaiarin wrote:
I've done it:
C:\WINDOWS\system32msiexec /qb /i
\\media\software\shareware\Utility\WPKG\WPKG Client 1.3.2.msi
SETTINGSFILE=\\file\wpkg\settings.xml ALLUSERS=1
C:\WINDOWS\system32echo %ERRORLEVEL%
0
FWIW:
Marco Gaiarin schrieb:
Mandi! Tomasz Chmielewski
In chel di` si favelave...
* Upgrading should work even if the service is running. In fact, it
probably worked earlier: prerequisite - Windows Installer 3.1 installed.
Ahem, sorry, can you explain better this?
I'm stuck with WPKGClient
WPKG Client 1.3.2 has been released.
This is *not* intended for production environments and is designed for
testing purposes only.
It is available for download at http://wpkg.org/files/client/beta/
Changes:
* When using offline mode, logon delay window was displayed longer than
necessary on
32 matches
Mail list logo
