landgrimtham
21st July 2005 07:52 UTC

Newbie need help
hi all a newbie here. and i need some help in solving this problem. Can anyone help me? The program keep prompting me "no files found"

thanks all


InstallDir: "$PROGRAMFILES\EngWin"
Section: "EngWin"
Call "InstallVBDLLs"
SetOutPath: "$(WinSysPathSysFile)"
File: "RICHED32.DLL" -> no files found.
Usage: File [/nonfatal] [/a] ([/r] filespec [...]|/oname=outfile one_file_only)
Error in script "C:\Documents and Settings\ptham.ATA\Desktop\IMPT DATELINE END OF SEP\testing.nsi" on line 281 -- aborting creation process

Yathosho
21st July 2005 08:38 UTC

make sure the RICHED32.DLL is in the same directory as your script or specify a path to that file (i.e. File "$SYSDIR\RICHED32.DLL")

Afrow UK
21st July 2005 12:05 UTC

What's with all the SetOutPath "$INSTDIR/Miscellaneous" and Push $INSTDIR/Miscellaneous\Busy.bmp
It's \ not / in Windows.

-Stu

landgrimtham
22nd July 2005 06:24 UTC

thanks bro Yathosho

the code works but now i have another problem while compiling. The upgradedll is giving me a problem. Can anyone help?


!define: "UPGRADEDLL_UNIQUE"="2.9"
SetOverwrite: try
StrCpy $R4 "$SYSDIR\Asycfilt.dll" () ()
StrCpy $R5 "$SYSDIR" () ()
IfFileExists: "$R4" ? 0 : upgradedll.copy_2.9
ClearErrors
GetDLLVersionLocal: error reading version info from ".\Asycfilt.dll"
Error in macro UpgradeDLL on macroline 26
!include: error in script: "C:\Program Files\NSIS\Include\installVB.nsh" on line 2
Error in script "C:\Documents and Settings\ptham\Desktop\IMPT DATELINE END OF SEP\testing.nsi" on line 42 -- aborting creation process

Here is the edited version of the nsi script.

landgrimtham
22nd July 2005 06:26 UTC

Bro afrow UK,

i'm trying to import the VB setup to a NISI script by using a program that *search 4 vbconvert* i have found here but it seems that i have some bugz that i need to squash before i can use it... :(

Afrow UK
22nd July 2005 13:01 UTC

GetDLLVersionLocal is failing there. Perhaps Asycfilt.dll in use or something?

-Stu

landgrimtham
25th July 2005 05:12 UTC

Originally posted by Afrow UK
GetDLLVersionLocal is failing there. Perhaps Asycfilt.dll in use or something?

-Stu

Comperio
25th July 2005 05:58 UTC

usually if a file is 'in use', you can't rename it. You might also get the error if for some reason you don't have permissions to the file. (Are you using the correct path to the DLL?)

I'd first try to make sure that you can access the version info from the file Asycfilt.dll from Windows Explorer. If you can and you know the paths are correct, then try to rename the file. If you can't rename, the file is probably in use. (If it does let you rename, remember to rename it back to what it was!)

landgrimtham
25th July 2005 10:55 UTC

Originally posted by Comperio
usually if a file is 'in use', you can't rename it. You might also get the error if for some reason you don't have permissions to the file. (Are you using the correct path to the DLL?)

I'd first try to make sure that you can access the version info from the file Asycfilt.dll from Windows Explorer. If you can and you know the paths are correct, then try to rename the file. If you can't rename, the file is probably in use. (If it does let you rename, remember to rename it back to what it was!)

landgrimtham
26th July 2005 04:18 UTC

can it be becoz of my pc setting that is affecting my script? :cry:

Comperio
26th July 2005 05:22 UTC

You seem to be missing a lot of the pieces to make this work. (Has this ever sucessfully compiled on this PC?)

I looked at your 1st and 2nd attachments. They don't quite tell the whole story. In the main script, I can see that asside from the MUI, 3 other files are being included: upgradeDll.nsh, shareddll.nsh, and installvb.nsh.

I can see in the last file (installvb.nsh) that there are several calls being made to the macro named "UpgradeDLL" and to the function named "AddSharedDLL". My best guess would be that the problem lies somewhere on one of these two.

Unfortunately, neither one of these are included in the files you've sent, so I assume that they live in one of the other 2 NSH files (shareddll.nsh or upgradedll.nsh). I'd examine both to see what they are doing--perhaps it will shed some light on what else you might be missing.

Also: you never did mention whether or not you were able obtain the version info from the file Asycfilt.dll from within Windows explorer.

landgrimtham
26th July 2005 07:32 UTC

Originally posted by Comperio
You seem to be missing a lot of the pieces to make this work. (Has this ever sucessfully compiled on this PC?)

I looked at your 1st and 2nd attachments. They don't quite tell the whole story. In the main script, I can see that asside from the MUI, 3 other files are being included: upgradeDll.nsh, shareddll.nsh, and installvb.nsh.

I can see in the last file (installvb.nsh) that there are several calls being made to the macro named "UpgradeDLL" and to the function named "AddSharedDLL". My best guess would be that the problem lies somewhere on one of these two.

Unfortunately, neither one of these are included in the files you've sent, so I assume that they live in one of the other 2 NSH files (shareddll.nsh or upgradedll.nsh). I'd examine both to see what they are doing--perhaps it will shed some light on what else you might be missing.

Also: you never did mention whether or not you were able obtain the version info from the file Asycfilt.dll from within Windows explorer.

landgrimtham
26th July 2005 07:40 UTC

Originally posted by Comperio
You seem to be missing a lot of the pieces to make this work. (Has this ever sucessfully compiled on this PC?)

Comperio
27th July 2005 05:23 UTC

See if this helps:
Since you install seems to be failing when installing the VB runtimes, I'd start with that.

Looking at your full script, it appears that the script is using some older macros for updating DLLs. This could be part of where it's failing. You may find it easier to rewrite using the newer methods.

I'd suggest reviewing Appendix B of the NSIS help files. It outlines how to use macros contained in library.nsh to install DLL. And there's a section dedicated to VB6 runtimes.

Sorry I couldn't be more help.

landgrimtham
27th July 2005 08:28 UTC

Originally posted by Comperio
See if this helps:
Since you install seems to be failing when installing the VB runtimes, I'd start with that.

Looking at your full script, it appears that the script is using some older macros for updating DLLs. This could be part of where it's failing. You may find it easier to rewrite using the newer methods.

I'd suggest reviewing Appendix B of the NSIS help files. It outlines how to use macros contained in library.nsh to install DLL. And there's a section dedicated to VB6 runtimes.

Sorry I couldn't be more help.