Skip to content
⌘ NSIS Forum Archive

System::Call is not working with Win98

40 posts

Gurleen#
Well I am attching the screenshot of what I got after running the command.
Gurleen#
Sorry for that. I did not realise I was running the command on Xp . Well when I ran that on win98 it said "Bdd Command" . Does that mean that I am missing some basic libraries on 98 .
kichik#
No, it probably means the path is not set right. Anyway, lets just skip the testing part and assume it is a missing import. Use Dependency Walker on the DLL (from Windows 98) and see what it's missing.
Gurleen#
Well I did run it. It gave the following error
kichik#
Taken from:



LoadLibrary("Dllname") failed. GetlastError returns 0x00000485

From Winerror.h, 0x00000485 = 1157 (ERROR_DLL_NOT_FOUND), which means "One of the library files needed to run this application cannot be found." For example, typing regsvr32 missing.dll returns this error message if the Missing.dll file is not found.
So it really is a missing import. Use Dependecy Walker to find out which one it is.

[edit] hmm... misread that... seems like it can't find the DLL. Assuming the DLL is really located in C:\, I'd still say it's a missing import.
KrYpT#
My two bits: Why are you tring to use the debug version of the DLL? Maybe switching to a release version would help.
kichik#
Then you must require the user to install MSI, or, the more reasonable solution, remove that dependency as it makes no sense. You're already using NSIS, why would you need MSI?
Gurleen#
Thanks Man .. It Worked

Well in the end it required MSI.dll . But why would it require MSI.dll . I just created a dll using VS6.0 .
But in the end it worked.. Thats what matters. Thanks a lot for helping me out. Now I can sleep tonight. Thanks to all of you who gave their input and special thanks to "kichik" for meking it work.