pkmusic

Yes, userenv. I spelt it wrong. Anyway it's moot now. The problem is completely solved and it's all thanks to both of you guys and your advice. Thank you. I easily found the dll files that were missing. I then had to search for rewire.dll. That was the one causing the main problem in the end even though it was present all along. I guess it became corrupt. I found a random link to it in a forum somewhere. Success! Thanks again. xoxoxoxox

Glock: I tried the full service pack. The one that downloads in several parts. And yes I've totally reinstalled the software a few times now, always with the same error on opening. EidenK: Opening the app came up with just the below two. APPHELP.DLL USERNV.DLL Profiling came up with all the others. So it just may be these two above that I really need? And are they windows files?

Submix.:-) Thank you. Yes I've been using the software for some time and the problem just suddenly started last week. Is your service pack the same as the one at microsoft? I tried theirs and it didn't help this problem. P.

Thanks eidenk. Dependency Walker was very helpful. It's telling me the below 6 files are missing. I presume they are all particularly related to the Reason software and are not just windows things. What should I do? I'm having the same problem with two different versions of the software when installing from two totally different cds. Weird. APPHELP.DLL USERNV.DLL REWIREBETA.DLL REWIREDEBUG.DLL REX SHARED LIBRARY BETA.DLL REX SHARED LIBRARY DEBUG.DLL

I installed the C++ service update pack too and that didn't solve the problem.

Thanks for answering. Yes the file msvcirt.dll is definitely there. It's version 6.10.8637.0 The software I'm having the problem with is Reason 2.5. Even a complete reinstall doesn't stop the error.

Hi. I'm in need of a windows 98 hotfix for the following error message concerning Microsoft visual C++.. "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information'. I found an article referring to it at Microsoft support. The error was identical but the article was referring to windows XP. The keyword they quoted was KB884538. But I'm not sure if that's relevant. Desperate! Can anyone help? Thanks. Peter.