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

Hi Brian, Brian May wrote: > This is pure speculation: > > * When I pushed OK on the dialog box yesterday, it expanded the file > size to the size specified in the control, which I assumed was the > current size. > > * The problem with logging events was because the current size of 64kb > was

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] 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] 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.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

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

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

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.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.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.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.js crashing?

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 file is setup to 512KB, and "overwri

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

Rainer Meier wrote: > On the other side Brian might have another issue as well. Hopefully > there is some error within his event logs he could provide. Of course I don't have anything in my event logs, it is this code which is causing the wpkg to prematurely abort. Can I please request the foll

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

Rainer Meier wrote: > Thanks for information. Was it just not logging (but executing properly) > or was it also "hanging" somehow when trying to write log entries? > > It looks like Brian is experiencing the second problem. However I guess > there should be at least some information within the s

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

Brian May wrote: > cscript doesn't seem to be running. This is a post I sent earlier. > What is odd is that it seems to crash at different points, I can't see a > pattern yet. On this occasion it stopped right after connecting to the > server (last event message is "Server connecting: successfu

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

Rainer Meier wrote: > And let me repeat again... WPKG does not seem to crash for you. Most > probably just the API call is hanging. So it is useless trying to catch > an exception if there is simply no exception thrown by Windows on the > logEvent() call. Let me repeat again: Yes it does. If th

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

Hi Jens, Jens Geile wrote: > I don't remember. :p But I'll just set a machine to debug and restart it a > couple of times to reproduce this later today and report back. Thanks for your support. I am not at home (where my testbed is) so I cannot do that at the moment. On the other side Brian mig

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 again. >

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

Hi Jens Jens Geile wrote: > 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 ac

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

Hi, > I thought to remember that somebody reported a similar problem where an error > was logged about full event log. After cleaning it it was OK again. 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 deb

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

Hi Brian, Brian May wrote: > I will have a look at the code ASAP. However, the fact remains, if I > comment the code out it works. If I leave the code it, wpkg.js exits > without doing anything else. I don' think you need to look at the WPKG code since it is about a simple API call. It looks l

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

Rainer Meier wrote:= > No, WPKG does not crash on your system - this for sure not. And there is > absolutely no need to wrap in in a try-catch clause. The reason is that > whole WPKG is wrapped in a try-catch clause. So if anything throws an > unexpected exception, then it will be catched and a

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

Hi Brian, Brian May wrote: > Where is the event log stored? Right click "my computer", select "manage", click "Event Viewer", right click "Application", chose "Clear all Events". > The configuration is identical to the other computers that were working; > I think it is 0xFF OK. > The INFO

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

Rainer Meier wrote: > There is nothing really to debug here. In case of quiet mode (/quiet > flag set at command line or quiet flag set to true in config.xml) it is > simply using the Windows logEvent method. In case that one fails it is a > Windows issue. Try commenting just the logEvent method

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

Hi Brian, Brian May wrote: > Brian May wrote: >> Ok, now I commented out this code in log(type, destination): >> >> //if ((type & 7) > 0 || isDebug()) { >> // if(isQuiet()) { >> // WshShell = WScript.CreateObject("WScript.Shell"); >> //

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

Brian May wrote: > > Ok, now I commented out this code in log(type, destination): > > //if ((type & 7) > 0 || isDebug()) { > // if(isQuiet()) { > // WshShell = WScript.CreateObject("WScript.Shell"); > // WshShell.logEvent(type, de

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

Brian May wrote: > 2008-04-15 15:58:33, DEBUG : Going to install package 'Java Runtime > Environment 6 Update 5' (java6), Revision 5, (execute flag is '', notify > flag is 'true'). > 2008-04-15 15:58:33, DEBUG : Package 'Java Runtime Environment 6 Update > 5' (java6): Not yet processed during

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

Brian May schrieb: > Tomasz Chmielewski wrote: >> I meant, config.xml you use for wpkg.js. > > What I pasted is the only config.xml file I have. Is there support for > more then one? You're correct. I must be still sleeping ;) -- Tomasz Chmielewski http://wpkg.org ---

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

Tomasz Chmielewski wrote: > I meant, config.xml you use for wpkg.js. What I pasted is the only config.xml file I have. Is there support for more then one? Brian May - Reporting bugs, all WPKG mailing lists >> http://wpkg.or

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

Brian May schrieb: > Tomasz Chmielewski wrote: >> Does it really crash here (i.e., cscript process is not running)? > > I will have to double check. If it is not still running, it is very slow > (as in taking hours). I have seen it run slow other times, but not > this slow. > >> The next mess

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

Brian May wrote: > Tomasz Chmielewski wrote: >> Does it really crash here (i.e., cscript process is not running)? > > I will have to double check. If it is not still running, it is very slow > (as in taking hours). I have seen it run slow other times, but not > this slow. cscript doesn't seem

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

Tomasz Chmielewski wrote: > Does it really crash here (i.e., cscript process is not running)? I will have to double check. If it is not still running, it is very slow (as in taking hours). I have seen it run slow other times, but not this slow. > The next message should be: > > INFO : User

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

Brian May schrieb: > Hello, > > Only seems to happen on this one computer; previously if I started the > wpkg service, nothing would happen, no log files, nothing installed, > etc. The service is marked as running though, and if I didn't know > better everything looks fine. > > Now it starts,

[wpkg-users] wpkg.js crashing?

Hello, Only seems to happen on this one computer; previously if I started the wpkg service, nothing would happen, no log files, nothing installed, etc. The service is marked as running though, and if I didn't know better everything looks fine. Now it starts, but then it stops for no apparent r