If you have the Pinnie installed in non PnP:
1)  Make sure the Audio driver works
2)  Remove any Main Synth (Kurzweil) driver from the Device Manager 
    in Safe mode
3)  Reboot in normal mode
4)  In Device Manager:
      Highlight Computer | click Properties | click Reserve Resources | 
      make sure IRQ is selected | click Add | In the Value field type 0X 
      (where "X" is the IRQ that you want to use) | say Yes to warnings
5)  Reboot the system without installing anything.
    (IMPORTANT: This implies that the Pinnie is in non PnP)
6)  While loading Windows watch for any error messages
7)  Repeat Shut Down and Reboot a couple of times without changing anything
    in your system. Just watch.
8)  From the Device Manager Un-reserve the previously Reserved IRQ (05) 
    or whatever.
9)  Reboot the system.
10) Reinstall the Audio & Kurzweil > Keep your fingers crossed....

If it works this time only but NOT next time you reboot, then you know for 
sure that something in the motherboard resources does not let you play.

If it does not work at all:
1a) Try the above procedure with another IRQ 
2a) Un-reserve from the Bios the ISA/Legacy setting for the candidate IRQ
3a) Reset Configuration Data in the Bios 
4a) Give it a spin again

If still no go:
1b) Remove the Pinnie from the system
    (carefully please as frustration can cause serious problems)
2b) Set it to PnP mode
3b) Repeat steps 2a & 3a above before rolling into Windows
4b) Let Windows detect the card (both audio & MIDI)

If still no luck:
From both Normal & Safe mode count the total number of 
"IRQ Holder for PCI Steering" you have.

If the number is greater than the known PCI devices in your system,
you found the problem: One (or more) redundant "IRQ PCI Steering Holder"
is holding resources rendering them unusable for ISA.
PCI architecture overrules.

If this is the case, in Safe mode, you would need to remove ALL OF THEM 
- as there is no way of knowing which is holding what - which means that 
you would need to reinstall all your PCI devices from scratch.

This time it should work.

NOTE:
   Although this Troubleshooting routine applies specifically to the problem
   stated in the title, it can generally apply to typical Windows conflicts
   for any device.


___________________________________________________________________________