|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
|
#1 |
|
Member
Join Date: Sep 2005
Location: Sitting next to my desk
Posts: 56
|
Warning 'Packer returned 1, "..." might still be unpacked'
I'm using NSIS 3.01 on a Windows 10 System. I get the warning:
1 warning: Packer returned 1, "C:\Users\TM\AppData\Local\Temp\exehead.tmp" might still be unpacked The NSIS script never made Problems with NSIS 2.46, and I do not know what this message will exactly tells me. The installer itself is created and seems to work correctly. Other Setup scritps does not return with this warning. Any idea for this warning? This signature is currently on vacation! |
|
|
|
|
|
#2 |
|
Moderator
Join Date: Jun 2002
Location: ${NSISDIR}
Posts: 5,442
|
It would have been helpful if you showed us how you are using !packhdr.
The warning is new for v3 but the end result is unchanged. If the child process started by !packhdr does not exit with error code 0 you will get this warning... IntOp $PostCount $PostCount + 1 |
|
|
|
|
|
#3 |
|
Member
Join Date: Sep 2005
Location: Sitting next to my desk
Posts: 56
|
The !packhdr macro is not used in my script at all.
This signature is currently on vacation! |
|
|
|
|
|
#4 |
|
Moderator
Join Date: Jun 2002
Location: ${NSISDIR}
Posts: 5,442
|
Of course it is, it is the only instruction that can generate that warning. Check the files you are !including...
IntOp $PostCount $PostCount + 1 |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|