tlvlr your not wrong. That article was taken from microsoft knowledge base. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q197667 The main problem is that your bios must support disks larger than 8gig as well. You can check this by accessing CMOS. If your bios doesn't you will need to upgrade/flash your bios. Newer versions of your bios may address the problem and allow the decribed article to work.

0

The priary partition must be no more than 2 gig or else the boot files could be loaded on the section past the int13 limit. Make your primary partition lo larger than 2048

0

Slight confusions here? Originally NT had a 'boot-code boundary' = 2Gig; but sp4 (or was it sp3) resolved this to a 4Gig limit. This means the total used/unused space ahead of the NT4 Primary 'must not exceed 4Gig' - preferably slightly less? If the partition is further than 4Gig physically into the drive - then NT4 will not boot... (it may not even install...?). '98 incidentally has an 8Gig boot-code boundary... You can have an NT Primary upto 4Gig (fat16/ntfs); the fact that you can create/format this during setup confirms this... http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q197295 discusses the issue; although it does not refer it as the boot-code boundary... And for more on partitions constraints for NT and the various OS - perhaps browse towards the end of: http://www.win.tue.nl/~aeb/partitions/partition_types-2.html has lots of info and links to M$ KB etc...

0

I previously installed win98SE on my 40GB HDD. But I had repartitioned it with the primary DOS partition (3342MB) formatted with FAT16. Same size as the partition on the other HDD which I got it running. Anyway, I haven't repartitioned the 40GB HDD as I am busy backing up files I have in it. meanwhile, I'm still studying what to do to make sure I get it up and running. Any suggestions with partition settings would be a great help. thanks

0

Presuming this a Server only drive/system: Make the Primary around 3-4Gig; can be fat16 or ntfs... Max partition that can be created during setup = 4Gig (fat16/ntfs). Install Server, (remember the atapi.exe util/large-drive issue outlined earlier in this post...); apply SP you want to use; use Disk Admin to configure/create Extended partition and a series of logical-drives - perhaps two, three or four? If wanting to use ntfs permissions them format one or more as ntfs - if over 4Gig they can only be ntfs; if upto 4Gig max. each 'drive' can be either fat16 or ntfs... If wanting a dual/multi-boot (NT/W2K, NT/'9x, or all three...?) environment - post back, things to consider first...

0

as a matter of fact I am planning to install w2k or xp pro in the future. meanwhile, i'm focusing on nt 4 server. but it would be better if I can set it up the way that I would have no trouble should I opt to have dual OS. I plan to have only two OS if I ever do.

0

There are a couple of ways ("at least") of setting up the dual-boot NT/W2K - without using add-in boot-utils. When starting from scratch, I favour the common single active Primary partition (for boot/start-up files only); each OS in its own logical-drive in the Extended partition; and one or more shared data logical-drives. Others will say just install NT into C: , and (using NT Disk Admin) create an Extended partition and sub-divide into two (or more) logical-drives; one for W2K (intended) and the other(s) for data... My preference for the fat16 C: primary (boot-files only) is because that arrangement allows just about ‘any’ M$ (and probably other) OS to go in more or less straightforward at any time’ allows greatest options for change at any time. Fat16 is the only common format for all M$ OS; so ‘all’ M$ OS in a dual/multi-boot can see that Primary at boot up... I know (some) others will probably disagree with my preferred route; it’s all a matter of choice/preference My preferred arrangement might resemble: Active Primary: C: = fat16 = 50-100Meg boot/start-up files only; Extended Partition: D: = 2 - 4Gig max = NT4 = fat16/ntfs4; E: = fat16/ntfs4 - usual size considerations depending on file format = data. F: = 3Gig min = W2K (intended) = fat16 (max = 4Gig) or ntfs4 if over 4Gig; And there could be more data/shared 'drives' - all preferably between the two OS. The 2 OS 'could' be adjacent with all data after them... BUT if W2K = fat32 then NT will have an issue with drive letters for data areas; NT cannot see fat32 'drives'... so (data) drive letters ‘could’ bounce around a little between OS? If W2K = ntfs(5) then the problem wouldn't arrive - as long as all data = fat16/ntfs, or any fat32 areas are after all fat16/ntfs areas... Also when W2K arrives, if you have/create fat32 data ‘drives’ – again NT4 won’t see them (without add-in utils). M$ advises that all fat32 areas on a drive be after any fat16/ntfs4 areas... for this reason amongst others. If you are au fait (OK) with NT4 in a 4Gig max logical-drive (fat16/ntfs4) then you can allow NT setup to create the space (logical-‘drive’). Once you have created the small C: fat16 (active) Primary (via DOS/'9x boot-disk), you just run NT setup as per norm and point it to the Extended area. Once NT installed OK use Disk Admin to configure balance of drive. If wanting NT in a 'drive' over 4Gig, one way is to create the C: partition around 250Meg = fat16; install a basic NT there (include the updated atapi.exe – see below); then via Disk Admin configure Extended partition; subdivide into various 'drives' - one of which will be over 4Gig = ntfs4; then run NT setup again and install a second version to the ntfs4 'drive'... You will have a dual-boot - NT in C: and again in D: . You can keep the C: winnt (fat16 version) folder or delete - your choice... When you come to add in W2K later just run W2K setup as norm; it will deposit its boot/startup files into fat16 C: Primary, replacing the NT versions; it will also overwrite/replace the NT mbr with the W2K version. It will complete the dual-boot. It will go (put the system files) where you point it. BUT... W2K will also forcibly convert (U have no say in the matter...) any ntfs4 areas it finds to ntfs5. NT4 cannot see ntfs5 unless it has sp4 or later installed - PRIOR to arrival of W2K on the same physical drive. So ensure you do have sp4 or later already installed in NT4 - before adding in W2K. Also address the large drive issue for NT4 – i.e. the updated atapi.exe - (regardless of how you set the whole scene up initially) for each installation you make with NT4; more in detail on this at: http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13894 If the 'drive' intended for W2K is over 4Gig then it would initially be ntfs4; W2K setup would change it to ntfs5. If it was initially fat16 (4Gig limit) then during W2K setup you could opt for fat16/fat32/ntfs5 - your choice. There are a couple (at least) of excellent articles on NT/W2K at: http://www.winnetmag.com/Issues/Index.cfm?IssueID=396 http://www.winnetmag.com/Issues/Index.cfm?IssueID=439 which would be worth reading… they cover various issues re’ the two OS co-habiting. Some could be critical in the wrong circumstances Again you can just install NT into C: (fat16/ntfs4), create the Extended partition; create a couple (or more) of logical-drives – one reserved for W2K and away you go… But the file format constraints (fat32 issues and ntfs4 to ntfs5) will still apply… It’s all a matter of choice/preference? If going XP instead of W2K the routine is the same. If wanting NT/W2K/XP then just allow for another 'drive' for the third OS? Golden rule - when practical: install oldest OS first then progress to newest. You can do it the other way round, but then you have to run a repair sequence at some stage to recover newer OS - disabled usually by the arrival of the older...

0