Any way to flash the DAM file to the Choosatron?


I presume you mean 64Gb ?

I’m only using a 4Gb, so I can’t say whether that’s the problem. It may well be that the Choosatron can only read 32Gb cards max. If you have a smaller card, I’d suggest you try that first.

Secondly, I hold down the ‘2’ button until I see ‘Press any button to start!’. At that point I know the Choosatron has booted fully and is ready to play a story. I make sure I press the button before I plug the power in.

Try the following file. It’s the Cinderella story I wrote a while back. It works fine on my Choosatron.



Thanks Rodney for the quick reply.

It actually is only a 64MB card, it’s just the first one I could lay my hands on around the house. Think it came from a camera about 10 years ago! Although maybe the issue is the size, just a case of it’s too small to be noticed rather than too big!

I do have a 4GB card so I will format that and try it out with both my story and yours.

In relation to booting the Choosatron that’s exactly how I did it (hold down the “2” key, plug power, wait for the “Press any key” message). As soon as I release the “2” button though, the usual story options appear.

As I said I’ll try with my 4GB card and your working story and report back in half an hour or so



Hi again, reporting back to say it was indeed the 64MB SD card that seems to have been the problem. I put the stories on a 4GB card and it happily loaded stories up when I held down the “2” button on boot.

My kids are going to lose their sh*t (pardon the expression!) when I tell them they can now put their own stories on the Choosatron :smile:

Thanks for the advice!


Hi Tim,

I’m glad that you got it working. It’s odd that a small card wouldn’t work. Usually SD readers have upper limits, not lower ones. You might try formatting it again, with a different cluster size (if available). Funnily enough, given the size of the .dam files, a 64MB card would hold quite a few stories.

Hopefully there will be a fix for the non working appended passages soon. I would really like to test my long story out on the Choosatron (70 passages and about 30% of the way through, with 8 endings so far).

If you have any stories, I’m sure we’d all like to read them. As for your children, I understand. I lost my marbles years ago, and never recovered them ! :stuck_out_tongue:

Have a great Easter.


Cheers Rodney

I will try experimenting with the smaller SD cards (I turned up a 256MB one as well!). I initially thought the 64MB would be perfect for holding a load of stories, I think I’ll be hard-pressed to fill up a 4GB one!

The current stories I just loaded onto the Choosatron are very far from complete, it was really just to reassure myself that I would be able to get them on there without too much hassle, before committing the time to really flesh them out.

Can see lots of potential for the variable setting/testing features, but it seemed a little flaky on the Choosatron. Most likely due to errors in my story authoring though. I also hope to make use of the append feature, so like you hope to hear of that being resolved soon.

And I will definitely share any stories I manage to complete! For Verison 0.1 of the software I’m pretty impressed with what can be done with it already. (Thanks Jerry!)

Have a great Easter yourself.



Of the two versions of Write I’ve compiled, I’m unable to have the Dev version generate the .dam file, whilst the normal version will (no idea why, I haven’t touched the code).

I haven’t played with the variables just yet. It’s something I want to do, but I wanted to test out a long story first. The software has issues I haven’t put on the bug tracker yet. Mostly if you notice it slowing down, exit back to the list of stories and go back in again. If it freezes for a fair few seconds, I can guarantee it hasn’t saved the last passage you’ve probably just written.

I’ve taken to writing the passages in Notepad and copy/pasting them into the passage windows. I’d also suggest using a grid reference system in order to track where your links come from and go to. I guess it all depends on how you write your stories. If you write all the way down one thread before back tracking to write down another or write each thread one step at a time.


The Python scripts ONLY work on source files exported from Twine. It has no understanding of the JSON format from the new writing software. It is simply a legacy solution to create binaries from Twine. :confused:


Honestly, to me it sounds like a bad card! Make sure it is FULLY formatted. No extra little files hanging around.

There is a hard limit of 20 stories on the Choosatron (after it reads in the first 20 available on an SD card it will stop looking, and internal memory it won’t let you put on more than that).

That can be very large stories however! Especially as new features are added like image support.


I figured that out. Once I realised the .dam file could be copied directly to the microSD, I was happy.

That’s plenty. Especially if the stories are large ones, with a lot of passages. I’ve written around 80 passages in my most recent one, which is around 35% complete. Hopefully over the next few weeks I’ll finish it off. I want to write around 10 passages a day, although sometimes… The creative juices just don’t flow very well.

Thanks for your help.


@Rodneyn, it sounds like the autosave feature on the app may be causing your problems (the slowdown issue.) It would still be great to have an issue filed for it, but in the meantime, to keep your headaches to a minimum, you may want to try editing your profile and disabling auto-save. You’ll have to manually hit the save icon, but it won’t drag down the app like it is for you now.


Hey Rodney. I believe I’ve got the fix in for the append issue on Choosatron binaries (only binaries at the moment). Try exporting again (from the main branch) and see how it goes!


@spleenboy, I will as soon as I know what steps I can do to reproduce it each time. It happens regularly, but I’m not paying attention to the actual steps and cause. I agree with the auto save being the culprit, because there are times the app won’t save the last passage, when it gets to that point. I’d guess it’s dropping into some sort of loop that’s not exiting properly.

@jerrytron, I’ll build another version soon and test it out. Thanks :slight_smile: I’m up to 100 passages on my 230+ passage epic. I can’t wait to finish it and let people read it (bring lots of paper).

Edit: It doesn’t work. I updated the files from the master branch, rebuilt the app, installed it, imported the story and exported it to a dam file (I love the name), stuck on the microSD and same thing. The story ends right at the end of the first passage. The appended passage never gets printed.


Ok! @Rodneyn and @spleenboy: I have a real fix in. First, I fixed the issue on the dev branch keeping exporting from working. Was a simple error where a variable had it’s old name.

Second, the binary creation now properly checks for append, ending, or choices. If it’s append, it populates the choices with the single appropriate link as well as setting the append flag. I’ve tested this on a Choosatron and it works!

Since dev branch is able to export again, I’ll be focusing my changes there until we organize things a bit more.

Finally, I notice @Rodneyn that you immediately have a fun rhyme that carefully makes sure to stay within the 32 character line limit while printing. Congrats! You found a firmware bug. Word wrapping breaks if a line has 32 characters followed by a newline (a special case where it needs to be treated similarly to a space).


@jerrytron, it works ! That’s awesome. I am curious, is the appended passage meant to ask to continue or just print out ? I know some of the built in stories have a ‘Press any button to continue’ when some passages are too long.
I don’t mind either way, but I think the ‘continue’ option would stop people from thinking there is too much to read.

As for the bug… Woohoo ! The rhyme wasn’t set to fit into a special size. I just wrote it out and that’s how it ended up. It’s good to see it picked up early on though, but then that’s one more thing to fix…

The ‘save’ bug I’ve posted may not be related to saving after all. I’ve turned autosave off, and added around 12 passages last night, but towards the end the app virtually stopped. When it slowed to taking 15 seconds per character to display, I tried to save and the app…stopped part way through saving (with the button stuck in a ghosted state). It didn’t save the last passage when I reloaded the app and the story.

I might PM you my story @jerrytron, so you can see how slow it is with 127 passages.

I’ll also update the build thread with the most recent dev build.


Yay! Yeah, I want to implement a feature for continues, or even to automatically insert them. Append is meant to be seamless. Maybe we add a continue options alongside append? So you pick? Either seamless, or a way to break things up. Hmm…


Would a check box work ? On the append passage page (or on the main page where the appended passage shows as a link) have a check box: Force Button Press to Continue ?

That would mean an additional flag / condition to check for, rather than a whole new passage type.

It’s not a priority at the moment, I don’t have too many appended passages (about 6 I believe in total). I’ll add it to the bug tracker / feature request.


This can definitely be done. It wouldn’t be extra work on the parser since internally we’d just make a single choice with a bit of default “1. Continue” type text. I was even thinking having a gentle warning when there is a lot of copy in a passage, or even allow an inline continue tag so you aren’t creating extra passage just for the sake of breaking it up. Good stuff to think about!


After getting the fix in to the source. I ended up changing the passage from an append to a normal passage and just linked it via a continue option anyway (it was a ‘Duh’ moment). It seems to work for my purpose. However, it would be nice to have still.

I uploaded a feature request the other day, with a mock photo of how I think it would look.

I also think the issue with the slowdown has to do with the stack being over run. I’ll post another bug, but watching the app using Google’s Chrome Apps & Extensions Developer Tools, it shows a fair few minor issues.


I saw! Thanks for going to the expect as to a quick visual mockup. :slight_smile: Yeah, the slowdown thing is a major issue. This last week was a mess, but after today will calm down. I’ll be finally diving back in so I can debug slowdown issues, and test / finish up setup coding.


Awesome news. I’ve taken to writing all my passages in a text file, so I can continue writing. At 186 passages, the app is getting a lot harder to use (at least I know it’s limitations).

I am getting somewhat stuck, having written 190+ different passages in a dungeon. I was hoping to have finished by now, but work and other generic life issues have gotten in the way. Hopefully the next 25-30 passages won’t take more than a week or so to finish.