#WShell mystery Problem
2 messages in this thread
Here's a problem I ran into when using WShell:
I use KickBoth (at least I *think* that's its name, or is it MakeBoth?
KickBench??) Anyway it's version 1.2.0 by Alonzo M. Gariepy, which allows one
disk to be both a Kickstart disk AND a Workbench disk.
Anyway… running under CBM's CLI I can eject the disk and reinsert it and
access it as a DOS disk without any problems. However, when running WShell, I
can access it as long as I don't eject and reinsert it. Once I eject and
reinsert, trying to access it brings up a requester saying that the disk in
DF0: is not a DOS disk (it probably thinks it's Kickstart). I haven't figured
out any workI=Unds, short of rebooting.
Why does this happen, and is there a way around it.
A point of interest: If I run WorkBench (LoadWB) while this disk is in the
drive, WorkBench brings up a requester which says
Not a DOS
KickBench
in Unit /
But once I eject the disk and reinsert it, Workbench is happy again.
Hope you've got an answer.
– Steve –
Steve,
I've not heard of this problem before and have never tried KickBoth or
whatever. I seem to recall that there was some trick you had to do to toggle
the disk between Kickstart and DOS mode — could it be that they've patched the
standard CLI to get a disk-inserted interrupt, and then do the switch? I'm
just speculating, but clearly if one is going to patch Kickstart, then anything
becomes possible.
Does anyone else here have any ideas?
-Bill Hawes