Ones again...Pops 'n Clicks !!
Setup:
Pulsar PC:
Intel PIII 700, Mobo Asus P2B(440BX),512mb SDRAM,IBM GXP60 40gb ,Matrox 400DH, LAN adapter
2 x Pulsar II v3.01 (ADAT masterclock), connected to sequencer via MIDI
Sequencer PC (Logic 4.81):
Intel PIII 733, Mobo Asus P2B-F(440BX),512mb SDRAM, IBM GXP60 40gb ,Matrox 450DH, Matrox Millenium II PCI, LAN adapter, SBlive! (Kx Project driver

), RME Digi9636 Hammerfall(ADAT slave clock), Adaptec 2904CD SCSI Adapter.
2 x Yamaha O2R v2.16 (4 x ADAT, 2 x TC Unity FX boards, both ADAT-slaveclock)
Emagic AMT8
Roland midi masterkeyboard
Rode Classic (1)
Genelec 1030A
On the Pulsar PC we have a dualboot system:
-Primary Partition 1 = Win Millenium with Pulsar v2.04
(STS4000,POISON,Modular 2)
-Primary Partition 2 = Win XP with Pulsar v3.01
(STS4000,POISON,Modular 2)
The RME Hammerfall and the 2 Pulsar's are connected to 2 O2R's via ADAT optical cables which works absolutely fine under Win ME + Pulsar v2.04 , except for WinXP+Pulsar v3.01.....we get hard ticks and pops in our sound (randomized)...
Here's our XP+P2v3.01 tweak summary:
- ULLI: latency = 18ms, we've also tried other latency settings, but same problem.
- Preload buffer (hardware properties of Pulsar) tried all modes (low, mid,high).....same problem
- Sample Rate = 48khz, 44.1khz.....same problem
- Video display settings: 2 monitors set to 1024/768@75hz, 16bit color
So it seems to be a software problem of v3.xx. I meantime i've discovered the STS samplers (4000, 2000P) are the evil source..... all synths are fine.
By the way: we never have had a PCI overflow with our motherboard (ASUS P2B/440BX)
Please anybody !! Please help us !!!!
thanx
Miguel Vasconcellos