archive.worldofdragon.org

Well, I go download those roms from your archive, and first of all, they come on weird extensions:
The 1st ROM comes with an ic37 extension
The 2nd ROM comes with an ic34 extension
The external generator comes with an ic1 extension
So, I rename them in a way that makes xroar happy, I go run it, select the 200E in the options... aaaaaaand it doesn't boot.
Instead I get this error screen: I tried changing the extensions of the files to rom, creating a conf file to specify the roms manually, but still nothing.
Kinda ironic that nobody complained about this until now tbh.
Maybe I am overlooking something obvious?
If anyone can help me it would be really neat.
PD:Yes, I tried renaming the external generator rom to something xroar couldn't detect, but it gave me a different error screen instead, the one with all the @ symbols.

I think either you or I have them the wrong way around. This is what XRoar thinks:

d200e_1 ic18_v1.4e.ic34 (32K BASIC)
d200e_2 ic17_v1.4e.ic37 (64K BASIC)

Tried changing that, and it does boot up, I can use the character set for things like Ñs and stuff. One thing I can't figure out is how to do lowercase... The manual says to press SHIFT+0, but I tried that and it just prints out its respective symbol. I also can't seem to do accents.

I tried it on XRoar 0.32 on MacOS and Dragon 64 switches to inverse video, while 200E prints the ç character and doesn't switch to lowercase.

Indeed - it's changed in the 200E ROM. Shift+Enter is capslock instead.

You're absolutely right, thanks!

By the way, what would be the way to use the accented letters and math symbols?

I think some in the charset you can't type, some are just shifted other keys. To put an acute accent over a supported letter, the ROM traps shift+7 as a dead key that then accents the next character. Lowercase only, I think. It also doesn't let you type anything other than an accepted character, which is a bit annoying

Something interesting I found is that while in the lowercase mode, if you type ?mem it gives ya a result of 0, when it should give ya the rough amount of memory you have available.
This is true in 32K mode: And in 64K mode: I thought it would just give ya a syntax error, because I tried running EXEC on lowercase and it gave me that exact error.

That's actually pretty cool - unlike the "stock" BASIC, it seems you can use lowercase as distinct variables...

Huh. I didn't knew that. Looks like Eurohard made some tweaks to this version of BASIC, beyond just adding the character set.