Username:
B
I
U
S
"
url
img
#
code
sup
sub
font
size
color
smiley
embarassed
thumbsup
happy
Huh?
Angry
Roll Eyes
Undecided
Lips Sealed
Kiss
Cry
Grin
Wink
Tongue
Shocked
Cheesy
Smiley
Sad
<- 1  -   of 69 ->
--
--
List results:
Search options:
Use \ before commas in usernames
gyth - nice. Smiley So I guess you're optimizing all the anri code?

Warepire - interesting!
Yah, rewriting the batch while I get my head around the code.
Hopefully migrate to python and get a gui up at some point.
Not a walrus
Mmm python.
Quote from gyth:
Yah, rewriting the batch while I get my head around the code.
Hopefully migrate to python and get a gui up at some point.

Great. Looking forward to seeing this.
Quote from gyth:
...and get a gui up at some point.

That sounds great!
Edit history:
gyth: 2011-11-27 03:08:11 pm
Puzzled by this line
Code:
IF "%statid%"=="y" ECHO>> "%projname%_temp.avs" nmf ? last : statid++last++statid

Was the nmf file expected to already include the statid?
Is there a reason the nmf shouldn't be able to have statid???

Edit: ah, the .avs is used to make the nmf and the encode
Edit history:
gyth: 2011-11-27 10:13:41 pm
:proc_anrisettings_project_parentdir
:proc_anrisettings_dvdripto_parentdir
Are identical.
The thing which should be different, but isn't, is the prompt string:
"Full path to project parent folder, type n to cancel: "
Is:
"Full path to DvdRipTo parent folder, type n to cancel: "
clear enough, or could someone suggest a better description?
Edit history:
Warepire: 2011-11-29 07:00:27 am
Heavy Metal Powered
I'd use something like "Full path to the folder containing the DVD rip, type n to cancel:"
Edit history:
DJS: 2011-12-02 01:36:30 pm
torch slug since 2006
I have never seen this before. stuff you might wanna know: windows 7 x64, freshly installed anri, importing norichan avi, have latest cccp installed...

Attachment:
It looks like something named FIND occurs in your %PATH% before the function anri is looking for.
What happens when you type "find /?" at a command prompt?
You should see this
Code:
Searches for a text string in a file or files.

FIND [/V] [/C] [/N] [/I] [/OFF[LINE]] "string" [[drive:][path]filename[ ...]]

  /V         Displays all lines NOT containing the specified string.
  /C         Displays only the count of lines containing the string.
  /N         Displays line numbers with the displayed lines.
  /I         Ignores the case of characters when searching for the string.
  /OFF[LINE] Do not skip files with offline attribute set.
  "string"   Specifies the text string to find.
  [drive:][path]filename
             Specifies a file or files to search.

If a path is not specified, FIND searches the text typed at the prompt
or piped from another command.
Edit history:
DJS: 2011-12-02 03:27:09 pm
torch slug since 2006
Yeah, it seems like I dont have the find command. wtf.
Guess Ill format/reinstall windows here someday, to solve it (hopefully). but still, weird
Why not google it? I'm sure there are some sources to find it somewhere.
Else, I could upload it, though I can't guarantee it will work on your OS/computer.
I use Win7 Prof myself.
torch slug since 2006
Sure I could just get the find.exe and put it in my system32 dir or whatever, but this is the first time this have happened for me, so im wondering what happened.
Quote from gyth:
What happens when you type "find /?" at a command prompt?
Edit history:
DJS: 2011-12-02 05:29:27 pm
torch slug since 2006
My main pc is shut down atm but ill check tommorow better if needed, but it was something like "not a recognized command" or "No such file or directory". however, if i just typed "find" it started listing alot of files (like a "dir" command almost)

But its just my installation of windows that is dumb for some reason, as ive used anri-chan on the exact same setup  without any problems before. I reformatted/reinstalled everything last sunday...

I will probably just reformat/reinstall again tommorow, to see if it fixes it...
Look for find.exe in C:\Windows\System32
that sounds like the unix find command ... do you have anything like cygwin or minsys or another unix compatibility layer installed?
Edit history:
DJS: 2011-12-03 06:29:23 am
DJS: 2011-12-03 06:27:46 am
torch slug since 2006
i have find.exe in my system32 and syswow64

Quote from nate:
that sounds like the unix find command ... do you have anything like cygwin or minsys or another unix compatibility layer installed?

nope.

edit : ok i took a cd to %windir%\system32 , and put find /? and there it works. so its like my find.exe isnt registered or something

Attachment:
Your output isn't right.
It should be as in attached picture.
You probably have some other "find" command somewhere and that directory is in your path. Suggest you remove or rename that file or remove that directory from your path.

Attachment:
torch slug since 2006
Pay attention to the current dir im running the command in.

Attachment:
Your point? This just confirms that there is some rogue file and/or path that's intercepting the find command.
torch slug since 2006
Okay you were right, I found the bad find.exe.
It was in devkitPro , so I just removed that one .exe and now it works.
Really weird imo, as windows own find.exe should always be registered I would think.
It depends on your path. Any program can change it, and some installers can change it for the worse.
When typing a command, the current directory is searched first, and then the directories in the path from left to right.
what are the odds references to find and other os utility programs could be hardcoded with %SYSTEM32%\ or whatever before their invocations? as far as i can tell, assuming that variable is expanded correctly regardless of locale and the programs are actually located there, it should prevent this kind of thing.
SET PATH=%windir%\system32;%anri_dir%
Smiley

Within anri it is only a copy of the environmental variable, so changing it only effects things inside anri.

P.S. might be better to derive it from %comspec% which is C:\Windows\System32\cmd.exe on standard installs. (post NT)
And the systems where it isn't are likely missing most of the commands we use. (98 and before)