Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

creopard

Member
  • Content Count

    534
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

1 Neutral

About creopard

  • Rank
    Unofficial Service Pack & Codec Pack maintainer

Contact Methods

  • Website URL
    https://www.creopard.de

Profile Information

  • OS
    98SE

Recent Profile Visitors

1,680 profile views
  1. For translation tasks you could also use the tools "reshack" or "exescope".
  2. Windows 98 SE (of course) in several retro gaming rigs...
  3. There is a workaround: https://communities.vmware.com/message/2947137#2947137
  4. Here's a quick fix for German users: While using the English version of FDISK.EXE or FORMAT.COM on a German keyboard layout/system, FDISK/FORMAT required you to enter "J" (for "Ja") instead of "Y" (for Yes) altough it displayed that you should choose between "Y" and "N". This was very confusing, so I changed the FDISK/FORMAT executables accordingly, that it would now display and accept "J/N" as it is way more user intuitive (see attached file). FDISK_FORMAT_fixed_de.zip
  5. Sorry for the late reply. Unfortunately, the link https://easyupload.io/w0hg8v does not work any more. The "list index out of bounds (3)" occurs if the infex.ini is malformed. Execute infex.exe to see if there are any errors (works also within Windows 10, but don't install anything) .
  6. If your concern is about space and you don't want to mess around with "iexpress", you could also follow a more pragmatic approach: unzip the U98SESP3.EXE remove components you don't want physically (e.g. "fonts.cab" and "dx9c.cab" as they require the most space) also remove the corresponding entries from the "infex.ini" file (so they don't appear as install option any more) create a new executable ZIP file (with e.g. Winrar 32bit) with a SFX option, that would call the "infex.exe" upon file extraction (you will create your own installer this way)
  7. Creating the installer package is pretty stright forward, you just need the files from the original and create your own package with "iexpress.exe": http://www.mdgx.com/INF_web/index.htm The installer will call the "infex.exe" file during unpacking the installation files and display the options that are entered in "infex.ini". Each option triggers then one of the .inf files that reside inside the package, e.g. SPUPDATE.INF or ZIPFLDR.INF ans so on...
  8. I would like to announce the German version of the unofficial Windows 98 SE SP Version 3.x based on PROBLEMCHYLD outstanding work. It's currently in beta state and lookingfor beta testers. It does not include all features of its English predecessor (yet?), however some more Win ME files were interspersed where appropriate. Its focus is also more on retro/games, thus spider solitaire and space cadet were also included, as well as Tihiy's "IPtest - network inducator" tool. If you run a German Windows 98 SE and would like to have a look, please feel free to download it at https
  9. Very helpfull, indeed. Currently, there are only PE files with zero headers left
  10. Obviously I chose the way "learning by doing" - I was not yet familiar to linear executables and new executables... But thanks for pointing at the right direction. I was assuming that "PEChecksum" would have a look at offset 80h and check for "PE" before calculating a new checksum. Would it also make senseo to correct the checksum of NE and LE executables?
  11. I'm patching them because I'm currently updating the outdated German "Windows 98 SE SP 3.0 beta4" to a new/fully tested version 3.1. As you can imagine this requires replacing/editing quite some files with the German equivalents... Based on PROBLEMCHYLD's "U98SESP3" Pack, I'm recreating the German version, hence the question about the checksums. Here is the list of files that had the checksum updated: However I didn't narrow the list down yet to specific files, that might provoke the protection error...
  12. I guess it's not a good idea to fix the checksums of .vxd files? After fixing all files with "PEChecksum" (from n7Epsilon) Windows 98 prompts me with a "protection error" "while initializing device CONFIGMS".
  13. I've seen in various threads that users modding/hacking Windows 9x files recalculate the PE header checksums of the modded file. What's the purpose of that?
  14. The wpi.net WEbsite is pretty dead / full of scam. Whoever want to have a look at the WPI Tool, have the only archived file from here: https://web.archive.org/web/20110501183832/http://www.wpiw.net/Downloads/WPI_Classic_v2.2.rar
×
×
  • Create New...