Dbx drivewire manual

The ICs in my series 2 don't match the schematic. Maybe there was more than 1 revision for the series 2 or it is in fact the correct series 1? I can't for the life of me find the series 2 schematic! This website is not affiliated with or sponsored by DBX. Gallery Requests Search. Submitted by w1jim on October 4th, The series I dbx 3bx service manual appears to have the schematic for the series II. Submitted by junkyardawg1 on August 24th, User login Login.

Create new account Request new password. See the Web User Interface manual for more details. The Debugging option on the command line or config file is global and is applied to All Instances. See the Debugging section for detail. Note: If your config file is in the default location you do not need to specify it on the command line.

Please see the Experimental Printing Support manual section for more detail about this feature. The Instance Selector allows you to change the current instance. The instance changes immediately upon selection and the Disk Images Box 2 is automatically updated. Each line in the Disk Images Section has a text box 2 for each virtual disk on the server. The text box shows the currently mounted disk image or None if no disk is mounted.

Note: This box shows the location of the disk image on the pyDriveWire Server which may be a different location than the Local File 5.

To Eject a disk image click the Eject button. The Remote File Box 2 will change to None. To Mount a disk image which resides on the local computer , click the Choose File button.

A file selection dialog box will pop up. The selected file is automatically uploaded to the pyDriveWire server. The Command Console screen allows you to run commands on the pyDriveWire server and also shows all the commands that have been run on the server by the user interface.

The screen has 2 parts: A scollable window with all the commands and command output, and second text box to enter commands and a button submit those commands to the server. The command window is designed to be interactive so that you can easily explore the available commands without looking up in the manual.

Please see the Command Console Interfaces manual section for more detail. Those interfaces are:. If you are a command line person this is for you. This is a fancy way of saying that it prints a prompt and waits for your input. If you hit enter on this command pyDriveWire will print some initialization info and then Greet you with a command prompt where you can type any DriveWire Command:.

See the Web User Interface manual section for a bit more detail on this, but in short you either put the option in your Config File. Change localhost and to the correct hostname and port number:. Type quit to exit:. This is useful for scripting control of pyDriveWire:. The server responded that help is not a valid command but it listed out the valid possible command prefixes dw tcp AT ui mc.

The user continues their exploration:. Here the user typed dw and the server responded with all of the available commands under dw. If the user was interested in disk operations they could type dw disk to see what sub commands are available:. The user is interested to show what disk images are mounted so this time the issued the full command:. If you already know the command you want you can of course type it directly without going through the exploratory steps above.

There are two ways to provide a config file to pyDriveWire:. If the config file exists it is read in. Options are applied to the config and commands are run through the command parser. Note: If both command line options and a config file are provided the command line options override the config file options.

Options -- Option entries can be used to set any of the command line options to pyDriveWire. Options always start with the word option and have the following format:. Commands -- are any lines in the config file that are not options, instance tags, or comments. These are standard pyDriveWire commands and they are run through the command parser immediately on start-up.

Instance Tags -- Tags are used to tell pyDriveWire that you want multiple instances. Please see the Multiple Instances manual section for more detail on how to configure this feature. Comments -- are any lines where the first non-whitespce character is a.

For a full description of all the config file options please see the Command Line and Config File Options guide. Each instance talks to one DriveWire client and each can mount different disk images. The instances are configured in a config file to specify the connection point and any options you wish to set for for each instance. Note: At the current time instances can only be specified in the config file and can only be started or stopped along with the main invocation of pyDriveWire.

The options and commands for first instance instance 0 starts at the top of the config file and includes any lines which are not comments or blank lines.

The main instance commands and options stop at the first instance tag. Instances are numbered sequentially. The first instance is always instance 0.

The instance following that one is instance 1, etc. Options and commands for the instance start after the instance tag and continue until the next instance tag. Instance 0 listens on port for incoming connections and is mounting a disk image. These commands should only be used from the command line interface, the web interface, or pyDwCli.

Note: Using instance commands from a DriveWire Client is not recommended. Shows a list of the currently configured instances. The server will respond with a line telling you which instance you just switched to. The command prompt will also change to show the current instance. You can see in the example above that the original prompt was instance 0 and it switched to instance 1.

When run in this mode there is no console repl and you must use either the Web UI or pyDwCli to control it. Daemon mode can be enabled from either the config file or from the command line. You do not need to specify both but you can. Note that if you do specify both the config file parameters will override the command line ones. The easiest way to use Daemon mode is to create a config file See Using a Config File and put the following options in it in instance This will start the server in daemon mode with a web UI listening on port The EmCee protocol support is always turned on allowing any application connected to a pyDriveWire server to use EmCee and DriveWire protocols simeltaneously.

The EmCee server in pyDriveWire is on by default and there are no commands to turn it on or off. Please see the rest of this documentation for how to invoke pyDriveWire. You must provide a full path name to the directory you want to switch to. List the directory on the server. The default directory is the one where pyDrivewire was invoked. The pyDriveWire server searches the provided. C10 or. CAS file and loads the first file in the tape image. The pyDriveWire server has a powerful "aliasing" system that is quite different than the official EmCee servers.

The pyDriveWire system has three different types of aliases. In the pyDriveWire server all alias names are converted to upper case. For example if you had an alias like this one:. The case of the alias requested from the MC is always converted to upper case so any of the following would load the same alias:.

Note that you won't see the actual file name, and when the file is closed the temp file will be automatically deleted. A path alias is an alias to a directory. A file alias points to a file. Full or relative pathnames could be used. When the MC requests the the alias the path to which the alias points to will be used and opened normally.

Adds the requested alias with path as the destination. The alias is always converted to upper case before addition lookup. The path that an alias points to is case sensitive.

Spaces and punctuation are permitted. Remove an alias. The alias is always converted to upper case before addition removal. The -x printer command line option enables it. This support was enhanced in pyDriveWire v0.

Printing support requires the reportlab module. This module can be installed with pip:. Most of the standard Nitros9 DriveWire builds have printing support built in. A simple example for testing:.