September 29, 20169 yr Would using NTLDR AND NTDETECT.COM from Win2k along with uniata driver overcome the limit or is it a hard limit of the OS
September 29, 20169 yr Uniata driver has nothing to do with the issue, it is just the INT13 BIOS limitation:https://support.microsoft.com/en-us/kb/224526 The UniAta driver may come into play to overcome another limit, the 128 Gib/137 Gb one:http://nt4ref.zcm.com.au/bigdisk.htm Which is present also in windows 2000 (up to SP3): Unfortunately (for whatever reasons) sites which contained a wealth of information on the matter (and related stuff) were "removed" or "abandoned", once again the Wayback Machine" comes to the rescue:http://www.nu2.nu/fixnt4/ https://web.archive.org/web/20121017215600/http://nu2.nu/fixnt4/ Re: the Windows 2000 needed Registry setting: http://www.cpu-central.com/wwwboard/msg71.asp?id=71290 https://web.archive.org/web/20100901065005/http://www.48bitlba.com/enablebiglbatool.htm jaclaz Edited September 29, 20169 yr by jaclaz
September 29, 20169 yr Author Thanks for the references. So using the win2k ntldr and ntdetect.com should be enough then. On the side side I'll use Norton Speeddisk and have it put ntoskrnl.exe at the front of the drive
September 29, 20169 yr 16 minutes ago, jholt5638 said: Thanks for the references. So using the win2k ntldr and ntdetect.com should be enough then. On the side side I'll use Norton Speeddisk and have it put ntoskrnl.exe at the front of the drive No, you will need also the bootsector code from Windows 2000, check the given reference: https://web.archive.org/web/20121017215600/http://nu2.nu/fixnt4/ AND (should you not be aware of this) remember that you most probably need to have NT4 at SP4 level at least: http://www.911cd.net/forums//index.php?showtopic=11383 http://www.911cd.net/forums//index.php?s=&showtopic=11383&view=findpost&p=70389 (maybe it is not needed unless you "ever" boot a later OS on that system, the NTFS version upgrade is sneaky and "dangerous" ) jaclaz
Create an account or sign in to comment