Announcement

Collapse
No announcement yet.

Windows 2000 and large Hard Drives

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows 2000 and large Hard Drives

    Well a couple days ago I tried installing Win2000 on a 30GB HD that was partioned into two roughly 15 GB partions. I had Win98 installed on the First partion and I wanted to put Win2000 on the second Partion Formated with FAT32 and dual boot between them. Well Win2000 during the install gave me two blue screens and then told me that Drive D was corrupt and on the second time I rebooted and deleated the D partion and it fowled up again. I went to reboot and then the BIOS reported to me that there wasn't a OS on the HD! I lost everything on the 30GB drive. Thankfullly I had my data still on the 13 GB and just transfered it over to the 30GB and formated the 13GB drive and Put WIN2000 on the 13GB drive where it runs like a dream. I don't want to swap the HD everytime I want to run Win2000, so any addition info would be great so I can just dual boot between them. I'm running 2195 verison of the beta also.

    Scott
    Why is it called tourist season, if we can't shoot at them?

  • #2
    I switch boot drives in the bios on my abit mobo will yours let you do that ? its clean and you dont have to worry about the OSes fighting ..Matt

    ------------------
    Abit BF6, P3 450 AT 620, G400 32meg Dh ,Promise fasttrack striping 2 Quantum ka 18gig's + 2 10gig IBM's ,Sb-live platinum ,Cambridge Fps2000 speakers ,Onstream 30gig tape ,Sony cdrw ,toshiba dvd, Lotsa fans,cables ,noise....

    Abit BF6, P3 secc 700E AT 1001,alpha cooler,256 megs Micron 7.5ns pc133 ram, G400 32meg Dh ,Promise fasttrack striping 2 Quantum ka 18gig's + 2 10gig IBM's ,Sb-live platinum ,Cambridge Fps2000 speakers ,Onstream 30gig tape ,Sony cdrw ,toshiba dvd, Lotsa fans,cables ,noise....

    Comment


    • #3
      Don't know if this helps, but here it is...

      References:
      Microsoft Knowledge Base Article Q114841
      Microsoft Knowledge Base Article Q127134


      If your Windows NT boot partition is too large or it is not the first
      partition on the hard disk, your computer may suddenly refuse to boot.
      This article explains why this can happen, how to recover from it, and how
      to prevent it in the first place.


      What is Happening

      Windows NT’s NTFS disk format allows huge partitions. With a 512 byte
      cluster size, you can format a partition of 2 terabytes (TB). That’s two
      trillion bytes, enough to hold about 4.5 million books. The maximum 64KB
      cluster size allows 256TB, or well over half a billion books. But even
      though Windows NT can address all of this huge space, the boot process
      starts with your BIOS (Basic Input/Output System), not Windows NT.

      The BIOS locates the beginning of a partition by using three numbers: The
      Starting Side (or Head), the Starting Cylinder, and the Starting Sector.
      The end of a partition is identified by three similar numbers. Now, the
      Side value is 8 bits, and can range from 0 to 255 (256 numbers); the
      Cylinder is 10 bits, and can range from 0 to 1023 (1024 numbers); the
      Sector is 6 bits, and can range from 1 to 63 (63 numbers). (Note that zero
      is not a valid sector number.) This means the maximum address on the disk
      is Side 255, Cylinder 1023, Sector 63. The number of sectors is 256 X 1023
      X 63, or almost 16.5 million sectors. Standard sectors are 512 bytes, so
      we have a size of 7.87GB.

      That’s the point: The BIOS cannot access anything beyond the first 7.87GB
      of the hard disk. If any critical boot data, such as the files NTLDR,
      NTDETECT or BOOT.INI, get moved to a point more than 7.87GB from the start
      of the hard disk, your computer will not boot. Anything that moves one of
      the critical files may cause the problem; you may copy the file from
      another partition, or you may edit the file. But you will not be aware of
      any problem till the next time you boot.

      You are vulnerable to this if the partition on which Windows NT is
      installed is larger than 7.87GB, or if this partition is not the first
      partition on the disk and the total of this partition and all of the
      partitions before it exceeds 7.87GB.


      Fixing the Problem

      First thing is to boot up the computer using a boot floppy. This is simply
      a floppy formatted on a Windows NT machine (that is vital), and containing
      copies of NTLDR, NTDETECT.COM and BOOT.INI. The BIOS accesses the floppy
      and finds the data it needs, then the floppy starts Windows NT, and
      everything runs fine. Of course, the next time you boot, the problem is
      back, but this gets the machine up and running so you can get your regular
      work done. Now you can schedule a time to fix it when you won’t disrupt
      production.

      Now, to fix it. The problem is simply that some critical file lies beyond
      the part of the disk which the BIOS can access. The simplest handling is
      to use the BIOS to rewrite the file. Start with your Windows NT Setup
      Floppies and CD, and proceed as if you were installing a second Windows NT
      installation. When asked which folder to use, specify a new folder, not
      the one that the existing Windows NT is in. When asked if you want to
      check the hard disks for errors, select “yes”. Once this check is done,
      you can abort the new installation and Windows NT will boot up
      successfully.

      Another handling is to move the critical files back closer to the beginning
      of the disk. This can be difficult because you really don’t know where the
      files will be placed when you copy or move them. However, the odds are on
      your side if the partition lies mostly within the 7.87GB limit. Trial and
      error will do it.


      Preventing the Problem

      The simplest prevention is to always have the boot partition as the first
      partition on the hard disk, and ensure that it is less than 7.87GB. If
      this is not feasible, take steps to ensure the critical files will not be
      moved. If the partition is in NTFS format, set the access on those files
      so that only an administrator can access them, and if you are using a
      defragmenter such as Diskeeper, add the critical files to the
      defragmenter’s exclusion list.


      Lance Jensen
      Technical Support Manager
      Executive Software International, Inc.


      If you do not wish to receive these articles, please send your request to
      follow the instructions at the end of this article.

      If you would like to be added to the list, send your request to
      MAILTO:tips@executive.com?subject=subscribe

      Back issues of these articles can be found at http://www.execsoft.com/tech-support...s/windows.htm;

      If you have any problems or questions regarding this article, please send
      them to us at tips@executive.com.

      For reprint permission for any of these technical articles, please
      contact Public Relations at e-mail dirpr@executive.com.

      If you have any comments, suggestions or successes from using Executive
      Software products, please send them to Quality Assurance at
      QA@executive.com.


      Copyright (c) 1999 Executive Software International, Inc. All Rights
      Reserved.

      Diskeeper, Undelete and Executive Software are trademarks owned by
      Executive Software International, Inc.

      Microsoft, Windows NT and Backoffice are either registered
      trademarks or trademarks of Microsoft Corporation in the
      United States and/or other countries.

      All other trademarks are the property of their respective owners.


      ------------------
      ABIT BP6, 192MB PC100 RAM, dual 366 Celerons oc'd to 550MHz, 3DFXCool GlobalWin FEP32 'Lil Mofo' h/s fans. G400 DH, 3COM 905B NIC, Buslogic FlashPoint LW Ultra-Wide SCSI, SBLive PCI 1024 (OEM SBLive Real Player). Segate Medalist PRO 9.1 GB UW SCSI 7200RPM, Maxtor 20.4GB ATA66 7200RPM 2MB Cache, 8GB tape b/u, IDE 32x CDROM, SCSI 4xwrite/8xread Panasonic CD writer, 4 more various 2GB SCSI drives.

      Tyan Thunder K7, 768MB Registered DDR ECC, 2xMP2200+, Radeon 9700 Pro, Adaptec 2940U2B Ultra2 SCSI, TB Santa Cruz, Pyro 1394DV. RAID 0 stripe set on hacked Promise UltraTX2 with dual WD 120MB SE drives. HP DVD200i DVD+RW drive.

      Comment


      • #4
        Try removing the "signature" in the BOOT.ini, you should have a line like this instead:
        multi(0)disk(0)rdisk(0)partition(2)\WIN2000="Windo ws 2000 Professional"

        Comment

        Working...
        X