My (-9093) problem

Hi seems like this 9093 is a reoccurance issue, anyway here is my 2 cents worth of problem... I get the error when I have a few duplicated chunk of audio record on the same track. For example short 2 sec drum loop duplicate a few time. usally it would play back the first 4 sec and than comes the 9093. The problem goes away if I do a "Shift Alt 3" on it( cant remeber the name of the function). As a matter of interest, I can play back the demo, the full demo, with out any problem and as we know the demo had a lot of loop and duplicated parts. My system is Abit BE6 M/B PIII 500 128 Ram 2 x fire ball Udm66 13GB H/D a network card which I disable b4 I launch PT Adaptec SCSI controller Can someone share somelight...{;o) Thanks

Hey, I had a similar problem and I have a similar set up 2 you, Abit m/b, udma 66 drive etc. I found that taking my UDMA 66 drive and putting it on a UDMA 33 slot solved the problem. I think there may be something with the High point UDMA66 controller that Pro tools doesn't like. My system runs like jam now. Steve C

Yes, there have been multiple reports of people having trouble with the HighPoint UDMA66 controller driver. It's my strong suspicion that this driver does something unfriendly like disable HW interrupts or run at an elevated priority for milliseconds at a time (an eternity on today's processors). Drivers are not supposed to do things like this, but can often get away with it because the user doesn't see any obvious negative side-effects. However, with a real-time low-latency system like PTLE, these things come to the forefront very quickly. Until we can properly investigate this problem and try to find a solution, I would recommend not using this UDMA66 controller and driver with PTLE. The maximum disk requirements of PTLE (24 tracks of 24-bit 48kHz audio with 30ms crossfades every 300ms) can be fullfilled with a single fast drive on a standard IDE controller. Eric Day DAE Engineer

I have the same setup as you and have had the exact same problem but only in 24 bit mode. I have put my data drives on the 33 bus and my OS drives (two different Windows98 installations) on the 66 bus. Works great I also had random lockups with the 66 bus when using the zoomer tool in 24 bit mode. I have only just changed my configuration, so hopefully the problem stays away. My hard drives are Western Digital 8.4 gig (OS 1), IBM 13.6 gig (OS 2), Seagate Barracuda 30.6 gig (data 1) and IBM 34.4 gig (data 2). I'm getting data rates of about 13 M/s on the 33 bus vs 16-17 M/s on the 66 bus. Not a great difference and more than enough in both cases for 24 tracks in 24 bit mode. The drives all contain partitions.

Did a 24 bit mastering job yesterday with a lot of zooming and editing and recording surround channel (LCR LS RS) information to HDD with not one hiccup. So far, so good. So, at this stage, it looks like OS on 66 bus and data on 33 bus seems to be stable for me

Thanks Doc very useful...I had just converted everything to 33 and seem to be stable now...so next stop put my OS back to 66 and see how I go...{;o)

I'm in the same predicament, and being new to Windows (I'm an old Mac guy), I want to know if there is an easy way to deactivate the 66 driver. Both my O/S and data drives are connected to the UDMA 33/66 slot on the Abit M/B (slot 4), and I would like to leave the O/S at 66. This seems like something relatively straight foward, but this IS windows! Thanks.