frew

Hello,

When I boot up, the kx dsp always reverts to it's default settings, even though I've created a custom configuration, saved it as a .kx file and loaded the custom .kx and exited kx mixer.

In the past this all worked fine, no problems, and system booted up and kx kept my configuration intact...but now everytime I restart my computer I have to go to kx dsp and reload my config file into kx dsp.

And ideas what I can do about this? What may have changed?

I've been playing with startup tools lately so something in registry may have changed....I don't wnat to have to reinstall kx since I had a little trouble last time I reinstalled it....

Is there a registry setting I can look at?

Thank you,

frew

Russ

Make sure that the kxmixer starts with Windows, and includes the '--startup' command line switch.
i.e. (kxmixer startup entry in the registry (RUN key)):
C:\WINDOWS\system32\kxmixer.exe --startup

frew

Wow, thank you very much that did it Russ!

And thanks very much for the example, showing me how and where to put the --startup

Everything's back to normal.

I use Mike Lin's Startup Selector and Startup Control Panel and it works great. But I thought I'd take out the ( --startup) part and that's when my kx configurations stopped loading. But I had made other changes too so I forgot that this may be a factor.

By the way, just curious, I wonder why ( /startup) does not work, but ( --startup) does work? I tried both. I don't know about switches etc.

Also I wonder if it makes a difference if the path is
C:\WINDOWS\system32\kxmixer.exe --startup
or
C:\Program Files\kX Project\3537\kxmixer.exe --startup

Thanks for any ideas about this.

frew

frew

Actually it turns out on my system (Win98SE) the windows path is
C:\WINDOWS\SYSTEM\kxmixer.exe --startup (no system32 in there)
...for anybody else who may ever run into this problem.

Thank you,

frew

Russ

It is really just a matter of what text the program is looking for (the delimiter for command line arguments is whitespace (i.e. space or tab), and not the "/", "-", or "--").

The one in the Windows\System32 directory should always be the currently installed version, whereas the kX directory being used, will change depending on version, otherwise it should not make much of a difference (provided that the versions match).

Good to know... If you are unsure about what path to use, look at the shortcut that kX places on the start menu for kX Mixer, and use the same path that it uses.

frew

Okay, Thank you very much again Russ, for your help about these questions I had.

You really helped me out a lot with this tricky one where I really couldn't pinpoint the problem.

frew

Russ

Your welcome