I realize I am a still a newbie, but I shouldn't be having this problem. I have configured 5 kernels already and have never had a problem like this!!

To get to the point. I have been trying discover the problem so I can configure my linux-2.4.22-21mdk kernel and it has crashed at the ALSA configuration point 26 times now in 3 days. No matter what I do I get the same error message and the same system report, which is really leaving me disgusted!!

The following is what I have been getting over and over and over. Is there anyone out there who can tell me where I got lost or whatever??
___
#1]________________________________________________________________________________
Menuconfig has encountered a possible error in one of the kernel's
configuration files and is unable to continue. Here is the error
report:

Q> scripts/Menuconfig: line 832: MCmenu78: command not found

Please report this to the maintainer <mec@shout.net>. You may also
send a problem report to <linux-kernel@vger.kernel.org>.

Please indicate the kernel version you are trying to configure and
which menu you were trying to enter when this error occurred.

make: *** [menuconfig] Error 1
___
#2]
________________________________________________________________________________
Then in the KDE Control Center I am told that I have, Type 10 ALSA Emulation, but I have absolutely no sound card.
___
3..]
________________________________________________________________________________
Then I go to the Mandrake Control Center and I am given the following info about my SB Live!

Vendor: ?Creative Labs

Alternative drivers: ?audigy:emu10k1

Bus: ?PCI

Bus identification: ?1102:2:1102:8064

Location on the bus: ?0:b:0

Description: ?SB Live! (audio)

Module: ?snd-emu10k1

Media class: ?MULTIMEDIA_AUDIO
________________________________________________________________________________

I have also been researching over 30 pages of instructions about installing the kernel, most being somewhat similar but at the same time being a bit different as well. So I tookt the majority of agreeing advice to do what I have already done 5 times before and just cannot figure the problem! I Sure do hoep someone can see what is going on here. PLEEEEEEEEEAAAAASE!!!

Oddly I had the same problem as well with the 2.4.22-21mdk kernel, maybe its a bug in one of the kernel patches, dunno. Just leave out the alsa bit, complie your kernel, then compile the alsa drivers afterwards manually(using the packages from the alsa website).

I am about to download MDK 9.2 is there a common problem with it?

Well its not really a concern if you're not planning to compile your own kernel.

I pretty much suspected I was going to have to do something similar if not exactly as you suggested regarding to configuring alsa seperately. Of course, I suppose I am still a bit spoiled or brainwashed by the old Windows functions. In that, even if Windows crashed or malfunctioned in some way, which was very frequently, at least it wasn't extremely difficult to get it functioning again. I just got very trired of having to do it so often, and now it seems that MDK and perhaps others are heading in that direction. Still, even that type of thought could be a remaining Microsoft infection.

Nevertheless, I did enjoy MDK 9.2 upgrading/loading so easilly, but they just left out so much that we have to do afterwards and being a non-programmer 9 month baby to Linux still doesn't help matters. In any case, I THANK YOU VERY MUCH FOR YOUR ASSIST!

While I am in here and I surely hope you will forgive me for not posting another thread, but this was a somewhat sudden impulse (so to speak). I am certain that my still being a newbie has most likely given me another perhaps serious problem that I may or may not be seeing affects of as yet. To get to the point! While I had said I have compiled kernels five times before (for each upgrade). I don't think I have truly done them correctly because I quite often notice strange combinations of kernels or distros (whichever term would be more appropriate).

For example; When I boot into Linux I get the boot menu that asks me where I would like to go and am offered at least 5 different distros of MDK (from 2.2.......13 to 2.4.22....mm). Then when I get into MDK I go to the KDE Control Center and it shows me the kernel I had asked for - in this case the MM (multimedia distro) - and I assume that is fine. So I then go to the console and enter the commands to bring me to /usr/src/linux to then enter the command "make config or make menuconfig", but when I do so I get a different MDK distro altogether (the main one for the update 2.4.22). The main one for .22 has nothing regarding to the mm distro except the core (so to speak).

SO NOW THE QUESTION! Do you have any idea of whether I am seeing things incorrectly or if I am right when I think I have really screwed things up somewhere along the way?? At the same time, if I have screwed things, do you have another solution for me??

Thanks again!