[Coco] Full GUI DriveWire 4 beta

[Bob Devries]

Hi Aaron,

Here's the output of the logfile for that event. I already had the log set 
to ALL.

18:14:29: [dwUIserver-10 ] new UI connection from 127.0.0.1
18:14:29: [dwUIserver-10 ] UI waiting for connection
18:14:29: [dwUIcliIn-43  ] run for client at localhost
18:14:29: [dwUIcliIn-43  ] server command: ui instance attach 0
18:14:29: [dwUIcliIn-43  ] instance command: dw disk insert 1 C:\Documents 
and Settings\Bob Devries\My Documents\COCO3\VCCBoot1.dsk
18:14:29: [dwUIcliIn-43  ] unregistering 0 for all events
18:14:29: [dwUIcliIn-43  ] exit

I get that when I typed the command per your suggestion (but using X1). I 
get a similar log if I use the button "Insert X1".

Regards, Bob Devries


----- Original Message ----- 
From: "Aaron Wolfe" <aawolfe at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Tuesday, December 28, 2010 5:44 PM
Subject: Re: [Coco] Full GUI DriveWire 4 beta


Thats an interesting one.  Do you have the same results using the Disk
menu, Insert.. as you do with the "quick buttons"?  what about typing:

dw disk insert 0 C:\some\path\to.dsk

in the text box along the bottom of the screen and hitting enter?

Could you set the logging level to DEBUG (Config menu, Server...) and
send me the log of what happens when you try the insert operation?
You can see the log in the server console window or (easier to
copy/paste) by opening a log viewer (Server menu, Log viewer) prior to
doing the insert.  Another option is to turn on logging to file and
just send me the whole file after trying it a couple times.  I'd
appreciate the info in any form thats easy for you.

-Aaron




On Tue, Dec 28, 2010 at 2:07 AM, Bob Devries <devries.bob at gmail.com> wrote:
> I installed and am successfully running DW4 also.
>
> One thing seems not to work, though.
>
> If I click on "Insert X0" (or any other DW drive) and try to insert a 
> local
> disk image from a folder on my PC, I get the following error:
>
> FAIL 100 dw disk insert requires a drive number and a URI or local path as
> arguments
>
> What am I doing wrong, or is this a (mis) feature?
>
> Regards, Bob Devries
> High and dry in
> Dalby, QLD, Australia
>
>
> ----- Original Message ----- From: "gene heskett" <gheskett at wdtv.com>
> To: <coco at maltedmedia.com>
> Sent: Tuesday, December 28, 2010 3:50 PM
> Subject: Re: [Coco] Full GUI DriveWire 4 beta
>
>
>> On Monday, December 27, 2010 11:54:03 pm Aaron Wolfe did opine:
>>
>>> inetd is pretty important, it is the primary way to access NitrOS9
>>> programs and shells from other computers across a network. I think it
>>> used to be part of the nightly build at one point, maybe it is failing
>>> there as well.
>>>
>>> there are a handful of tools that are sort of part of DriveWire and
>>> sort of part of NitrOS9.. inetd, the telnet client, the http server,
>>> etc. I'd love to see these support multiple networking solutions and
>>> be a sort of standard set of tools for all NitrOS9 users, but right
>>> now DriveWire is the only way to do such things.
>>>
>>> I guess the question is should we be building inetd, telnet, httpd,
>>> etc as part of the NitrOS9 disks? Or maybe as a seperate "extras"
>>> disk? I can probably sort out the build process to do whatever is
>>> acceptable.
>>>
>>> -Aaron
>>>
>> My build here on Dec 9, contains inetd in the cmds dirs of all levels,
>> however I'm not sure it is making it into the .dsk images. No, so the
>> makefile stanza for the dsk's would appear to be suspect, and I am not a
>> makefile expert Aaron.
>>
>> This is true at least for the coco3_6309 .dsk's. also, no identd in the
>> coco3-6809 dsk's, and none of the makefiles that make dsk's mention
>> inetd,
>> but it does exist in the cmds dirs freshly built, all up and down the
>> tree.
>>
>> I am actually getting ready for your dw4-Go for linux, I've moved Rogers
>> pack to the #0 slot so its not buried in the rest of the stuff, and it
>> appears to be working well again. That means I can cobble up a device
>> descriptor named p that will use the sc6551.dr to drive the BT thing, and
>> I
>> can switch my listening script to listen to /dev/rfcomm0 and get my laser
>> printer back online from the coco3's vantage point, but with the 
>> bitbanger
>> port then free for DW's use.
>>
>> Progress of sorts. ;-)
>>
>> However its not helped by having to edit the level 2 krn.asm everytime I
>> do
>> a 'cvs up', it winds up with the first 85 lines having 3 garbage lines
>> inserted that give mamou an upset tummy. Delete them and everything is
>> kewl. Bit rot maybe... Dunno.
>>
>> Thanks Aaron.
>>
>> --
>> Cheers, Gene
>> "There are four boxes to be used in defense of liberty:
>> soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author)
>> Humor in the Court:
>> Q: Are you qualified to give a urine sample?
>> A: Yes, I have been since early childhood.
>>
>> --
>> 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