diff --git a/com.wudsn.ide.lng/help/7800.8bitdev.org/index.html b/com.wudsn.ide.lng/help/7800.8bitdev.org/index.html index 6f10d11a..cfdd1ae1 100644 --- a/com.wudsn.ide.lng/help/7800.8bitdev.org/index.html +++ b/com.wudsn.ide.lng/help/7800.8bitdev.org/index.html @@ -12,27 +12,27 @@

You can begin by checking out one of the links presented in the next section, or you may use the wiki search function to quickly find information on a specific topic.

Wiki Sections

-
The 7800 Software Guide
+
The 7800 Software Guide
An updated version of the documentation originally produced by Atari and GCC. Several inaccuracies have been discovered and corrected, and new sections have been added.
-
The 7800 Minnie sound chip
+
The 7800 Minnie sound chip
An overview of GCC's innovative sound chip that was going to be used as the 7800 in-cart sound solution.
-
7800AsmDevKit
+
7800AsmDevKit
A quick way to get started with programming the 7800 using assembly language. All the tools you need to create a game, cross-platform and available for multiple OSes. 7800.8bitdev.org is the official home of the 7800AsmDevKit.
-
7800basic
+
7800basic
A quick way to get started with programming the 7800 using a higher level language. 7800basic is a compiled language, designed for efficiency. 7800.8bitdev.org is the official home of 7800basic.
-
7800 Tutorials and Guides
+
7800 Tutorials and Guides
Covers more advanced 7800 topics.
-
Emulators and Tools
+
Emulators and Tools
Covers information on tools useful to the 7800 developer.
diff --git a/com.wudsn.ide.lng/help/ide-credits.section.html b/com.wudsn.ide.lng/help/ide-credits.section.html index c4424d9b..e11c4bd9 100644 --- a/com.wudsn.ide.lng/help/ide-credits.section.html +++ b/com.wudsn.ide.lng/help/ide-credits.section.html @@ -18,7 +18,7 @@ Matthew Dillon, Olaf Seibert (Rhialto), Andrew Davie, Peter H. Froehlich (pfh), the DASM team -KickAss +KickAss Mads Nielsen (Slammer) @@ -48,7 +48,7 @@ Piotr Fusik (fox) -Grafx2 +Grafx2 Adrien Destugues (PulkoMandy), Yves Rizoud (yrizoud) @@ -60,7 +60,7 @@ Contributor -ASAP +ASAP Piotr Fusik (fox) @@ -74,7 +74,7 @@ Contributor -AppleCommander +AppleCommander Robert Greene (robgreene) @@ -90,11 +90,11 @@ Nick Westgate (sicklittlemonkey) -Altirra (Atari 8-bit) +Altirra (Atari 8-bit) Avery Lee (phaeron) -Atari800Win (Atari 8-bit) +Atari800Win (Atari 8-bit) Marcin Lewandowski (jaskier) @@ -102,7 +102,7 @@ Håkan Sundell (phs) -JACE (Apple II) +JACE (Apple II) Brendan Robert (BLuRry) @@ -132,15 +132,15 @@ Mozilla Foundation -Eclipse Hex Editor Plugin (used as inspiration) +Eclipse Hex Editor Plugin (used as inspiration) Marcel Palko (randallco) -Java Hex Editor & Plugin +Java Hex Editor & Plugin Pordi Estaqual (pestatije) -Java Expression Language Parser +

Why is WUDSN IDE not available via the update site?

-

You likely typed in the wrong update site URL, for example, using "wusdn" instead of "wudsn". The correct URL is "http://www.wudsn.com/update". In addition, you should uncheck the checkbox "Hide items that are already installed" to see what is there. See the "Installing WUDSN IDE" section for the required steps on the " Installation " tab.

+

You likely typed in the wrong update site URL, for example, using "wusdn" instead of "wudsn". The correct URL is "https://www.wudsn.com/update". In addition, you should uncheck the checkbox "Hide items that are already installed" to see what is there. See the "Installing WUDSN IDE" section for the required steps on the " Installation " tab.

Installation dialog with update site

Why do I get "Unable to read repository at ... Read timed out" when accessing the update site?

@@ -85,7 +85,7 @@

Why is the "Assembler" section not visible in the preferences?

-

If the WUDSN IDE sections and features are not visible after a successful installation, you probably use an outdated Java version. For example, Java 1.6 has been out of maintenance since 2013/02. This seems to be a common problem on Mac OS X, even in Mavericks (10.9), which still uses Java 1.6 by default. Ensure you have at least the Java version mentioned in the installation section for the IDE installed and that Eclipse has started using that version.

+

If the WUDSN IDE sections and features are not visible after a successful installation, you probably use an outdated Java version. For example, Java 1.6 has been out of maintenance since 2013/02. This seems to be a common problem on Mac OS X, even in Mavericks (10.9), which still uses Java 1.6 by default. Ensure you have at least the Java version mentioned in the installation section for the IDE installed and that Eclipse has started using that version.

How do I select the translation for the menus and messages?

@@ -98,7 +98,7 @@

How do I associate my source file extensions with the correct editor?

-

The IDE supports many compilers and provides specialized editors. Typically, you have some preferred source file extension (".asm" or ".a") and a preferred compiler. The procedure to associate the file extension with the editor via the preferences is described in this video tutorial WUDSN IDE Tutorial 3: Setting up Editors and File Extensions correctly.

+

The IDE supports many compilers and provides specialized editors. Typically, you have some preferred source file extension (".asm" or ".a") and a preferred compiler. The procedure to associate the file extension with the editor via the preferences is described in this video tutorial WUDSN IDE Tutorial 3: Setting up Editors and File Extensions correctly.

Why must I put ";@com.wudsn.ide.lng.hardware=..." in the source file?

@@ -167,7 +167,7 @@ Alternatively you can configure "Option-Space" instead via the "General/Keys/Con
@@ -205,7 +205,7 @@ Alternatively you can configure "Option-Space" instead via the "General/Keys/Con

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, 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 command line 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 command line tool and emulator, and this archive's "files" folder. Unpack the archive to your output folder. Double-click "makefile.bat" to see how the disk image is created and started. Read the section "How to run a makefile script instead of an emulator?" for the details on configuring the call to "makefile.bat". For productive usage, you should put the "hias" folder into a central location and use the most recent version from Matthias Reichl's 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.

+

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, 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 command line 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 command line tool and emulator, and this archive's "files" folder. Unpack the archive to your output folder. Double-click "makefile.bat" to see how the disk image is created and started. Read the section "How to run a makefile script instead of an emulator?" for the details on configuring the call to "makefile.bat". For productive usage, you should put the "hias" folder into a central location and use the most recent version from Matthias Reichl's 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're going to put more files onto the disk after compilation, you can use the command line version of AppleCommander to achieve this. Create and configure a makefile script 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 to store this information in the directory entry. The IDE evaluates the file extension to detect the load address from the executable file. Supported extensions are ".b", ".prg," and ".xex". Here's the logic for the built-in disk image creation: