• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Western Digital 250gig drive

R

Rilescat

Senior member
Ok.....

Bought myself a retail Western Digital 250gig drive.

Put it in my Tyan Thunder K7 S2462UNG (on the retail Promise TX2 controller that comes with the HDD).

I don't want to put "Data LifeGuard" crap on the drive, so I try to install it normally. Get into XP Pro, and find that OH DAMN YAHOO, I have the non-48 bit compliant version of XP Pro, and yee damn ha......if I put the EnableBigLba registry key in and enable it, I still get a whopping 128gig (137) worth of disk space out of my drive. Can't get the damn thing to recognize the full size.

My system BIOS is at its highest level, but that shouldn't matter anyway because I am using the Promise controller.

So....I finally give in and try Data LifeGuard....thinking I can put EZ-BIOS on the drive and finally be done with this crud.....NO....EZ-BIOS doesn't even see the hard drive, even though the detection works fine. So........looks like I will have to take the damn drive and card out, put it in another machine, and try to use EZBios from there.

Anybody have any additional thoughts of things I could try rather than use EZ-BIOS?

 
Did you do all of this? Microsoft has helpful information to deal with their OSes.

EZ-BIOS is Satan's Imp and in my experience causes more trouble than it's work.

\Dan
 
Rile.. are you positive that you have enabled it?

Did you delete the volume completely and then reboot?
 
What exactly are you afraid of when speaking of Data Life Guard tools? The worst it could do is format your drive correctly.
 
I am not afraid of EZ-BIOS. There are no problems with it. Other than it installs something to the hard drive that is hard to get rid of later, may prevent some disk utilities from performing correctly, may make the drive unusable in other systems should you want to move the drive, hurt performance. Other than that, though, it's fine. Why add extra crap that may make things more difficult when the tools you already have (but may need to be configured right) will do the job without any potential problems?

\Dan
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top