In clean Pulsar3.01 install on clean XP install, Pulsar locks up very easily, usually within 20-30 mouse-clicks, or a minute or two after starting the app.
When this happens, the my mouse still moves the cursor in pulsar, and cursor changes correctly over modules versus background, but no click response at all, either menus or module controls. Only way out is to kill pulsar in task manager and restart.
This occurs merely when clicking around within pulsar environment, such as setting up projects and looking at dialogues boxes. New setup; I have not even started streaming to audio software, though I have successfully tested synth modules triggered through hardware MIDI-in, and played through Pulsar hardware audio-out. The lockup can happen while doing this, but also with no signals travelling through card at all, merely while clicking around various Pulsar controls. Also, this lack of response to clicks is only in pulsar - I can move cursor to non-pulsar parts of desktop and all is fine.
Can't yet identify a specific series of actions causing this.
I have: clean XP install, with no other apps in yet, virgin installs of 3.0 pulsar drivers and software, followed by 3.01. ACPI disabled at beginning of XP install, only other tweaks to XP involve disabling sexier GUI stuff. I run a CUSL2, 512, bios v1002, Matrox dual on AGP, IBM 14.5G on one onboard channel, plex 12/10/32 on other, 2x30G IBMs on Promise Fastrack100 on slot 3.
my CW cards (P2 and Luna) are in slots 2 and 6, respectively. I have both on IRQ4, forced in BIOS, with no conflicts indicated on this IRQ or any other.
My best guess would be that my problem involves XP or BIOS settings. Any suggestions what to try to remedy this??
TIA
