Why do CTRL-SHIFT-0/9 and other key combinations not work?

You probably have another program outside of Eclipse that has already captured these keys or key combinations. A frequent problem is the Windows Input Methods Editor (IME) which is used to switch keyboard layouts. For example, if you are using multiple keyboard layouts, the CTRL-Space is mapped to allow you to cycle between the different keyboard regional layouts. You should probably be aware of how to turn the feature off since you're probably using this feature, but if you don't...

Windows 7

1. Within "Windows Control Panel", open "Region and Settings".
2. Select the "Keyboard and Languages" tab, select "Change Keyboards...".
3. In the "Text Services and Input Languages" windows, select "Advanced Key Settings".
4. In the "Hot Keys for input languages" list box, select "Between input languages" and then select "Change Key Sequence..."
5. In the "Change Key Sequence" window, choose another radio button other than the one next to CTRL+Shift. At best you choose "(None)".
6. Click OK until you closed all popup windows.

Windows 10

1. Open "Control Panel\Clock, Language, and Region\Language\Advanced settings.
2. Click "Change Language bar hot keys".
3. Set all key sequences to "(None)".
4. Click OK until you closed all popup windows.

Of course, this is Windows 7/10 and we know how Microsoft loves to change their layouts and names, but in fact, this option is available back to Windows XP.

Why is MADS the primary compiler?

When I started with WUDSN IDE, ATASM was the first supported compiler. The reason was simple: 90% of my sources are in ATASM format. ATASM is very comprehensive and fast. Its capabilities to define constants and byte sequences are very complete (".BYTE", ".WORD", ".DBYTE", ".FLOAT", ".SBYTE" for ATASCII, ".CBYTE" for terminated strings, separate offset for all constants). Over time additional platform compilers have been added and support for them will be completed step by step. When the support for MADS was rather complete, I found that it is the most powerful compiler I have ever seen and used. The support for ".PROC/.ENDPROC" has revolutionized the way I write assembler code now. It allows logical structuring and visibility control without any runtime overhead. At the same time, MADS is compatible with MAC/65 and XASM, and even ATASM sources can be adapted to MADS with a few minor changes described below. Therefore MADS is the primary compiler since WUDSN IDE version 1.6.0.

Why do I get the error "No ORG defined" when compiling the example from the tutorial?

Since WUDSN IDE version 1.6.0 MADS is the primary compiler that is registered for the file extensions ".asm" upon installation. You are trying to run the code example for version 1.5.0 or before, which is in ATASM format. Therefore you can either

• Convert the source t MADS format as described in How do I convert an ATASM source to MADS format? , this is the recommended way
• Open the source with the ATASM editor using "Open With..." in the context menu of the Project Explorer
• Change the default editor for the file extension ".asm" in the preferences for "File Associations" as described in the video tutorial Part 3: Setting up Editors and File Extensions correctly.

Why are the errors and warnings from an include file assigned to the main source file in the problems view?

You use a case-insensitive file system and have used different upper or lower case writing in the source include statement than in the actual file system. For example, you have written "ICL 'example.asm'" for a file named "Example.asm" on the file system. In Eclipse the file names of all resources are treated as case-sensitive, even if the underlying file system is case-insensitive. Therefore the file name issued by the compiler will not match the file name of the source include. As a fallback, the IDE assigns the error message to the main source file. To fix this, you have to adapt the spelling of the file name in the source include statement.

How do I convert an ATASM source to MADS format?

Because both ATASM's and MADS's syntax are based on the MAC/65 syntax. There are not really many differences. Therefore manual conversion using "Find/Replace (CTRL-F)" is very easy.

• Replace the origin definition "* = address" with "ORG address".
• Replace ".INCLUDE" with "ICL" for source includes.
• Replace ".INCBIN" with "INS" for binary includes.
• Replace "* = $2E0; .WORD address" with "RUN address" to specify the run address.
• Replace "* = $2E2; .WORD address" with "INI address" to specify the init address.
• Check the quotes of ".BYTE" and "DTA" statements. In MADS, single quotes result in ASCII codes, double quotes in ATARI screen codes.
• Remove all ".BANK" statements. While ATASM sorts and merges all segments within one bank statement, MADS simply uses the order of segments as defined in the source file. Every "ORG" statement automatically generates a new file segment.

How does ATASM generate segments in executable files?

A helpful feature for small projects is that by default ATASM sorts the segments by address and warns if the same address is overwritten by code or data. Since version 1.05 the ".BANK" directive is available, which allows you to create COM files with "INITAD" segments and arbitrary segment counts. If you don't use the ".BANK" directive, ATASM will sort the segments by their address and will put consecutive blocks into a single segment by default. While this saves some bytes, it might be confusing if you are used to other assemblers. Note that you have to use the ".SET 6" directive to set the assembler origin offset in every bank if you use it in one of the banks.

How do I compile into ROM images?

Plain ROM Images do not have header bytes by default, or at least they do not have the same header bytes as executable files. In order to create raw object files without headers, compiler-specific options have to be used. Some cases are listed below. See the manual of the specific compiler for more details.

• ACME: Use the compiler parameter " -f plain " instead of "-f cbm" (default) to switch to "plain" mode without a header
• ATASM: Extend the compiler parameter "-o${outputFilePath}" to " -r -o${outputFilePath}" to switch to "raw" mode without header
• MADS: Use " OPT h-f+ " at the very beginning of the source file to disable the COM header and enable "fill" mode, i.e. no segments are created if there are gaps in the object code

How do I compile into disk images?

Atari 8-bit

For Atari 8-bit, the ATASM compiler has a dedicated parameter to write the executable file directly into ".ATR" or ".XFD" disk images. The disk image must be formatted with Atari DOS 2.0S, Atari DOS DOS 2.5, or a compatible DOS. All Atari 8-bit disk formats can be created using the "dir2atr.exe" tool of the AtariSIO tools by Matthias Reichl (hias). The tool can create a complete disk image with arbitrary DOS (Atari DOS 2.5, MyDos, SpartaDOS) and size based on a folder that contains "DOS.SYS", "DUP.SYS" (or the equivalent files of the respective DOS) and all other files requires. I have packaged an example including the "dir2atr" tool, a batch script to call the tool and the emulator, and the "files" folder in this archive. Unpack the archive to your output folder. Double-click "makefile.bat" to see how the disk image is created and started. Read section How to run a makefile script instead of an emulator? for the details on how to configure the call to "makefile.bat". For productive usage, you should of course put the "hias" folder into a central location and use the most recent version from hias' website. For MacOS X users, the download also contains a "makefile.sh" script and MacOS X binaries of Matthias Reichl's tools. The binaries have been provided by Fredrick Holst (freetz) and you can find the latest versions on his website.

Apple II

For Apple II, WUDSN IDE automatically generates a bootable AppleDos 3.3 disk image with the extension ".dsk" if one of the predefined emulators is used for execution. If you want to use another DOS or disk size or if you want to put more files onto the disk after compilation, you can use the command line version of AppleCommander to achieve this. Create a makefile script and configured it as described in How to run a makefile script instead of an emulator?. In the case of Apple Disk images always remember to use the correct file content/load/run address. The IDE needs to know the load address of an executable file in order to store this information in the directory entry. To detect the load address from the executable file, the IDE evaluates the file extension. Supported extensions are ".b", ".prg" and ".xex". Here's the logic for the built-in disk image creation:

• File extension ".b"
  // AppleDos 3.3 binary file: start-lo,start-hi,length-lo,length-hi,data
  address = getWord(outputFileContent, 0);length = length - 4;content = getData(outputFileContent, 4);
• File extension ".prg" and length > 2
  // C64 program file: start-lo,start-hi,data
  address = getWord(outputFileContent, 0);length = length - 2;content = getData(outputFileContent, 2);
• File extension ".xex" and length > 6 and (getWord(outputFileContent, 0) & 0xffff) == 0xffff)
  // AtariDOS 2.5 binary file:$ff,$ff,start-lo,start-hi,end-lo,end-hi,data
  address = getWord(outputFileContent, 2);length = length - 6;content = getData(outputFileContent, 6);

Other hardwares

If you find a tool similar to "dir2atr.exe" for the Atari 8-bit or "AppleCommander" for the Apple II, you can use create your own script and run it as described in How to run a makefile script instead of an emulator?.

How can I run a makefile or script instead of an emulator?

Sometimes it is useful to run a makefile script instead of the emulator, for example, if the output file shall be combined with other files into a single ATR file. To execute such a script select "User Defined Application" as the "Default Application to open Output File". Specify the path to the shell as "Path to Application". On the command line, you can then use the standard variables to start the shell, pass the name of the script and pass the file path of the compiled output file. Since the working directory at the time of execution is the output folder of the compiler you must place the script file there or you must specify the script file with its absolute path. If you are using Windows and "cmd.exe" as your shell, you must specify "/c" before the name of the script to prevent "cmd.exe" from remaining as a process after the script has finished. The resulting command line is "${runnerExecutablePath} /c makefile.bat ${outputFilePath}", assuming "makefile.bat" is located in the output folder". See section How do I compile into disk images? for the description of how to use this for compiling complete disk images.

How can I use other emulators?

You can "re-use" the existing tabs and simply specify another emulator's executable. If you use "User Defined Application", you can specify whatever you want. When using "User Defined Application", no disk image is created or updated. You can use this setting to have your own script which puts the executable file onto a disk image of your choice using additional tools like "dir2atr.exe" or "AppleCommander" for example.