Re: [wpkg-users] wpkg.js crashing?

Hi Brian, Brian May wrote: > Sounds good. I guess the question is: if all logging fails, do we > continue anyway, or abort? I finally decided to continue as normal. As long as writing to STDOUT and the log file still works. I think it might be a bad decision to just stop processing due to the

Re: [wpkg-users] wpkg.js crashing?

Tomasz Chmielewski wrote: > Missing? Why? Don't tell me you don't use 720k floppies any more (and > those who remember Amiga could format these floppies to use 880k, that > was something!) ;) Now you got me ;-) I still use some extremely old hardware... I like retro style. But usually I don't l

Re: [wpkg-users] [Bug 110] WPKG seems to disable /debug if "quiet" is set to "false" in config.xml

Hi Brian, Brian May wrote: > While I don't feel strongly about the issue, I can't help think the > above behaviour is confusing. > > I am use to /quiet on other command line tools which enables/disables > STDOUT output. It shouldn't control both STDOUT and the Event Handler. > > The debug set

Re: [wpkg-users] wpkg.js crashing?

> It doesn't mention XP though, you may have problems implementing it on your > friend's PC ;) At the bottom it says "Microsoft Windows XP Home Edition" and "Microsoft Windows XP Professional" in the "Applies to" section. Filling the security event log is a little harder than the application even

Re: [wpkg-users] wpkg.js crashing?

Rainer Meier schrieb: > Hi Tomasz, > > Tomasz Chmielewski wrote: >> Ah, you're just being ignorant. >> It's by design: it has an advantage that it perfectly fits on a >> single, 720k floppy. > > Missing some irony tags here? Missing? Why? Don't tell me you don't use 720k floppies any more (and

Re: [wpkg-users] wpkg.js crashing?

Adam Williams schrieb: > > > Tomasz Chmielewski wrote: >> >> >> You can configure a Windows system to make a BSOD when the Event Log is >> full. I doubt many (non-paranoid) people use it, though. >> >> >> > > how do you do that? sounds like an evil trick I could use on friend's > PCs :) h

Re: [wpkg-users] [Bug 110] WPKG seems to disable /debug if "quiet" is set to "false" in config.xml

[EMAIL PROTECTED] wrote: > /quiet => output to event log, hide STDOUT > else everything is printed on STDOUT, no output to event log. While I don't feel strongly about the issue, I can't help think the above behaviour is confusing. I am use to /quiet on other command line tools which enables/dis

Re: [wpkg-users] wpkg.js crashing?

Rainer Meier wrote: >> - log to event log >>- log to log file if event log throws an exception >> - log to STDOUT/STDERR if even logfile writing fails Sounds good. I guess the question is: if all logging fails, do we continue anyway, or abort? There are probably pros/cons either way, ju

Re: [wpkg-users] wpkg.js crashing?

Tomasz Chmielewski wrote: > Does WPKG still misbehave for you if you clear the event log? I would assume not. Hmm... I shouldn't make assumptions. Assumptions bad. Ok. Lets test it out. Oh damn. It looks like my log file expanded from 64kb to 512kb. I now wonder if I pushed "Ok" or "Cancel" on

Re: [wpkg-users] WPKG client upgrade

Tomasz Chmielewski wrote: > I asked some Microsoft MVPs and it doesn't look too promising: > > 1) Most (all?) installers do an upgrade by stopping the service first Another approach might be to look at what is done my Mozilla Firefox, Mozilla Thunderbird, etc. I am not sure of the details, I th

Re: [wpkg-users] WPKG client upgrade

Tomasz Chmielewski wrote: > I think killing WPKGSrv.exe will also kill its child processes: > - cscript ...\wpkg.js > \- any other child of cscript I am not convinced of this. That doesn't mean it won't kill the child processes, but unless I see proof... When I ran it on my system, I think i

[wpkg-users] [Bug 109] WPKG uncleanly exits if event log writing fails

http://bugzilla.wpkg.org/show_bug.cgi?id=109 --- Comment #6 from Rainer Meier <[EMAIL PROTECTED]> 2008-04-22 00:01:38 --- Just an additional note about the /debug flag: I strongly recommend NOT to use /debug in conjunction with the /silent flag (or corresponding properties within config.xml)

Re: [wpkg-users] wpkg.js crashing?

Rainer Meier wrote: > Well, I think you're right regarding this issue. However to log events > to any facility (STDERR, log file, event log...) you have to rely on > certain system resources and API calls. I will try to improve the error > handling as much as possible and try establish the follo

[wpkg-users] [Bug 109] WPKG uncleanly exits if event log writing fails

http://bugzilla.wpkg.org/show_bug.cgi?id=109 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution

[wpkg-users] [Bug 109] WPKG uncleanly exits if event log writing fails

http://bugzilla.wpkg.org/show_bug.cgi?id=109 --- Comment #4 from Rainer Meier <[EMAIL PROTECTED]> 2008-04-21 23:50:03 --- Created an attachment (id=112) --> (http://bugzilla.wpkg.org/attachment.cgi?id=112) Full package, added error handling in case of event log exceptions. (1.1.0-M5 mileston

[wpkg-users] [Bug 109] WPKG uncleanly exits if event log writing fails

http://bugzilla.wpkg.org/show_bug.cgi?id=109 --- Comment #3 from Rainer Meier <[EMAIL PROTECTED]> 2008-04-21 23:49:09 --- Created an attachment (id=111) --> (http://bugzilla.wpkg.org/attachment.cgi?id=111) Full package, added error handling in case of event log exceptions. Changes 2008-04-2

[wpkg-users] [Bug 109] WPKG uncleanly exits if event log writing fails

http://bugzilla.wpkg.org/show_bug.cgi?id=109 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #2

[wpkg-users] [Bug 110] WPKG seems to disable /debug if "quiet" is set to "false" in config.xml

http://bugzilla.wpkg.org/show_bug.cgi?id=110 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Resolution|FIXED |INVALID --- Comment #3 f

Re: [wpkg-users] wpkg.js crashing?

Hi Jens Jens Geile wrote: > After some more testing even "" is > working now but it seems to disable "/debug". I created a bug report (just for the records): However I verified it and it works exactly as expected. Setting 'quiet' do 'false' will

[wpkg-users] [Bug 110] WPKG seems to disable /debug if "quiet" is set to "false" in config.xml

http://bugzilla.wpkg.org/show_bug.cgi?id=110 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution

[wpkg-users] [Bug 110] WPKG seems to disable /debug if "quiet" is set to "false" in config.xml

http://bugzilla.wpkg.org/show_bug.cgi?id=110 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1

Re: [wpkg-users] wpkg.js crashing?

Hi Tomasz, Tomasz Chmielewski wrote: > Ah, you're just being ignorant. > It's by design: it has an advantage that it perfectly fits on a single, > 720k floppy. Missing some irony tags here? Well XP was introduced in ~2001 I think. USB and memory sticks have already replaced 1.44MB floppies by t

Re: [wpkg-users] wpkg.js crashing?

Tomasz Chmielewski wrote: You can configure a Windows system to make a BSOD when the Event Log is full. I doubt many (non-paranoid) people use it, though. how do you do that? sounds like an evil trick I could use on friend's PCs :) --

Re: [wpkg-users] wpkg.js crashing?

Rainer Meier schrieb: (...) > I am simply astonished about this ridiculous small amount of space > Microsoft seems to assign to the event logs (512kB each) I wonder how Ah, you're just being ignorant. It's by design: it has an advantage that it perfectly fits on a single, 720k floppy. > I j

[wpkg-users] [Bug 110] New: WPKG seems to disable /debug if "quiet" is set to "false" in config.xml

http://bugzilla.wpkg.org/show_bug.cgi?id=110 Summary: WPKG seems to disable /debug if "quiet" is set to "false" in config.xml Product: WPKG Version: 1.0.1 Platform: PC OS/Version: All Status: NEW Severity:

[wpkg-users] [Bug 109] WPKG uncleanly exits if event log writing fails

http://bugzilla.wpkg.org/show_bug.cgi?id=109 Tomasz Chmielewski <[EMAIL PROTECTED]> changed: What|Removed |Added CC||[EMAIL PROTECTED]

Re: [wpkg-users] WPKG client upgrade

Hi Tomasz, Tomasz Chmielewski wrote: > - there is a switch/hack, but we don't know it yet I don't think it is very hidden or a hack. Just did a quick (very quick) Google search and found the following interesting pages:

Re: [wpkg-users] wpkg.js crashing?

Hi all, Sorry Falko, forgot to reply to the list... Falko Trojahn wrote: > Don't think so, but all debug output goes to eventlog then -> this is > why eventlog is filled so quickly. Yes, quiet mode just makes WPKG not to print anything on STDOUT (except if /printStatus is enabled for WPKG 1.1).

Re: [wpkg-users] WPKG client upgrade

Tomasz Chmielewski schrieb: > Rainer Meier schrieb: > > (...) > >> It's an ugly work-around trying to kill applications which are currently >> running just to unlock these files. Especially since you never know >> which other applications (indexing serivice, 3rd party tools...) open >> the sam

[wpkg-users] [Bug 109] New: WPKG uncleanly exits if event log writing fails

http://bugzilla.wpkg.org/show_bug.cgi?id=109 Summary: WPKG uncleanly exits if event log writing fails Product: WPKG Version: 1.0.1 Platform: PC OS/Version: All Status: NEW Severity: minor Priority: P2 Compo

[wpkg-users] [Bug 108] wpkg 1.1.0-m4

http://bugzilla.wpkg.org/show_bug.cgi?id=108 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #8 fr

Re: [wpkg-users] Upgrade V0.9x to 1.0x Question 2

Simon Walters schrieb: > I did my first test of 1.0.1 in one of schools and I jsut copied my existing > hosts,profile and pagkage.xml files into a new folder containg wpkg 1.0.1 > and it worked without error :) > > However, I just run wpkg as a batch file in the All Users Start folder > and use >

Re: [wpkg-users] WPKG client upgrade

Rainer Meier schrieb: (...) > It's an ugly work-around trying to kill applications which are currently > running just to unlock these files. Especially since you never know > which other applications (indexing serivice, 3rd party tools...) open > the same file. So replacing a file might fail a

Re: [wpkg-users] WPKG client upgrade

Mandi! Rainer Meier In chel di` si favelave... > files immediately. I am quite sure Windows installer must support something > like this as a built-in service. As a total windows ignorant, i suppose (or i hope? ;) the same thing. ;) > It's an ugly work-around trying to kill applications whic

[wpkg-users] Upgrade V0.9x to 1.0x Question 2

I did my first test of 1.0.1 in one of schools and I jsut copied my existing hosts,profile and pagkage.xml files into a new folder containg wpkg 1.0.1 and it worked without error :) However, I just run wpkg as a batch file in the All Users Start folder and use this cscript \\suitec01\icttech\wpk

Re: [wpkg-users] WPKG client upgrade

Hi Marco Marco Gaiarin wrote: > A question (but i'm a unix guy): for me it is normal to upgrade binary > in execution, simply the newer version will be available next time we > reboot the machine. > > Asked in another way: why not rewrite the installer so it handle all > this stuff, upgrade the b

Re: [wpkg-users] WPKG client upgrade

Sorry, but i'm a bit missed in this thread. 1) to upgrade wpkg client, the service have to be stopped; because the service run wpkg.js that run the install batch script, we cannot kill the service without 'start' or we will kill ourself. Relatively easy. 2) but if we have 'delayed logon' featur

Re: [wpkg-users] wpkg.js crashing?

Hi Brian, Brian May wrote: > Here if any exception occurs, error is called which tries to log a > message via the log function. However I just established that the the > log function probably causes an exception when trying to write to the > event handler - Guess what - it will cause an excepti

Re: [wpkg-users] wpkg.js crashing?

Hi Jens, Jens Geile wrote: > While testing this I found that using "" > in config.xml seems to break WPKG. WPKG starts and stops immediately. No > software is installed even when eventlog is empty. Starting wpkg manually > through commandline gives: > "WPKG Service konnte nicht gestartet werden

Re: [wpkg-users] WPKG client upgrade

> > Tomasz Chmielewski napsal(a): >> Vladimír Pšenička schrieb: >>> Yes I use logon delay feature, I try batch file with killing >>> wpkgmessage.exe and I have no luck, still no upgrade is done... >>> >>> I try upgrade cmd with and without "start" >>> and same error occurs... >> If th

Re: [wpkg-users] WPKG client upgrade

Process that use wpkglogon.dll is winlogon.exe (SYSTEM process that shouldn't be killed)... Tomasz Chmielewski napsal(a): > Vladimír Pšenička schrieb: >> Yes I use logon delay feature, I try batch file with killing >> wpkgmessage.exe and I have no luck, still no upgrade is done... >> >> I try upgr

Re: [wpkg-users] wpkg.js crashing?

Jens Geile schrieb: > So it seems that when eventlog is full wpkg fails to do anything. And because > the eventlog is already full it cannot even log why it failed. > > While testing this I found that using "" > in config.xml seems to break WPKG. WPKG starts and stops immediately. No > softwar

Re: [wpkg-users] wpkg.js crashing?

Hi, > > > I remember a machine in my setup that didnt log anything to the event log > > > anymore because it was full. This happened after running wpkg in debug > > > mode two or three times (previous log entries left there). Cleaning the > > > event log solved this and wpkg logged its actions

Re: [wpkg-users] WPKG client upgrade

Vladimír Pšenička schrieb: > Yes I use logon delay feature, I try batch file with killing > wpkgmessage.exe and I have no luck, still no upgrade is done... > > I try upgrade cmd with and without "start" >> >> > > and same error occurs... If the same error occurs (wpkglogon.dll is used by ano

Re: [wpkg-users] WPKG client upgrade

Yes I use logon delay feature, I try batch file with killing wpkgmessage.exe and I have no luck, still no upgrade is done... I try upgrade cmd with and without "start" > > and same error occurs... Tomasz Chmielewski napsal(a): > Vladimír Pšenička schrieb: >> When I upgrade WPKG client this w

Re: [wpkg-users] wpkg.js crashing?

Brian May schrieb: > Rainer Meier wrote: >> Right click "my computer", select "manage", click "Event Viewer", right >> click "Application", chose "Clear all Events". > > Ok, if I got to log file properties, I see that the log file size is > 65,536 bytes long. > > The maximum size of the log fil

Re: [wpkg-users] WPKG client upgrade

Vladimír Pšenička schrieb: > When I upgrade WPKG client this way (without "start"): > >> > > it doesn't work, on client I see errors: > >> Product: WPKG -- Error 1722. There is a problem with this Windows Installer >> package. A program run as part of the setup did not finish as expected. >>

Re: [wpkg-users] WPKG client upgrade

Brian May schrieb: > Brian May wrote: >> It seems to work. >> >> Can I please confirm why you use "start"? Is this for extra debugging? > > Looks like a race condition exists, due to using start. The process is > started for upgrading wpkg, and at the same time wpkg continues and > checks the la

Re: [wpkg-users] WPKG client upgrade

Brian May schrieb: > Tomasz Chmielewski wrote: >> I added some (hopefully) more detailed instructions and verified that >> they work on my workstation: >> >> http://wpkg.org/WPKG >> >> Could you verify if it works for you? > > There seem to be some typos, I changed it to: > > id="wpkg" >

Re: [wpkg-users] WPKG client upgrade

When I upgrade WPKG client this way (without "start"): > it doesn't work, on client I see errors: > Product: WPKG -- Error 1722. There is a problem with this Windows Installer > package. A program run as part of the setup did not finish as expected. > Contact your support personnel or packag

Re: [wpkg-users] WPKG client upgrade

I tested this upgrade (I have condition="versionequalto", on website is condition="sizeequals" and value="1.0.0.8") >id="wpkg" > name="WPKG Client 1.2.1" > revision="2" > reboot="false" > priority="3000"> > >