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

Set directory path outside sys32 #3

Closed
masterrite opened this issue Oct 4, 2017 · 6 comments
Closed

Set directory path outside sys32 #3

masterrite opened this issue Oct 4, 2017 · 6 comments

Comments

@masterrite
Copy link

It'd be cool if we can set an output path - my copy of pkg2zip zipped the file into sys32 folder.

@mmozeiko
Copy link
Owner

mmozeiko commented Oct 4, 2017

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.

@masterrite
Copy link
Author

uh... I kept and launched the program in my download folder. That's why I'm surprised it outputted in sys32

@mmozeiko
Copy link
Owner

mmozeiko commented Oct 4, 2017

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)?

@masterrite
Copy link
Author

masterrite commented Oct 4, 2017

I'm running directly from cmd.exe window... ah, looking again at the command, I think I see what's wrong here:

C:\Windows\system32>"D:\Game tools\pkg2zip.exe" C:\users\username\downloads\package.pkg [zrif string]

snipaste_20171004_130458

@mmozeiko
Copy link
Owner

mmozeiko commented Oct 4, 2017

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".

@masterrite
Copy link
Author

Awesome - thanks! I've got a lot to learn yet

sigmaboy pushed a commit to sigmaboy/pkg2zip that referenced this issue Jun 14, 2020
command line argument improvements
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

2 participants