[Coco] wget hangup

[Joel Ewy]

On 03/04/2013 10:18 AM, Aaron Wolfe wrote:
> On Mar 4, 2013 10:35 AM, "Joel Ewy" <jcewy at swbell.net> wrote:
>> On 03/04/2013 09:29 AM, Joel Ewy wrote:
>>> On 03/04/2013 04:23 AM, Aaron Wolfe wrote:
>>>> Where did this dw4_l2_6309 disk come from?  I dont recall anything
>>>> with that name, but maybe i'm forgetting something.
>>>> I would recommend using only disks from the nitros9 nightly site or
>>>> the drivewire download page.
>>>>
>>>>
>>>> On Sun, Mar 3, 2013 at 10:44 PM, Joel Ewy <jcewy at swbell.net> wrote:
>>>>> So, I'm trying to use wget on the dw4_l2_6309.dsk image with a syntax
> like:
>>> Sorry Aaron, the disk image is named dw4_server_l2_6309.dsk and I'm
> pretty sure it came from one of the two mentioned sites, though it's been a
> couple years since I grabbed it.  Must have been getting sleepy last night.
>   Does the DW4 server have error logs I can check?
>> OK, here's a clue:  Mon Mar 04 2013 09:32:21.139  WARN DWVPortHandler
>   dwproto-0-9         Unknown API command: 'url get http://www.google.com/'
>> Is my wget using an obsolete version of the API?  If so, is there an
> alternative place to get a more current build if www.nitros9.org is down?
>> JCE
>>
>>
> Ah yes, its coming back to me now.
> Wget does indeed use an old api that is not present in current servers.
>
> Instead of wget, you can use the dw utility (which is just a shim that
> provides access to the high level dw api).
>
> dw server list http://google.com
>
> Or the shorthand
>
> dw s l http://url
>
> And you can use standard io redirection to put the data into a file.
>
> Please get rid of that old disk,  I think it can only cause trouble.  The
> dw download page has disks with current software.

FWIW, there is still a wget on 
https://sites.google.com/site/drivewire4/download/nos96309l2v030209coco3_dw3.dsk?attredirects=0&d=1 
that's identical to the one I've been trying to use:

Module size:  $02C1  #705
Module CRC:  $CE3316

So even a new disk image still has this problem.  I found an assembly 
source file for wget on my hard drive.  What would it take to update it 
to the current API?  My 6809 is pretty rusty, but a project like that 
might be about my speed.  Until then, I'll use the dw command.

JCE
>
>>> By the way, where's www.nitros9.org gone?  Surely it doesn't have
> anything to do with a possible future project name change yet, does it?
>>> JCE
>>>
>>>>> "wget http://www.google.com/" or "wget http://www.google.com/>google.html"
>>>>> and wget seems to just hang.  scdwn and /n (etc) are loaded in memory
> from
>>>>> the bootfile, and I can use a terminal program to connect to the
> outside
>>>>> world over /n.  I can hit <break> and end the program. If I redirect
> the
>>>>> output to a file, it creates an empty file.  wget doesn't put out an
> error
>>>>> message or anything, just silently stalls. Ideas?
>>>>>
>>>>> JCE
>>>>>
>>>>>
>>>>> --
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>