- Jul 14, 2017
- 89
- 334
I just downloaded that game to check and there are 3 fairly long animations in the game/animation folder without the need to use UnRen.
- Jun 21, 2018
- 526
- 383
after checking out the game files I found out that the animation videos are out in the open, so I had full access to all pics and videos without needs to extract anything, I just need to find them insideI just downloaded that game to check and there are 3 fairly long animations in the game/animation folder without the need to use UnRen.
Option #2. This happens regardless of the directory location or name. It used to work fine. Can still use decompile.rpy but that thing makes a mess.
- Jun 10, 2017
- 10,110
- 14,782
Yes, I already tried that. I know python can be bitchy about such things. Still doesnt work. Even when I copy folder into root dir, and name it "A" still same issue.
- Jun 10, 2017
- 10,110
- 14,782
Yen symbol is the same as \. Its visual only. Just a side-effect of using japanese locale
- Dec 17, 2017
- 806
- 461
I will never understand why some people think 'others' know somehow what they know themselves, without telling them.
R. Please do this few things:
I noticed something unusual in your screenshot and think its possible people here focused on the wrong facts.
The shot says
and then
Thats fishy i'd say. Either your powershell thingy fucks up or some access rights problem. Perhaps also a broken UnRen.
R. Please do this few things:
- Please cite your used CLI command(s) fully and exact
- State used OS version, UnRen version and DL location
- Add info of the project you're working on(name, special stuff about it...)
- Try just with unrypc itself to decompile your project
I noticed something unusual in your screenshot and think its possible people here focused on the wrong facts.
The shot says
Code:
Extracting _unrpyc.cab...
Code:
expand: invalid option -- F
Last edited:
- This happens when using 2) Decompile rpyc files
- Windows 8.1, typically using unren0.8 but happens with other versions as well. DL location doesnt matter because as i mentioned even if i put the game in root directory and name folder "A" same shit happens.
- I tried it with dozens of games. Nothing changes except the number of files it fails to extract.
- I'm a user, not a dev so i dont have knowledge to compile and use unrpyc.
Using decompile.rpy i got from somewhere works except it dumps all the files into main game directory. At this point i'd be happy just to have a rpy file that can do the same without making a mess.
- Dec 17, 2017
- 7,425
- 9,680
So the problem isn't version of windows, but something in your windows PATH. I've got the same thing happening to me, but if you check, you'll also note the error says to try 'expand --help' for options. Do that from a command prompt.
You'll probably find that the resultant text includes the phrase 'GNU coreutils', as it's not calling the Windows EXPAND command, instead it's calling the GNU coreutils expand command, probably installed with a devkit of some sort.
Two fixes. One less fun one, search your windows environmental variables, make some educated guesses as to what's causing the issue in the path, and remove it.
Better fix:
Edit the unren batch file, and replace
Code:
expand -F:* "%unrpyccab%" "%decompilerdir%" >nul
Code:
%WINDIR%\system32\expand.exe -F:* "%unrpyccab%" "%decompilerdir%" >nul- Dec 17, 2017
- 806
- 461
You missunderstood.
1) I asked about the DL location where you did get your UnRen from. Just wanted to make sure the errors are not from a corrupted UnRen or from a untrustworthy place.
2) You dont need to compile anything fro unrpyc. But ok. Thats no prob. For this is UnRen.
You must be registered to see the links
Like documented there the -F option is just to pass the cab file(s) into "expand".
Am I wrong or does it sound suspiciously like there no cab's or corrupt ones? And this points IMO again to a powershell issue.
EDIT: I was to slow with my post and did not see the post before mine.
Last edited:
- Dec 17, 2017
- 7,425
- 9,680
I'd expect a different error message if there wasn't a valid file passed in via -F. But yeah, this does smell like a shell issue.You must be registered to see the links
Like documented there the -F option is just to pass the cab file(s) into "expand".
Am I wrong or does it sound suspiciously like there no cab's or corrupt ones? And this points IMO again to a powershell issue.
- Dec 17, 2017
- 806
- 461
Holy hanna entarotine. Something so much f*ck*d up like a wrong expand executable was not on my radar. If you're right with this... uh-hu, i dont know what to say about it just now.
Very intriguing problem. Did'n expect.
On a side note: I wonder just now why sam used powershell at all. You can merge strings without it.
Yes. This is related to entarotine's idea. I think he is right.
Very intriguing problem. Did'n expect.
On a side note: I wonder just now why sam used powershell at all. You can merge strings without it.
Last edited:
- Jun 10, 2017
- 10,110
- 14,782
It have it, the
F option was introduced in Vista. But what can be the cause is the use of - as prefix in place of the usual / used by Windows. Both are supposed to works, but who know.
- Dec 17, 2017
- 806
- 461
Actually no. The -F parameter was added '99 and came with Win 2000. The use of the minus is also total correct because the app predates the fuckup of Microsofts use of slash's as parameter prefix. "expand" and "compress" came in 1990 with "DOS 5.0" out from the look of it.
I have here somewhere in my magic computer cabinet the disks for DOS 6.22 and Windows 3.1 dusting. However no 3,5" floppydrive anymore.
Last edited:
- Jun 10, 2017
- 10,110
- 14,782
Well, it's not what
You must be registered to see the links
say, but in the same time it's what
You must be registered to see the links
say, so my memory can have betrayed me, which is something that happen.I never said that it wasn't correct, but that, time to time in the long history of the MS-DOS tools, some of them had a fucked behavior and among consequences some simply didn't recognized
- as parameter prefix.Good for you, and so ? Is this a contest, and if yes, what I win if I found my DOS 3.0 floppy disk ?
All this said, since you sent us back in time, I took another look at the screenshot, and the explanation is in fact obvious ; the error message clearly show that this is not the
expand command of MS-DOS.The output should start with a one line description of the tools, then MS copyright. The error message should be "invalid option -F", not "invalid option -- F", and finally the reference to an "--help" command is twice wrong. Firstly because
expand have no help screen, and secondly because of the -- which isn't a MS-DOS prefix. Therefore, the error is in the path environment variable.R. installed (or had installed behind his back) an application that include an
expand program (a port of GNU tools by example) and, for whatever reason, the path to this application is defined before the path to MS-DOS commands in the path environment variable. Therefore, UnRen is simply using the wrong command.My Win10 is "old school configured" and not in English, so you'll perhaps have to improvise with this :
- Go the the configuration panel ;
- Choose "System" ;
- Choose "Advanced parameters" ;
- Click on "Environment variables" on the bottom of the "advanced parameters" tab which should be the one actually selected ;
- On the "System variable" list (the one on the bottom) search the line "path" and select it ;
- Click on the "modify" button ;
- Search the line "C:\Windows\system32" and select it ;
- Move it to the top of the list ;
- Click on "OK".