Firewire drive question

Discussion in 'Converters / Interfaces' started by jonyoung, Nov 20, 2004.

  1. jonyoung

    jonyoung Well-Known Member

    Hey gang, I recently bought a couple of drives to use in a firewire case I have, for the purpose of backing up mixes done in Sonar. After picking some brains at the Sonar forum, I went ahead and formatted the drives (60G Maxtor Diamond Plus 9) in NTFS from my DAW, running W2k Pro. I just tried to backup some mixes, and when I start the firewire case, the drive is showing up as if it's associated with a Panasonic DVD multidrive I have as master on the 2nd IDE bus. I thought at first it might be that the jumpers on the drives were wrong (cable selected) so I set one to slave, but the same thing happens, I can't get the system to see the drive. I have multple drives that are FAT32 format for transferrring files from my Mackie SDR2496 to the DAW to import Sonar, no problems at all. Interestingly, if I summon up a disk defrag utility, it sees the drive no problem. Any thoughts, suggestions greatly appreciated, as I have more than a weeks worth of mixes to backup!!!!
  2. michaeltk

    michaeltk Guest

    Sorry, but you lost me. Please be more specific about how the drive is "showing up as if it's associated with" the DVD drive. Showing up in what program? Windows explorer? And how is it "associated" with the DVD drive?
  3. jonyoung

    jonyoung Well-Known Member

    The drives I have for Sonar backup are labeled "Sonar b/u1" or "Sonar b/u2". When I start the firewire case up, "My Computer" shows the drive as K:, which is the designation for the Panasonic DVD RAM utility (DVD drive brand). If I right click on K: and choose properties, I get a window with various options ie: scan drive sectors, defrag, etc..... a list of various drives shows up, and the 1394 Oxford Chipset device (firewire) shows up with the proper label (Sonar b/u1) and the same characteristics as C: and D:, my two internal drives. What's happening apparently is that the DVD drive and associated utlilties are seizing control of the firewire port with the NTFS formatted drives. I don't have the same problem with the drives that are formatted with the Mackie version of FAT32. Is this making more sense? BTW, thanks for your interest.
  4. inLoco

    inLoco Active Member

    i think that win 2000 doesn't work with ntfs! only fat 32!
    do a google search with ntfs and fat 32 and i'm sure you'll find this!
    don't know if i'm right but i think it's the problem... (tell me if it is...)
  5. jonyoung

    jonyoung Well-Known Member

    Well , I formatted the new drives from W2K, so NTFS seems to be the protocol. FWIW, I use W2K Pro, maybe Home version is FAT32? On a side note, I backed up my mixes on one of my FAT32 drives today, think I'll just reformat these two drives that way and be done with it.
  6. scottme

    scottme Guest

    There is only Windows 2000 Professional (no home). It is the equivalent of Windows Xp Professional. And yes, NTFS is the native file format for W2k.

    Did you add more than the firewire case at the same time (other hardware?). Although I have Xp Pro, I recently added an external USB2 DVD and a new SCSI drive and I had a similar thing happen before I pulled the USB cable, restarted and reinserted the USB drive when windows loaded (hotplug).

    Check the properties of the drive (right click or harware manager) or have a look in Disk Manager (in Computer Management). Check that the disk manager services (Logical Disk Manager and Logical Disk Manager Admin - are in XP, not sure about 2k).

    Try starting up with the Panasonic disconected.

    Hope these help - it's been a while since I used w2k

  7. jonyoung

    jonyoung Well-Known Member

    scott, I've been using the firewire drive with the FAT32 drives with no problems for several months. This only showed up on the drives I formatted NTFS, and no other hardware added. I'm taking the easy way out . I initially went with NTFS on a recommendation based on a 4Gig file size limit in FAT23. Well, all my 24 track Sonar projects are in the 750Meg range, so FAT32 is just fine.

Share This Page