enhance the crashrpt.xml file about crashrpt HOT 4 CLOSED

1. Computer name and IP address is personally identifiable information. I do not
think someone will want to provide such information. Can you give an example of 
why
you may need such info? 

Even if we implement such feature, we need to warn user and request his consent
before sending report.

2. The number of CPUs is already implemented as standard feature.

3. Amount of RAM installed as well as how much memory the process was using at 
the
time of crash - OK, this is not personal info, we can easily add this.

4. "Would be very useful to know the type of video card installed as well as the
driver version of that video card." I do not think many developers will use such
feature, but we can implement this as option. User consent is required to send 
such
info. 

5. "total amount of disk space that and free disk space". This may be useful, 
but
what if there are several disks? User consent is required on this.

In my case I want to identify the person that sent the crash report. The 
reports are
less useful without knowing from which company the report came from.

My companies use of an automated report system is perhaps different than 
others. My
company provides the hardware to end-users that our software runs on. These 
systems
do not belong to any individual end-users. The PCs are company workstations that
perform data processing.

I understand that CrashRpt is used by other companies or individuals where 
personal
information could be a problem, but in my case personal information is not an 
issue.
My end-users do not use the systems as personal workstations.

As far as user consent goes, there are times where no one will be around to 
consent.
For example, a server style process is running and crashes. The desired 
behavior is
that a crash report is automatically sent and the process is restarted (I 
requested
auto process restart upon crash in another request) - User consent is not 
possible
here yet we will still need screenshots as well as the PC name. 

My experience has been with bugtrap. It requires user consent only if the 
programmer
requests it. It is possible to configure bugtrap in such a way that it does not 
ask
for any consent. Sometimes this is necessary.

I'm thinking about your need of user's identification. You would like to 
identify
users by IP or by NetBIOS computer name, while other developers may need other 
ways
of identification (e.g., by license key or by user name). We can't add all these
identification mechainsms in CrashRpt.

So, I would offer to implement some extension mechanism for CrashRpt XML file. 
We can
introduce crAddProperty(lpszPropId, lpszPropValue); function that would allow
developer to collect some custom info on crash and add it to XML (for example 
to add
user IP). On the side of crprober.exe, this property can be extracted from ZIP 
file
by using crpGetProperty() function. 

What do you think?