archive.worldofdragon.org

Unfortunately the last xroar-gtk I have access to is version 0.31, not the 0.31.1 or the latest snapshot. Is there any chance for you to add this version whith every update? I would really appreciate it. The GTK+ versions and latest snapshots are available from the XRoar temporary directory . I und...

zephyr wrote:This problem is caused by a bug in the original Dragon 32 and 64 BASIC ROMs.

You're right, I should have corrected the post.

I don't mind waiting for the 30 seconds or less that it takes to load most source code from cassette. I dont even mind waiting for the 4 to 5 minutes that it takes to load some of the biggest games from cassette. :) You're a masochist! When I wanted to play a quick game of something the ten minute ...

Regarding the Dragon 64 producing monochrome output. You state that you obtained it in 1988, if it is second-hand it could be that the previous owner modified it to produce a clearer video signal. It's a relatively simple procedure that was mentioned in an issue of Dragon User (though I cannot reme...

I assume that I'm okay to use the 32 power brick to power the 64 ? just not the actual board inside for my 32 ? The external power bricks are fine, it's the internal power boards that cannot be swapped between 32s and 64s. Regarding the Dragon 64 producing monochrome output. You state that you obta...

Re. memory areas, Graham E. Kinns collected a lot of information which is available at his site. Detailed Memory Map, Dragon DOS Information, and possibly Dragon 64 Differences are most likely to be of interest to you.

A word of warning. Do not swap power boards between Dragon 32s and 64s, should you be thinking of swapping them around for testing purposes, because their outputs differ (+12V, 0V, & -5V on a Dragon 32, and +12V, 0V, & -12V on a Dragon 64).

Just a note that nowhere in the manual does it mention that the extra ROM for the Dragon 200-E should have the name "d200e_26.rom".

Try recording in mono only and switch off all instances of automatic volume boost that may be in the recording train. Also, if possible, use line-in rather than a microphone socket on your recording computer.

sixxie wrote:Edit: ok, added a timeout (1.5 * the buffer length). If for some reason the audio callback fails to fire, there should just be a small glitch and the emulator will carry on. Let me know if that helps.

Thanks, snap-2013-49459-w32 seems to have fixed the problem.