Hi, At 10:37 AM 8/24/2002 +0100, Gareth Randall wrote: >Any chance of implementing some sort of status output to say "I got to >here..."? Something like this: > >[time] PID etc DNS resolved server #think this is actually just an IP >[time] PID etc Open connection to proxy >[time] PID etc Connection to proxy made >[time] PID etc Asked to connect to primenet server >[time] PID etc Got connected to primenet server >[time] PID etc Sent the data or request # you know what I mean >[time] PID etc Got the expected response >[time] PID etc Saved the updated state to disk # catch filesys errors >[time] PID etc Closed connection to proxy > >Whichever is the last entry in the log is the next stage at which you >should be looking at. Ideally a competent user can see immediately where >it got stuck.
The closest thing to this is setting Debug=1 in primenet.ini (version 22 only). It is a bit more verbose than this and the output is a little more cryptic. >This sort of error tracking is particularly relevant to me at the moment, >because I have recently been involved in supporting Windows apps, and >no-one has designed anything to narrow down problems. I can sympathize with your plight. Administration is often a thankless job. > Error messages are useless and say nothing more than "er, it didn't > work", and no clue is given as to which part of the procedure failed. Guilty as charged. >On the subject, all programmers should try to avoid giving their error >messages in little pop-ups that can't be cut and pasted. Don't just follow >the crowd. Make your error messages appear in text boxes which don't >require people to manually retype them. :-) But this is the Microsoft standard! The right answer is for MS to change the way windows works - to allow copying text from message boxes. Best regards, George _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
