Jump to content

Gape

Member
  • Posts

    446
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Turkey

Posts posted by Gape

  1. Well my above system handles 200 and 250 GB without additional controller card or the Intel Application Accelerator.  Athlon 2600 on Abit NF7S nForce2 chipset. The 200 GB drive has been spinning under ME (and maybe 98 but I can't be sure anymore) on an MSI motherboard with a Duron and then the above Athlon.

    I would think one may think he needs that stuff only if one wants to plug large capacity drives on VERY OLD motherboards.

    I am far from being an expert but I think this thing maybe a rip-off as I don't see how a driver patch can affect the limitations of the BIOS.  In those cases I am not sure one can do anything if one can't flash the BIOS with a firmware upgrade.

    Thanks to correct me if I am wrong.

    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.

  2. Recently maximus have sent me a hexed copy of that patch which works with drives up to 400GB; i'm currently testing it now.

    Also some DOS/Windows tools can't handle this limit as well.

    It can be fixed by using Windows ME tools like scandiskw or defrag. New DOS tools can be used from FreeDOS.

    "DOS driveletter fix" is a patch for any io.sys which makes DOS to forget drive letter order when installing new drive.

    This patch is commercial. :angry: 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.

  3. Not exactly true. It uses same Windows install mechanism and does not contains any IE/MDAC/WSH/MSI/VCRT updates, so all updates can be installed well.

    Install order. It's tested many times and different from SE SP.

    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.

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

  5. OK, and what does the command %winbootdir%\VERINST.EXE q240308 in the RUNPST.BAT file? I have no idea how verinst works.
    It adds this fix's info into IE's About Dialog Box.
    Regsvr32.exe in IE 6.0SP1 English is 5.0.1586.1, i.e. even older (in Gsetup95.cab).

    Maybe it's from Win2000 SP4, I try to find the source.

    I have also noticed one file that was included with IE 5.0 but in Win98SE is older:

    iphlpapi.dll - Windows 98 SE (Net7.cab):  5.0.1717.2

    iphlpapi.dll - IE 5.0 (mobile.cab): 5.0.1952.1

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

  6. Hi Petr, Thanks for this feedback ! :thumbup

    Maybe instead of 3 lines

    if exist %winbootdir%\system\iosubsys\SMARTVSD.VXD goto end

    if exist %winbootdir%\system\SMARTVSD.VXD copy

    %winbootdir%\system\SMARTVSD.VXD %winbootdir%\system\iosubsys

    if exist %winbootdir%\system\SMARTVSD.VXD del %winbootdir%\system\SMARTVSD.VXD

    would be better just one line and without "goto":

    if exist %winbootdir%\system\SMARTVSD.VXD move

    %winbootdir%\system\SMARTVSD.VXD %winbootdir%\system\iosubsys

    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.

    I see no Q240308 patch in the SP but it is referenced in the bat file:

    if errorlevel 0 %winbootdir%\VERINST.EXE q240308

    This patch contains only a few REGISTRY settings, they're in the SPUPDATE.INF.

    2 to 4 Digit Date Conversion Tool

    http://www.microsoft.com/windows98/downloa...ion/Default.asp

    seems to be just for Windows 98 Gold, Windows 98 SE seems to have the

    4 digit year display in Control Panel/Regional Settings already set.

    At least in Czech version of Windows 98 SE.

    Probably there is no need for this tool, I'll remove it.

    regsvr32.exe - according to spupdate.inf it is from vs6sp6, but:

    SESP2RC3 contains version 5.0.2134.1

    vs6sp6 contains version 5.00.1641.1

    Verinst.exe - according to spupdate.inf it is from 313829, but:

    SESP2RC3 contains file 3072 bytes, 23.11.1998 9:33

    Q313829 contains file 21504 bytes, 21.11.1997 8:10

    Ctl3dv2.dll - I don't know what is the source of version 2.31.001.

    Do you know where they came from?

    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.

    Then some unclarities with IE:

    Sens.dll - according to spupdate.inf it is from 258191, but

    SESP2RC3 contains version 5.50.4807.2300 (from Internet Explorer 5.5

    Service Pack 2)

    Q258191 contains version 5.0.2729.1800

    This version is latest and compatible with IE 5.0, 5.5 and 6.0.

    Q319303 - http://support.microsoft.com/kb/q319303

    seems to be upgrade just for Microsoft Internet Explorer version 6 but

    you don't include other updates for MSIE other versions than the 5.0

    supplied with Win98SE?

    It is only a WAV file, and it's compatible with IE 5.0, 5.5, and 6.0.

    RICHED20.DLL

    SESP2RC3 contains version  5.30.23.1215

    w2ksp4 contains version 5.30.23.1215

    wxpsp2 contains version 5.30.23.1221

    Maybe this newer version could be used? Or there is any incompatibity?

    I haven't tested it. If it works properly with Win98SE, I can include it.
    New hotfixes from Microsoft for Windows 98 Second Edition

    888113 - http://support.microsoft.com/kb/q888113

    891781 - http://support.microsoft.com/kb/q891781

    They will in the 2.0 FINAL.

    Adaptec's ASPI - I'm not sure why version 4.60 is included in

    SESP2RC3, according to the Adaptec website:

    http://www.adaptec.com/worldwide/support/d...=aspi_471a2.exe

    the right version for Windows 98 is 4.71.2, version 4.60

    http://www.adaptec.com/worldwide/support/d...ekey=aspi32.exe

    is older and "requires that either an Adaptec host adapter or an

    Adaptec version of the ASPI layer be installed on your system"

    I remember that there were some rumors about a bug in 4.71.2, but this

    version was released on 23 Nov 2002 and is still recommended by

    Adaptec.

    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.

    Why not to add registry entries for QFECheck?

    There are lots of updates in the SP 2.0, and it is very difficult to maintain all these QFECHECK entries with INF installers.

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

  8. Hello guys,

    I've got a problem during the shutdown of windows 98.

    I installed a fresh windows 98 and only actualized the graphic drivers, because the other drivers were identified correctly by the operating system . After a system reboot it looked quite good. But the next reboot produced a so called Mprexe-error and the system stopped. Only a restart helped.

    In the next step I installed win98 but added no more drivers. After the installation of SP2 RC3 the same error appeared.

    What should I do?

    Alex

    PS: I also miss the KB891711 and the KB891781 Update. Perhaps you can release the fixes, or Tihiy's new KB891711 version, in the next RC.

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

  9. A question concerning the "runpost.bat":

    if exist %winbootdir%\system\iosubsys\SMARTVSD.VXD goto end

    why should the batch end here, when SMARTVSD.VXD is present?

    SHELL32.INF or SLEEK.INF and PATCHRE, PATCHNP, q240308-update won't be executed.

    Is the behaviour really wanted this way?

    Thanks swgreed, looks like a bug.

    Please also look at this post.

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

  11. But when I power down my 98PC. The next time I powered up again, most likely it'll go to 16 color and resorted on restart.  :huh:

    It looks to me likely it does not load the graphic driver correctly when first power up. I wonder why...even thought i update my nvidia to 71.84.  :angry:

    Gape, here is my 98SE boot.ini contain;

    --deleted--

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

  12. randiroo76073 is right on with KB891711; causes major BSOD problems at Windows startup, especially if using certain firewall or proxy software installed.

    Hopefully the KB891781 and KB888113 W98 patches will be included either in 2.0 RC4 or 2.0 final.  Let's see if Gape will include them if he can respond to this topic.

    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.

×
×
  • Create New...