archive.worldofdragon.org

Hi all,

OK so I have xroard on Windows 10 64 bit it's in : G:\Emulate\xroar\xroar-1.7.3-w64

I can run xroar dragon32 and I get dragon 32 emulation.....

Reading the docs the xroar configs should be in %LOCALAPPDATA%\XRoar but that directory doesn't exist, so where are they ?

Is there a way to get xroar to tell me?

Cheers.

Phill.

If I remember correctly, if you type: In the Command Prompt, it should tell you where that is.

Most probably somewhere like C:\Users\Prime\AppData\Local\...

In my XRoar folder, there is a file named "xroar.conf" that contains as the very first line this:
rompath=:d:/XRoar/DOS-ROMs/ :d:/XRoar/ROMs/
I asume that this line was added by me at some point many time ago ...
I have the ROMs for Dragon/Coco in the two folders indicated in that rompath command.
cheers!

Phill, if all of the above fails then open a command prompt with admin rights and type:

g:
cd \
dir /a /s /p d*.rom

and wait. If nothing Dragon related shows up then change the above g: to c: and repeat the other two lines. Again, if nothing shows up then repeat with d: etc.

Running with -v 2 will show the actual path for each rom loaded, so in windows you'd run xroar.exe -C -v 2

(That's the case for the current version, 1.7 is long enough ago I can't remember if anything to do with that would have changed).

sixxie wrote: ↑Sun Feb 15, 2026 8:50 pm Running with -v 2 will show the actual path for each rom loaded, so in windows you'd run xroar.exe -C -v 2

(That's the case for the current version, 1.7 is long enough ago I can't remember if anything to do with that would have changed).

Eventually found it with :

xroar -C --config-print

And then checked along it's search path which lead me to : %USERPROFILE%"\Documents\Xroar\roms which is where my roms where.....

BTW is there any reason why windows *NEEDS* to have -C in addition to the flags? I'm presuming that -C is telling xroar to do something it only needs to do on windows? So why not do it automatically for flags that need it? Or at the very least tell the user that they might want it? As getting no feedback when you use (for example) --config print, makes the user wonder what they did wrong, or if the program is crashing badly?

Anyway thanks for the help everyone.

Cheers.

Phill.

prime wrote: ↑Sun Feb 15, 2026 11:11 pm BTW is there any reason why windows *NEEDS* to have -C in addition to the flags? I'm presuming that -C is telling xroar to do something it only needs to do on windows? So why not do it automatically for flags that need it? Or at the very least tell the user that they might want it? As getting no feedback when you use (for example) --config print, makes the user wonder what they did wrong, or if the program is crashing badly?

A good question! The actual answer is just the history of me finding stuff out. Windows doesn't do any of this by default as it treats command line apps and GUI apps completely differently. Long ago, SDL1 would do a bit of magic to get console output into special files (stdout.txt, stderr.txt).

Then under SDL2, it seemed the only way was to add the option to create a new console window - it had to be optional because you wouldn't normally want a second big text window opening up if you just double clicked the icon.

Then I was told you can actually try attaching to the console of the parent process (e.g. cmd.exe), so I changed it to try that first. But it's still guided by the option.

So what I should probably do is always try that parent attach, then if it fails, only create the console window if the option is specified. Then either way, redirect io.

I'll give it a shot for the next release...

..ciaran

I've pushed out a snapshot build here that might do the right thing: https://www.6809.org.uk/tmp/xroar/