cookiemonster
New Member
- Joined
- May 28, 2015
- Messages
- 1
- Reaction score
- 0
- Country
- Germany
For Windows users having trouble getting the autoexec.ash files to work...
I know it has been posted before, however "use UNIX format" might not be enough info for everybody.
A couple of pages back in this thread someone saved their file as UNIX script file in the file menu and noted there wasn't any *.ash suffix to select but only *.sh and *.bsh. By doing so you just change the file suffix but not the format of the EOL setting which is what actually matters.
1) Use Notepad++
2) Create/load/paste/edit file as desired
3) Menu: View - Show Symbol - Show End of Line (most likely, you will now see [CR][LF] at the end of each line)
4) Menu: Edit - EOL Conversion - Convert to UNIX Format ([CR] symbols are now gone, only [LF] symbols at the end of each line)
5) Save file as autoexec.ash (filetype can be "normal text file" or anything) and copy to root of SD card
If this doesn't help at least you know it's not the format but the contents of the file itself that's wrong
I know it has been posted before, however "use UNIX format" might not be enough info for everybody.
A couple of pages back in this thread someone saved their file as UNIX script file in the file menu and noted there wasn't any *.ash suffix to select but only *.sh and *.bsh. By doing so you just change the file suffix but not the format of the EOL setting which is what actually matters.
1) Use Notepad++
2) Create/load/paste/edit file as desired
3) Menu: View - Show Symbol - Show End of Line (most likely, you will now see [CR][LF] at the end of each line)
4) Menu: Edit - EOL Conversion - Convert to UNIX Format ([CR] symbols are now gone, only [LF] symbols at the end of each line)
5) Save file as autoexec.ash (filetype can be "normal text file" or anything) and copy to root of SD card
If this doesn't help at least you know it's not the format but the contents of the file itself that's wrong