PCI bus overflow on upgrade
Yo Sub - I've followed all the relevent advice offered by all of the planet z members and my BX based computer still chokes.But the 'old' 440BX still has great PCI performance if you follow any of the advice I've given over & over in the past, you can avoid PCI overflows on those, too!
I think, from Paul Tanti's reply, that something IS going on, some cock up HAS been made, and that your advice may not help me at all.
Well, many thanks for your offer of help remixme, but I've gotta remind you that v2.01 was working fine with my system (as described below). Now that I've started projects with v3 I'm very reluctant to go back to v2 and have to build all my projects again (from text notes I guess... v boring).
Still, just in case you know something I don't about the way the new Pulsar software has changed the handling of the PCI bus (priviliged info indeed) here's my setup:
Asus P2B-s (old BX - SCSI onboard)
192MB RAM
IBM IDE HD
Internal Zip drive on IDE
Pulsar v1
56k modem on PCI
Cheapo 8MB AGP card
Midiman 4x4 midi interface on USB port
I've ripped out my old Terratec EWS64 from it's ISA port: system runs better generally but no change in PCI resource.
I've also tried removing the modem: no change to performance.
My sampler's connected to my computer via SCSI.
I've applied all recommendations made in the tips & tricks section of planet z.
But really mate, something has changed with regards to PCI bus handling.
<font size=-1>[ This Message was edited by: Sam Glass on 2002-02-26 01:48 ]</font>
<font size=-1>[ This Message was edited by: Sam Glass on 2002-02-26 01:53 ]</font>
Still, just in case you know something I don't about the way the new Pulsar software has changed the handling of the PCI bus (priviliged info indeed) here's my setup:
Asus P2B-s (old BX - SCSI onboard)
192MB RAM
IBM IDE HD
Internal Zip drive on IDE
Pulsar v1
56k modem on PCI
Cheapo 8MB AGP card
Midiman 4x4 midi interface on USB port
I've ripped out my old Terratec EWS64 from it's ISA port: system runs better generally but no change in PCI resource.
I've also tried removing the modem: no change to performance.
My sampler's connected to my computer via SCSI.
I've applied all recommendations made in the tips & tricks section of planet z.
But really mate, something has changed with regards to PCI bus handling.
<font size=-1>[ This Message was edited by: Sam Glass on 2002-02-26 01:48 ]</font>
<font size=-1>[ This Message was edited by: Sam Glass on 2002-02-26 01:53 ]</font>
I suppose it is possible that PCI handling has changed between software versions. Although Subhumans experience proves otherwise.
For me fixing the problem involved changing the amount of PCI latency allocated to each particular card, I increased the Pci latency for pulsar to 128. I installed a pci latency patch, and disabled usb, disabled IRQ for USB (strange!) and removed sblive. Disabled ACPi, and made sure each card has its own interrupt
But no one of these things worked by themselves it was only a combination of all of them that solved the problem for me.
I have a thread http://www.planetz.com/forums/viewtopic ... &forum=1&9
Which detailes the steps, I dont know if you have tried this. Not everything there applies to you.
But the result is 5 masterverbs, on pulsar 1.
But I can imagine how annoying it is, to have to waste time fixing a system that worked perfectly before.
Are you sure you didn't change anything else at the time of installing Pulsar?
Did you update to the driver that came with V3? (stupid question I know)
But it is possible that updating the driver changed the IRq assignment of the card, and that could cause PCi overflow. Just a guess.
(Does anyone know; as I don't have V2 software, does the V2 driver work with v3 sofware. Thats a very long shot, sort of grasping a straws to install V2 driver with v3 software)
I think if I was in your position I would reinstall the OS, installing reference drivers for graphics card (geared for stability not speed) Install pulsar, and your HDD, that would be it, everything else taken out or disabled; USB, scsi, modem, zip.
I know by this stage if it overflowed, in your postition I would be throwing the bloody thing out the window. But just before that Id see if tweaking the Pci allocations made any difference. Then chuck the thing out the window. If the computer is still in one piece after the Id go back to v2 software.
For me fixing the problem involved changing the amount of PCI latency allocated to each particular card, I increased the Pci latency for pulsar to 128. I installed a pci latency patch, and disabled usb, disabled IRQ for USB (strange!) and removed sblive. Disabled ACPi, and made sure each card has its own interrupt
But no one of these things worked by themselves it was only a combination of all of them that solved the problem for me.
I have a thread http://www.planetz.com/forums/viewtopic ... &forum=1&9
Which detailes the steps, I dont know if you have tried this. Not everything there applies to you.
But the result is 5 masterverbs, on pulsar 1.
But I can imagine how annoying it is, to have to waste time fixing a system that worked perfectly before.
Are you sure you didn't change anything else at the time of installing Pulsar?
Did you update to the driver that came with V3? (stupid question I know)
But it is possible that updating the driver changed the IRq assignment of the card, and that could cause PCi overflow. Just a guess.
(Does anyone know; as I don't have V2 software, does the V2 driver work with v3 sofware. Thats a very long shot, sort of grasping a straws to install V2 driver with v3 software)
I think if I was in your position I would reinstall the OS, installing reference drivers for graphics card (geared for stability not speed) Install pulsar, and your HDD, that would be it, everything else taken out or disabled; USB, scsi, modem, zip.
I know by this stage if it overflowed, in your postition I would be throwing the bloody thing out the window. But just before that Id see if tweaking the Pci allocations made any difference. Then chuck the thing out the window. If the computer is still in one piece after the Id go back to v2 software.
win98 lite....
hmmmmm.....is it worth it? I don't have problems now with 98SE but if I could eek out a few more clock cycles...maybe a post of optimizing 98Lite vs. 98 would be helpful.
I learn something new everyday. I've not experienced the PCI problems at all with the new upgrade to 3.1. In fact, works great. I850 chipset! I'm so glad I went that way!
hmmmmm.....is it worth it? I don't have problems now with 98SE but if I could eek out a few more clock cycles...maybe a post of optimizing 98Lite vs. 98 would be helpful.
I learn something new everyday. I've not experienced the PCI problems at all with the new upgrade to 3.1. In fact, works great. I850 chipset! I'm so glad I went that way!
You the man remixme: thanks v much for another helpful post.
When I discovered the problem, I had done a fresh up-to-date reinstall of everything, drivers / minimum apps etc.
My BIOS is maxed out PCI latency-wise. All settings are configurable on boot on my mobo.
ALL win98 tweaks have been applied.
Lastly, though I do have a 4 ins/outs midi box running from USB, I didn't have this when I first started getting overflow problems. And I only got overflow with v3, not v2, with exactly the same devices loaded!
I'll possibly try again at the weekend, but I did make sure I'd tried everything before going off complaining to Creamware. I actually reformatted & went back to V2 with all Windows tweaks - no prob - then reformatted again, tweaked, and went to v3 and the v2 project PCI-overflowed madly. Back to v2 - fine. Back to v3 - cos I had to continue certain projects - no surprises, the trial project overflowed again.
I've been working with semi-pro audio cards on the PC for five years now and I know what bitches they can be, so I know alot of tricks. I had a Terratec EWS64 which was touchy as hell, kept mucking up the OS, so reformat & retweak & reinstall is well practiced.
There IS a problem with the v3 system.
Why would Paul Tanti ask me to look forward to the next release if they hadn't already identified the prob?
<font size=-1>[ This Message was edited by: Sam Glass on 2002-02-28 07:00 ]</font>
When I discovered the problem, I had done a fresh up-to-date reinstall of everything, drivers / minimum apps etc.
My BIOS is maxed out PCI latency-wise. All settings are configurable on boot on my mobo.
ALL win98 tweaks have been applied.
Lastly, though I do have a 4 ins/outs midi box running from USB, I didn't have this when I first started getting overflow problems. And I only got overflow with v3, not v2, with exactly the same devices loaded!
I'll possibly try again at the weekend, but I did make sure I'd tried everything before going off complaining to Creamware. I actually reformatted & went back to V2 with all Windows tweaks - no prob - then reformatted again, tweaked, and went to v3 and the v2 project PCI-overflowed madly. Back to v2 - fine. Back to v3 - cos I had to continue certain projects - no surprises, the trial project overflowed again.
I've been working with semi-pro audio cards on the PC for five years now and I know what bitches they can be, so I know alot of tricks. I had a Terratec EWS64 which was touchy as hell, kept mucking up the OS, so reformat & retweak & reinstall is well practiced.
There IS a problem with the v3 system.
Why would Paul Tanti ask me to look forward to the next release if they hadn't already identified the prob?
<font size=-1>[ This Message was edited by: Sam Glass on 2002-02-28 07:00 ]</font>
it's best to put v3 i/o's and devices in v2 projects when working in v3.(rebuild/replace) if that's too much trouble,keep v2 on your machine WITH v3 and finish old stuff in v2 and start new stuff in v3.(i built new projects it was worth it)
oh yeah-save the old project too!
<font size=-1>[ This Message was edited by: garyb on 2002-02-28 10:22 ]</font>
oh yeah-save the old project too!
<font size=-1>[ This Message was edited by: garyb on 2002-02-28 10:22 ]</font>
I believe the new devices are automatically used - the project files reference components, they aren't embedded. So I think the new V3 devs were loaded up when opening the old V2 project in the V3 environment. I'd better check this tho.
I can't do both systems on same machine so easily cos of Pulsar drivers. Ideally I'd multiboot and my HD ain't set up for that at the mo. Anyway, WTF! Why should I for god's sake?
And anyway, it isn't just the old project. New projects have piss poor PCI performance too.
Anyway, this ain't getting me anywhere. Thanks for all your offered help: I'll wait till V3.1
Pulsar still kicks ass, hobbled or not
I can't do both systems on same machine so easily cos of Pulsar drivers. Ideally I'd multiboot and my HD ain't set up for that at the mo. Anyway, WTF! Why should I for god's sake?
And anyway, it isn't just the old project. New projects have piss poor PCI performance too.
Eh? Course I saved the old v2 project and didn't overwrite with v3. I'm not a prat amigo.oh yeah-save the old project too!
Anyway, this ain't getting me anywhere. Thanks for all your offered help: I'll wait till V3.1
Pulsar still kicks ass, hobbled or not
<i>New projects have piss poor PCI performance too. </i>
Absolutely zero change on i815/i845/i850 boards between V2.04 and V3.01: I have tested these extensively. Do you have Pulsar V3.01 installed? Garyb is correct, you need to rebuild your projects in V3 for "complete" stability and to <i>be sure</i> you're using newer atoms. SOME things are referenced, other things are NOT.
There IS a difference between 2.04a and 3.0, however (most notably with the STS samplers), but 3.01 fixes this as far as I have seen. In any case I get the same number of reverbs & STS voices under both on these sytems.
BTW - I believe Paul told you about the next Pulsar version - 3.01 - because you were probably on V3 when you asked the first time.
Anyway, you can run V2 and V3 on the same machine. Copy V3's "Sim*.dll" files overtop of your V2's install files by the same name, and now you can run both.
Absolutely zero change on i815/i845/i850 boards between V2.04 and V3.01: I have tested these extensively. Do you have Pulsar V3.01 installed? Garyb is correct, you need to rebuild your projects in V3 for "complete" stability and to <i>be sure</i> you're using newer atoms. SOME things are referenced, other things are NOT.
There IS a difference between 2.04a and 3.0, however (most notably with the STS samplers), but 3.01 fixes this as far as I have seen. In any case I get the same number of reverbs & STS voices under both on these sytems.
BTW - I believe Paul told you about the next Pulsar version - 3.01 - because you were probably on V3 when you asked the first time.
Anyway, you can run V2 and V3 on the same machine. Copy V3's "Sim*.dll" files overtop of your V2's install files by the same name, and now you can run both.
so do i have to install v2 again? or??On 2002-03-01 08:56, subhuman wrote:
<i>New projects have piss poor PCI performance too. </i>
Absolutely zero change on i815/i845/i850 boards between V2.04 and V3.01: I have tested these extensively. Do you have Pulsar V3.01 installed? Garyb is correct, you need to rebuild your projects in V3 for "complete" stability and to <i>be sure</i> you're using newer atoms. SOME things are referenced, other things are NOT.
There IS a difference between 2.04a and 3.0, however (most notably with the STS samplers), but 3.01 fixes this as far as I have seen. In any case I get the same number of reverbs & STS voices under both on these sytems.
BTW - I believe Paul told you about the next Pulsar version - 3.01 - because you were probably on V3 when you asked the first time.
Anyway, you can run V2 and V3 on the same machine. Copy V3's "Sim*.dll" files overtop of your V2's install files by the same name, and now you can run both.
help !
in order to get rid of pci-overflow-messages I want to get rid of USB (I have tested this on different installations and in my system the problems are coming from usb (I have a ASUS CUBX with intel 440BX chipset) and use a pulsarI with a luna II and a lunabreakoutbox using 8 i/o´s at once.
the strange thing: I deactivated USB in the BIOS Settings correctly; still everytime win98se boots up it finds new usb-devices I deinstalled before. who can I get rid of the usb-devices ?
thilowski
http://www.thilohuber.de
in order to get rid of pci-overflow-messages I want to get rid of USB (I have tested this on different installations and in my system the problems are coming from usb (I have a ASUS CUBX with intel 440BX chipset) and use a pulsarI with a luna II and a lunabreakoutbox using 8 i/o´s at once.
the strange thing: I deactivated USB in the BIOS Settings correctly; still everytime win98se boots up it finds new usb-devices I deinstalled before. who can I get rid of the usb-devices ?
thilowski
http://www.thilohuber.de
Thanks Sub! You are right, I only have first release V3 installed. Tanti's post talks about v3.1 but he isn't the most thorough email writer so you may be right there too.BTW - I believe Paul told you about the next Pulsar version - 3.01 - because you were probably on V3 when you asked the first time.
Anyway, you can run V2 and V3 on the same machine. Copy V3's "Sim*.dll" files overtop of your V2's install files by the same name, and now you can run both.
Will let y'all know how it goes.
In order to keep win98 from finding & installing USB drivers, disable the USB support on your mobo. You might be able to do this in bios (i'd think most boards would do this) or if not find the appropriate jumper on the mobo and set it.
I'm also wondering if Pulsar1 is worse from the pci perspective than Pulsar2....
I'm also wondering if Pulsar1 is worse from the pci perspective than Pulsar2....