dukdukgoos

I took a look at Github and it seems like maybe this has been fixed a few days ago, but maybe not released yet: https://github.com/wudsn/wudsn-ide/commit/6520f1e27af721dbcfb246cd9901268867b6f8ad

@JAC! Getting the following error when compiling anything. Fresh manual install with Eclipse 2023-12, Temurin Java 21.0.1+12, WUDSN 1.7.2.202401300233 from "daily" repo java.lang.Error: Unresolved compilation problem: Invalid escape sequence (valid ones are \b \t \n \f \r \" \' \\ ) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommand.splitAtSpaces(LanguageEditorCompileCommand.java:199) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommand.executeInternal(LanguageEditorCompileCommand.java:303) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommand.execute(LanguageEditorCompileCommand.java:165) at com.wudsn.ide.lng.editor.LanguageEditorCompileCommandHandler.execute(LanguageEditorCompileCommandHandler.java:55) at com.wudsn.ide.lng.editor.LanguageEditorFilesCommandHandler.execute(LanguageEditorFilesCommandHandler.java:64) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:99) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:298) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:232) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:174) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:488) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:485) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4273) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4071) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3659) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:342) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:648) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:342) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:651) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:588) at org.eclipse.equinox.launcher.Main.run(Main.java:1459)

Just a friendly bump to see if there's anything new planned for this app. It's quite useful and a shame it hasn't seen much activity lately...

I noticed something today when doing some reconfiguring of my emulators: WUDSN doesn't seem to be able to find any emulators unless the full path is configured in the settings dialog, even if the emulator is part of the system PATH. So for example, I changed the Stella config in preferences from: C:\Programs\Emulators\Stella\Stella.exe to stella I have my Stella folder added to the system PATH so I can access Stella directly in the command line with just "stella" but WUDSN won't see it unless it has the full path to the executable. It's weird because the compilers work fine if they're in the system PATH (EDIT: compilers don't work either), but the emulators don't. Any ideas? EDIT: compilers don't work with only the executable name either, so it appears WUDSN or Eclipse isn't using the system path when executing a command.

As it sounds like this is useful information to retain, for now I'm just going to manually remove the lines from the DAT I use in RomVault. Maybe the RomVault developer will update his parser at some point. We also might consider changing the DAT format to the XML-based one. Not sure if this would fix the issue with RomVault, but it's probably better in any case to use XML if you're tracking rich data in the file (more extensible, flexible data structures, easier for other tools to parse/use the data, etc.)

Yeah, I agree it should ignore unexpected tags, but as the ClrMamePro DAT format is non-standard it has to have a custom parser written, and I guess he just followed the spec verbatim. Most DAT files I see these days are in XML format, which is super easy to parse with standard tools. RomVault is a GREAT rom manager though, nothing else comes close imo... except for this issue What are the custom tags used for in this case? Something on the a8p site?

Confirmed with the ROMVault dev that custom tags are not supported. I found the file format definition for ClrMamePro-style DATs here: http://www.logiqx.com/DatFAQs/CMPro.php

This new DAT crashes ROMVault when updated. Is it because of the "a8p" datapoints that have been added to every game?

I was affected by this (I imagine everyone on Windows with an extra keyboard installed would be) I remapped to Ctrl-Shift-8 and -9 (just moved everything down one key to avoid 0) What I did worked fine if you want to keep it pretty close to how it was before. I'd be fine with the F11/Ctrl-F11 as it's Eclipse standard too

New installer didn't work for me on Windows. Here's the relevant error lines: Unpacking wudsn-ide-tools-main.zip to C:\Programs\WUDSN\Install. wudsn-ide-tools-main/ASM/DASM/test/cmdline_defs/declare_var_mac.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\cmdline_defs\\declare_var_mac.asm' wudsn-ide-tools-main/ASM/DASM/test/delete_empty_binary.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\delete_empty_binary.asm' wudsn-ide-tools-main/ASM/DASM/test/m_switch_2.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\m_switch_2.asm' wudsn-ide-tools-main/ASM/DASM/test/m_switch_3.asm: Can't create '\\\\?\\C:\\Programs\\WUDSN\\Install\\wudsn-ide-tools-main\\ASM\\DASM\\test\\m_switch_3.asm' tar: Error exit delayed from previous errors. Copying files to C:\Programs\WUDSN\Tools. 1918 File(s) copied Removing folder wudsn-ide-tools-main. Installing Eclipse. Downloading eclipse-platform-4.19-win32-x86_64.zip from https://www.wudsn.com/productions/java/ide/downloads/eclipse-platform-4.19-win32-x86_64.zip. Unpacking eclipse-platform-4.19-win32-x86_64.zip to C:\Programs\WUDSN\Tools\IDE\Eclipse. tar: Error opening archive: Unrecognized archive format Looks like there's some corruption at the beginning of the paths and it's trying to use tar for zip files

Great, thanks! It looks like you already had the zipped DAT on your server (35382958_Atari8bitPreservedSoftware2022-09-10.zip) so you don't need mine if you want to delete it

Yes, that's exactly the process I had in mind, as it ensures all renames and deletes are handled by the DAT and don't need to be included in the update pack. I went ahead and made an update pack for the current release. Comes in at a much slimmer 102mb. Could be helpful for those who haven't already got the full pack. Optimally the update packs would be posted and archived on the archive sites (https://atari-cellar.net/ and https://atari8bit.net/) along with the full releases. 1210149540_Atari8bitPreservedSoftware2022-09-10UPDATE.zip Atari 8bit Preserved Software 2022-09-10.zip

Do you think we could get an "update pack" when a new release is made? That is, a zip with only the new and changed files plus the DAT for the new release (which is already available now). This would allow us to update to the latest version using ClrMamePro or other ROM managers to process the previous release plus the update pack to make the new release while saving bandwidth by avoiding redownloading the whole thing again. Files that were only renamed or deleted between releases would be handled by the ROM manager with the DAT file without needed additional space in the update pack. Atari files are small so it's not a huge deal to download the whole thing every time, but doing things efficiently is always good, and if we start adding more cassette WAVs or raw Kyroflux images the releases could get much bigger in a hurry.

Maybe this has been asked and answered already, but is there a DAT available for this collection?

That's exactly the stuff I'm interested in though... the conversion of a 2600 kernel to 8-bit. I assume the 8-bit version is still a kernel, "racing the beam" style? Alternately if you know of any examples of other 2600 kernel to 8-bit conversions that helped you learn how to do it I'd be interested in seeing those.

I'd love to see the source for this!

i guessing that maybe you were trying to assemble the C64 example file with MADS instead of KickAss assembler. You have to manually open the C64 file with the KickAss editor to get the normal assemble and run buttons to work correctly. The other example files are all MADS compatible, so they work with the default settings for .ASM files Unfortunately due to a change in Eclipse you have to manually open files that need a non-default editor every time. In the past it would remember the preferred editor for each file, but no longer with the latest versions of Eclipse.

Computereyes v1.1 (1985)(Digital Vision)(US)[disk].zip doesn't match the DAT file for the archive. DAT files says there is supposed to be a "side b" image also in the ZIP. game ( name "Computereyes v1.1 (1985)(Digital Vision)(US)[disk]" description "Computereyes v1.1 (1985)(Digital Vision)(US)[disk]" rom ( name "Computereyes v1.1 (1985)(Digital Vision)(US)(Side A)[BASIC].atx" size 100208 crc 592766ef md5 1d228d579fa804cfc99251f3176cca1c sha1 0645e4c967bfeaa3ecc0a67381b539f027b46fd8 ) rom ( name "Computereyes v1.1 (1985)(Digital Vision)(US)(Side B)(Graphics 9)[BASIC].atx" size 100208 crc 5b4d7dbd md5 092393b7b76b29975f213edca9867178 sha1 640829966a75306d4b3f0d84a6c384a588c8ada3 ) )

Nevermind, I found it. Thanks again for all the hard work in putting this together

Thank you!! Is there a new DAT file for this release?

Wow, great, DATs make everything sooo much cleaner and easier! And on that note, I can see a problem with the last release that I caught by looking at the DAT: The Academy on Computers ROM is messed up because it has a "/" in the ROM name. It's changed to a "-" in the zip file name but the structure inside the zip is messed up because the ROM manager translates the "/" into a new directory. For the next build consider changing all those "/" to "-" or some other innocuous character. game ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)[cassette]" description "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)[cassette]" rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 1 of 5 Side A)(Lesson 1)[CLOAD+RUN][BASIC].cas" size 11640 crc 64335414 md5 c8544e07c0618367c9d3c10358cf6aca sha1 aaf8af105c6e0b6d270b835154b6f97f11b05ac6 ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 1 of 5 Side B)(Lesson 2)[CLOAD+RUN][BASIC].cas" size 11212 crc 7ff83f79 md5 f4cee5378617d93b966dd40a794834a4 sha1 b3dd02c4278d6db8f797cef121d3df462a963516 ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 2 of 5 Side A)(Lesson 3)[CLOAD+RUN][BASIC].cas" size 11503 crc 1f7b3959 md5 dfa08bd20f1ddc6c72e6e3c33674ef47 sha1 c2066d313050148121624a0790d71820f1021963 ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 2 of 5 Side B)(Lesson 4)[CLOAD+RUN][BASIC].cas" size 11216 crc d192f7a1 md5 c5ddcb6c876a45c2d40bdce2a85c8fee sha1 dd6356cd3287d8d2f1b196c121d9496aef9c33f4 ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 3 of 5 Side A)(Lesson 5)[CLOAD+RUN][BASIC].cas" size 11773 crc cd745548 md5 c4c173e55ff76dd6429de61a50cc94f4 sha1 5e29477a6c990bb4ce5d6b0bf8496895f148029e ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 3 of 5 Side B)(Lesson 6)[CLOAD+RUN][BASIC].cas" size 11353 crc 6c780b22 md5 126b6bfdd2dc7d8e72b4e82f30f8d192 sha1 45ddeb17b3573a986a6c90ddf9ff133e44bf80a9 ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 4 of 5 Side A)(Lesson 7)[CLOAD+RUN][BASIC].cas" size 11071 crc 1aa7aa29 md5 7cbbbee82dd72a5b90d1c262f19cc988 sha1 eff28ed3c5c563d666c1693ac67d4d90d1f6756f ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 4 of 5 Side B)(Lesson 8)[CLOAD+RUN][BASIC].cas" size 11347 crc 12da099f md5 2e4e2614384701e22e8b9485608f0ad7 sha1 9b38abf545769c4cf3ead0a5448bffba292d633d ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 5 of 5 Side A)(Lesson 9)[CLOAD+RUN][BASIC].cas" size 11496 crc b9fde969 md5 052159fc7263218717ff99073efe3c38 sha1 b841be5e2a9b7caddb9187bf6dbaf6b78c00c560 ) rom ( name "Academy on Computers - Atari Self-Tests AT1.1.1 (1983)(WNET/THIRTEEN)(US)(Tape 5 of 5 Side B)(Lesson 10)[CLOAD+RUN][BASIC].cas" size 10929 crc e09c45f8 md5 e3afa7b3532c2ffec23b83c9dc110e69 sha1 ea3381ba14e8faccd37b03db4bf7b45fbfd03002 ) )

I don't want to update Eclipse past 2020-09 because of the file extension/editor regression, so should I stay at 1.7.1? I could try updating to 1.7.2 as it's likely it works with 2020-09, but if you know it doesn't I won't try.

According to the developer update on that bug report it looks like it's intentional and they won't be fixing it. It seems like "Open with... Other" will do basically the same thing? I'm unclear as it whether it still remembers the setting per file or only by filename or ext. If it's the latter then that's a drag, as lots of files with the same name or extension need to open in different editors.

Glad to hear you're doing fine and healthy!

Has anyone heard anything from JAC recently? It's been a while and with covid going around it's a bit worrying...