[Coco] Drive letter issue in paths with toolshed os9 copy command on Windows

[David Ladd]

​If you feel this is a bug you may wish to fill out the bug report at the
toolshed project so it gets filtered to the contributors. This will help
keep track of the bug reports.​

+-----------------------------------------------------------------------+
| David Ladd a.k.a. PacoOtaktay a.k.a. Drencor                          |
| YouTube: http://www.youtube.com/user/PacoOtaktay                      |
| YouTube Gaming Live: https://gaming.youtube.com/user/PacoOtaktay/live |
| Websites: http://dwladd.com     &     http://www.theterrorzone.com    |
| G+:  https://plus.google.com/113262444659438038657                    |
| G+:  https://plus.google.com/+DavidLaddPacoOtaktay                    |
|                                                                       |
| Do you have your CoCo 3 yet?                                          |
+-----------------------------------------------------------------------+


On Tue, Sep 27, 2016 at 8:46 PM, Guillaume Major <guillaume.major at gmail.com>
wrote:

> Hi all!
>
> I'm currently writing some batch files on Windows to automate the process
> of building OS-9 disk images. I use toolshed's os9 command to copy the
> files on the disk images. The command works as expected except when I
> include the drive letter in absolute paths. Example:
>
> os9 format sq1-becker.dsk
> os9 copy Startup sq1-becker.dsk,Startup        <-- works
>
> os9 format sq1-becker.dsk
> os9 copy Startup c:\coco\sq1-becker.dsk,Startup        <-- fails with
> error 248: disk is filled to capacity
>
> Digging in the source code, I found out that when the path contains a
> colon, the disk is identified as a DECB disk without looking at the disk
> file content (step 2a in function _coco_identify_image in
> libcoco/libcocoopen.c). While it works well on Linux, it prevents using
> drive letters in paths on Windows.
>
> I compiled toolshed on my Windows machine with the latest source code. If
> I comment out step 2a in _coco_identify_image, the disk image is
> successfully identified as an OS9 disk and the command works as expected.
>
> My question is for the toolshed gurus: can this step be removed (at least
> for Windows) for identifying the disk/cassette image?
>
> Thanks,
> Guillaume
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>