| Author |
Spid's Wed (12/18) Win2k Pro. QoD
|
|
|
| Happy Humpday everyone!! 
I'm the administrator of a Windows 2000 Professional computer. My stupid computer displayed this message:
Stop 0x00000079 MISMATCHED_HAL.
What the is the most likely cause of this Windows 2000 Stop message? (Select the best choice).
A. An incompatible device driver has been loaded.
B. The BIOS hardware is incompatible with Windows 2000.
C. Multiprocessor configuration files exist on a single-processor system.
D. Single-processor and multiprocessor configuration files both exist on the same system.
Good luck and see you tomorrow for the answer!! | |
| WPFossil 2002-12-18, 8:20 am |
| I'm going with D | |
|
| D for me as well.
PS What's "Humpday" Spid?! Or shouldn't I ask?  | |
| WPFossil 2002-12-18, 8:42 am |
| Humpday means you're halfway through the week and you've gotten "over the hump". So Humpday is Wednesday. | |
| soccer4net 2002-12-18, 9:16 am |
| I'll say C, just to be different. | |
|
| quote:
Originally posted by tharg
D for me as well.
PS What's "Humpday" Spid?! Or shouldn't I ask?
Traditionally (in the US anyways) Humpday means Wednesday as WPFossill stated. You're halfway through the work week (you've made it over the hump and the weekend is right around the corner).
Of course there are other definitions with respect to "Hump". I'm sure Enforcer will be around shortly to educate all of us on these alternative definitions and their creative use in sentences.  | |
| cm2gj 2002-12-18, 10:54 am |
| spid what is the answer? | |
| djmaplethorpe 2002-12-18, 11:05 am |
| Okay, today i read the whole question first, but now I'm not sure I know what to do. Anyway, I checked a couple of resources that didn't realy spell it out, so I'll go with
B
and see what it gets me. | |
| Surender 2002-12-18, 12:03 pm |
| D | |
| jonhiker 2002-12-18, 12:39 pm |
| I'm going to say "A"...
from microsoft knowledge base:
it stops during the second Setup disk, just after loading the keyboard driver and the file allocation table (FAT) file system. The following Stop message appears:
STOP 0x00000079 MISMATCHED_HAL
The manufacturer-supplied hardware abstraction layer (HAL) must be manually specified. At the beginning of the first Setup disk, when Setup displays "Setup is Inspecting Hardware," press F5. After a while, a message will come up saying that Setup could not detect your computer type, or that you chose to specify the computer type. Select Other and put in the OEM- supplied disk containing the HAL (in this case, the device driver disk). Select the only HAL presented and continue. | |
|
| This STOP error seems to have more than one cause.
"Q. I've disabled ACPI in my BIOS now Windows 2000 will not boot.
A. During installation if Advanced Configuration and Power Interface (ACPI) is detected specific changes are made to the configuration in the form of registry entries and system files.
If you then disable ACPI in the BIOS the OS will fail to boot with a BSOD:
0x00000079 (0x00000004, 0x0000AC31, 0x00000000, 0x00000000)
This is because a separate HAL is used for ACPI, non-ACPI systems. If you no longer want ACPI you will need to reinstall Windows 2000."
http://www.windows2000faq.com/Artic...ArticleID=14640
On XP it seems an ACPI issue as well:
http://www.microsoft.com/technet/tr...md_stp_fwal.asp
I'll put my money on D. With a side bet on C | |
|
| Well even after some research I still can't give a solid answer but I am going to go out on a limb and say: (C) | |
| enforcer 2002-12-18, 5:29 pm |
| gut instinct goes for C
as for hump day, first i saw it was in flext's A+ question of the day. I just assumed it was the only day of the week his missus put out.
Oh well another day soemthing new learnt.
Ps. thanks for the build up Spid. you looking for a job as a straight man? | |
|
| quote:
Originally posted by jonhiker
I'm going to say "A"...
from microsoft knowledge base:
it stops during the second Setup disk, just after loading the keyboard driver and the file allocation table (FAT) file system. The following Stop message appears:
STOP 0x00000079 MISMATCHED_HAL
The manufacturer-supplied hardware abstraction layer (HAL) must be manually specified. At the beginning of the first Setup disk, when Setup displays "Setup is Inspecting Hardware," press F5. After a while, a message will come up saying that Setup could not detect your computer type, or that you chose to specify the computer type. Select Other and put in the OEM- supplied disk containing the HAL (in this case, the device driver disk). Select the only HAL presented and continue.
jonhiker, your quoting knowledgebase article "Err Msg: "STOP 0x00000079 MISMATCHED_HAL" on IBM PC Server 320 [Q148975]". Which refers to Windows NT versions 3.5 and 3.51 on a IBM PC Server version 320. That article does not apply to this question.
I'll admit, I have never personally seen this message. I saw a similar question and researched out the answer just to be sure the author was right.
The answer I have is from the Windows 2000 Professional Resource Kit Chapter 33 and answer "A" is not it.
Maybe this was a bad question, especially if there are possible multiple answers, but honestly, I have only found reference to one of the answers which is listed.  | |
| Deja-vue 2002-12-18, 8:57 pm |
| this is what Microsoft has to say
A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the system. This error also occurs when using mismatched files, such as copying a multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The kernel and HAL files for single-processor and multiprocessor systems are stored on the Windows XP Professional operating system CD using two different file names. For example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy the correct HAL or kernel files from the CD to the appropriate folder on the hard disk.
So my Answer is C | |
| Deja-vue 2002-12-18, 9:05 pm |
| Excellent Question, by the way...
| |
|
|
|
| quote:
Originally posted by Spid
Happy Humpday everyone!!
I'm the administrator of a Windows 2000 Professional computer. My stupid computer displayed this message:
Stop 0x00000079 MISMATCHED_HAL.
What the is the most likely cause of this Windows 2000 Stop message? (Select the best choice).
A. An incompatible device driver has been loaded.
B. The BIOS hardware is incompatible with Windows 2000.
C. Multiprocessor configuration files exist on a single-processor system.
D. Single-processor and multiprocessor configuration files both exist on the same system.
Good luck and see you tomorrow for the answer!!
Well, didn't we all have some fun with this one.
I know not all of you will agree with the answer but at least it gave our brains a good workout and we all learned something.
According to my research, the answer is.....D
Windows 2000 Stop Messages
This message, also known as Stop 0x79, is displayed when the hardware abstraction layer (HAL) and the kernel or the computer type do not match. This error most often occurs when single-processor and multiprocessor configuration files are mixed on the same system.
Here's the link to the resource kit reference I was referring to:
http://www.microsoft.com/windows200...hd_exe_qsde.asp | |
|
| It was a good question Spid. Nice one! | |
|
| Not that I want to argue but this is what I found in a Technet article:
"A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the system. This error also occurs when using mismatched files, such as copying a multiprocessor HAL on to a system using a single-processor kernel (or vice versa)."
I found it here:
http://www.microsoft.com/technet/tr...md_stp_fwal.asp | |
|
| No problem F150. Like I said, there could very well be more than 1 answer to it. But, the article link you posted is taken from the Windows XP Professional resource kit. It may apply to Windows 2000, it may not. I honestly don't know 
I do know for a fact that my defending of answer "D" was taken directly from the Windows 2000 Professional Resource Kit. Both the Server and Professional resource kits mention answer "D" as the most likely cause.
It's unfortunate that the XP Professional resource kit link that you posted seems to conflict with what the Windows 2000 resource kit states. It interjects a level of uncertainty into what the actual answer is.
Hopefully, we all took something good away from this question. And I'm really glad people posted links to defend their answers as well. It's all good, and it helps everyone learn. |
|
|
|