UNMOUNT ?
6 messages in this thread
Can anyone tell me how to UNMOUNT a device ? Or, alternatively, how to make
its icon disappear from the WorkBench ?
I am trying to do two things…
First is to make my working partitions on my HD iaccessible to the kids…
all their stuff is now in a separate partition. (Currently I'm using a VERY
TINY icon that <10 yr old motor skill have a hard time hitting with the
mouse – but that becomes a challenge).
Second is to temporarily access pseudo-floppies created on the HD using
FMSdisk (GREAT TOOL). A specific application needs them and I MOUNT via an
Xicon script, but once its done I'd like them gone from WB (the app may
MOUNT 2 or 3 of these over the day and I prefer not to have them cluttering
up WB, plus the re-mount later in the day fails if its still mounted.
I AM currently using pairs of "ASSIGN nnnnn: REMOVE" to accomplish this
latter which I found through trial and error to work, specifially ASSIGN
FF0: REMOVE then ASSIGN VOLNAME: REMOVE. Both seem required.
BUT this does not seem like the intended usage of ASSIGN REMOVE ? Is it ?
I've had a few wierd gurus lately and worry that this aproach is screwing
things up internally…
-tnx
– da – via Whap!
Daryl,
You didn't state what kind of system or HD controller you are using, but if
you have one that uses the mountlist and mounts from the startup-sequence
with a 'mount dhx:" command, take that command out of your s-s and do it
manually when you need it. However you probably not really be able to
"Unmount" it reliabily. You will need to reboot to make it disappear again.
If your system uses the Rigid Disk Blocks you probably can rewrite the RDB
and turn off the automount command. Then generate a mountlist and then
mount it with a command as needed, like above.
If this has gotten you completely lost, let me know and I'll try again.
Greg
Greg White / MicroSearch 72230,1617
We listen to our customers..carefully
Greg,
The controller is Xetec which uses the HardBlocks approach – but the other
"devices" I need to UNMOUNT are the FMS "pseudo-floppies" which are in the
mountlist.
I can figure out how to, e.g., reboot and have a different set of WB disk
icons — I'm being a little lazy here tho…
I would like to be able to UNMOUNT my DH1: partition when I walk away from
the machine so little hands on mousies can only get to the DH0: partition
with the games n stuff on it. Course I could reboot and mix startup-seqs
to have DH1: not automatically accessed (and thus not automatically mounted
from the HardBlocks) BUT I'm just looking for an easy way to leave
everything on all day. The "ASSIGN DH1: REMOVE" gurus tho.
The FMS pseudo-floppies are a different story since I want my kids to have
access to their "Ready Robot Magazine" disks (GREAT STUFF for the 3-10 set)
without fiddling with floppies. Since the RR disks are, ahem, "encrypted"
I need a pseudo-floppy "partition" on disk which I can DiskCopy the floppy
to — FMS is GREAT for this but eventually they end up with 2,3 or more
Ready Robot WB disk icons plus my BOOT:, DH0:, DH1: and RAM:. In this case
the "ASSIGN FF0: REMOVE" paired with "ASSIGN VOLNAME: REMOVE" work fine…
i think !
– da – via Whap!
Daryl,
Try using the 1.3 "LOCK" command to 'legally' toggle access on an FFS
partition. I believe this will only prevent the partition from being
written to or changed in any way, and devices running in locked partitions
like FMS disks should also lock once the parent HD partition has.
Chris,
Good suggestion. Funny I've had 1.3 for what, a year now ? and still
uncover things that I saw on first reading of the manual but never got
around to testing out and using…
Course Write-LOCK will keep the kids from writing to the Budget data and
such but I've found that many programs just crash or hang when they
encounte write-protected files (using the protection bit) so I'd still
rather prevent the kids from even running the Budget program…
– da – via Whap!
Daryl,
LOCK doesn't use a file protection bit, it write-protects the whole disk,
as if you had flipped a write-protect tab somewhere. An attempt to write
will cause the usual write-protect requester.
LOCK can also accept a password-key, so you can lock/unlock the partition
with a codeword or sumesuch.