[Coco] DriveWire 4 - Version 4.0

[Aaron Wolfe]

There are a handful of handy command line options, using the --help
option is the best way to find out about them.
Sorry, I'm just not really into doing documentation, and the wiki is
sadly out of date.  Maybe someday...

There are a several logging options available in the config.xml file.
 These are not currently exposed in the UI because I haven't finished
the full config editor.  You can edit config.xml with any text editor.
  Eventually, every item in the config will be available in the GUI.
Someday.

Its XML, if you're not familiar.. basically your setting goes between
the tags.  you can ignore the tags themselves and their attributes.
So if I want to set MyOption to "myvalue", it would look like:

<MyOption>myvalue</MyOption>

or maybe

<MyOption myattribute="somestuff" myotherattrib="some more
stuff">myvalue</MyOption>

Basically, just edit the stuff between > and <.  for toggles, set them
to 'true' or 'false' (no quotes).

Here are the options you are probably interested in:

First you, might like the --logviewer command line option, this opens
a powerful log viewer tool in a separate window, it lets you filter
sort etc.

You might also want the --backup option, which tells DW to backup your
config.xml every time it starts to config.xml.bak.. that way you can't
break anything too badly :)

Then, in config.xml these are the options you want to set:

Set the verbosity of the log (you want to set DEBUG, or --debug turns this on)
<LogLevel category="server, logging"
list="ALL,DEBUG,INFO,WARN,ERROR,FATAL" type="list">DEBUG</LogLevel>

Toggle log to the console (--debug also turns this on):
<LogToConsole category="logging" type="boolean">false</LogToConsole>

Toggle logging to a file:
<LogToFile category="logging" type="boolean">false</LogToFile>

If you want file logging, you must also set what file to write the logs to:
<LogFile category="logging" type="file"> path to your log file, will
be created if necessary </LogFile>

toggle logging of each OP_CODE (you want this true, to get behavior
similar to DW3's logging)
<LogOpCodes category="logging,advanced" type="boolean">false</LogOpCodes>

toggle logging of every byte sent or received on the serial port (you
might want to see what your controller is sending exactly)
<LogDeviceBytes category="logging,advanced"
type="boolean">false</LogDeviceBytes>





On Fri, Jan 6, 2012 at 7:00 AM, Mark Marlette <mmarlette at frontiernet.net> wrote:
> Aaron,
>
> v4.0.2, I see you added a --debug option. Looked on wiki for the .docs on this. Didn't see it. Did I miss it?
>
> I see that you added the support to the OP_READ command. That is now working as well for legacy DW3 support.
>
> Using DW3 & 4 as a test platform to the FAT SD CoCo Interface. I see the results graphically, I can click on the .dsk to get the drive. How can I tell what is being transmitted/received from the packet level? Basically the LOGGING feature that DW3 provided.
>
> Currently all code is working on the new interface, should be able to do a DIR/LOADon a FATx formatted SD plugged in to the CoCo here shortly.
>
> Thanks for the update and FAST turn.
>
> Mark
> http://www.cloud9tech.com
>
>
> ----- Original Message -----
> From: "Aaron Wolfe" <aawolfe at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Thursday, January 5, 2012 11:53:53 PM
> Subject: Re: [Coco] DriveWire 4 - Version 4.0
>
> Thanks for the bug reports!
> Version 4.0.2 is now available: https://sites.google.com/site/drivewire4/
>
> Fixed scrolling of wizard for smaller screens
> Added FPGA to device selection, added baud rate setting to wizard for
> FPGA devices
> Fixed display issues in Help.. About on Linux systems
> Fixed RXTX issue on 32 bit Linuxes
> Fixed premature "out of memory" error on loading large disk images
> Added --debug command line option
>
> -Aaron
>
>
> On Thu, Jan 5, 2012 at 2:31 AM, Aaron Wolfe <aawolfe at gmail.com> wrote:
>> It's done.. almost.
>>
>> https://sites.google.com/site/drivewire4/
>>
>> There is one feature disabled: the advanced configuration editor. Its
>> a beast, and has been holding everything else back.
>> The software is still quite usable without it, as the simple wizard
>> will walk you through the basic configuration and the
>> config file can always be edited by hand or manipulated from the CoCo
>> using dw commands anyway.
>>
>> Speaking of config files... things have changed. Configs from all
>> previous versions will not work well with this and future versions.
>> I tried to avoid this but early mistakes have taken a toll and it's
>> time to fix things. I hope it's not too inconvenient. If you have
>> created an elaborate configuration that you're attached to, let me
>> know and maybe it can be edited in place to work with the new version,
>> but it isn't trivial.
>>
>> Enough bad news, the good news is:
>>
>> New easy guided setup wizard thing to help you get started
>> New fancy pants graphics everywhere
>> Simplified interface that makes managing disks very easy
>> New DW Browser for the easiest Internet -> CoCo process ever.
>> Added support for DMK, JVC and VDK images
>> Local server built right into client
>> Lower memory use/better performance
>> A single package now supports Win/Lin/Mac/BSD in 32 or 64 bit flavors.
>> Maybe not a big deal to most folks, but very very nice for me
>> RXTX is built in and the libpaths are mangled automagically so it
>> "just works".. no more worrying about what craziness your linux distro
>> has done to it's Java.
>> Built in bug reporting.. when things go wrong, just push the button to
>> send me everything I need to know. Or don't.. privacy is fully
>> respected.
>> Countless minor improvements and fixes
>>
>> I also added a little thank you to lots of the folks that have helped
>> me with the project in the Help.. About area.
>>
>> -Aaron
>
> --
> 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