|
|
|
In a RADAR I version 1.68 system upgrade, can I install the new v1.68 software directly to new internal SCSI drives, or do I have to load a previous software version first?
|
|
|
|
|
|
|
|
|
|
In order to install RADAR I v1.68 system software on your new internal SCSI drives, you will first have to install v1.46 software (available from Otari). After installing v1.46 per the instructions in the v1.46 release notes, install v1.68 per the v1.68 release notes. If your RADAR is currently running a software version earlier than v1.46, again, you must first upgrade to v1.46 before installing v1.68.
|
|
|
|
|
Which brand and model of SCSI tape drives are approved for use with RADAR I and RADAR II?
|
|
|
|
|
|
|
|
|
|
|
|
|
Please see the list of approved tape drives below:
|
RADAR I
|
|
#
|
Manufacturer (Name)
|
Size (GB)
|
Model Number
|
Mfg. Part No.
|
Status
|
|
1 |
Exabyte 8505 |
5 Gb (112m) |
EXB-8505S |
870010-025 |
Discontinued |
|
2 |
Exabyte 8505XL |
7 Gb (160m) |
EXB-8505XLS |
870013-025 |
Discontinued |
|
3 |
Exabyte Eliant 820S |
7 Gb (160 m) |
Eliant 820S |
2700001-23 |
Available |
|
|
http://www.exabyte.com/home/products.html
|
|
RADAR II
|
|
#
|
Manufacturer (Name)
|
Size (GB)
|
Model Number
|
Mfg. Part No.
|
Status
|
|
1 |
Exabyte Mammoth |
20 Gb (170m) |
EXB-8900-LVD |
8900-899 |
Available |
|
2 |
Exabyte Mammoth |
20 Gb (170m) |
EXB-8900-SW |
890210-000 |
Discontinued |
|
3 |
Exabyte Mammoth-LT |
14 Gb (125m) |
MAMM-LTLVD |
270012-821 |
Available |
|
4 |
Exabyte Eliant 820 |
7 Gb (160m) |
Eliant 820S |
270001-23 |
Available |
|
5 |
Exabyte 8505XL |
7 Gb (160m) |
EXB-8505XLS |
870013-000 |
Discontinued |
|
6 |
Exabyte 8505 |
5 Gb (112 m) |
EXB-8505S |
870010-000 |
Discontinued |
|
|
http://www.exabyte.com/home/products.html
|
|
|
#
|
Manufacturer (Name)
|
Size (GB)
|
Model Number
|
Mfg. Part No.
|
Status
|
|
1 |
Seagate Sidewinder, AIT-1 |
25 Gb (170m) |
STA250000W |
70102600-001 |
Discontinued |
|
2 |
Sony SDX-300C, AIT-1 |
25 Gb (170m) |
SDX300C |
n/a |
Available |
|
|
|
|
|
|
|
Which brand and model of SCSI hard drives are approved for use with RADAR I and RADAR II?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please see the list of approved drives below:
|
RADAR I
|
|
#
|
Manufacturer (Name)
|
Size (GB)
|
Model Number
|
Mfg. Part No.
|
Status
|
|
1 |
Seagate Barracuda |
9 Gb |
ST39216N |
9N3004-001 |
Discontinued |
|
2 |
Seagate Medalist Pro |
4 Gb |
ST34520N |
9L1001-001 |
Discontinued |
|
3 |
Seagate Barracuda |
4 Gb |
ST34573N |
9J4001-010 |
Discontinued |
|
4 |
Seagate Barracuda |
2 Gb |
ST32272N |
9J6004-010 |
Discontinued |
|
5 |
Seagate Barracuda |
2 Gb |
ST32171N |
9C6002-026 |
Discontinued |
|
|
Note: In order to be approved for use in a RADAR I system, a drive must have passed both internal qualification and external qualification.
|
|
RADAR II
|
|
#
|
Manufacturer (Name)
|
Size (GB)
|
Model Number
|
Mfg. Part No.
|
# Tracks
|
Status
|
|
1 |
IBM UltraStar |
36 Gb |
36ZX |
09L-3903 |
16 |
Discontinued |
|
2 |
Seagate Cheetah |
18 Gb |
ST318203LW |
9L8005-001 |
13 |
Discontinued |
|
3 |
Seagate Cheetah |
18 Gb |
ST318404LW |
9N9002-001 |
13 |
Discontinued |
|
4 |
Seagate Cheetah |
9 Gb |
ST39103LW |
9L9005-001 |
13 |
Discontinued |
|
5 |
Seagate Cheetah |
9 Gb |
ST39102LW |
9J8005-001 |
16 |
Discontinued |
|
6 |
Seagate Cheetah |
9 Gb |
ST39204LW |
9P4002-001 |
16 |
Discontinued |
|
7 |
IBM UltraStar |
18 Gb |
18LZX |
09L-3905 |
15 |
Discontinued |
|
8 |
IBM UltraStar |
9 Gb |
9LZX |
08L-8261 |
15 |
Discontinued |
|
9 |
Seagate |
18 Gb |
ST318406LW |
********** |
15 |
Discontinued |
|
10 |
IBM UltraStar |
36 Gb |
DDTS-T36950 |
07N6340 |
15 |
Discontinued |
|
|
Note: The number to the right of the hard drive name/model number refers to the highest number of observed flawless punch-in tracks. |
|
|
|
|
|
Which brand and model of DVD-RAM drives are approved for use with RADAR II v2.09 and later software?
|
|
|
|
|
|
|
|
|
|
|
|
|
Please see the list of approved DVD-RAM drives below:
|
RADAR II
|
|
|
#
|
Manufacturer (Name)
|
Size (GB)
|
Model Number
|
Mfg. Part No.
|
Status
|
|
1 |
Hitachi |
9.4 Gb |
GF-2050 |
GF-2050 |
Available |
|
2 |
Hitachi |
5.2 Gb |
GF-1050 |
GF-1050 |
Available |
|
3 |
Panasonic |
5.2 Gb |
LF-D103U |
LF-D103U |
Available |
|
|
|
|
|
|
How does RADAR II connect to an analog console?
|
|
|
|
|
|
|
|
|
|
|
|
|
RADAR II contains 12 (two channel) A to D converters and 12 (two channel) D to A converters that supply 24 tracks of analog/digital conversion. They are accessable through (6) 25pin D-sub connectors on the back panel of the unit.
|
|
|
|
|
How long does it take to back up 9 gigs worth of data? |
|
|
|
|
|
|
|
|
|
|
|
|
Although it depends on how much data you're actually backing up, the short answer is that it takes between 2-3 times realtime when the data is 24-bit at 24-tracks wide. So, a five minute song using all 24-tracks recorded at 24-bits will take approx. 12 minutes to back up. Therefore, since a 9 gig drive will hold about 42 minutes of 24-track 24-bit data it will take approximately 106 min. to back up. However, this is not reccomended unless it is absolutly neccessary (ie; basic tracking dates, live shows, etc.). We recommend that the backup process be performed on a more regular basis so that it would almost never be neccessary to backup an entire hard drive at once (except for the circumstances that I already outlined). |
|
|
|
|
Is M/O possible? |
|
|
|
|
|
|
|
|
|
|
|
|
Yes, the disk configuration can be customized for M/O. |
|
|
|
|
Is Jaz possible? |
|
|
|
|
|
|
|
|
|
|
|
|
No. We used to support Jaz in RADAR I, but Iomega changed some of their protocol, and because we found that Jaz drives couldn't achieve the access speeds neccessary for RADAR II, we stopped supporting that medium.
|
|
|
|
|
I've noticed that every once in a while, I see a message on the remote"s screen that says SAVING STATE and then it disappears instantly. Is there something wrong with my RADAR?
|
|
|
|
|
|
|
|
|
|
|
|
|
Not at all! Saving state is RADAR"s way of saving edits and newly recorded audio. You"ll notice that you will not get this message during times of inactivity, but only after you perform an edit, complete a recording or change an item in the PREFERENCES menu. If this message gets in the way of your working (for instance, it always occurs just as you are about to perform a function), you can change the SAVE STATE DELAY under the PREFERENCES menu. HOWEVER, it is important to note that you MUST allow RADAR to perform this procedure from time to time. If you are constantly working pressing this button and that, and RADAR does not have a chance to do a SAVE STATE, and God forbid if your power ever failed, you would find that all the work you have done since the last SAVE STATE would be lost! This is why it is important to perform the SHUTDOWN procedure before you power down, as one last SAVE STATE is activated before you power off.
|
|
|
|
|
I've been working all night on an extremely important project and, I mistakenly deleted the project. Undo says that there is nothing to undo. Is there anyway that I can recover the data? |
|
|
|
|
|
|
|
|
|
|
|
|
The unfortunate answer to this question is both Yes and No. There is a hidden mode called RECOVER SPACE which you can use to recover the deleted project, but it will not restore the project back to the state it was in before you deleted it. The "play-list" (the information that tells where the audio files belong) is gone forever. The new project created after performing the RECOVER SPACE procedure will take all the audio files and place them end to end, all on track 1 (keep in mind that each punch-in is a separate audio file and that the data will not be track specific either). You must then search for and find the individual sections, then Copy and Paste them to their proper places in time and proper track locations. While this is a great deal of work, it could facilitate the recovery of the "priceless" performance that can never be duplicated.
To enter this mode on the remote you must enable the options dialog so that the feature will show up in the diagnostics menu. To do this, perform the following procedure:
1. Press and hold the SHIFT button
2. While holding SHIFT, press the # button
3. Type in;
iodebug
4. Press ENTER
5. Return to the DIAGNOSTICS menu
6. Select RECOVER SPACE and perform the function
7. Go to the newest project created and you will find the recovered data
|
|
|
|
|
I've mistakenly erased all disks. Undo says that there is nothing to undo. Is there anyway that I can recover the data? |
|
|
|
|
|
|
|
|
|
|
|
|
Unfortunately there is nothing in the UNDO buffer to recall after erasing the disk, therefore the data is no longer available. |
|
|
|
|
What is the difference between INITIALIZE DISK and ERASE ALL DISKS? |
|
|
|
|
|
|
|
|
|
|
|
|
For RADAR I, ERASE ALL DISKS is recommended because it will wipe all 3 (or all 6) drives in the system, but it will retain user preferences (since the user preferences are stored on Drive 0). INITIALIZE ALL DISKS can be used, but will also reset the Preferences to default values. Also, you will need to perform the keystrokes for the initialize routine for EVERY drive in your system. Note: INITIALIZE ALL DISKS can be used as a way to prevent serious problems from occuring, since it will ultimately "defragment " each drive.
For RADAR II, INITIALIZE ALL DISKS is recommended. There is only one removable 9GB (or 18 GB) drive used in RADAR II, but the user preferences are NOT stored on this drive. Instead, they are stored on the same internal IDE drive which contains the SYSTEM software. The Initialize process only takes a few seconds, and gives users the added confidence that their drive is now back to it"s original, "defragmented", initialized state.
・ In short, for RADAR I - Continue to use ERASE ALL DISKS.
・ for RADAR II - Use INITIALIZE ALL DISKS.
|
|
|
|
|
Is there any easy way to quickly get to the IN point or the OUT point without selecting REC LOC, pressing the IN or OUT and then pressing ENTER? This requires 3 keystrokes and time is of the essence!! |
|
|
|
|
|
|
|
|
|
|
|
|
Yes! On the cursor buttons (The buttons with the arrows), simply press the button with the arrow that points to the left and you will be located to the IN Point. Furthermore, pressing the button with the arrow that points to the right will take you to the OUT point. Finally, pressing the button with the arrow that points "DOWN" will instantly play all track info marked between the IN and OUT points. |
|
|
|
|
I've created a Project (Lets call it Project 1 - "Song 1"), then I copy the project to a new project (the copied project is called "Song 1 V-2" by the RADAR). After more recording and working on "Song 1 V-2", I get to the point where I"m running out of disk space. So, I go into the Project Menu and delete Project 1 (Song 1). My logic is that I"m no longer working on "Song 1" but I"m now working on "Song 1 V-2" and therefore I can delete this project, reclaim the space and then continue recording. After I delete "Song 1", why hasn't RADAR freed up more space on the hard disk?
|
|
|
|
|
|
|
|
|
|
|
|
|
When the RADAR copies a project, you are correct when you state that it does not use additional space. This is because a copied project is simply a new play-list. The audio files currently present in project 1 (at the time of copy) are now shared with project 2. Therefore deleting the first (master) project cannot give you back more disk space, because the audio files from the master project are still needed for playback in project 2.. That is, the copied project"s playlist is looking for exactly the same files as the master project at the time of the copy. This also applies if you copy project 2 and now have project 3, (V3). Project 3 now shares the same files as 2. Additionally, project 3 also shares the files that are shared between 2 and 1 even though project 1 wasn't copied in this case.
Only freshly recorded audio in any of the 3 projects will use new disk space (i.e. - a new guitar solo on the 3rd project). The user could do a guitar solo on the first project also, but the solo would not be added to the second or the third (as the guitar solo in project 3 is not added to the first or second). This is a great feature as you could have various performances on various projects. The best parts of these projects can be copied between projects. However, if you get to a point where you no longer need some of the "un-shared" material in projects 1, and you can delete projects 1 and 3, you will get back the disk space that is specific or "un-shared" in these 2 deleted projects. Even the stuff that you "pasted over" on project 2 is now deleted (leaving the newly pasted stuff from project 1 and 3).
|
|
|
|
|
This issue of shared files also raises another issue: In the above scenario, when you individually backup "Song 1 V-2" to Exabyte, does RADAR write the audio files associated with this copied project to Exabyte as well as the playlist so that, in the future, one can restore "Song 1 V-2" without having to first restore "Song 1"?
|
|
|
|
|
|
|
|
|
|
|
|
|
When you archive a project as a "selected project", all the playlist and audio data for that individual project is being saved. Restoration of this "selected" project will now require it's own disk space (for all the data). If you want the data to be saved as shared information, you must do an "ALL" save or "CURRENT VERSIONS" so that a restore can properly put stuff back in their proper "shared" relationships once restored. |
|
|
|
|
I have a RADAR I project I have been working on that has required significant editing on many tracks, I received an error message, "OUT OF MEMORY", why? What should I do?
|
|
|
|
|
|
|
|
|
|
|
|
|
A standard RADAR system ships with 4 MB of memory on the motherboard. This memory is used to store both the operating system as well as the data for the file system and data for the playlists of the current project. The operating system takes about 1.5 MB, and the file system takes about 1.2 MB, leaving about 1.3 MB for playlist data. NOTE: For the file system, we calculate about 0.4 MB per disk drive. If more than 3 drives are used in the system, multiply the amount of drives by 0.4 MB to determine the total RAM required for the file system. If you are using 6 drives, for example, then 2.4 MB of RAM are required. Therefore, you will likely need more memory in your RADAR I system if you want use more than 3 drives or if you are editing a complicated project. The system has been designed to allow for increased memory capacity. Simply purchase the necessary RAM SIMM according to the information below from your local computer vendor and complete the installation according to the instructions mentioned later on in this FAQ.
RADAR motherboards use industry standard SIMM (Single Inline Memory Module) technology, so you can go down to your local computer store and buy extra memory as required. Here are the configuration details:
|
|
|
|
・ Pin Count: |
30-pin or 32-pin (all SIMMs should be the same type) |
|
・ Access Speed: |
70 nanosecond (all SIMMs should be the same speed) |
|
・ Memory Size: |
1 MB x 9 bit SIMM
4 MB x 9 bit SIMM
16 MB x 9 bit SIMM
|
|
|
|
|
|
In a RADAR I system, how much RAM memory is recommended to be installed on the motherboard for the following hard drive configurations?
|
|
|
|
|
|
|
|
|
|
|
|
|
Firstly, determine the necessary RAM requirements using the table below for your particular hard drive configuration.
|
Internal or External Only (3 Hard drives) |
|
Internal + External (6 Hard drives) |
|
|
|
|
|
|
|
1 GB (Total 3 GB)
|
4 MB |
|
1 GB (Total 6 GB)
|
8 MB |
|
2 GB (Total 6 GB) |
8 MB |
2 GB (Total 12 GB) |
8 MB |
|
4 GB (Total 12 GB) |
8 MB |
4 GB (Total 24 GB) |
16 MB |
|
9 GB (Total 27 GB) |
16 MB |
9 GB (Total 54 GB) |
32 MB |
|
18 GB (Total 54 GB) |
32 MB |
18 GB (Total 108 GB) |
32 MB |
Note: If Internal and External hard drive capacities are different, add up the total size of all drives and use the table (above) to select the equivalent RAM required. If the sum of your total hard drive capacity falls in between the ranges detailed above, select the next highest RAM size to be safe.
Follow the RAM requirements and installation process listed in this FAQ.
|
|
|
|
|
How do I go about upgrading my RADAR I motherboard with additional RAM?
|
|
|
|
|
|
|
|
|
|
|
|
|
Purchase and follow the follow the attached procedure. A listing of the required RAM SIMM"s can be found earlier in this FAQ.
RADAR Motherboard Memory Upgrade Procedure
Memory Type: RADAR motherboards use industry standard SIMM (Single Inline Memory Module) technology, so you can go down to your local computer store and buy extra memory as required. Here are the configuration details:
|
|
|
|
・ Pin Count: |
30-pin or 32-pin (all SIMMs should be the same type) |
|
・ Access Speed: |
70 nanosecond (all SIMMs should be the same speed) |
|
・ Memory Size: |
1 MB x 9 bit SIMM
4 MB x 9 bit SIMM
16 MB x 9 bit SIMM
|
Possible Memory Configurations: SIMMs are installed in banks of 4, and there are sockets for two memory banks on the motherboard. So the possible configurations are:
|
|
|
|
|
Bank-0 |
Bank-1 |
Total Memory |
|
1M |
- |
4MB |
|
1M |
1M |
8MB |
|
1M |
4M |
20MB |
|
1M |
16M |
68MB |
|
4M |
- |
16MB |
|
4M |
1M |
20MB |
|
4M |
4M |
32MB |
|
4M |
16M |
80MB |
|
16M |
- |
64MB |
|
16M |
1M |
68MB |
|
16M |
4M |
80MB |
|
16M |
16M |
128MB |
Early RADAR System Limitations: Early RADAR systems (the first 20 or so) used an older-style motherboard with "U4VL2" printed on the board, and a blue plastic socket for the 486 chip. Newer RADAR systems all use a new-style motherboard with "Green 4GLX" printed on the board and a beige plastic socket for the 486 chip. The early systems can only accommodate 1 MB x 9 and 4 MB x 9 SIMMs. They are therefore limited to 32 MB total memory. This 32 MB limit is still more than adequate for RADAR's needs.
|
|
|
|
|
How Do I Install More Memory? |
|
|
|
|
|
|
|
|
|
|
|
|
To install extra memory, follow these steps: # Power off RADAR.
|
|
|
|
1. |
Remove the case lid. |
|
2. |
Locate the empty memory bank (Bank-1) on the motherboard. The two banks are located nearest the power supply and the SCSI disk drives. |
|
3. |
Remove any cables in the way of Bank-1. You probably will only need to disconnect the cable connecting the SCSI drives to the CM24. |
|
4. |
Install the extra SIMMs into Bank-1. The new SIMMs should face the same direction as those currently installed. Start with the socket closest to Bank-0. Insert each SIMM into its socket by a) sliding the bottom SIMM edge into the socket at an angle, so that the top edge can pivot freely and b) rotate the SIMM until it is completely vertical and the top edge snaps into the holes and the metal clasps lock the SIMM in place. |
|
5. |
Reattach any cables removed in step 4. |
|
6. |
Install a VGA card, VGA monitor, and a PC keyboard. Any VGA card will do, and it can be installed in the empty motherboard slot next to the MF3. The PC keyboard attaches on the back panel of RADAR.
|
|
7. |
Power On RADAR. The VGA monitor will display the normal PC boot sequence. It should show that the new RAM was installed correctly as it tests all available memory. It will stop with a "Memory Mismatch" or "Bad memory size" message. This message is expected and does not indicate an error. (The message is stupid, misleading, and unnecessary, but unfortunately it will appear. ARGH!)
|
|
8. |
After the "mismatch" message press F1 to enter the BIOS setup screen. |
|
9. |
From the main BIOS setup menu, select "Standard CMOS setup" and press ENTER. |
|
10. |
Don't change anything here, just press ESC to get back to the main menu. |
|
11. |
From the main BIOS setup menu, press F10 to Save & Exit. Press Y to confirm the save operation. This operation will record the new memory size into the battery-backed configuration memory. |
|
12. |
The RADAR system will now reboot. This time, no "mismatch" message will occur and the RADAR system should now boot off the SCSI drives.
|
|
13. |
From the RADAR "DIAGNOSTICS MENU" select "SHOW FREE RAM". Verify that the new RAM has been recognized by the RADAR operating system. If you upgraded from 4 MB to 8 MB, the system should now be reporting more the 4MB of free ram (it will probably report around 5000 KB free).Power off RADAR.
|
|
14. |
Remove the VGA card and keyboard. |
|
15. |
Close the case lid. |
|
|
|
|
|
In a RADAR I system configured with Internal + External drives, what is the recommended software upgrade procedure?
|
|
|
|
|
|
|
|
|
|
|
|
|
For maximum flexibility, we recommend installing the RADAR system software on both the Internal and External hard drives. The reason for this is to allow the RADAR to boot properly if the user happens to switch the hard drive configuration to "External Only" mode. Since the RADAR boot software will also be located on the external drives, the RADAR will boot properly.
Below is the recommended procedure to install the system software on a RADAR system employing Internal and External hard drives.
|
|
|
|
1. |
Under the System Menu, select "CONFIGURE DRIVES" and configure for EXTernal disks. |
|
2. |
Now (from the System Menu) select "UPGRADE SYSTEM" |
|
3. |
Power down RADAR, insert the 2.xx diskette and power up RADAR.
When RADAR prompts you to install 2.xx, choose YES. This will be installed to SCSI drive #3. The following will now occur:
|
|
|
|
|
a. |
The front panel and RE8 LCDs should show the following status messages: |
|
|
|
"RADAR DIGITAL 24 TRACK"
"Booting from floppy..."
|
|
b. |
You should see the messages: |
|
|
|
"Copying BOOTLOAD.386..."
"Copying BOOTPART.386..."
"Copying CM24.BIN..."
"Copying EM8B.BIN..."
"Copying KS1.ISP..."
"Copying RADARL.BIN..."
"Copying RADARH.BIN..."
"Updating KS1 ..."
|
|
C. |
The LCD should now say "Install Complete... Press Any Button". Press a key and 'the LCD says
"Remove Floppy, Power off & Reboot". If the install has failed, it will be reported on the LCD.
Contact Otari if problems are encountered.
|
|
|
4. |
After 2.xx has been installed, power down RADAR, remove the 2.xx floppy diskette and reboot RADAR.
|
|
5. |
Under the System Menu, select "CONFIGURE DRIVES" and configure for INTernal disks. You will see a "WRONG OP SYS S/W" message at this point. This is expected and can be ignored. |
|
6. |
Remove the 2.xx floppy diskette and reboot your RADAR
|
|
7. |
Now (from the System Menu) select "UPGRADE SYSTEM" |
|
8. |
Power down RADAR, insert the 2.xx diskette and power up RADAR.
When RADAR prompts you to install 2.xx, choose YES. This will now be installed to SCSI drive #O. The following will now occur:
|
|
|
|
|
a. |
The front panel and RE8 LCDs should show the following status messages: |
|
|
|
"RADAR DIGITAL 24 TRACK"
"Booting from floppy"
|
|
b. |
You should see the messages: |
|
|
|
"Copying BOOTLOAD.386..."
"Copying BOOTPART.386..."
"Copying CM24.BIN..."
"Copying EM8B.BIN..."
"Copying KS1.ISP..."
"Copying RADARL.BIN..."
"Copying RADARH.BIN..."
"Updating KS1 ..."
|
| C. |
The LCD should now say 'Install Complete... Press Any Button'. Press a key and the LCD says "Remove Floppy, Power off & Reboot'. If the install has failed, it will be reported on the LCD. Contact Otari if problems are encountered. |
|
|
9. |
After 2.xx has been installed, power down RADAR, remove the 2.xx floppy diskette and reboot RADAR.
|
|
10. |
Enter the Diagnostics Menu and choose INIT drives. |
|
11. |
Re-initialize all drives in your system. |
|
12. |
You may now continue with your work. |
|
|
|
|
