Jump to content

137GB limit - ESDI_506.PDR and other limits


Recommended Posts


Oddly, in Safe Mode the Primary and Secondary controller drivers now say ESDI_506.PDR but I can't delete the VIA Bus Mastering entry. It says I need to delete its parent device first.

Then do it. To make your system boot normally at least.

I'm really sorry that I dont exactly remember the procedure I used and can't help you in a better way. It's possible that I was forced into safe-mode as well, I don't remember but it's not unusual for me :)

Sometimes when you don't know what to do then it's a good idea to do just what Windows tells you. I do recall exactly the same situation, the right esdi.pdr combined with the wrong busmaster. So trash it all to make windows happy. Then see what comes back, if you're lucky the good drivers. But please don't forget that officially the Via driver cannot be uninstalled as stated by Via. That does not mean that it is always impossible but that the results are unpredictable. If there was a reliable uninstal method for all systems then Via could have offered it.

Link to comment
Share on other sites


Try booting into Safe mode, and removing everyything under Hard Drisk Controllers.

If you suspect there is "deeper" corruption, you can try removing everything from your device manager. I have done this before with mixed results; sometimes Windows will reboot and auto-detect all the hardware properly... other times, it just stays dead.

If VIA are the drivers taht are bad, you *should* be able to remove everything VIA-related in safe mode, in dev man, and reboot to initialize the hardware install again...

If it picks the wrong drivers again, DO NOT REBOOT AFTER INSTALL. As long as you DO NOT REBOOT, the system hasn't yet "locked in" the files. Try swapping out your drivers now, then reboot after you select the proper driver... If it doesn't work, boot into safe mode again, remove that piece of hardware in dev man, reboot and try again.

Honestly, it seems to me like you already hit a brick wall... I would try the above, simply because there's nothing to lose now, right?


Your particular problem may have an easier solution... I am not familiar with it, sorry...

Edited by DeadDude
Link to comment
Share on other sites


That's the direct download link from the mdgx.com page. I don't know if it will work from here but it's on his 98SE fixes page there, and this thread here is the one he links to for further info.

The auto-patcher includes that and installs it by default. I toggled it off as I wasn't using a large hard drive and would rather not change the file if not necessary. But that's the one I would use only because of my personal preference to not change the buttons in the Close Program box to the older, Windows 3.1 style where the buttons don't pop out at you. I don't know for sure, but I think that is the only difference between the exe and LLXX's version. Well. besides needing to install LLXX's from the command prompt only or MS-DOS Mode. The exe just runs by double clicking it in Windows.

Hmm, interesting that the Via driver allows 48 Bit LBA. I think your's were the posts I read telling that it does this, but then I read others and a Via Readme as well that stated otherwise. Someone asked me to find the Via readme once. Heh. It's somewhere. I read it. No, I'm not looking for it!

At this point I don't mind who's correct as I don't use a 686b southbridge board anymore. I wouldn't myself install it into any of my newer boards. Never used Windows 2000 either!

Link to comment
Share on other sites

Gentlemen, I thank you all for your replies and I'll respond to all of you in ONE message:

noguru: I can't remove the parent device because Windows doesn't know what it is (and neither do I). In fact, in Safe Mode, I have 2 copies of everything under Hard Disk Controllers and I can't delete any of them for the same reason.

DeadDude: I did try removing everything. See paragraph above. ;)

Eck: I have yet to try the direct DL of 48bitlba.exe. I don't seem to have any Inet connection when I'm in Safe Mode. :P

Link to comment
Share on other sites

To manually remove a device, start up Regedit and go to HKEY_LOCAL_MACHINE\Enum\. Search for exactly the same name you see in Device Manager, and remove the whole key (folder) which contains it. Then reboot to unload the drivers.

For example, to remove my IDE controller i should delete the HKEY_LOCAL_MACHINE\Enum\PCI\VEN_1106&DEV_0571&SUBSYS_05711106&REV_06\BUS_00&DEV_07&FUNC_01 key which contains the value "VIA Bus Master PCI IDE Controller", and the child devices in HKEY_LOCAL_MACHINE\Enum\MF\

Edited by RainyShadow
Link to comment
Share on other sites

Problem solved. Here's what I did....

In Safe Mode, I attempted to install the VIA 4-in-1 drivers. This failed! It went looking for some via file that it and I were unable to find. (I've just now found it in windows\system\CatRoot\{40-char hex string}. Gosh, why didn't I think to look there? :P )

So once it failed and I rebooted, it did reboot normally HOWEVER my high-cylinders partition (D:) was completely hosed. I then used 48bitLBA.exe, which installed 4102225 - not the one I have! And LLXX had said to use the same version number. Attempting to restart had me shutting down eternally. Used the switch. Switched back on and it hung when the systray would be filled. So I put back the original version (which is 4.10.2222).

Came alive again with D: scrambled. Put 4102222 in place and rebooted. VOILA!!! I am a happy camper! And I thank all who assisted here, with a particular tip of the hat to LLXX.

Link to comment
Share on other sites

See, this is why I never recommended using an automatic installer in the first place.

There is just too much bloat and overhead associated with such (how hard is is to boot into DOS, copy a single file, and then reboot?), and if something goes wrong, whoever installed it in the first place now has no idea how to uninstall, because you need to have Windows functioning to use the (rather useless IMHO) "uninstall" feature. On the other hand, following my procedure, she would know to copy back the original file, and it is done in DOS which practically runs on every PC in existence.

Also, this is why I recommend replacing your ESDI_506.PDR with the fixed exact same version, and also why I don't recommend using newer versions just because they claim certain benefits. Don't fix it if it ain't broken.

Link to comment
Share on other sites

Ah! Okay, I see your point completely. I've just been so used to Windows installers and had read MDGx's post where he pushed the newer versions are better message.

Plus, when I had experimented with both using the same version file installed from Command Prompt Only and the exe version that installs that one version regardless of the one it replaces I had no ill effects either way. Both worked fine, but the exe version did not change the buttons in the Close Program box so I liked that better.

Since I had no ill effects with the installer version I had no idea it might have a different, disabling effect on someone else's system. Kind of like Microsoft releasing a Critical Update in Windows Update and then seeing if it messed up peoples systems, and only then fixing and rereleasing it.

I suppose even they cannot test for every possible system configuration and so that's why that kind of stuff happens.

I am happy the problem was fixed up and sorry about the effect the exe version had! Yes it is very easy to just install the correct, matching version number using MS-DOS. I just hadn't realized that having the same version was critical.

Haven't used it in a while as I haven't installed 98SE to a partition over 120GB lately. I even toggled off the installation of the exe version in the auto-patcher as I didn't see the need to install a fix for a problem that wouldn't occur on a smaller partition.

Link to comment
Share on other sites

Gosh, I also made a stupid mistake here! The LLXX vs. Anonymous EXE file I had experimented with in the past was not the ESDI_506.PDR fix, but rather the KERNEL32.DLL patch to prevent large file copy/delete problems using Explorer.

I've never installed either version of the ESDI_506.PDR patch.

So, wrong thread, wrong advice, and butting in where more techy (and less confused) heads dare tread!

Good job. Well, I tried. I feel like Emily Litella (Gilda Radner) from Saturday Night Live.

Never mind.

Link to comment
Share on other sites

  • 1 year later...
If anybody objects to "Commercial" code, they can write their own, independently of course. My Patch is not suited for any of the Open Source Business models.

Dear Mr. Loew,

Its amazing to see your posts in this forum, caz we see all here are to help each other, not to sell "commercialized" products. And btw why you yoursellf be not the person to make "Open Source" your work? see, win98SE needs open source now, not commercial anymore.

Sorry if it shocks :)

Link to comment
Share on other sites

  • 8 months later...

:sneaky:In seek of a right ICH7 SATA / ATA driver for Windows 9X

My problem is deep rooted and frightening but it is a single problem – Lack of ICH7 SATA driver set for Windows 98SE. I believe that one of software giants has discouraged Intel to further provide Windows 9X drivers for newer chipset. The newer chipset happened to be in my Dell Dimension. With this excessively bitter experience, I may not buy Dell or any newer MS-OS ever again in my life time as longer as Windows 98SE, Solaris and Linux remain strong. In my Dell, Windows 98 is barely surviving without correct driver. USB GEforce and SB Audigy works well because I was able to overcome through cut and paste pci/ven hundreds of time to establish right pci-e root bridge in CPU/motherboard resouce hook.

Windows 9x and Windows NT are built with right and altruistic mind and I can welcome their personalities so to speak and live with them but not with XP or Vista.

I do not want OS itself to get into every operations of computer. OS only should perform launching the programmes and minimal house keeping of memory. I do not expect anything out from it.

I do not want CPU bus bridges (a.k.a., memory controller or multifunction bridge) themselves to get into every operations of computer. Making them emulate sound card, video card and RAID controller are out of question.

My real dream system would pave 10 or so PCI-X slots of 133 or 266MHz bus with at least 18 hardware IRQ allotted. Each card go into these slot has i80303 or better PCI bridge/dedicated IO Controller with embedded CPU with 256 MB on card memory. It means that printer card, mouse card, floppy card, sound card all shoals have own CPU/LPU/MPU and memory subsystem that OS does not even have to know. Give a file name to all such subsystem as memory block.

I did succeed to build a system at leaset a halfway close to this ideal in 2000

Two Xeon CPUs

Intel 80303 on SCSI card 256MB (7 Int13 compatible GDT Logical Volumes formed before OS start)

Motorola 68030 and Emu DSP on Sound Card 64MB

Intel i80960 on Tektronix Printer 64MB

Matrox Millennium 400 (to gain Unix compatibility otherwise GE force GTS is OK)

Another AHA3950 for CD/CDR and scanner

OS supported: Solaris, BSD Unix, Caldera-SCO, Redhat, Suse, O/S2

PC-DOS7. Window 3.1, Windows 95a, Windows 98SE, Windows ME

Windows NT 4.0, Windows 2000, Windows XP 1.0

Supported OS means they can co-exist without modifying metafile structure of legacy form NTFS 1.X. System runs XP and Vista fine but they modifies old Windows NT 4.0 basic data volumes exist in extended partitions if you do not manually pre-mark their EPBR ID from 07 to that of an Unix type such as bf. This invasive personality of Vista and XP 2.0 or 3.0 rules out their qualification of compatibility to any of my system. They can even kill their own sister Windows NT 4.0’s partition.

I am not so much affected by LBA28 LBA32 or LBA48 issues since I never have owned any SCSI disk larger than 280GB (Cheetahs 15.5 Series) nor SATA (Barracuda ES2) larger than 0.954TB per single unit. To install any new OS on SATA platform, I temporarily put an Adaptec 39160 with SCSI drive in channel A and DVD or CD rom on channel B for temporary installation then check if OS and driver correctly mount and recognise file system on SATA. Run series of test from there, then ghost new OS partition from SCSI onto SATA and hide original partitions on SCSI after marking newly ghosted partition active on SATA MBR. Believe or not, it is not too much work. I am used to boot Unix OSes from command line with single or double line strings invoking boot loader. You get used to it. The first, I had to develop a mind to comprehend to different device block mapping expressions pointing out OS kernel location in the system such as c0t0d0p1s:a, /dev/sda1, h0,0,1 or multi(0)disk(0)rdisk(0)partition(1). Then lean primitive commands like map, remap, hide, find, offset, root, boot, kernel and setup.

I never knew anything except SCSI because SCSI was easy and friendly due to being shared bus system with its addressing manually setup by controller slot and jumper pins on target. Of course I was charmed by new generation WD VelociRaptor SATA II disks which boot Windows XP faster than 15000RPM Seagate Cheetah 15.5 series drives. But I trust more familiar SCSI a lot more. SCSI has never given me any headache for past 15 years in any OS arising out from driver issue.

Economic interest was not build into hardware enumeration hierarchy until 486 or even early P5. Pci/ven code started to appear in Windows registry after P5 era. Windows block device mapping has no logical relation to physical device mapping e.g., c0t0d0p0s:b (hba ID, target ID, disk ID, partition ID, slice ID) which makes more sense over Windows device vendor signature based mapping perhaps arising from its economic interests.

What a bitter world has it become! It can possibly mean that if a hardware manufacturer wasn’t nice enough to software giants then the hardware manufacturer can be easily killed by deprived of sales unless the manufacturer was independently powerful as Hitachi, NEC, Panasonic, Pioneer, Sony, Siemens and like. Sadly IBM, Sun and Apple have slightly lost their level of freedom and power comparable to Sony in the past 8 years. Lets give them chances to restore themselves in the next 8 years!

Long Live the MSFN to succeed in its unbiased altruistic mission!

Long Live Windows NT and 9X!


Link to comment
Share on other sites

Thanks firstly for the info on this thread.

The BIOS is also a crucial issue AFAICT....

Found a free utility that says it will tell you if your BIOS supports 48-bit Logical Block Addressing (LBA). Not tried it yet, though.


Note the free version is for those with a floppy disk drive which I guess covers most of us here.

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...