-
Notifications
You must be signed in to change notification settings - Fork 90
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
Set directory path outside sys32 #3
Comments
I would like to keep arguments as simple as possible. The current implementation simply writes to current folder. So as long as you are in correct folder, it will unpack into this folder. Unpacking inside System32 can probably happen if you keep pkg2zip.exe inside it? I suggest to not keep custom binaries in Windows internal folders. That's a trouble waiting to happen. Create new folder where you keep your utilities/binaries (for example "c:\bin") and add it to PATH. |
uh... I kept and launched the program in my download folder. That's why I'm surprised it outputted in sys32 |
Hmm. That's strange. Can you give me more details what exactly were you running? Do you have .bat file that calls pkg2zip.exe? Or are you running directly from cmd.exe window? If from cmd.exe what are exact arguments you are using (could you please post whole command line you are executing)? |
Right, you are running it from C:\Windows\System32. That's why it creates output there. You can either do "cd c:\folder\where\you\want\to\output" before running command. Or open cmd.exe directly in folder where to unpack. To do that, keep Shift pressed, click right mouse button and select "Open command window here". |
Awesome - thanks! I've got a lot to learn yet |
command line argument improvements
It'd be cool if we can set an output path - my copy of pkg2zip zipped the file into sys32 folder.
The text was updated successfully, but these errors were encountered: