[Coco] [Color Computer] Got my Coco out of mothballs...

[Richard E. Crislip]

On 09/26/2013 02:01 PM, Gene Heskett wrote:
> On Thursday 26 September 2013 12:53:16 Al Hartman did opine:
>
>> Why is it nobody understands what I want to do?
>>
>> I want to take a file, such as the Drivewire ROM image, that exists on
>> the PC as a file, and get that file over to the Coco.
>>
>> I'd like a Windows based program like Explorer that will let you have a
>> two window display, one side being the PC, and the other being a Coco
>> .dsk image. Then, you can copy files back and forth, make a new Coco
>> .dsk image, delete files on either side, rename files on either side,
>> copy or move files from one side to the other.
>>
>> Everything I've found is either confusing, or DOS only.
>>
>> I can already write Coco disks on my Coco. I don't have 5.25" drives on
>> any of my PCs, except my XT which is not on my network, and without
>> 640k, I can't Laplink stuff to it.
>>
>> There are no USB solutions for writing 5.25" disks on a modern PC.
>>
>> Not all modern PCs even support having a 5.25" drive internally.
>>
>> All I want is to be able to move files into and out of Coco .dsk images
>> easily.
>>
>> Is that so much to ask for?
>>
>> -[ Al ]-
> The coco, running stock, or nitros9, does not have the concept of a move,
> only copy then delete. On the coco, I have worked on that some, but never
> felt it was vetted enough to expose it to new users, os9 only of course.
> Like the linux version of such a utility, if the mv is on the same file
> system, just move the directory entry to where you want the file to be
> visible, but if not on the same filesystem (different disk) then do a copy
> instead, and if the copy then compares, then do the source deletion.
>
> The toolshed stuff syntax is a little arcane but the job is 100% doable
> from the command line by the host pc.  But because the syntax is a bit
> arcane, (it should yell at the idiot between the keyboard and the chair if
> the comma is missing) it would be well appreciated by folks who are stuck
> on the gui idea, if a 2 pain file manager was to become part of the default
> build in toolshed.  Its grown some with version 2.0, but I've not run
> across such a utility yet.
>
> But it would indeed be handier than the turn button on the outhouse door if
> it was to grow one.  Hint hint.
>
> I also tend to agree with those who don't want to run all over the planet,
> and who often don't have the build tools installed to even do step 1, which
> is to obtain & build/install lwtools.  Then, get, build & install toolshed,
> followed by nitros9 if thats your bent.  For those of you running a linux
> system, and really, if you are at all familiar with os9/nitros9, the closed
> shop of windows and mac's is a world you you _can_ get used to, but I've
> never found it a comfortable place to live.  So if you're running a linux
> that uses apt for a package manager, then "apt-get install build-
> essentials" will install everything you need to run my script to get and
> built it all.  2 command lines to type and run.
Hi Gene, tried that command on my x32 Mint15 distro and below was the 
results. What am I doing wrong? TIA

richard at saratoga ~ $ sudo apt-get install build-essentials
[sudo] password for richard:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package build-essentials