Recent changes to Using_DriveWire

Using_DriveWire modified by Aaron Wolfe

Aaron Wolfe — Fri, 20 Jun 2014 18:50:29 -0000

--- v76
+++ v77
@@ -316,6 +316,41 @@

 **protect** \- Use the IP address and geolocation banning system to prevent unwanted clients from connecting. This prevents the unwanted sources from ever talking with the CoCo, they are blocked in the DriveWire server prior to connection. 

+## Printing
+
+In config.xml you'll find one or more printer sections like this (you can have as many as you'd like): 
+    
+    
+    <Printer category="printing">
+       <Driver list="TEXT,FX80" type="list">FX80</Driver>
+       <OutputDir type="directory"/>
+       <OutputFile type="file"/>
+       <FlushCommand type="string"/>
+       <CharacterFile type="file">default.chars</CharacterFile>
+       <Columns max="132" min="1" type="int">80</Columns>
+       <Lines max="132" min="1" type="int">66</Lines>
+       <DPI max="1200" min="50" type="int">300</DPI>
+       <ImageFormat list="JPG,GIF,PNG,BMP" type="list">PNG</ImageFormat>
+    </Printer>
+    
+
+**Driver** can be TEXT or FX80. If TEXT, Drivewire just writes whatever the CoCo sends to a file. If FX80, DW sends it to an emulated epson fx80, which then outputs image files. 
+
+**OutputDir** and **OutputFile** specify where the output is created. If OutputFile is set, all output is written (appended) to the same specified file. Probably not what you want unless it sounds like exactly what you want. Most folks will not want to set it, and instead will set OutputDir which tells DW to create new files for each print job (or page, in FX80 mode) in the specified directory. If both are set, OutputFile wins. 
+
+**FlushCommand** is any command you'd like executed after DW writes a new file or appends to the OutputFile. If the string '$file' is in this command, it will be replaced with the full path of the file DW just created. 
+
+The remaining settings only apply to FX80 mode: 
+
+**CharacterFile** is the font definition for the FX80. The default setting specifies an included file that matches the default font the FX80 used. Its a very simple human readable format. 
+
+**Columns** and **Lines** define the dimensions of an FX80 text page. You could for instance change Columns to 132 to emulate one of those really wide variants in the epson fx family, or change Lines to simulate different paper length. The defaults match what a regular FX80 used on 8.5x11 paper. 
+
+**DPI** and **ImageFormat** control the image files that the FX80 emulator produces. 
+
+  
+
+
 ## Note for users of FTDI USB-Serial adapters

 While working on DW4, I found that my FTDI adapter performed about 20% slower than my Prolific adapter and a 16550 "real" serial port. There is a simple change that can be made in the FTDI driver's settings to bring it's performance in line with the other hardware.

Using_DriveWire modified by Aaron Wolfe

Aaron Wolfe — Fri, 20 Jun 2014 18:50:29 -0000

--- v75
+++ v76
@@ -87,16 +87,13 @@

 ## The 'dw' command

-The 'dw' utility runs in OS9, it can be found on the latest NitrOS9 disks for DriveWire. You can mount these disks directly from the nitros9.org website using the included disksets. The sub commands and options available in dw provide many informational displays and give you a way to configure every aspect of DriveWire operation right from your CoCo. 
-
-You can also issue any dw command from the GUI client using the command box at the bottom of the main form. 
+The 'dw' utility runs in OS9, it can be found on the latest NitrOS9 disks for DriveWire. The sub commands and options available in dw provide many informational displays and give you a way to configure every aspect of DriveWire operation right from your CoCo. 
+
+You can also issue any dw command from the DW4UI GUI using the command box at the bottom of the main form. 

 All of the sub commands and options to dw may be abbreviated to their shortest unique form. For example, the command "dw server show threads" can be given as "dw s s t". 

 For quick help on what sub commands are available, type "dw" by itself. For help on an individual sub command, type "dw subcommand", for instance "dw disk". 
-
-  
-

 ## HDBDOSMode

Using_DriveWire modified by Aaron Wolfe

Aaron Wolfe — Fri, 20 Jun 2014 18:50:29 -0000

--- v74
+++ v75
@@ -4,13 +4,15 @@

 DriveWire provides many services to your CoCo. These include disk drives that can mount disk image files, serial ports that can be used to communicate over the internet, a real time clock, MIDI, and printing support. 

-You can define as many <Instance> sections in your config file as you'd like. Each instance supports one CoCo via one connection, such as a serial link or TCP/IP connection. A single server can run one or many instances at the same time. Each instance has its own set of virtual disks, ports, etc. Instances can be started and stopped individually or all together. 
+## Instances
+
+The DriveWire server can provide any number of instances. Each instance supports one CoCo via one connection, such as a serial link or TCP/IP connection. A single server can run one or many instances at the same time. Each instance has its own set of virtual disks, ports, etc. Instances can be started and stopped using dw commands or using the Instance Manager in the DW4UI. 

 [[img src=drivewireserver block.jpg]] 

-There are multiple interfaces which can be used to configure and control these services. The most basic tool for these tasks is the OS-9 command 'dw' which comes on a DriveWire bootable NitrOS-9 image and can be found in the DriveWire CVS repository in source form. If you prefer to manage DriveWire from a PC, you can use the DriveWire User Interface which is available on the DW beta web page. The UI is a graphical program which connects to the DriveWire server via TCP/IP. 
+There are multiple interfaces which can be used to configure and control these services. The most basic tool for these tasks is the OS-9 command 'dw' which comes on a DriveWire bootable NitrOS-9 image and can be found in the DriveWire CVS repository in source form. If you prefer to manage DriveWire from a PC, you can use the DriveWire 4 User Interface, a GUI that runs on modern computers. 

 ## Starting the DriveWire server and GUI

Using_DriveWire modified by Aaron Wolfe

Aaron Wolfe — Fri, 20 Jun 2014 18:50:29 -0000

--- v73
+++ v74
@@ -317,17 +317,6 @@

 **protect** \- Use the IP address and geolocation banning system to prevent unwanted clients from connecting. This prevents the unwanted sources from ever talking with the CoCo, they are blocked in the DriveWire server prior to connection. 

-## Remote File Manager (incomplete in beta 1.4)
-
-The Remote File Manager is a new OS-9 file manager that allows you to attach a folder on a local or remote file system (any file system supported by Apache Commons VFS) as a standard disk device. For instance, you could map /Y0 to C:\cocostuff and /Y1 to ftp.rsti.com. You can then access these file systems directly as if they were standard OS-9 disks, using regular commands to view files or even execute programs from them. 
-
-Beta 1.4 contains initial support. There are bugs o' plenty, but you can read and write to the remote file system in some ways. Directory listing does not work, and most getstt/setstt calls are not yet implemented. You can use 'list' and copy with some success, but little more. 
-
-This is (probably) the last major feature to be included in DW4. An OS-9 file manager is not simple to write (although thanks to the underlying DriveWire protocol, this one is about as simple as one can be) so this capability may take a while to perfect. I think once it is finished, it will make working with modern projects on the CoCo much more pleasant. Disk images and all the associated utilities required to get files in and out of them are no longer needed. 
-
-  
-
-
 ## Note for users of FTDI USB-Serial adapters

 While working on DW4, I found that my FTDI adapter performed about 20% slower than my Prolific adapter and a 16550 "real" serial port. There is a simple change that can be made in the FTDI driver's settings to bring it's performance in line with the other hardware.

Using_DriveWire modified by Aaron Wolfe

Aaron Wolfe — Fri, 20 Jun 2014 18:50:29 -0000

--- v72
+++ v73
@@ -66,6 +66,23 @@

 java -jar DW4UI.jar --liteui 

+  
+
+
+## Disk Buffers
+
+When you insert a disk into one of DriveWire's drives, the contents of the source image are read into a buffer. All reads and writes done from the CoCo operate on the buffer contents, not directly on the source. This is similar to how applications such as word processors work: you load a file into the word processor and make changes to an in memory copy of the document. 
+
+Similar to a word processor's "auto save" function, DriveWire will periodically write any changes made to the buffer back to the source in some situations. You can load a disk image from a wide variety of sources, and some are not writable or do not support random access operations. If DriveWire cannot do random access writes to the source, you will have to use the 'dw disk write' or the equivalent "Write to.." function in the GUI to save any changes you make to the buffer. The "Write to.." function writes the entire buffer and so can support sources that are not random writable such as WebDAV and FTP servers. 
+
+This diagram displays how the various disk settings effect the operation of the buffers. These settings can be specified using the GUI, using various 'dw disk' commands, or stored along with a source path in a disk set. 
+
+  
+[[img src=dw_buffer.gif]] 
+
+  
+
+
 ## The 'dw' command

 The 'dw' utility runs in OS9, it can be found on the latest NitrOS9 disks for DriveWire. You can mount these disks directly from the nitros9.org website using the included disksets. The sub commands and options available in dw provide many informational displays and give you a way to configure every aspect of DriveWire operation right from your CoCo. 
@@ -76,16 +93,8 @@

 For quick help on what sub commands are available, type "dw" by itself. For help on an individual sub command, type "dw subcommand", for instance "dw disk". 

-## Disk Buffers
-
-When you insert a disk into one of DriveWire's drives, the contents of the source image are read into a buffer. All reads and writes done from the CoCo operate on the buffer contents, not directly on the source. This is similar to how applications such as word processors work: you load a file into the word processor and make changes to an in memory copy of the document. 
-
-Similar to a word processor's "auto save" function, DriveWire will periodically write any changes made to the buffer back to the source in some situations. You can load a disk image from a wide variety of sources, and some are not writable or do not support random access operations. If DriveWire cannot do random access writes to the source, you will have to use the 'dw disk write' or the equivalent "Write to.." function in the GUI to save any changes you make to the buffer. The "Write to.." function writes the entire buffer and so can support sources that are not random writable such as WebDAV and FTP servers. 
-
-This diagram displays how the various disk settings effect the operation of the buffers. These settings can be specified using the GUI, using various 'dw disk' commands, or stored along with a source path in a disk set. 
-
-  
-[[img src=dw_buffer.gif]] 
+  
+

 ## HDBDOSMode

Using_DriveWire modified by Aaron Wolfe