General Peer-to-Peer Setup

 

This is a general overview of a basic peer-to-peer setup. Your situation may vary depending on number of physical drives used. This example is using the ONAIR machine as the ‘server’ with the PROD machine as the ‘client’.

In this example below, the ONAIR machine has a C:\ and D:\ drive. The Operating system and the DAD program live on C:\. The D:\ will be used for audio storage only. This drive has a \CUTS directory.

The ONAIR machine will map it’s own C: and D: drives as F: (mapped to C: ) and G: (mapped to D: )

 

 

ONAIR

PROD

Share the C:\ through Windows.

Share the D:\ through Windows.

 

Create a user / password on this machine for the PROD machine. 

 

This workstation will map a drive to it’s own C:\ drive as F: and it’s own D:\ drive as G:

This workstation will map a drive to the ONAIR’s C:\ drive as F: and a drive to the ONAIR’s D:\ drive as G:.

In this workstations DADnet.BAT file near the top, add:

 

SUBST F: C:\

SUBST G: D:\

 

This will create a ‘mapping’ of the C:\ as the F: drive and a ‘mapping’ of the D:\ as the G: drive. 

 

Use Windows to map the ONAIR’s C:\ as drive letter F: and the ONAIR’s D:\ drive as the drive letter G:

 

 

In BOTH workstations DADnet.BAT file, you will modify the line:

@set data_drive=F:

This will tell DAD that the shared database files will be on drive F: with the shared audio being on G:.

Both workstations will run DAD Network.

All data will now be saved to the F: drive with all the audio being saved to the G: drive.

One should change the Record Deck settings so all audio is now recorded to the G: drive.