![]() ![]() Support for mounting logical DOS partitions in disk images’ extended partitions Also added “shellhigh” config option to decide whether to load DOSBox-X’s built-in command shell to UMB memory (with default setting of “auto”, it is enabled if reported DOS version is at least 7, similar to MS-DOS 7+). You can now load DOS programs into the high memory (UMB) using LH/LOADHIGH command when it is available (previously this command did not load programs into UMB). Support for loading programs into UMB memory with LH/LOADHIGH command It is supported in all Windows builds as well SDL2 builds on Linux and macOS platforms. Support for transparent window (all Windows builds and Linux/macOS SDL2 builds)ĭOSBox-X now supports the transparent window feature (so that you can make the DOSBox-X window semi-transparent), which can be set via config option “transparency” in section (with value from 0 to 90, low to high transparency). Windows installers are now reorganized to two installers installing 32-bit and 64-bit DOSBox-X binaries, for Windows XP+ (32/64-bit) and Vista+ 64-bit respectively, reducing the sizes of installers significantly while adding the SarasaGothicFixed TTF font (supporting both SBCS and DBCS languages) and a language selection page for choosing existing language translations (with new language files for French and Traditional Chinese). I've tried using the Title command in a batch file, but that changes the Title after the window opens, and the Save properties for future windows with same title option uses the original window title, before the Title command can change it.Reorganized Windows installers to 32-bit and 64-bit installers with new language selection page The Command Prompt window will remain open when the batch file exits unless you use the exit command, so you may need to use this in your "Starting" files: When you OK the properties dialog, choose the Save properties for future windows with same title option. Assign each window a different title, then position and size them. Otherwise, only way I know is to use the Start command to start each batch file. If you have a batch file named batch.cmd, when you create a shortcut, the shortcut is. Not familiar with FireDaemon, and you may have already done this, but remember that the extension for shortcuts is not displayed by Windows. ![]() This is how I have currently set the buffer size and window size to what I need, but I cannot set the window position, for if I do set the window position then all 6 batch Jobs end up directly over one another. ![]() But then these default settings are applied to all future windows. If I open a command window I can set the default buffer size, window size and window position. I want to specify the position for each window so that it makes it easier for me to see exactly what each batch job is doing, without having to shuffle windows around on the screen. Currently when they are launched at the scheduled time the windows appear in a cascading order (overlapping one another). What I would like to do is include a parameter within these DOS Batch jobs to indicate the exact window position for each batch job. I have 6 DOS batch jobs that do many different tasks, these are set up to run as scheduled tasks and run from 6am to midnight every day, their in a constant loop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |