Difference between revisions of "Talk:AUTOEXEC"
From DOSBoxWiki
Jump to navigationJump to search (cls kinda fixes it, looks like) |
(No autoexec call when DOSBOX is run with parameters) |
||
| Line 9: | Line 9: | ||
Looks like the quick'n'dirty workaround is to put cls as the first line in [autoexec]! :) I'd still be happy to hear better suggestions. | Looks like the quick'n'dirty workaround is to put cls as the first line in [autoexec]! :) I'd still be happy to hear better suggestions. | ||
| + | |||
| + | == No autoexec call when DOSBOX is run with parameters == | ||
| + | |||
| + | When running DOSBOX with command line paramters (-c option), the AUTOEXEC section of the dosbox.conf file is not executed. Why? And how to fix it? | ||
Revision as of 22:31, 13 April 2009
- Any tips about how to set FILES=200 and BUFFERS=30 ? Some MSDOS APPs need them.
DOSBox has FILES=127 and buffers=50 you can change those by either recompiling dosbox or by booting a disk image in DOSBox. however they should fire the programmer who ever coded the FILES=200 requirement.
- At startup there's displayed the ugly SETBLASTER, SETULTRASOUND and SETULTRADIR variables. Is there a way to hide them?
Looks like the quick'n'dirty workaround is to put cls as the first line in [autoexec]! :) I'd still be happy to hear better suggestions.
No autoexec call when DOSBOX is run with parameters
When running DOSBOX with command line paramters (-c option), the AUTOEXEC section of the dosbox.conf file is not executed. Why? And how to fix it?
