Gape

Windows ME's FDISK supports big HDDs. So partitioning and formatting is not a problem. The problem is not the detection, too. The problem is to cross the 137 GB barrier. Look Petr's comments, and 48bitlba.com for more information.

nForce's drivers support more than 137 GB HDDs. Also VIA, SiS, ALi etc. supports more than 137 GB with their drivers on the Windows 98/ME. Intel also supports more than 137 GB on Win98/ME with their Application Accelerator product. This problem is from ESDI_506.PDR, which is internal main IDE driver file of the Windows 98 / ME. If you don't use internal IDE drivers of the Win98/ME, you will not have this problem.

This patch is commercial. How did this guy hacked Esdi_506.pdr? It should not be difficult. I think Windows ME's Scandisk and Defrag doesn't handle big HDDs, too.

What is this? Is that a modified version of Q311561? Tihiy, what can we do about RAM problems and 137 GB HDD limit? Can we hack VCache.VxD and/or Esdi_506.pdr?

Interesting. IE 5.01 SP2 and IE 5.5 SP2 have also this iphlpapi.dll file.

Not exactly true? I said it for the hotfixes' installation... MDCU only installs all files with: filename.ext,,,32 (COPYFLG_NO_VERSION_DIALOG) But SE SP installs files with four different methods: filename.ext filename.ext,,,32 (COPYFLG_NO_VERSION_DIALOG) filename.ext,,,1024 (COPYFLG_REPLACEONLY) filename.ext,,,1056 (1024 AND 32) If a user doesn't have a file on his/her system, generally SE SP will not copy the updated file. So SE SP tries to install only needed updates as much as possible with this mechanism. Of course, because of "preserving" mechanism of Windows 98, if system needs this file later, it is copied from SP2.CAB, not from Windows's setup CABs. More info about INF CopyFiles. Thanks for the other additions/corrections.

Comparison of SE SP 2.0 and MDCU 2.1: - SE SP tries to install only necessary updates for your system, MDCU installs all updates. - MDCU contains a good generic USB mass storage device drivers adopted from Windows ME. - MDCU doesn't support uninstallation. - MDCU doesn't contain some features of SE SP: # Solves 512 MB of RAM problem. # Better Notepad. # Windows Scripting Host 5.6. # Microsoft Installer 2.0. # MDGx's HTML Help Update. # TweakUI (Optional). # Command Prompt Here (Optional). # New Animated Boot Logo (Optional). # Supports 98lite 4.7. # Windows 2000/ME desktop icons. # Windows 2000 color scheme (Optional). # Shows attributes column in details view on the Windows Explorer. # Some tweaks (Optional).

Look here.

It adds this fix's info into IE's About Dialog Box. Maybe it's from Win2000 SP4, I try to find the source. I extracted this file from MOBILE.CAB, but its version is something like 4.10.1500.1 (Both Windows 98 and XP shows it as 4.10.1500.1).

Hi Petr, Thanks for this feedback ! Yes, but "copy" is in the command.com, and it exists on all systems.Sometimes "move" doesn't exist on some systems like some 98lite users. This patch contains only a few REGISTRY settings, they're in the SPUPDATE.INF. Probably there is no need for this tool, I'll remove it. My Q313829 (ENGLISH) contains 3072 bytes VERINST.EXE.About Regsvr32.exe and Ctl3dv2.dll, I'm not sure now. (Ctl3dv2.dll sent by MDGx, Regsvr32.exe is probably from IE60SP1). I'll correct these entries on SPUPDATE.INF. This version is latest and compatible with IE 5.0, 5.5 and 6.0. It is only a WAV file, and it's compatible with IE 5.0, 5.5, and 6.0. I haven't tested it. If it works properly with Win98SE, I can include it. They will in the 2.0 FINAL. ASPI 4.60 (ForceASPI 1.7) works properly on Windows 98 SE, and lots of users say that It's best ASPI layer for Windows 98 (SE). Just search 471.2 (ForceASPI 1.8), you will see some complaints about this version. There are lots of updates in the SP 2.0, and it is very difficult to maintain all these QFECHECK entries with INF installers.

@simon109s I'm almost sure that it is a driver issue. Boot in safe mode. Go to the Control Panel, delete all listed Nvidia Drivers. Also look for any device which is listed twice. If you find any twice listed device, delete one of them. Reboot, and let the Windows detect your Nvidia card. Areyou installed your AGP drivers properly? @all I want to ask that what do you think about 891711? We have two different fixes, Tihiy's and Microsoft's. As a programmer I think Tihiy's work is better. I didn't understand that why Microsoft did solve it with additional files, and an additional background file (KB891711.EXE).

Did you use German version? Can you list your detailed hardware list? Please look at this post, too.

Thanks swgreed, looks like a bug. Please also look at this post.

Thanks HSI.

It looks like a hack problem. Maybe German version's Kernel32.dll and/or User.exe files are not hacked correctly. swgreed, who makes German version, can provide more info about this.

Did you install SP 2.0 RC3 German or English? Is your hardware OK? Especially are you sure that your RAM is OK? Can you write a detailed list of your hardware?

Don't uninstall it. You can install it again without uninstalling. Update your drivers, and install the SP again.

I tested your fix, it works great, but I haven't tested MS's new fix. In fact, I don't like MS's fix. It requires a seperate process to load.

Latest status: 888113, and 891711 (Tihiy's) hotfixes are added, and fixed 98lite Sleek uninstallation problem. Everything seems OK. I will test it today and tomorrow. I hope I'll release 2.0 FINAL in this weekend. Thanks for your support!

Your Bootlog.txt file looks OK. Other ideas: Try to update all of your drivers (especially mainboard, and sound drivers). Try to install SP 2.0 again.

These drivers are not for all USB devices, jasinwa. They're only for storage based USB devices such as flash disks, cameras.

Open your computer, and immediately after BIOS screen press F8 to show boot menu. In this menu, select logged startup. After that, you will probably have a BOOTLOG.TXT

Interesting problem, but I said "BOOTLOG.TXT", not "BOOT.INI". (Note: It is in the C:\, and sometimes BOOTLOG.TXT file is marked as hidden.)

You're right.

891781 looks like IE specific update. So, it will not be in the SP 2.0. 888113 will be in the SP 2.0. Probably, Tihiy's fix for 871711 will be in the SP 2.0, too.