Lea, can't say I've ever had this problem. I presume you are refering to the WIN32 API version of LoadString? Looking at it in the MSDN my first guess was that maybe you are having buffer problems, NT being UNICODE and Win98 being...well what is it exactly? ;) (sorry that was not very helpfull was it). My advice is to try using the API call GetLastError(), which will return you an error code (that may have been set by the LoadString call). There is an error list in the MSDN some where which will help you decipher what the error code means. Accept that some days you are the pigeon and some days the statue.