I did rebuilt the servers a few time (this a test environment). I always kept my D partition since I had files on it and delete my OS partition (C:) and re-install Win2k from scratch. Could it be the cause of the problem ? Benoît Pilon NavCanada R & D Section (613) 563-5508 -----Original Message----- From: Kevin Hopley [mailto:khopley@xxxxxxxxxxx] Sent: Friday, September 27, 2002 11:37 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Windows NT could not start...Ntoskrnl.exe This error is "normally" a result of the boot.ini file pointing to the = wrong controller/drive/partition - has anything changed in the hard = drive configuration I believe that the 7.8GB limit was a "feature" of NT and is no longer a = problem on 2k (got a few servers with larger system drives anyway) Kev Hopley -----Original Message----- From: Pilon, Benoit [mailto:PilonB@xxxxxxxxxxxx] Sent: 27 September 2002 16:11 To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Windows NT could not start...Ntoskrnl.exe I have been having problem with my servers lately (Compaq DL380G2 with = Win2k SP3, Metaframe XP FR2). After rebooting, I got the following message: Windows NT could not start because the following file is missing or corrupt: =20 <Winnt_root>\System32\Ntoskrnl.exe =20 Please re-install a copy of the above file. In one occassion, I had just removed Citrix Metaframe and I had to = reboot and on the other server I install a new application. If you read the article below, it said that there is a limitation if = your partition is larger than 7.8 gig. I am using the whole drive which is 18 gig. Does this mean that I have to re-install my servers with a = partition less than 7.8 gig to avoid this problem ? The article is not clear if Windows 2000 rectify the problem. I would like to know if you guys experience the same problem and how did = you resolve it ? Thanks Beno=EEt Pilon NavCanada R & D Section (613) 563-5508 PSS ID Number: Q124550 Article last modified on 01-21-2002 =20 :2000,3.5,3.51,4.0 =20 =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -------------------------------------------------------------------------= --- --- The information in this article applies to: =20 - Microsoft Windows 2000 Advanced Server=20 - Microsoft Windows 2000 Server=20 - Microsoft Windows 2000 Datacenter Server=20 - Microsoft Windows 2000 Professional=20 - Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0=20 - Microsoft Windows NT Server versions 3.5, 3.51, 4.0=20 -------------------------------------------------------------------------= --- --- =20 For a Microsoft Windows XP version of this article, see Q314477. =20 SYMPTOMS =3D=3D=3D=3D=3D=3D=3D=3D =20 When you attempt to start Windows NT, you may receive the following = error message: =20 Windows NT could not start because the following file is missing or corrupt: =20 <Winnt_root>\System32\Ntoskrnl.exe =20 Please re-install a copy of the above file. =20 CAUSE =3D=3D=3D=3D=3D =20 This behavior can occur if any of the following conditions exist: =20 - The Default value in the [Boot Loader] section of the Boot.ini file = is missing or invalid. =20 - Windows NT is not installed in the location specified in the Boot.ini file. =20 NOTE: This issue can also occur in Windows NT 4.0 and 3.5 if the system partition is larger than 7.8 gigabytes and system boot files have be placed = outside of the 7.8 GB limit (possibly as a result of applying a service pack or defragmenting the drive). Windows XP does not have this limitation. This is a hardware limitation and occurs independently of the operating system. This should = not be an issue on newer computer if their BIOS supports INT13 Extensions and = this feature is turned on, which it is by default. =20 For additional information, click the article number below to view the article in the Microsoft Knowledge Base: =20 Q224526 Windows NT 4.0 Supports Maximum of 7.8-GB System Partition =20 RESOLUTION =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 To resolve this problem, use one of the following methods: =20 Method One ---------- =20 Edit the Boot.ini file to restore or correct the Default entry and to = ensure that the other entries in the [Operating Systems] section of the Boot.ini = file point to the appropriate directories. =20 Method Two ---------- =20 Use the repair process to correct inconsistencies in the Boot.ini file. = To do so, follow these steps: =20 1. Start your computer using the three Windows NT Setup diskettes. When prompted, type R to begin the repair process. =20 2. Insert the Emergency Repair Disk (ERD) in the floppy drive when you = are prompted. =20 3. When prompted, enable only the Inspect Startup Environment option to correct inconsistencies in the Boot.ini file. =20 4. Follow the instructions on your screen to complete the repair = process. =20 Method Three ------------ =20 If you determine the system partition is larger than 7.8 GB, Windows NT = has been setup in an unsupported configuration, and the drive will need to be repartitioned to a size less than 7.8 GB. =20 MORE INFORMATION =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 If the Default value in the [Boot Loader] section of the Boot.ini file = is missing, Windows NT displays a new entry in the OS Loader (boot loader) = menu named "NT (default)" and defaults to the new entry. The "NT (default)" = entry points to the following path to load Windows NT: =20 multi(0)disk(0)rdisk(0)partition(1)\WINNT =20 For additional information about the Boot.ini file, click the article = number below to view the article in the Microsoft Knowledge Base: =20 Q102873 BOOT.INI and ARC Path Naming Conventions and Usage =20 Additional query words: =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Keywords : kberrmsg kbfaq Technology : kbWinNTsearch kbWinNTWsearch kbWinNTW400 kbWinNTW400search kbWinNT351search kbWinNT350search kbWinNT400search kbWinNTW350 kbWinNTW350search kbWinNTW351search kbWinNTW351 = kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000DataServ kbwin2000DataServSearch kbwin2000Serv kbWinNTSsearch kbWinNTS400search kbWinNTS400 kbWinNTS351 kbWinNTS350 kbwin2000ServSearch kbwin2000Search kbwin2000ProSearch kbwin2000Pro kbWinNTS351search kbWinNTS350search kbWinAdvServSearch kbWinDataServSearch Version : :2000,3.5,3.51,4.0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D =3D Copyright Microsoft Corporation 2002. =20 ********************************************** This weeks sponsor Kevsoft Corporation=20 TScale by Kevsoft Corporation=20 Support 30% to 40% more users on your server farm without buying new hardware! =20 http://www.kevsoft.com/ *********************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm ********************************************** This weeks sponsor Kevsoft Corporation TScale by Kevsoft Corporation Support 30% to 40% more users on your server farm without buying new hardware! http://www.kevsoft.com/ *********************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm ********************************************** This weeks sponsor Kevsoft Corporation TScale by Kevsoft Corporation Support 30% to 40% more users on your server farm without buying new hardware! http://www.kevsoft.com/ *********************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm