NEW: ProFx (3538) Update Incl. MX6 and AC97

janez · Sep 28, 2009, 01:21 AM

here is another thought: So far I always installed the driver via the windows dialog "replace driver" after it had automaticly installed the sblive wdm driver. It does that each time after reboot and I couldn´t stop that process. Now I figured out that thats why the kx installer doesn´t recognize the card, even though I always uninstalled the wdm driver again before starting the kx installer.
I started the kx setup early enough once and it recognized the card as a 4832. But it doesn´t seem to make sense to let those two driver installers fight against each other about who is first. So it made more sense to me to use the "update driver" function and lead it to the driver by hand.

I doubt it makes any difference, but is there a way to stop that automatic windows driver installation for the sblive?

Another try brought the same results. ProFx310_48 won´t register.
I guess I´ll try the same computer with another card and let you know how it goes.
But not today ;-)

janez · Sep 28, 2009, 01:25 AM

Quote:

Originally Posted by Lex Nahumury

(I'll see if I can compile without that dependancy)

Janez, you can get Dependancy walker here;
Dependency Walker (depends.exe) Home Page
Just load the profxxxx.kxl and It will show if you have MSVCR80.DLL missing.

I´ll do that. Couldn´t I just search the windows folder for that file?

Tyrsonswood · Sep 28, 2009, 01:27 AM

Only way I know how to stop the windows "found new hardware/SBlive install is to completely remove those drivers from the machine..... this was only an issue for me once and that was several versions ago.....

Recently I've just installed KX while all that was going on it the background and it installed fine.... it must automatically replace the windows default SBlive driver.

Lex Nahumury · Sep 28, 2009, 01:48 AM

Quote:

Originally Posted by janez

I´ll do that. Couldn´t I just search the windows folder for that file?

Try this release. It doesn't depend on MSVCR80.DLL.

ProFx 3.11_48/49/50 Update:
Note: This is for 32-bit x86 only!!

http://members.home.nl/nahutec/ProFx/ProFx311_48.rar
Let me know if it works.

/Lex.

Lex Nahumury · Sep 28, 2009, 01:57 AM

Quote:

Originally Posted by janez

.... automaticly installed the sblive wdm
... but is there a way to stop that automatic windows driver installation for the sblive?

IIRC you could try delete c:\windows\inf\wdma10k1.inf

Lex Nahumury · Sep 28, 2009, 02:13 AM

Quote:

Originally Posted by Russ

@Lex,
BTW: I am not sure if you are aware of this, but the MX6/MX8 peak meters do not register the negative side of waveforms.

Yes, IIRC it saved (6+2)*2 = 16 abs(x) instructions at the expense of peak detection accuracy. No one (untill now lol) noticed or bothered.

Russ · Sep 28, 2009, 02:33 AM

Hehe, I thought that might be the case, but thought I would mention it, just in case.

BTW: No problems for me with ProFx 3.11.

Tyrsonswood · Sep 28, 2009, 02:46 AM

Ditto on the 3.11, Lex, working fine

Lex Nahumury · Sep 28, 2009, 02:48 AM

Quote:

Originally Posted by Russ

Hehe, I thought that might be the case, but thought I would mention it, just in case.

Don't you have anything better to do? j/k LoL

Quote:

Originally Posted by Russ

BTW: No problems for me with ProFx 3.11.

Yeah, I'm almost certain that that is the problem in janez case;
Xp sp2, fresh windows install, maybe no updates, no ie8, no .NET crap or whatever
hence no "msvcrt80 joy".

Lex Nahumury · Sep 28, 2009, 02:50 AM

Quote:

Originally Posted by Tyrsonswood

Ditto on the 3.11, Lex, working fine

Ok Thanks Tyrs!
I read you used it on win7 too?
What machine specs?

Tyrsonswood · Sep 28, 2009, 03:01 AM

Quote:

Originally Posted by Lex Nahumury

Ok Thanks Tyrs!
I read you used it on win7 too?
What machine specs?

The win7 machine (dual booting w/xp) is the one I haven't built a dsp on yet, but did register the FX in XP. I should go check that for you because I don't know if I registered them in win7. It's the dual PIII in my system specs.

Right now it has only 512meg but it runs fine, a bit slow. I've got a SB0060 with a livedrive IR in there.

I'll go check those plugins in win7 and post back.

Lex Nahumury · Sep 28, 2009, 03:10 AM

Quote:

Originally Posted by Tyrsonswood

It's the dual PIII in my system specs.

Right now it has only 512meg but it runs fine, a bit slow. I've got a SB0060 with a livedrive IR in there.

I see. I expected win 7 on the 3gig machine you mentioned.

Lex Nahumury · Sep 28, 2009, 03:17 AM

How about it Janez!
It's 3:20 in the middle of the night over here and I just compiled a version specially for you LOL!

Tyrsonswood · Sep 28, 2009, 03:36 AM

Quote:

Originally Posted by Lex Nahumury

I see. I expected win 7 on the 3gig machine you mentioned.

Yeah me too, but the RC didn't like dual soundcards and KX so it got removed long ago from that machine. XP runs better on it anyways so I won't be doing the win7 upgrade right now. The PIII with Win7 was just to see how it ran on such a machine.... lol

About your plugins on Win7..... Big thumbs up! and I tried both the 3.10 and 3.11_48 versions on Win7 7100 RTM 32bit with the 3550 KX drivers on a live! SB0060. I just did a simple DSP so I didn't check each plugin, ADC and K1lt work as expected.

Lex Nahumury · Sep 28, 2009, 03:52 AM

Quote:

Originally Posted by Tyrsonswood

XP runs better on it anyways so I won't be doing the win7 upgrade right now.

Yeah, me neither. XP works fine for me too but as usual in the end there's no escaping the "upgrade bleus" I'm afraid.
Thanks for the tests/feedback!

janez · Sep 28, 2009, 03:23 PM

Quote:

Originally Posted by Lex Nahumury

How about it Janez!
It's 3:20 in the middle of the night over here and I just compiled a version specially for you LOL!

I guess we are in the same time zone. Sorry, I got some sleep in the meantime ;-)

Now it works
I started dependency walker and it was bitching about the kx mixer and some other kx related file. Nothing about msvcr80.dll, which is not present on that computer. So I figured there was something corrupt about my installation.
What I used to do was to remove the sblive wdm driver before installing kx and it wouldn´t recognize the card, as I described.
Deleting the wdma10k1.inf and other 10k1 related files is not enough to stop Windows from installing the driver. The 10k1somethin.sys is still in Driver.cab and I couldn´t delete it from there.
Now I booted after deinstallation of kx and just let Windows do its thing and left the driver alone before starting the 3550 installer. Now it recocnized the card (as a 4832). And registering ProFx311_48 after that was no problem. And it works, too :-)

But maybe the installation was ok before already, as I did not try to register ProFx310_48 but went straight to the Version 311_48. So I didn´t compare whether the last installation made any diffrence. But I started dependency walker again and it misses
kxapi.dll
kxmixer.exe
msjava.dll
in both cases (310 and 311)

although it works.
So I think that last compilation was the solution.
You guys are great, did I mention that? :-)
Now all I need are the Plugins in Uniform, but I guess thats a subject for another thread.
Thanx
Janez

Lex Nahumury · Sep 28, 2009, 04:10 PM

Quote:

Originally Posted by janez

But I started dependency walker again and it misses
kxapi.dll
kxmixer.exe
msjava.dll
in both cases (301 and 311)

That is normal behaviour since Dep walker looks in certain system dirs only
while kxapi.dll etc reside in kX install dir.
Nothing to worry about, Dep walker almost always reports some missing stuff.

Quote:

Originally Posted by janez

although it works.
So I think that last compilation was the solution.

Good, although I am still curious if your problems were msvc80.dll related.

Quote:

Originally Posted by janez

You guys are great, did I mention that? :-)

Don't know if you did, but we can't hear it enough

Btw; The trick with deleting the wdma10k1.inf or oem#.inf files and whatnot must work in preventing Windows to install it's default sblive wdm driver.
I have done so in the past but don't remember the exact details.
The exact procedure has been posted somewhere in the general section.

janez · Sep 28, 2009, 05:17 PM

Quote:

Originally Posted by Lex Nahumury

Good, although I am still curious if your problems were msvc80.dll related.

How can I find that out for you. Should I try to register the previous version again? Did you compile it into the new file?

Quote:

Originally Posted by Lex Nahumury

Don't know if you did, but we can't hear it enough

Then here you go: you guys are awesome. :-)

I´m very impressed

Quote:

Originally Posted by Lex Nahumury

Btw; The trick with deleting the wdma10k1.inf ...

Didn´t seem to matter after all. Apparently I should have ignored it from the beginning on, instead of trying to get rid of it.

Lex Nahumury · Sep 28, 2009, 05:21 PM

Quote:

Originally Posted by janez

How can I find that out for you. Should I try to register the previous version again?

Yes you can simply try to register the previous 3.10 kxl.
The 3.10 needs msvcrt80.dll, the 3.11 does not.

janez · Sep 28, 2009, 05:44 PM

it produces the same error message: invalid program library

Lex Nahumury · Sep 28, 2009, 05:47 PM

Quote:

Originally Posted by janez

Did you compile it into the new file?

No, it links to older msvcrt dll version.

janez · Sep 28, 2009, 06:01 PM

I downloaded the msvcr80.dll. Does it just have to be there, in sys32 or so? What does it do?

Russ · Sep 28, 2009, 06:49 PM

If you add the kX 3550 directory to your System PATH, then Dependency Walker will be able to find the kX dll's (you should add kX to the PATH anyway, as it is needed for some other things).

Regarding msvcr80.dll, that is not a file installed by kX, or ProFX (if that is what you were thinking), it is a MS file that is usually installed from some Windows update, etc. Mine is in c:\windows\winsxs\... but you can probably just put it in the System32 directory.

Lex Nahumury · Sep 28, 2009, 07:31 PM

Quote:

Originally Posted by janez

it produces the same error message: invalid program library

Yep. Ok then it's solved; msvcrt80.dll is missing on your system.

I wouldn't mess with randomly copying windows system DLLs.
Either use the 3.11 kxl I compiled for you, or install some windows update like the .NET framework.
Either way it doesn't influence kX driver functionality or my plugins in anyway.
Like I said before, most people have msvcrt80.dll automaticly installed through windows update.

janez · Sep 28, 2009, 07:40 PM

Quote:

Originally Posted by Russ

(you should add kX to the PATH anyway, as it is needed for some other things).

like what?

Russ · Sep 28, 2009, 07:45 PM

Quote:

Originally Posted by janez

like what?

It is needed for some soundfont stuff (related to sfman32.dll).

janez · Sep 28, 2009, 09:27 PM

thanx, thats a relevant piece of information. Is there any further documentation about that?
I havn´t gotten around to really testing the midi and synth functionality but on another machine I used to use soundfonts a lot with the creative drivers. There are a couple of nice tools around the sf2 format, some of them with driver support and realtime editing.
But I guess thats offtopic in this thread.

Russ · Sep 28, 2009, 09:32 PM

It is only with newer versions of kX (3548 and up). kX used to place these files in the System32 directory, but it does not do this in newer versions of the driver, so programs (like Vienna) that might be looking for these files cannot find them. Eugene mentioned it in the release notes for 3550 (and I mentioned it in the 3548 (x86) Bug Reports thread).

janez · Sep 28, 2009, 09:46 PM

so shouldn´t the installer write that path information, too? Quite a few users might stumble over this one.
On my main machine I still use 3545

Russ · Sep 28, 2009, 10:00 PM

Quote:

Originally Posted by janez

so shouldn´t the installer write that path information, too? Quite a few users might stumble over this one.
On my main machine I still use 3545

Maybe... or maybe registering the dll's... I do not know... But yeah, this is getting OT for this thread.

Sep 28, 2009, 01:21 AM	#721
janez HardwareHeaven Lover Join Date: Oct 2008 Posts: 118 Rep Power: 26	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 here is another thought: So far I always installed the driver via the windows dialog "replace driver" after it had automaticly installed the sblive wdm driver. It does that each time after reboot and I couldn´t stop that process. Now I figured out that thats why the kx installer doesn´t recognize the card, even though I always uninstalled the wdm driver again before starting the kx installer. I started the kx setup early enough once and it recognized the card as a 4832. But it doesn´t seem to make sense to let those two driver installers fight against each other about who is first. So it made more sense to me to use the "update driver" function and lead it to the driver by hand. I doubt it makes any difference, but is there a way to stop that automatic windows driver installation for the sblive? Another try brought the same results. ProFx310_48 won´t register. I guess I´ll try the same computer with another card and let you know how it goes. But not today ;-) Last edited by janez; Sep 28, 2009 at 03:07 PM.

Sep 28, 2009, 02:33 AM	#727
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 Hehe, I thought that might be the case, but thought I would mention it, just in case. BTW: No problems for me with ProFx 3.11.

Sep 28, 2009, 03:17 AM	Thread Starter #733
Lex Nahumury DH Senior Member Join Date: Jan 2003 Location: The Netherlands Posts: 1,930 Rep Power: 62	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 How about it Janez! It's 3:20 in the middle of the night over here and I just compiled a version specially for you LOL!

Sep 28, 2009, 05:44 PM	#740
janez HardwareHeaven Lover Join Date: Oct 2008 Posts: 118 Rep Power: 26	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 it produces the same error message: invalid program library

Sep 28, 2009, 06:01 PM	#742
janez HardwareHeaven Lover Join Date: Oct 2008 Posts: 118 Rep Power: 26	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 I downloaded the msvcr80.dll. Does it just have to be there, in sys32 or so? What does it do?

Sep 28, 2009, 06:49 PM	#743
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 If you add the kX 3550 directory to your System PATH, then Dependency Walker will be able to find the kX dll's (you should add kX to the PATH anyway, as it is needed for some other things). Regarding msvcr80.dll, that is not a file installed by kX, or ProFX (if that is what you were thinking), it is a MS file that is usually installed from some Windows update, etc. Mine is in c:\windows\winsxs\... but you can probably just put it in the System32 directory.

Sep 28, 2009, 09:27 PM	#747
janez HardwareHeaven Lover Join Date: Oct 2008 Posts: 118 Rep Power: 26	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 thanx, thats a relevant piece of information. Is there any further documentation about that? I havn´t gotten around to really testing the midi and synth functionality but on another machine I used to use soundfonts a lot with the creative drivers. There are a couple of nice tools around the sf2 format, some of them with driver support and realtime editing. But I guess thats offtopic in this thread.

Sep 28, 2009, 09:32 PM	#748
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,507 Rep Power: 61	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 It is only with newer versions of kX (3548 and up). kX used to place these files in the System32 directory, but it does not do this in newer versions of the driver, so programs (like Vienna) that might be looking for these files cannot find them. Eugene mentioned it in the release notes for 3550 (and I mentioned it in the 3548 (x86) Bug Reports thread).

Sep 28, 2009, 09:46 PM	#749
janez HardwareHeaven Lover Join Date: Oct 2008 Posts: 118 Rep Power: 26	Re: NEW: ProFx (3538) Update Incl. MX6 and AC97 so shouldn´t the installer write that path information, too? Quite a few users might stumble over this one. On my main machine I still use 3545