Please make available shared disc '_S0'

While trying to configure an rpi with RO5.28, I have started getting the “Message from share – Please insert of make available shared disc ‘_S0’”. It has to be cancelled 8 times each time I boot the system.

I have a distant recollection of this being due to something trying to access a non-existent floppy drive, and putting a command into the boot sequence to suppress. I now can’t find out what the magic is.

If it helps, the last thing I was doing before this problem showee up was setting up a PS3 duplex printer.

Interestingly moving !Printers to the end of the list in “Run at startup” seems to have made it go away.

Funnily enough, I also saw this today, but didn’t pursue it (lack of time). Usually discs with funny names like that are actually shared printers or other resources. So, I wonder, did you share the PS3 printer at any point?

I made no attempt to share the printers.

I’ve found this on the RPC. It used to be in boot:tasks, but wasn’t needed more recently.

filename _S0fix, the underscore puts it first in the list to be run.

| quit
| don’t run this when we have ShareFS disabled
|
set fix yes
rmensure sharefs 0 set fix no
if “”=“yes” then share adfs::4.$ _S0 -noicon
unset fix

I’ve just seen this when trying to open a shared drive via LanMan98. It only happens with the new IPv6 stack, and, very unfortunately, totally stiffs the machine.

Edit: But I can open the same share via Omni, and it’s fine. I’m running a very long backup to the share now.

Edit 2, months later: it probably didn’t totally stiff the machine, but the frozen mouse pointer and lack of response to Alt-Break probably convinced me that it had. I agree with the observation that it takes 8 presses of Escape to get back to normal. Sadly I can’t truly confirm this without a time machine.

“I made no attempt to share the printers.”
Do you have any shared printers on your network?
Spurious “Please insert of make available shared…” messages occasionally happen on our network, IIRC we concluded it was shared printers related.
n.b. It doesn’t seem to happen so often now and I’m not sure why. Two of our shared printers are still on early versions of RISC OS (3.7 & 4.02)

Curiously, I’ve just seen it again. I thought the machine was stiffed – the mouse cursor wouldn’t move – but NumLock still worked, and multiple presses of Escape may have brought the system back.

These questions about shared printers: how does one go about sharing a printer? Since I don’t even know how to share one, I have to assume that my printer is not shared.

Well, actually it is, but only via JDServer, which means that RISC OS would have no idea that it’s shared.

set fix yes
rmensure sharefs 0 set fix no
if “”=“yes” then share adfs::4.$ _S0 -noicon
unset fix

Looking at the above, it’s not the cause of the problem, it’s a fix, in that it ensures that shared disc ‘_S0’ really does exist, so whatever asks for it will find it rather than put up an error box. It gets us no nearer to discovering what is spuriously requesting the disc. Or why it’s doing so.

The title bar of the dialogue box does indeed say “Message from Share”. But what is “Share”? Is it an app, or is it actually ShareFS?

I just clicked on the ShareFS icon on the icon bar, which opened a dialogue box saying there were no shared discs – briefly, until the network came back. But the title bar said “Message from ShareFS”.

how does one go about sharing a printer?

Sharing of Printers is via ‘Printer control’ from Printer’s icon bar menu, then Menu click on the printer entries. The status column shows shares. To unshare select active.

*Shares reveals shared printers.

Note that shared printers share names start with “_S”.

That’s some misc. info, why it’s messing up is undefined but over the years it has been a recurring issue.