there is a predicate inside MGDx' post that I sort of like …
and that is the idea that windows 98 is definitely not being put to bed just yet … I have no doubt that there will definitely be updates in the future.
so, setting aside the flak I may take for this … because what I'm going to do is suggest that as Autopatcher98se gets finalized, its one-gulp format (which is excellent for consolidating development overview but at 230M gives everyone on dialup heartburn) will cause accessibility problems and a reactionary political pressure.
Might I suggest that AP98se be eventually merged with DefinitiveList98se … in the manner of jcarle's wonderful msfn project called Windows Update Downloader for Unattended CDs see
http://www.msfn.org/...p?showforum=147
For w2k, the WUD Windows Update Downloader reads a text-based updatelist .ul file (contained in a zip .ulz), and maintains a homebase directory of patches and add-ons for 2K-autopatcher. The homebase directory is divided into sensible categories, each category maintained in its own directory, specifically, [.NET Framework 1.1] [.NET Framework 2.0] [Critical Updates] [Service Packs] [Windows Media Player] [Other]. "Other" contains things like Windows Rights Management, Windows Installer, etc. etc.
The .ul updatelist file is a text-based xml file, which for 98se is almost already prepared from soporific's update list. An example of the first listing in the current .ul file is
<?xml version="1.0" encoding="ISO-8859-1"?>
<updatelist product="Windows 2000 Professional" platform="x86" language="ENU" lastupdate="2007-03-13" xmlns="http://wud.jcarle.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://wud.jcarle.com http://wud.jcarle.com/wud.xsd">
<!--Generated file by Rj's ulTranslate v1.6, translated from w2k-v3.xml (2007-03-13)-->
<categories>
<category id="1">Critical Updates</category>
<category id="2">Service Packs</category>
<category id="4">.NET Framework 1.1</category>
<category id="5">.NET Framework 2.0</category>
<category id="7">Windows Media Player</category>
<category id="9">Other</category>
</categories>
<updates>
<update id="KB928090" category="1" publishdate="2007-02-13" article="http://support.microsoft.com/?kbid=928090">
<!--http://www.microsoft.com/downloads/details.aspx?familyid=D9E4181A-05F9-4186-BDCA-C95351983844&displaylang=en-->
<title>Cumulative Update for Internet Explorer 6 SP1 (KB928090)</title>
<description>This update addresses the vulnerability discussed in Microsoft Security Bulletin MS07-016. To find out if other security updates are available for you, see the Additional Information section at the bottom of this page.</description>
<filename>IE6.0sp1-KB928090-Windows2000-x86-ENU.exe</filename>
<url>http://download.microsoft.com/download/1/2/c/12c22818-1b18-4f7b-88b6-e17c97a98bc8/IE6.0sp1-KB928090-Windows2000-x86-ENU.exe</url>
</update>
jcarle's WUD, if fed an updatelist for the 98se patches, could be used by any user to automatically maintain his or her homebase of update files in 1-10 Meg chunks. The schema for 98se would obviously differ from that for w2k, so I'll outline the w2k process: the user downloads the latest .ulz (10k), unzips it to a .ul (53k), and opens it in WUD update downloader. WUD reads the home directory of the user, and compares its filelist to the latest update. It graphically gives the user the option to select which files needed, and then downloads them (a nice feature). It can delete the unwanted files from the home directory. For w2k, different .ulz files can be maintained for different languages too, which might be nice for 98se too.
After soporific finalizes Autopatcher98se technology (for which for testing he obviously needs total control of patches available on the computer and their locations), I would love to see his technology compressed to a zip file and then combined with a companion .ulz file. The companion 98se.ulz could then maintain the precise directory structure on the user's computer, exactly to soporific's specifications, through the WUD downloader. That would solve the problem of the big-endian 230M one-gulp, and it would solve MGDx' softly expressed concern that room be left open for future growth -- it might be one way to make soporific's technology a part of the future of 98se.