• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About dajhorn

Profile Information

  • OS
    Windows 7 x64
  • Country
  1. Yes, the .NET installer for Windows XP does update some DirectX components. For example, it installs enough of the media runtime to provide the EVR filter.
  2. Windows Update will glitch if the current Office 2016 beta is installed over an earlier version. At the moment, completely uninstalling earlier versions ensures that Office 2016 will be automatically updated.
  3. This file was usually installed with Internet Explorer or the Visual Studio runtimes. Although it was not bundled in early releases, it eventually became a standard system component, so avoiding it will be difficult. The oleaut32.dll file in POSReady 2009 was updated by this patch: * https://support.microsoft.com/kb/3006226 File: C:\windows\system32\oleaut32.dll Date: Friday, October 17, 2014, 8:17:56 PM Version: 5.1.2600.6663 MD5: 02e2f13ba0e52e41f5e0fb768e11b604 SHA256: 43a4d942709dac1059c89dcd5239448bfad155e5b7cb2fc49a3539b8c93473df The schannel files were updated last Patch Tuesday too. Watch for it here: * http://www.htasoft.com/u98sesp/
  4. Yes, you need this trick because POSReady defaults to sector 63. The bundled diskpart.exe does not implement the 'offset' or 'align' parameters. POSReady 2009 is identical to Windows XP in all the ways that matter.
  5. Microsoft Security Essentials can be installed on POSReady 2009 by merging the attached stub into the registry. This resolves MSSE installation error 0x8004FF04.
  6. It looks like the default memory area for this card isn't sensible, but Windows 98 doesn't know how to remap devices on the Intel 945 chipset. You're probably stuck because Intel didn't publish a Windows 98 chipset update for this motherboard. Try your luck with a regular PCI video card instead.
  7. Microsoft too often buries that kind of useful page. This link is a list of Knowledge Base articles sorted by product, which is something similar: http://kbupdate.info/
  8. Spiffy. Thanks for posting this.
  9. I went back and traced the U98SESP3 installation on my computer. I'm running Windows 98 SE from the last MSDN distribution for 95/98/ME. U98SESP3 installs updated DUN system files, but does not register the new adapter if the old adapter is not already installed and configured. To reproduce, click: Control Panel Network Configuration, Add Adapter, Add Manufacturers, Microsoft Network Adapters, Microsoft Virtual Private Networking Adapter OK (and the dialog silently fails) This seems to happen because U98SESP3 breaks the "Virtual Private Network " component dependencies for Windows Setup during the SP3.CAB override. The usual dependencies for "Virtual Private Network" disappear, which are "Dial-Up Networking", "ISDN Configuration Wizard", and "Telephony Support". A silent dependency on "Dial-Up ATM Support" is also added, because if the registry changes for that component don't happen, then the new adapter is not registered. Toggling the entire "Communications" section or running dun14-se.exe resolves the adapter registration glitch after running U98SESP3. Does this project have a repo for developers? The changelog doesn't explain how or why things happened, and having the change history would make it easier for me to submit a patch instead of a bug report.
  10. @PROBLEMCHYLD For the 3.1 release, please add Dial-Up Networking 1.4: http://support.microsoft.com/kb/297816 http://support.microsoft.com/kb/297840 This update for Windows 98 from Microsoft has general networking fixes (for SLIP, PPP, ISDN), adds VPN support, and provides some 128-bit crypto facilities. The files linked through Windows Update had these MD5 hashes: 7b7355cebbd14b8b99cfa882e512ff6b *dun14-95.exe 1dd0e9d6050cc37d69a054124fcc7d9b *dun14-98.exe 170bcb2ff5e1e458040c9b54ecb3d8fc *dun14-SE.exe