SD card creation made easy

...AIUI the image is written to the blank file in the sd create dir. Copied that, renamed it to blank.img…

IIRC SDCreate aks you to specify where to save the image file.

Somehow not working… Windows now claims that the card isn’t formated and contains 0 Kb…

Have you tried formatting the card under Windows before writing the image to it?

IIRC SDCreate aks you to specify where to save the image file.

That’s what puzzled me too. Clicking on the save options just closes the menu, nothing more.

Have you tried formatting the card under Windows before writing the image to it?

First time I used it without formating it, just deleting the old files (came out of an old phone). Second time I tried formating it to fat32, then fat.

Okay, I downloaded the beagleboard-validation-201008201549.img.gz, and un-7-zipped it to my windows box. Formatted the 1GB microSD and wrote the image to it using 32diskImager. Works fine and boots to Angstrom just as the original card. Obviously my problem is somewhere on the RISC OS side of things and has nothing to do with windows.

It seems I’m not saving an image at all. All I can save, as a text file, is the actual “completed” message. Somebody mentioned a window popping up with a “save as option” but I’m not getting that. SD Create completes the job but leaves me without an image it seems.

Interesting. Which version of the FronteEnd module do you have? What happens if you try using the latest version (1.30) that’s included in the !System zip file on this page? (down in the “Resources” section).

If you have “Create image” ticked and “Write image” unticked, and the image creation works properly (last line of the output window will be “Done”) then as soon as the “Done” line appears a save as box should pop up to allow you to save the image.

Also: Is it possible you have the autosave option enabled? (Options → Auto Save on the iconbar menu). I’m not sure if I’ve noticed that option before, but if it’s ticked then it seems to result in the image being saved (as “SDImage”) to the same directory as SDCreate.

There’s also command-line usage as an option, isn’t there?

Right, updated FrontEnd and DDEUtils (both slightly vintage) at first seemed to make no difference though. Just when I was about to go through the whole procedure again with a fresh install of VRPC I found an SDcreate image. Copied it and wrote it to my card and hey presto! Booted to supervisor, plugged in keyboard and mouse. Typing *desktop now gives me a mode 28 640×480 RISC OS desktop, yay!

yay!

Good to know you’ve got the image and are up and running :-)

Also: Is it possible you have the autosave option enabled? ...I’m not sure if I’ve noticed that option before…

Looks like it’s optional

Bearing in mind the following, would there be any problems or prohibitions with building SD card images for hosting here? (It seems logical to then link to them from Using the Cortex-A8 port.)

• The manual method is probably a bit of a turn-off (for most), if you’ll pardon the term
• The entire contents of an SD image are already currently available, so I can’t see why there should be any licensing issues
• We now have file hosting on the wiki – thanks ROOL :-)

I don’t think there would necessarily be a need to ensure such images contain recent ROM builds – just working ones, which could then be updated by users running SDCreate under their new RISC OS environment.