Version 1.1 is now available.

2006-07-13 15:19 Finished driver analysis, initial announcement
2006-07-14 10:43 Working on inserting new code
2006-07-15 09:56 First successful build
2006-07-15 22:03 Major change of plan
2006-07-20 18:10 Version 1.0 released
2006-07-21 04:51 Begin work on WinME version
2006-07-21 05:50 Finish WinME version
2006-07-21 06:22 Begin work on 4.10.2225
2006-07-21 06:37 Version 1.1 (4.10.2225) released
2006-07-22 07:34 Win98FE version (4.10.2001) released
2006-07-23 08:51 Win98FE version (4.10.2186) released
2006-07-29 20:05 Win98SE version (4.10.2226) released - only for replacing an existing v4.10.2226 file
2006-08-02 17:57 Win95 OSR2+ version (4.00.1111) released
2006-08-04 20:27 Win95 OSR2+ version (4.00.1119) released

For those that don't know, this is an attempt to implement 48-bit LBA support into Windows 98se's default IDE driver, enabling the use of hard drives in excess of 128Gb. This is not just another variant of Loew's "High Capacity Disk Patch" because

1] It's completely free (and of course, has no guarantee)
2] Addressing to 2048Gb is possible (limit of FAT32)
3] A large portion of driver code has been rewritten and optimised
4] LBA-48 commands implemented in separate routines instead of "patched into" existing 28-bit's code
5] Slightly increased performance over Loew's patch due to [4]

If Enable48BitLBA has worked for you, please post a link to a validation image containing the following:

1. Properties page of a drive filled past 137Gb
2. Information dialog, the results of a successful scandisk on the drive
3. System Properties -> Device Manager -> (your IDE controller) Properties -> Driver -> Driver File Details (must show ESDI_506.PDR being used)
Also specify your hardware (in particular, mobo chipset and HDD specs).

This will help to confirm that it works.

Reference: http://www.msfn.org/board/index.php?showtopic=46752

I am not responsible for any damage caused by the use of these drivers.

This post has been edited by LLXX: Aug 4 2006, 03:29 AM

Try here, right below Office Viewers.

@Drugwash:

Thank you very much!
But in the file in post#56 is also the dskmaint.dll from ME.
Need I this dll or not?
Thanks!

BigHDD 3.0 new download link

English: http://rapidshare.com/files/5999772/bhdd30e.zip.html
Russian: http://rapidshare.com/files/5999855/bhdd30r.zip.html

The disk tools URL is actually:
http://www.mdgx.com/add.htm#TLS

BHDD 3.0 link [347 KB, English]:
http://www.mdgx.com/files/BHDD30.ZIP

Enjoy.

Hi,
I just tested new bighdd package aslo with scandisk and defrag are working now I use NU2002 anyway but good work.
Tested om 500GB SATA drive with 2x192GB FAT32 partitions

Only for Czech Windows98 with czech version files:
http://windows98.ic.cz/win98se/bighdd30.exe (372kB classic install- made with iexpress)
or http://windows98.ic.cz/win98se/bighdd30.zip (_install.bat)

Btw: tested with 500GB MyBook WD and any FAT32 partitions drive (160GB WD)

Thx LLXX, Petr, RayeR and Maximus Decim!

This post has been edited by Philco: Apr 20 2008, 02:09 PM

Just read all 22 pages of thread, `cuz I know many competent advisors hate it when visitors ask an already-answered question. There were some good clues, but I don't think it's been exactly asked & answered. Hope someone can help.

Background: (I have newer, faster computers with later OS; but Win95 on an old, slow Acer-built IBM Aptiva remains far and away my favorite. Win 95 won't "die" for me until I can't get it to work any more! It's plenty fast for all I do on it; and all my applications are configured exactly as I like them.) Some years back I put a Promise Technology Ultra 100 TX2 ATA controller into my beloved "antique" Win95 computer to use bigger hard drives than it could originally handle (I think the factory limit was 6 GB per drive). First I put in a 60GB and 80GB drive. They worked fine for several years, but recently one began clattering. I scurried out fast to get a single 320 GB WD EIDE HDD to replace both smaller drives. I used Maxtor Maxblast to partition, format, copy files from the old drives, and make new drive bootable. (Doc for the WD utility said it wanted a newer OS.) OS reports partitions as 90, 98, and 120 GB. So far so good.

It seemed to be working perfectly. But I actually only have about 30 GB total data and prograrms, plus whatever the SWAP file uses. Then I ran into warnings on the Internet about drives which seemed to work but corrupted data when the total in all partitions exceeded 137 GB, with other warnings about ScanDisk and Defrag not working if the drive was over 127 GB or so. I found this site while searching for answers, and installed LXXX's modified ESDI_506.PDR (the latest 4.0 one for Win95, not one of the 4.1 versions for Win98). My system continues to boot and run well; but I have not death-tested it by filling up the drive to greater than 137 GB yet.

Meanwhile, Promise Technology has newer drivers and a newer BIOS for download than I was using, even for Win95. (Thanks to Promise Tech!) I downloaded and successfully installed the new drivers and successfully flashed the BIOS to the newest version. If I understand things correctly, doing so has given me 48-bit LBA large hard drive addressing through the combo of the add-on hardware (Ultra 100 TX2 card) and latest drivers and BIOS update. An early post in the thread says that PCI ATA adapters bypass both the computer's BIOS and the Win95 ESDI_506.PDR file.

This leads me to the actual question: Now wottabout LXXX's modified ESDI_506.PDR file? Which of the three following descriptions and advice applies?

(1) I need all the following to safely address big partitions on my antique Acer-built IBM Aptiva: LXXX's patched ESDI_506.PDR file -- plus the PCI ATA card, driver, and new BIOS.

(2) I don't need the patched ESDI_506.PDR file; but it's harmless since all disk activity is now handled by the PCI ATA card, OK to leave LXXX's PDR file installed.

(3) The patched ESDI_506.PDR file could cause conflicts with the PCI ATA set-up; I should remove it and go back to the original M$ version I saved.

(4) Something else?

I have several computers. I use the Win95 one most; but I reserve the newer, faster ones for software that "old faithful" cannot handle, primarily multi-media, Open Office, and a few resource-intensive hogs. This process has led me to realize I also may need to address the control of large hard drives I have running in a Win 98 machines, too! It's got a 200 GB drive which seems to be working, but I hadn't taken any of the steps above to protect it from file corruption above the 137 GB barrier.

My thanks to LXXX, the other participants, and especially anyone who can eliminate the remaining confusion by answering the above!

The answer is (2)
But it is more than just harmless, it is playing it safe, for who knows the future? Some day you might decide or be forced to transfer your installation to another hardware, not using the Promise board but the motherboard BIOS instead, so your system is already ready for it.

BTW, welcome to the forum!

That's not true. the adapter card bypasses the BIOS, but only the supplied driver can bypass the windows default driver.

I agree with dencorso. The ESDI_506.PDR driver is in use or not. In the first case you should have the patched version, in the second case it's not used, and harmless.

Thank you both. I very much appreciate such prompt response to a topic most would consider "old news." It looks like my "old favorite" machine is again now set to run ... as long as something else doesn't break. It's had quite a few new parts over the years, both to replace and upgrade; but the MOBO is still the original.

I had a little success this morning with the second machine, which is running Win98SE. Its ATA card is a Maxtor-branded Ultra ATA 100, originally sold in a drive bundle, though now controlling a WD disk, set up similar but not identical to the one in my Win95 box. Although this card was built by Promise and the original drivers pack included files from Promise, it was private-label branded. Seagate's got Maxtor now; and although their WEB site still has a support downloads page for both a 48 bit LBA large drive drivers pack and an updated BIOS flashing kit, neither of these files would actually download. Possibly some alternate files direct from Promise would work; and I might have tried them but for the following.

I went to the Wayback Machine (http://web.archive.org/) and pasted in the URL for the page at Seagate's site where they offer the files that didn't (or don't) download (that is, perhaps they would at a less busy time? Don't know). Wayback has several earlier versions from February 2007 to later that year. They all reference the same file versions for both the latest driver and the flash update. I also saved full copies of both download pages, as they contain instructions.

Here's the icing on the cake: Although the Wayback machine does not actually have the missing compressed files, the download pages do preserve the filenames and direct download URLs which were in use in 2007. They both proved to be still valid at Seagate's site! I copied those back into my browser and both BIOS 2.01.0.43 in file U100b43.exe and driver version 2.0.0050.42 in file ATADRVR.exe came right through. So, the Wayback Machine helped me grab what was just beyond reach using plain-vanilla methods. Sometimes the extra step leads to good luck.

This wasn't complex like writing code, but it was a "kinda involved" stepwise procedure for an end-user. Thought this note might help someone coming by later in search of the same sort of solution.

Wow! That's a quite nice trick. I've been using the Wayback Machine to get otherwise lost text for a long time, but never thought to try the URLs retrieved in the process, as you just did. Thanks a lot for the idea! You rock!

I have only just encountered the 137Gb problem in Win98SE with the acquisition and installation of two large HDDs (one - the boot drive - 250GB PATA and a 320GB SATA). All was well until a massive amount of data collected under WinXP must have spilled past the bounderies and appeared as gibberish in Win98!

Your version of ESDI_506.PDR seemed to offer the solution - but isn't there a "gotcha"? How do you replace an existing v4.10.2226 with a v4.10.2226 if I didn't have a v4.10.2226 in the first place? Isn't this a paradox?

Anyway, reading another thread, it is suggested that removing ESDI_506.PDR will force the system to use the BIOS setting and make the large HDDs accessible at the cost of slowing things down. This works as predicted but with other interesting side effects (which I will address in a response to that thread)!

(This is supposed to be a query to LLXX on page 1!)

This post has been edited by Squeek: May 22 2008, 02:41 PM

It's not. Simply add the file to %windir%\SYSTEM\VMM32 and you're set. Do it in Real DOS Mode. And, while you're at it, be sure to add ESDI_506.PDR v. 4.10.2225, because v. 2226 is for IBM laptops only.



She'll never answer, I'm sorry to tell you, for she's been banned for some time already, and AFAIK has disappeared from known cyberspace.

First try v. 4.10.2225, then v. 4.10.2222 if you are still in DOS compatibility mode.
(Not every PC supports v. 4.10.2225).

You can do in Windows (then reboot),since you are already in trouble. (Using DOS is required during a fresh Windows98 OS install).

hi all~
my biggest question is that,how to see that the new driver file is working successfully?
and to setup it,just copy the file to the direction "iosubsys" in the real dos mode?
thanks all~

This post has been edited by aqcww: Jan 21 2009, 09:46 PM

That's pretty much it.
Copy the updated ESDI_506.PDR to x:\WINDOWS\SYSTEM\IOSUBSYS (x:\WINDOWS is your Windows boot folder, normally C:\WINDOWS).
I don't think the file is locked by Windows, so you can probably copy it in Windows and restart.
Although, as with any file replacement, take a copy of the old one just-in-case!

Something to be aware of...
I found out that even though I copied the updated file into IOSUBSYS, Windows was actually loading an older version at run time from C:\WINDOWS\OPTIONS\CABS!!!
I found many drivers that were loading this way. Even some 98SE2ME updated files were actually loading old 98SE official Microsoft files from OPTIONS\CABS instead...
I copied all the newer files over the old ones in OPTIONS\CABS.
I searched the registry and could not find or understand WHY Windows would load some files from OPTIONS\CABS and some from WINDOWS\SYSTEM and sub-folders...

To check, go to Device Manager, Properties on the device - for example Primary IDE Controller, Driver, Driver File Details.
Then look at the path for each file.
If any are loading from a different location, then either update that file, or delete it (with caution!).
I would suggest checking all devices in Device Manager since I found a scattering of wrongly loaded drivers.

EDIT: Weird! I have found some files that are loaded from two different places by two different drivers???
Does this mean that there are two images of the file in memory? - Resource wastage!

This post has been edited by RetroOS: Jan 21 2009, 11:39 PM

The important part of that was "in real dos mode". The reason we suggest that you switch the file before Windows starts is that otherwise it is possible for file corruption to occur on the drive because Windows will be seeing the wrong size of drive and possibly write over important files. Therefore do NOT do the change of file from within Windows.

It appears from the subsequent post that there are other reasons, but this is the primary reason - in DOS, the file system will remain intact and safe, whereas in Windows, until you change that file, your file system is in danger of corruption. Just stop Windows loading and go into the DOS prompt to do the switch.

If you want to ensure that Windows installs with the new file, see earlier posts regarding inserting the replacement file into the CAB files on your installation disk.

Hope that helps.