pyinstxtractor runs to completion without problem, and then suggests to decompress the PYC to get the final .PY file (my goal)
However when I tried to use uncompyle2, uncompyle6, and plethora of other tools none of them worked. (Magic Number Mismatch!) Which means that the file outputted is not a .PYC file...
I opened the outputted file with a hex editor and I can see the source code decoded from hex however Im not able to extract that code in an efficient manner.. It's filled with .'s which should probably be spaces and indentation etc. However nothing i seem to do is able to succesffuly retrieve the source code from hex, or "PYC"
Help?
Related
I am quite new to work working with .stl files and in my research, I found they can be opened in a text editor where faces and vertices were clearly written out and easy to read. However, whenever I download a .stl file and open it with a text editor, I get a series of random characters. The same thing happens when I take a .blend file and export it to a .stl file. In spite of this, the .stl files still render correctly. I have attached a picture of what my problem looks like. If anyone could help me out, I would appreciate it.
Thanks.
The random characters when I open .stl files in a text editor.
I have a large text file that I take notes in; Recently, after saving it, it won't open and gives following error. I tried a few things on web that didn't work---opening in different encoding format, etc. Nothing worked. Any idea how I can open it again? Is there a language I can use from bash? I'm very familiar with PHP. Any ideas? Different text editor?
Error:
"The document “ToDo.txt” could not be opened. Text encoding Unicode (UTF-8) isn’t applicable."
"The file may have been saved using a different text encoding, or it may not be a text file."
cat the file from the CLI and make sure your data is still there. Then you could simply copy and paste the output into a new file and hopefully get rid of whatever weird encodings are causing that text editor to not read the file.
I'm auto-generating .doc files (.mht really) according to this tutorial.
Generated files work great locally but not on other computers as the file is requesting the header to be loaded from my local path instead of using the base64 version that is embedded. The main content is loading fine. Here's the generated file.
I can't find the reason for this behaviour. Any suggestions appreciated.
EDIT
Turned out that the problem was caused by unnecessary carriage return and line feed characters at the beginning of my base64 strings.
I'm trying to get this text file back to well readable text but I can't seem to find the encoding, it's for an Android application here is the one I'm trying to convert http://ge.tt/53SmHRP1/v/0
Can anyone point me in the right direction or give me a few tips on how to go about this as this is my first time with anything like this.
I've tried opening this with notepad, notepad++ & jedit to no avail the reason why I'm doing this is because I'm trying to create a cheat program for Plague Inc for Android but I can't seem to find the encoding for this file.
I need to insert a generated file into an exe at the time of download. Currently, I create an "empty" file (filled with a repeating character) and package that with the exe. When it comes time to download, I look at the bytes for the installer, find the file by looking for the repeating character, and insert the generated file.
This process however is not working. The repeating character just does not show in the bytes. But I am certain the file is there as it is unpacked if I run the exe. Am I doing something wrong or is inserting a file into an exe even possible?
Also note that I am using Inno Setup Script v5.5.1 to compile the project into an exe.
If you want to change the contents of a file specified in a [Files] entry and compiled into the setup executable, then you must:
Make a dummy file that is at least as large as the largest content you will want to insert.
Fill the file (or at least the first 64 bytes or so) with something unique and easily distinguishable.
Mark its [Files] entry with the "nocompression noencryption dontverifychecksum" flags.
You should then be able to scan the resulting executable for the marker in #2 and then substitute the data that you want. Note however that doing this might invalidate any digital signature on the setup file, although I haven't tested this to be sure.
Note that if the content you are inserting is smaller than the dummy file size, the extra bytes will still remain on the end of your inserted content. So whatever reads the file will have to have some way to ignore that or to recognise the end of the interesting content.
So, if your are making changes in the existing exe file, and if the text is not much, you can probably use some hex editor and make changes at desired location. If text is more , you might want to include some meaningless bytes, just as fillers.