Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zlib.dll call returns error 12 #1

Open
bienieck opened this issue Apr 24, 2023 · 4 comments
Open

zlib.dll call returns error 12 #1

bienieck opened this issue Apr 24, 2023 · 4 comments

Comments

@bienieck
Copy link

I'm getting error 12 when using this tool in 64-bit version of LV. I guess zlib.dll is compiled for 32-bit and can't be called by 64-bit LV process.

@crowmatt
Copy link

I'm getting error 12 when using this tool in 64-bit version of LV. I guess zlib.dll is compiled for 32-bit and can't be called by 64-bit LV process.

Same here: Code: 12. Call Library Function Node in VI-Hacker.lvlib:zlib Uncompress.vi->VI-Hacker.lvlib:VI-Hacker.vi
I used another version (v1.2.8.0) of zlib.dll which solved my problem. See the attached file.
zlib.zip

@2k9laojia
Copy link

why it also need password after i crack. the error is :
Unitled 1 belongs to a password-protected library. the library is either missing or its password has changed. enter the library's previous password to access the block diagram.

Note that: i have copy the vi file from the previous folder

@rcpacini
Copy link
Owner

LabVIEW project libraries can be password protected using a different authentication protocol than this tool provides. Lvlib passwords more secure and cannot be decrypted easily. Link below.

https://www.ni.com/docs/en-US/bundle/labview/page/protecting-project-libraries.html

At this time, I have no way to reverse engineer the project library's password to unlock the VI members.

@Novgorod
Copy link

Novgorod commented Jul 2, 2024

why it also need password after i crack. the error is : Unitled 1 belongs to a password-protected library. the library is either missing or its password has changed. enter the library's previous password to access the block diagram.

VIs that are (locked) library members are more annoying but not more secure. The "security" is still only provided by obfuscation, not by encryption, because the source code has to stay compilable, i.e. accessible. This "hack tool" only overwrites the password hash in the VI but doesn't unlink it from the library. Labview checks whether the VI is a locked library member and asks for the library password in that case to show the block diagram, even if the VI itself has an empty password. You have to regenerate the block index of the VI and remove the library membership.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants