JADGuerzoni

Thank you for your answer. As far as the question, I don´t have any peculiar reason, it is for completeness or, you may say, obsession, perfeccionism. Yes I-m "fairly detail oriented"

You are right. I have tried to install the hotfix manually and it is impossible because language conflict. But I think that is something strange: the support to new locales only to systems with locale 409 (US)! By the way how to find out the encoding of a txt file in Windows environment?

Thanks for your answer. I think that is the problem " HFSLIP takes INTL.INF from KB897338 and puts it into the new source ", so it puts this file in the SOURCESS and not the one wich has a defaul locale differente from 00000409 in the source (this hotfix is in english and there is no language neutral or my language portugues). "

Hi, I think I have put my post in the wrong plance and this is the better one. There is a little problem with sliplstream of KB897338 for non-US Windows, because this hotfix change the default value (in INTL.INF, sectio [Defaultvalue]) of locale to 00000409, this make the UWCD useless for atualization and give conflict of idiom. I think it would not dificult to implement a correction in batch file for non US to return the original value. I have slipstreamed with and without this hotfix and the problem occur only with it (by the way I´m using the HFSLIP_60518a version)

The hotfix KB897338 change the locale to US (00000409) in the section [Defaultvalue] of the file INTL.INF This alter the idiom of the Cd instalattion to US and make it useless for atualization. No amiricam should manually correct the INTL.INF. I think that this is correct, I have slipstreamd with e without the referred hotfix Thanks Excuse for my very poor english