*Copy with wildcards

Hi All,
I’m trying to write an Obey file to copy the PiBoot Wheezey config.txt etc. files from a subdirectory to the root, so that my son can play Minecraft-Pi without me talking him through RISCOS, but I’ve fallen at the very very first hurdle.

copy Wheezey.* @
results in
File ‘$.Wheezey.*’ not found.

cat Wheezey.*
‘Wheezey.*’ is a file

info Wheezey.*
gives me a directory listing of the files I wanted to copy!

The ADFS manual (which is all I have found so far, RISCOS newby!) suggests that this should work, but I can’t get wildcards to work at all!

Can anyone point me towards the light?

Thanks
Jon

How exciting! I seem to be much more advanced that I thought. No one can answer my question!

Either that or I’m being very thick and you’re all too polite to point it out :-)

Jon

Minecraft-Pi isn’t that a Wheezey program?
You can’t run Wheesey from RISC OS or vice-versa.

I gather you can (with the right set up) swap which flavour of Linux is running. This AIUI is done using a common kernel.
RISC OS has its own kernel so can’t join the party!

n.b. The last time I used wild card file access was ADFS on a BBC Master. I suspect many other RISC OS users have had little or no experience of them!

The syntax of the cat command is cat [<directory>]. cat <filename> will produce the error you mention. You can see this by typing *Help Cat

copy Wheezey.* @.* will copy @.Wheezey.* to @.Wheezey.* because @ is the currently selected directory (not much use) but as Wheezey is a file and not a directory it will fail with the error you have quoted. The root directory is called $

info Wheezey.* will tell you about the object Wheezey. Objects can be files or directories or image files. Image files are files that are interpreted to contain files, like a zip archive. If the software that interprets the image file has not been seen by the filer, then the image file will appear to the system as a file.

Why not do the copy from the desktop?

Hi,
sloppy description on my part, sorry.

I have RISCOS and linux dual booting on my raspberry pi just fine, but currently I have to drag-and-drop copy the kernel,config.txt etc. for whichever OS I want to reboot into from a storage folder to the root of the PiBoot (speudo) partition.
So I have a RISCOS directory with it’s kernel, config.txt etc. plus
a Wheezey directory with it’s kernel, cmdline.txt, config.txt etc.
I just copy the relevent one to root and hey presto.

All I wanted to do was to automate this in a script so my son could run it with a quick mouse click, to get from RISCOS to booting linux (to run Minecraft-pi). this way I can leave the Pi setup to boot RISCOS, and he can switch to Linux when needed.
I assumed an Obey file would be the best/quickest way to script that.

I want to copy the contents of $.Wheezey to $ overwriting any identically named files in the process. I can do this in the filer, no problem at all, and it works fine.

But with Copy, even if I use full pathnames it doesn’t like the source being a wildcard
COPY $.Wheezey.* $
file $.Wheezey.* not found

I think RiscOS (which I’m still familiarizing myself with) is amazing, so I can’t believe that it can’t handle moving an arbitrary number of files from one specified directory to another specified directory…
I just need to find the expected way to do this.

BTW info $.Wheezey.* in fact gives me a list of the files inside the directory $.Wheezey, so I’m not sure why you suggest that…

Does no-one do this sort of stuff any more? What do they use for scripting file moves etc?

Thanks for responding!
Jonathan

What do they use for scripting file moves etc?

Given that most applications are self contained (upgrades typically mean drag-dropping the new on top of the old), and user files can easily be moved in the Filer (within the Desktop), I think the simple answer is . . . they don’t.

While I have used *Copy on RISC OS, I can’t help you as it has been years (if not decades) and the last time I did it chronologically was on a Beeb. The drag and drop thing takes most of the pain out of moving files around, and it even works consistently unlike Windows (which by default moves on same media, copy to others).

Okay. I accept that my previous answer was rubbish, and a little niggling feeling in the back of my mind annoyed me as I carefully brewed a teabag in a mug. That’s a bad thing, tea is restful.

COPY $.Wheezey.* $

RISC OS will interpret that literally – as in attempt to copy each of the files, one by one, as $. This, it cannot do.

To make the copy work, you should:

*Copy $.Wheezey.* $.* ~CRQ~V

The ~CRQ~V means: Don’t ask for confirmation, recurse into subdirectories, quick copy (uses application workspace) and don’t be verbose.
Use *Help Copy for a list of available options, and *Show Copy$Options to see the defaults on your system.

There. Hope that’s more useful! (^_^)

In RISC OS it is easy to copy the Wheezey files into the root so that the next boot will be Linux. I am sure a Linux expert will tell you how to copy the RISC OS files into the root so that the next boot will be RISC OS.

Having already got an SD card which dual boots into RISC OS or into Linux

The only file that you need to change is the file ‘config.txt’ which tells the system where the operating system image file resides. Under RISC OS therefore, all you need to do is to have two files in the FAT partition on the SDcard, SDFS::0.$.!Boot.Loader, called ‘CONFIGLX.TXT’ and ‘CONFIGRO.TXT’. Under RISC OS just issue the command:

*copy SDFS::0.$.!Boot.Loader.CONFIGLX/TXT SDFS::0.$.!Boot.Loader.CONFIG/TXT ~C~V

The file ‘CONFIGLX.TXT’ will simply contain something like (the lines starting with a hash, i.e. all of them, can be omitted):

# uncomment if you get no picture on HDMI for a default “safe” mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display’s size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# for more options see http://elinux.org/RPi_config.txt

fake_vsync_isr=1
gpu_mem=64
init_emmc_clock=100000000
kernel=RISCOS.IMG

The important difference is the line ‘kernel=’ which tells the Pi that the operating system is in ‘RISCOS.IMG’ and not the default ‘KERNEL.IMG’, both of which will be present on your dual-booting card.

Rick, ah, thanks. I didn’t realize you need the destination to also be .* That works for me, and thanks for the extra flags, which I would never have worked out!

Chris, that’s a good point, and will make things much easier (and take a little less disk space)
Still, I’m glad I now understand how this works.

Thanks for your help guys!
Jonathan