Jump to content

W2K and big partitions


XibaD

Recommended Posts

Hi!

After slipstreaming W2K Pro hotfixes and install it in my HDD (Maxtor 160GB), checkdisk starts scanning in my partition that exceeds the limit of Windows 2000 default partition size, and, obviously, corrupts my data.

I include REG.EXE in HFTOOLS folder but even in first setup text screen my HDD is not properly detected in size (setup detects 136GB HDD aprox).

Is there any fix for that? Have I missed something to enable large partition support?

Thanks :)

P.D. : I forgot, this is my HFSLIP config:

HFSLIP Version - 70402b

MSIE Version - 2KIE6

DirectX Slipstreamed

Drivers - DRIVER.CAB Updated

HFCLEANUP Detected

CD Install Path - Default

CDTAG - CDROM_NT.5

===============================================================================

Files in your FIX folder:

NTDETECT.COM

NTLDR

Files in your HF folder:

aolsupp.exe

gdiplus_dnld.exe

IE6.0sp1-KB905495-Windows2000-x86-ESN.exe

IE6.0sp1-KB918439-Windows-2000-XP-x86-ESN.exe

IE6.0sp1-KB928090-Windows2000-x86-ESN.exe

IE6.0sp1-KB929969-Windows2000-x86-ESN.exe

MDAC281-KB927779-x86-ESN.exe

MDAC_TYP.EXE

MPSetup.exe

msxml2sp6-kb887606-x86-esn.exe

msxml4-KB927978-esn.exe

OE6.0sp1-KB923694-Windows2000-x86-ESN.exe

rootsupd_fe44934fd80dd11fec2f0f9b24431658a4f6d589.exe

Windows-KB890830-V1.28.exe

Windows-KB909520-v1.000-x86-ESN.exe

Windows2000-KB842773-x86-ESN.EXE

Windows2000-KB891861-v2-x86-ESN.EXE

Windows2000-KB893756-x86-ESN.EXE

Windows2000-KB896358-x86-ESN.EXE

Windows2000-KB896423-x86-ESN.EXE

Windows2000-KB899587-x86-ESN.EXE

Windows2000-KB899589-x86-ESN.EXE

Windows2000-KB900725-x86-ESN.EXE

Windows2000-KB901017-x86-ESN.EXE

Windows2000-KB901214-x86-ESN.EXE

Windows2000-KB904706-DX9-x86-ESN.exe

Windows2000-KB905414-x86-ESN.EXE

Windows2000-KB905749-x86-ESN.EXE

Windows2000-KB908506-x86-ESN.EXE

Windows2000-KB908519-x86-ESN.EXE

Windows2000-KB908531-v2-x86-ESN.EXE

Windows2000-KB911280-v2-x86-ESN.EXE

Windows2000-KB913580-x86-ESN.EXE

Windows2000-KB914388-x86-ESN.EXE

Windows2000-KB914389-x86-ESN.EXE

Windows2000-KB917008-x86-ESN.EXE

Windows2000-KB917422-x86-ESN.EXE

Windows2000-KB917537-x86-ESN.EXE

Windows2000-KB917736-x86-ESN.EXE

Windows2000-KB917953-x86-ESN.EXE

Windows2000-KB918118-x86-ESN.EXE

Windows2000-KB920213-x86-ESN.EXE

Windows2000-KB920670-x86-ESN.EXE

Windows2000-KB920683-x86-ESN.EXE

Windows2000-KB920685-x86-ESN.EXE

Windows2000-KB921398-x86-ESN.EXE

Windows2000-KB922582-x86-ESN.EXE

Windows2000-KB923191-x86-ESN.EXE

Windows2000-KB923414-x86-ESN.EXE

Windows2000-KB923689-x86-ESN.exe

Windows2000-KB923980-x86-ESN.EXE

Windows2000-KB924191-v2-x86-ESN.EXE

Windows2000-KB924270-x86-ESN.EXE

Windows2000-KB924667-x86-ESN.EXE

Windows2000-KB925902-x86-ESN.EXE

Windows2000-KB926121-x86-ESN.EXE

Windows2000-KB926247-x86-ESN.EXE

Windows2000-KB926436-x86-ESN.EXE

Windows2000-KB928843-x86-ESN.EXE

Windows2000-KB930178-x86-ESN.EXE

Windows2000-KB931784-x86-ESN.EXE

Windows2000-KB932168-x86-ESN.EXE

WindowsInstaller-KB893803-v2-x86.exe

WindowsMedia-KB911564-x86-ESN.exe

WindowsMedia6-KB925398-x86-ESN.exe

WindowsMedia9-KB917734-x86-ESN.exe

WindowsRightsManagementServicesSP2-KB917275-Client-ESN-x86.exe

WindowsServer2003-KB931836-x86-ESN.exe

WindowsUpdateAgent20-x86.exe

WindowsXP-KB928388-x86-ESN.exe

WindowsXP-KB931836-x86-ESN.exe

WindowsXP-Windows2000-Script56-KB917344-x86-esn.exe

wmfdist.exe

wmp6cdcs.exe

msxml2.msi

msxml6_x86.msi

Files in your HFCABS folder:

Apr2005_d3dx9_25_x86.cab

Apr2006_d3dx9_30_x86.cab

Apr2006_XACT_x86.cab

Apr2006_xinput_x86.cab

APR2007_d3dx10_33_x86.cab

APR2007_d3dx9_33_x86.cab

APR2007_XACT_x86.cab

APR2007_xinput_x86.cab

Aug2005_d3dx9_27_x86.cab

AUG2006_XACT_x86.cab

AUG2006_xinput_x86.cab

BDANT.cab

BRANDING.CAB

Dec2005_d3dx9_28_x86.cab

DEC2006_d3dx10_00_x86.cab

DEC2006_d3dx9_32_x86.cab

DEC2006_XACT_x86.cab

dxnt.cab

Feb2005_d3dx9_24_x86.cab

Feb2006_d3dx9_29_x86.cab

Feb2006_XACT_x86.cab

FEB2007_XACT_x86.cab

IEAWSDC.CAB

IEW2K_1.CAB

IEW2K_2.CAB

IEW2K_3.CAB

IEW2K_4.CAB

IUCTL.CAB

Jun2005_d3dx9_26_x86.cab

JUN2006_XACT_x86.cab

LegitCheckControl.cab

MAILNEWS.CAB

MUWEB_SITE.CAB

Oct2005_xinput_x86.cab

OCT2006_d3dx9_31_x86.cab

OCT2006_XACT_x86.cab

OCT2006_xinput_x86.cab

OEEXCEP.CAB

OGAControl.cab

OPUC4.CAB

SCRIPTES.CAB

swflash.cab

WAB.CAB

Files in your HFSVCPACK_SW folder:

msdrmclient.msi

Files in your HFGUIRUNONCE folder:

UPHClean-Setup.msi

WindowsDefender.msi

Files in your HFTOOLS folder:

7za.exe

cmdow.exe

EXTRACT.EXE

HFANSWER.INI

modifyPE.exe

reg.exe

Files in your HFCLEANUP folder:

2000SP4.EXT

Edited by XibaD
Link to comment
Share on other sites


Is your motherboard and BIOS capable of supporting 48 Bit LBA?

If not you will not be able to have partition sizes greater than 137 GB.

So long as the motherboard & BIOS support 48 Bit LBA and you are running either windows 2k SP3 or later or Windows XP SP1 or later, you should not see this problem.

Hope it helps.

Link to comment
Share on other sites

Check these:

- for Win2K, include REG.EXE in HFTOOLS folder before running HFSLIP

- as mosaddique said, the BIOS/HDD controller must support 48-bit LBA

- the hard disk's jumper should not be limiting the size (though I've only seen a 32GB limiter before)

Link to comment
Share on other sites

But I run perfectly any other OS (like Windows XP, Ubuntu etc) and it recognises the whole lenght of my hard disk. How can it be possible?

mosaddique, Tomcat76 thanks for the help

Link to comment
Share on other sites

I found the source of the problem. In order to apply the 48 bit LBA fix correctly, the path to the source\i386 folder cannot contain names with more than 8 characters lenght (I mean any directory must be renamed to 8 characters or less).

Then the fix works and text based part of installation recognises the HDD real size.

Thanks to all :)

Edited by XibaD
Link to comment
Share on other sites

I suppose you meant spaces. My 2K work folder is named "hfslip2ken" and that works fine.

Try the latest test release. It should work around the problem if spaces were the issue. :)

Oh, it may be the spaces then. My old folder that cointained the source folder, was named Custom WXP. Now I changed it to hf_WXP. Maybe the space was messing up everything.

Thanks Tomcat76

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...