Hi,
registry uploaded, tested on win xp with latest updates installed and
the 2.1 version of the agent, I think.

Cheers

Am 01.11.2010 15:14, schrieb Gonéri Le Bouder:
> On Wed, Oct 06, 2010 at 08:52:06PM +0200, Guillaume Rousse wrote:
>> Le 06/10/2010 20:45, Mario Gzuk a écrit :
>>> <VERSION>3.0.0.3...@software\\microsoft\\windows\\currentversion\\uninstall\\</VERSION>
>>>       <VERSION_MAJOR>3</VERSION_MAJOR>
>>>       <VERSION_MINOR>0</VERSION_MINOR>
>>>     </SOFTWARES>
>>>
>>> There is an non UTF-8 char in the version string. Following the xml
>>> charset this should not be happen if the agent sends its data, or what
>>> you think about that? I doesnt test this with the FusionInventory Server
>>> library, but xml functions from php like:
>>> simplexml_load_string()
>>> xml_parse_into_struct()
>>> fail with this char... Can the validate to UTF-8 be done by the client?
>> It is supposed to be the case, so you found a bug. Can you open a ticket
>> on the project forge
>> (http://forge.fusioninventory.org/projects/fusioninventory-agent/issues), 
>> with
>> a bit more details on your setup (agent version, platform, etc...) ?
> Hi Mario,
> 
> I answered to you ticket here: http://forge.fusioninventory.org/issues/415
> 
> What agent release and Windows version are you using?i
> 
> I've the feeling the information stored in the registry was already not in a
> valide encoding? It's suppose to be the charset found in
> LMachine\SYSTEM\CurrentControlSet\Control\Nls\CodePage
> 
> Best regards,
> 
>      Gonéri Le Bouder
> 

_______________________________________________
Fusioninventory-devel mailing list
Fusioninventory-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/fusioninventory-devel

Répondre à