 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows NT / Setup / September 2004Stop message installing NT 4.0 Server on IBM xSeries
Trying to install NT 4.0 Server on new IBM xSeries 206. Processor is 2.8 GHz pentium with 256 mb ram and 2 simple-swap 80 gb serial ATA drives in RAID 1 configuration. Using Promise PCI raid controller card that has NT drivers. Drives have been partitioned and formatted. Setup gets to a point, after controller driver is loaded but still in text part of setup, and stops with same message at same point everytime. Stop 0x0000003E (0x00000080, 0x00000000, 0x00000000, 0x00000000) with no descriptive text for message. Can't find any relative info for this. According to IBM site, this particular model has not been certified for NT 4.0 but see no reason why shouldn't work. Charlie 0x3E means MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED. Is your processor hyper-threading capable? If it is, what happens if you turn this off in BIOS? Best regards Bjorn  SignatureBjorn Landemoo - mvp2@landemoo.com - http://landemoo.com/ Microsoft MVP (Windows Server - File System) >Trying to install NT 4.0 Server on new IBM xSeries 206. Processor is 2.8 GHz >pentium with 256 mb ram and 2 simple-swap 80 gb serial ATA drives in RAID 1 [quoted text clipped - 9 lines] >particular model has not been certified for NT 4.0 but see no reason why >shouldn't work. Turned off. Makes no difference. > Charlie > [quoted text clipped - 19 lines] > >particular model has not been certified for NT 4.0 but see no reason why > >shouldn't work. Charlie What happens if you force setup to use the uniprocessor HAL? This MS Knowledge Base article might help in the process: http://support.microsoft.com/?id=132512 The error message must, as far as I can understand, mean that NT4 setup detects a multiprocessor system that it doesn't support. If you cannot get a HAL that works, a possibility might be running NT4 within VMWare, while using Win2000 as a host OS. Best regards Bjorn SignatureBjorn Landemoo - mvp2@landemoo.com - http://landemoo.com/ Microsoft MVP (Windows Server - File System) >Turned off. Makes no difference. >> Charlie [quoted text clipped - 24 lines] >> >particular model has not been certified for NT 4.0 but see no reason why >> >shouldn't work. It is running HAL.DLL which as far as I can tell is the correct one for single processor, Intel based machines. Have run debug version of NTDETECT at startup to try and resolve hardware conflicts but hasn't helped. This message also appears to be for Windows 2000. Cannot be sure it is pointing to same type of problem due to lack of descriptive text. Have already purchased 2000 Server and hope I can get applications to work correctly which is main reason for trying to stick with NT in the first place. Its one thing to know what does not work and why but to not know for sure where the problem lies is the hard part. Thanks for your continued input. > Charlie > [quoted text clipped - 40 lines] > >> >particular model has not been certified for NT 4.0 but see no reason why > >> >shouldn't work. Charlie If you get problems also with Win2000 I would suspect some type of hardware problem. Also, NT4 shouldn't have any specific problem with the processor, as it seems to be a regular P4 2.8GHz with 800MHz FSB according to IBM spec sheet. You say that Win2000 doesn't give you any descriptive text when it errors out. What happens? Just a hang, a blue screen, any information at all, that could be used for a search in MSKB, MSDN, Google? Best regards Bjorn SignatureBjorn Landemoo - mvp2@landemoo.com - http://landemoo.com/ Microsoft MVP (Windows Server - File System) >It is running HAL.DLL which as far as I can tell is the correct one for >single processor, Intel based machines. Have run debug version of NTDETECT [quoted text clipped - 58 lines] >why >> >> >shouldn't work. The only hits you get for this message are for Windows 2000 installs and they all reference the same text about multiple processors but this is occurring during NT setup and the message has no text. Don't know if it is referencing same type of problem or is misleading. Windows 200 Server installed with no problem. > Charlie > [quoted text clipped - 73 lines] > >why > >> >> >shouldn't work. Charlie After Googling a bit I found many that had exactly the same problem with NT4, but not with later Windows operating systems. It seems to be a problem with NT4 and a "Prescott" CPU. Even Microsoft employees has confirmed the problem. This link, for instance, gives you a news thread about the problem: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=uJfDKPadEHA.3616%40TK 2MSFTNGP10.phx.gbl&rnum=1&prev=/groups%3Fq%3D0x0000003E%2Bnt%26ie%3DUTF-8%26hl%3 Den (Beware, URL might wrap) Best regards Bjorn SignatureBjorn Landemoo - mvp2@landemoo.com - http://landemoo.com/ Microsoft MVP (Windows Server - File System) >The only hits you get for this message are for Windows 2000 installs and >they all reference the same text about multiple processors but this is [quoted text clipped - 93 lines] >> >why >> >> >> >shouldn't work. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.