Duke4.net Forums: Hendricks266 - Viewing Profile - Duke4.net Forums

Jump to content

Hide message Show message
Welcome to the Duke4.net Forums!

Register an account now to get access to all board features. After you've registered and logged in, you'll be able to create topics, post replies, send and receive private messages, disable the viewing of ads and more!

Reputation: 6311 My posts turn threads into gold
Active Posts:
7,550 (2.1 per day)
Most Active In:
Everything EDuke32 (2745 posts)
08-May 09
Profile Views:
Last Active:
User is online 32 minutes ago
Viewing Topic: What are you working on for Duke...

My Information

Member Title:
Sperge Overlord
23 years old
May 31, 1995
Male Male
United States

Contact Information

Click here to e-mail me
Website URL:
Website URL  http://hendricks266.duke4.net

Latest Visitors

Topics I've Started

  1. Shadow Warrior 1.0-1.2 EXEs Accurately Recreated, Source Code Re-released

    06 February 2019 - 10:37 AM

    With access to SW materials from the 3D Realms archives and official blessing from Devolver, NY00123 has extended his gamesrc-ver-recreation project to cover Shadow Warrior (1997). In addition to accurately recreating 1.2 Registered, we can also recreate several versions and variations, including 1.0, 1.1, and 1.2 Shareware.


    NY00123 said:

    Thanks to @devolverdigital, @3DRealms, @Hendricks266, TerminX (@voidpnt) and Ken Silverman, you can now download the following package consisting of Shadow Warrior sources matching versions 1.0-1.2, a few older Build engine sources, and other files:


    NY00123 said:

    Shadow Warrior (1997) and bonus Build Engine Source Codes Release - 2019


    This archive covers differing source snapshots of Shadow Warrior (1997),
    a few Build Engine sources, and other files.

    The Build Engine sources are licensed under the terms
    of the Build Source Code License. They can be found in BUILDLIC.TXT.

    The Shadow Warrior (1997) code is licensed under the terms of the GNU GPL
    (General Public License) version 2 or later. See GPL-2.0.TXT for the details.

    In addition to the terms of the GNU GPL referenced above, you are granted
    a linking exception, for the purpose of linking any of the aforementioned
    Shadow Warrior (1997) sources with other code used in
    the original EXEs from 1997. This also covers derivatives
    of the same code, like modern ports of the Build Engine.

    Be warned that in general, the terms of the GNU GPL do *NOT* apply to any
    such additional code. The Build Engine is a good example of this.

    In particular, commercial exploitation of the additional code
    is *NOT* allowed unless specifically permitted.

    Please do not contact us for help with using the source code. We cannot
    assist with getting this running and there is no guarantee of any kind.
    Use at your own risk.

    Any following mention of "Shadow Warrior" or "SW" will refer to the 1997 game.


    This release is dedicated to the memory of Terence Colligan. Further known as
    Terry, he was the founder of Tenberry Software (previously Rational Systems).
    A notable product of this company for the time was DOS/4G, a DOS extender
    used for a myriad of 32-bit DOS programs, and games in particular.
    These include games made with the Build engine,
    Shadow Warrior being no exception.

    Many thanks go to 3D Realms for digging up old materials found in this
    archive, including the Shadow Warrior source codes, later to be sent to
    Richard Gobeille and Evan Ramos, who further inspected such materials.

    Additional thanks go to Evan for getting the ball rolling, Devolver Digital
    for their permission to release the old Shadow Warrior materials, and
    Ken Silverman for his consent to release the older Build Engine sources.

    Further thanks go to Ken Silverman for open-sourcing the Build Engine on 2000,
    and to anybody involved in open-sourcing Shadow Warrior on 2005.
    This includes Frank Maddin (one of the original Shadow Warrior programmers)
    for digging up the sources and assisting with their release, Jonathon Fowler
    (responsible for the JonoF ports of Build, Duke3D and SW) using his experience
    for technical assistance, Charlie Wiederhold for preparing the
    sources for release and 3D Realms for paving the way.

    Finally, thanks to all fans of 3D Realms, Devolver Digital,
    General Arcade, Shadow Warrior and the Build engine!

    Building any of the Shadow Warrior EXEs or the SW Build editor EXE

    The Shadow Warrior sources found in this archive were prepared in
    such a way that with the right tools, you can create EXEs functionally
    equivalent to the ones released on 1997, up to the following differences:
    - Adding MemCheck (MC) 3.5 library code in the linking stage.
    - Binding the DOS/4GW Professional 1.97 extender.

    The SW EXEs in question can be found under the "exes" subdirectory, all
    being named SWNMC.EXE. The SWB.EXE files are the originals from 1997, while
    the SW.EXE ones are essentially SWB.EXE with the DOS/4GW extender removed.

    For the Build editor, the relevant EXE is BUILDNMC.EXE.
    As in the case of SW, BUILDB.EXE is the original EXE from 1997,
    while BUILD.EXE is simply BUILDB.EXE without the extender.

    For the behaviors to be as close to the originals as possible, it is important
    to use Watcom C32 10.6, and no other version. If you don't mind the
    accuracy, you can still try to use a different version,
    but this has *NOT* been tested.

    The following build directories are recommended if you want to further
    increase the accuracy of the recreation (mostly for debugging information):
    - Shareware versions 1.0 and 1.1, as well as the registered and
    parental locked releases (1.2): C:\DEV\SW.
    - Version 1.2, shareware and UK releases: H:\DEV\SW.
    - The Build editor (as originally distributed with the game): C:\JIM\SW\CODE.

    Additionally, for SW 1.2, it's recommended that the copy of Watcom C32
    in use is found exactly at C:\WATCOM. In particular, this includes
    setting the INCLUDE environment variable's value to C:\WATCOM\H,
    in an uppercase (well, UPPERCASE) form.

    Side-note: For SW 1.0 and 1.1, the Watcom path is shown in the original SW.MAP
    files in the lowercase form of c:\watcom (as a part of c:\watcom\lib386).

    Steps for building any of the EXEs:
    1. Make sure you have a compatible DOS environment with a ready installation
    of Watcom C32. As stated above, version 10.6 is (highly) recommended.
    2. Further ensure there's no existing directory named DEV in the same
    location as this README.TXT file and the PREP.BAT file.
    3. Run PREP.BAT and then select the SW EXE you want to make. If you want
    to make the editor EXE, choose any of the SW 1.2 EXEs.
    4. Wait for PREP.BAT's run to complete. You should end up with files ready for
    building under DEV\SW. As stated above, you may wish to set the exact location
    appropriately (e.g., to H:\DEV\SW for the UK version), but this is optional.
    5. Change to this same directory. To make the SW EXE, run MAKESW.BAT.
    6. If you have previously chosen to prepare the files for any EXE matching
    version 1.2, you can further make the Build Editor EXE by running MAKEBLD.BAT.
    7. Please be warned that you may wish to ensure the DEV\SW\OBJ directory does
    *not* include any of the following files first: MDASTR.OBJ, COLORMAP.OBJ.
    Otherwise, the layout of any involved EXE may change, at least if
    you're trying to build the game and editor EXEs altogether.

    Faithfully recreating any EXE, given access to additional files

    Please note that any output EXE file might still differ from the original,
    depending on the specific MemCheck and DOS/4GW Professional files in use.

    You should first prepare a modification of the PREP.BAT file:
    1. Comment out this command: "call tools\striphdr DEV\SW newstuff\HOOKS.C"
    2. Uncomment the next line: "REM copy source\CODE\OBJ\HOOKS.OBJ DEV\SW\OBJ"
    3. Make sure the original unmodified make files are copied. In particular,
    replace newstuff\sws10\MAKEFILE with source\sws10\MAKEFILE,
    newstuff\SWV11\MAKEFILE with source\SWV11\MAKEFILE and/or
    newstuff\SWV12ADD\MAKEFILE with source\CODE\MAKEFILE,
    depending on the SW EXEs you want to recreate. For the Build editor,
    replace newstuff\SWV12ADD\makebld with source\CODE\makebld.

    Afterwards, you may create a source tree with the modified PREP.BAT file
    (under DEV\SW) as previously described. You should then follow these steps:

    1. Optionally edit the make file to omit the dependencies
    on MC35A3S.LIB and RXA3S.LIB.
    2. Make sure the following files from MemCheck 3.5 are present
    in the same source tree: MC35A3R.LIB, RXA3R.LIB. If you don't edit
    the make file, you'll also have to add MC35A3S.LIB and RXA3S.LIB.
    3. Build the EXE as previously described.
    4. To bind the DOS/4GW Professional 1.97 stub, make sure the files 4GWPRO.EXE
    and 4GWBIND.EXE are present in the same directory. Use them like this:
    "4gwpro 4gwbind sw.exe swb.exe -v"

    Bonus addendum - Making the ENGINE.OBJ file (SW 1.1 & 1.2)

    As stated above, a few older Build Engine sources were released. These
    include an old CACHE1D.TXT file from 1995, as well as a "blddbg" subdir
    that has the required source files for ENGINE.OBJ as originally used
    for Shadow Warrior versions 1.1 and 1.2.

    To make sure the created file is sufficiently close to the original
    (and even has the exact same file size):
    - Use Watcom C32 10.6, and no other version. It should be installed
    to c:\watcom. In particular, the INCLUDE environment variable should
    be set to c:\watcom\h. Be warned that unlike the case of the SW 1.2
    game code, here, "c:\watcom\h" should be fully lowercase
    (which is actually matching SW 1.1's SW.MAP).
    - Ensure the ENGINE.OBJ sources are ready under the "D:" path.

    Use this command to create ENGINE.OBJ: wcc386 engine /4r /s /or

    If done correctly, the output file will be the same as the original,
    up to differences related to the timestamps of the source files.

    Description of the contents of this archive

    For a little background, there were originally a few directories found in
    3D Realms' archives, with their contents later being split across differing
    directories for this release. In particular, there was this directory
    named "CODE" that had not just a Shadow Warrior source snapshot,
    but also additional files required for making the EXEs.
    It also turned out to have a backup of a few older Build engine sources.

    If you want to have a really short summary, then basically, source\sws10
    has the code for SW 1.0, source\SWV11 covers 1.1, and for 1.2 you need
    to combine source\REGCODE with the correct files from source\SWV12ADD.

    It is possible that this package will be updated in the future,
    provided that more work is done on additional contents.

    A summary of the included contents is following.

    README.TXT: This file.

    FILESLST.TXT: A list of old files with their original line counts
    (for textual files), sizes and timestamps, before modifications
    were applied (like the addition of GNU GPL headers).

    PREP.BAT: A helper Batch file that can be used for preparing a source code
    tree, eventually letting you make a working EXE with Watcom C.

    tools: Helper batch files and an extra tool, each of these
    being copied/used by PREP.BAT.

    build\CODE: This includes a few Build Engine source materials.
    BUILD.TXT and BUILD2.TXT are earlier revisions of the documents
    released by Ken to the public on 2000. CACHE1D.TXT is an old
    renamed version of CACHE1D.C from 1995. The blddbg subdir
    includes the code for ENGINE.OBJ as originally used
    in versions 1.1 and 1.2 of Shadow Warrior.

    F_OBJS: The contents of a miscellaneous OBJS.ZIP file which was found. Out of
    these files, ENGINE.OBJ was used for version 1.0 of Shadow Warrior.

    newstuff: Some new or recreated files. For one, this includes OBJ files made
    out of proprietary code, for which the sources are not included. As stated
    above, the terms of the GNU GPL do *NOT* apply to this code. These files
    are provided for the purpose of recreating SW EXEs as close to the
    originals as possible.
    There are also MAKEFILEs edited from the originals, found under the "source"
    subdirs of sws10, SWV11, CODE and REGCODE, in order to remove the dependencies
    on MC. As a bonus, static symbols are now added to the linker's output MAP
    files. Another file added is HOOKS.C, recreated from HOOKS.OBJ as used in
    SW 1.0-1.2. Reason is that the original HOOKS.OBJ file depends on the
    MC library. In particular, it is guessed that the same HOOKS.OBJ file
    was built using headers from SWC0507B, including GAME.H, which had
    DEBUG defined to 1 (and thus, leading to a dependency on MC).

    exes: A collection consisting of the original SW and Build editor EXEs,
    in binded and unbinded forms. The latter lack the binded DOS/4GW extender.
    There are also alternative unbinded EXEs excluding the MC
    libraries' code that you may use for comparisons.

    source: Differing snapshots of the Shadow Warrior sources.

    source\sws10: Version 1.0.

    source\SWV11: Version 1.1.

    source\REGCODE: A revision earlier than 1.2 by not more than a few
    days. This revision is the closest to version 1.2 out of what was found.

    source\SWV12ADD: A list of changes on top of REGCODE intended for the
    recreation of the code in 1.2. While some of these come from the GPLed
    release of 2005, other missing code pieces had to be re-filled in GAME.C.

    source\SWV12ADD\ALT: Alternative files for the registered and parental
    locked versions. Compared to the shareware and UK versions, the differences
    are a bit silly: A few global variables were shuffled around in order
    to recreate the original EXEs' layouts. There are good chances
    this wasn't the way the EXEs were originally created; Maybe
    about 1-3 header files were modified instead.

    source\SWC0507: A source snapshot added for the simple reason
    we also have SWC0507B covered...

    source\SWC0507B: A source snapshot that is assumed to be the one used
    for building HOOKS.OBJ as present in SW 1.0-1.2.

    source\SWC0511: A source snapshot originally used while trying
    to recreate the EXE from version 1.0, in conjunction with sws10.
    It isn't in use by PREP.BAT, but it's provided for reference.

    source\SWC0519: A source snapshot similarly used while attempting
    to recreate SWV11's EXE. It's also not in use by PREP.BAT.

    source\CODE: A snapshot of contents from the "CODE" dir,
    covering not just a Shadow Warrior source snapshot
    (earlier than REGCODE by about 3 days), but also
    additional files used for building all EXEs.

    extras: Unused files from the above-mentioned source code subdirs
    (like SWV11), as well as additional files not in direct use by PREP.BAT.

    -Yoav N.
  2. Halloween Harry beta released

    10 October 2018 - 01:41 PM




    Halloween Harry is 2018 Red Sprite Studios
  3. Bio Menace beta released!

    03 August 2018 - 01:03 PM

    [ All text taken from RELEASE.TXT and https://www.facebook...076257905961485 ]

    25 years ago today, Snake Logan was unleashed on the world!

    Snake is the star of Bio Menace, which celebrates its 25th birthday today! The game was originally released on Aug 3, 1993! Bio Menace was the creation of Jim Norwood, who also went on to be one of the co-creators of the original version of Shadow Warrior!

    Bio Menace was released at the hight of our time in the 90's putting out side scrollers. We had a few published at this time (the original Duke Nukem, Commander Keen), so this was a popular game. It was later released as freeware on Dec 23, 2005, so it has been free to play for some time now.

    Before the game was released, when it was in development we referred to it as "Bio Hazard". Given the nature of the plot line and the things you ran into, that fit the theme well. However, before the game came out, we changed it to "Bio Menace". When we asked Jim Norwood about that, he had this to say..

    "That happened because it turned out that there was some rock band named BioHazard who already held the copyright to that name. I'm not sure why we couldn't still use the name anyway since my use was for a video game versus a music brand. You'd have to ask Scott and George about the why's on that one."



    We asked Jim this week to send us some thoughts looking back on Bio Menace now that it has reached it's silver anniversary.

    Bio Menace was really the first game that I ever designed, did all the level design, art, and code for as my first full on game project. And if that wasn't enough, it had to be a Trilogy! That was quite a project for a lone dude that was completely new to the gaming industry, but, it got done eventually and we shipped that full Trilogy in the end.

    Bobby Prince did the music and I used Id's Keen Dreams engine to back the 2D game. Having the Keen Dreams engine is the only thing that made doing this game alone possible.

    As John Carmack used to quote, 'There really is no such thing as a trivial game.' So true! Every game that is worth anything is going to take significant effort to finish and bring to market. However, I had some of the most fun working on this title that I've ever had working on any game since. Working nowadays in the AAA industry, I'm no longer the 'driving force' behind new IP's and as a Senior Engineer, I am a significant contributor to really large titles, but I'm really more now a piece of machinery in the giant teams required to ship such ambitious projects. That's just how this industry has evolved and I'm ok with that. But that doesn't stop me from looking back fondly on the glory days when I lone guy could make a great selling 2D platformer by himself. In some ways, those days have come back with mobile games, and then grew again to where even top tier mobile games are still going to require a competent team to create anything great.

    I did manage to do another game called Tekken Bowling for iOS while I was at Namco where I was the sole programmer for the entire project, and I worked with only one designer and two artists on it. That was the closest I've come to making a game alone since the Bio Menace days.

    --- Jim



    One the Bio Menace game characters looks like he could be Cosmo, only his slightly more angrier brother. Jim seemed confused by the question when we asked him about this, as this exchange shows:

    Joe Siegler: Angry Cosmo - is that what that really was?

    Jim Norwood: I actually cannot remember the Angry Cosmo except vaguely? Was it cool? LOL!

    JS: Here you go. Angry Cosmo... :) (with a picture sent to Jim)

    JN: Haha nice. Ok, but that was one of the main creatures throughout the game. I thought you meant I had added actual Cosmo as an Easter egg.

    JS: No no - most folks who played the game thought it was supposed to be Cosmo - just his angrier brother or something. Seriously - even *I* thought that back before the game came out.

    JN: Well, you are right. It sure as heck looks like Cosmo!

    JS: The main difference is Cosmo has those spots on him, and the suckers. But visually your character is like an Angry Cosmo.

    One of the more fun things that was in this game was something called "The Apogee Room". Was a very hidden section in one of the maps where Jim Norwood, Scott Miller, & George Broussard were visualized, along with a few computers and a ton of Apogee visual gags - mostly from Commander Keen & Duke Nukem. Here's what Jim had to say about this.. "That was all me. I loved the Easter Eggs in Commander Keen at the time and I wanted to put something similar in Bio Menace - hence the Apogee Room. :)"



    It's always fun looking back on games like this, but today, we're going a bit beyond than what we usually do for these anniversary stories. We've dug into the archives and found a working copy (well, after some massaging) of one of the game's betas that we are releasing for free today!

    The game was actually still called "Bio Hazard" at this point, and was dated July 15, 1992.

    We've also thrown in a PDF the "Secret Moves" paper that we used to send out with Bio Menace orders placed with us.

    Big thanks to Jim Norwood for allowing this to be released, and for Evan Ramos for whipping it into shape. There were some fiddly tech issues with this release that he goes into in greater detail in the release.txt file in the game directory about what fixes had to be made to the beta for release. Make sure and read it for additional info, as some of it is quite interesting.

    You can download the zip file here: http://legacy.3dreal...e/bh_071592.zip

    Some other Bio Menace related links for you to check out:

    1) Our original Bio Menace webpage here: http://legacy.3drealms.com/menace
    2) Youtube Video showing you the Apogee Room:

    3) Frenkel's Bio Menace Maps: http://legacy.3dreal...maps/index.html
    4) Apogee Legacy Interview with Jim Norwood: http://legacy.3dreal...jim_norwoo.html
    5) 3D Realms' Bio Menace Trailer:

    Thanks for checking this all out, and thanks for playing our games these last 25-30 years or so!

    Joe Siegler
    Apogee Software / 3D Realms
    Aug 3, 2018




    There are several interesting things to note in this prototype. First and foremost, it can be seen that the final game's Episode 2 was originally slotted to be Episode 1. The final boss of the episode is a floating head of Dr. Mangle (whose art can still be found in the final game's data) rather than The Enforcer, though their behavior is functionally similar, if not identical. The in-level save feature inherited as part of the Keen Galaxy engine is still active in this build, before being disabled for technical reasons in the final game. Some of the item sprites differ in this beta. I'm sure there are more curiosities waiting to be discovered and documented.

    Unfortunately, some of the files that make up the game's graphics banks were found to have experienced some kind of data corruption. The data was collected into a zip file that passed all checksum tests, meaning whatever happened took place before archival. My collaborator NY00123 stepped up and repaired the damage by inspecting it with various tools, including one of his own design, and cross-referencing with the final BM2 where necessary.

    In testing, NY discovered a crash that manifests at two points in the episode, and we agreed that he would make a one-byte edit to fix the problem, improving Quality of Life for players. As copy protection, the executable performs a date check that aims to make the beta expire after a certain time. Bypassing this would require changing the system clock or intercepting the call with a TSR, but since we already modified the exe, he simply disabled the check with another one-byte change. Additionally, the executable requires a password to be entered on the command line, so we inspected the exe to find it and have provided it for you as part of PLAY.BAT. (If you wish to compare our modified exe with the original, you will need to use UNLZEXE to unpack both files.)

    Unmodified versions of all edited files, as well as the original internal beta tester documentation text files, are available in the folder named "ORIGINAL". Below you can find a detailed technical description of modifications made, written by NY00123.

    -Evan Ramos / Hendricks266


    BHAZARD1.EXE, EGAGRAPH.BH1 and EGAHEAD.BH1 were modified. Details are given below. This text file, PLAY.BAT, and SecretMoves.pdf were not originally present.

    Original timestamps (local timezone information is unavailable):

    ABOUT.BH1    1992-03-22 16:40:04
    AUDIOHED.BH1 1992-06-10 12:44:24
    AUDIOT.BH1   1992-06-10 12:44:22
    BHAZARD1.EXE 1992-07-15 22:36:40 *
    CONTEXT.BH1  1992-03-15 16:24:26
    CONTRART.BH1 1992-03-22 18:26:14
    DEMO0.BH1    1992-07-14 03:07:12
    EGADICT.BH1  1992-07-13 19:03:44
    EGAGRAPH.BH1 1992-07-13 19:03:44 *
    EGAHEAD.BH1  1992-07-13 19:03:44 *
    ENDART.BH1   1992-07-12 19:12:16
    GAMEMAPS.BH1 1992-06-17 17:17:48
    GAMETEXT.BH1 1992-03-15 16:24:26
    GFXINFOE.BH1 1992-07-13 19:03:46
    HELPART.BH1  1992-03-22 18:07:42
    MAPHEAD.BH1  1992-07-12 19:23:50
    MAPTEMP.BH1  1992-07-12 19:23:46
    MAPTHEAD.BH1 1992-07-12 19:23:44
    MUSEINFO.BH1 1992-06-10 12:44:22
    ORDERART.BH1 1992-03-23 02:09:16
    README2.TXT  1992-07-15 17:06:40 *
    README.TXT   1992-06-29 20:58:54 *
    STORYART.BH1 1992-03-22 18:07:42
    STORY.BH1    1992-03-22 16:40:04
    TEDINFO.BH1  1992-07-12 19:23:48
    TEDINFOE.BH1 1992-03-15 16:24:26

    * The unmodified original copies can be found under "ORIGINAL".

    BHAZARD1.EXE had the following edits applied, changing exactly two bytes of code (in the LZEXE-unpacked EXE):
    - The beta expiration date check (which is somewhat buggy) is skipped.
    - With the original EXE, if you try to read the color sequence in "Ant Caves" (level 3) or activate the easter egg in "Specimens Labs" (level 10), the game will abort from a call to the StartMusic function with (virtual) level number 20 (21st level). Based on the note from README2.TXT saying that the amount of playable levels was reduced by 6, this was fixed so StartMusic is called with the value of 14, leading to playback of "Resting" (as in the final game).

    The original EGA data is partially corrupted, so EGAGRAPH.BH1 and EGAHEAD.BH1 had to be recreated. ModId was used for exporting and importing graphics.
    - The presence of two complete 16x16 tiles in the initially exported data gave the hint that 7725 bytes shall be removed from some offset in EGAGRAPH.BH1 (done at offset 0x16308). This assisted with getting virtually all tiles, which were the same as in Bio Menace ep. 2 for most. A small amount of missing or partially corrupted tiles were simply copied from BM2.
    - An internal tool was written for displaying the sprites, including the separate EGA planes. At some point, it could let one "move" the EGA planes around and export them as separate BMP files. Eventually, most sprites were actually copied from BM2 as-is. It's only most of the player sprites and other few sprites which needed more edits.
    - After modifying the tool for usage with masked 8x8 tiles, it was found out that they were exactly the same as in BM2. As for unmasked 8x8 tiles, it was separately found out that such tiles were only added between BH1 and BM2, not removed or replaced.
    - A portion of the "This is -NOT- Shareware" picture had to be recreated. The rest of the unmasked pictures remained intact, while the only masked picture (used in the menu) was copied from BM2.

  4. Extracting CON Files from Duke 64 and Total Meltdown

    01 March 2018 - 08:25 PM

    In August 2017, Fox alerted me that he had discovered what looked like CON bytecode inside the executable file on the Total Meltdown disc. We set to work reverse engineering this data into a format that could be used in his mod. During the process, he also found bytecode in the Duke 64 cartridge.

    I ended up writing a small program, decon, that can take a Duke PS1 executable ("SLUS_003.55" for US, "SLES_007.03" for EU, "SLPS_015.57" for JP) or a Duke 64 cartridge dump (from the U, E, or F regions, and additionally the publicly known prototype) and output functional CON files, albeit lacking the names of all defines, states, actions, AIs, and moves, as well as any comments in the code, and the exact formatting.

    The key to studying this process and getting reproducible output is a companion utility I wrote, dosdukecon, which compiles 1.4+ CONs to the bytecode format as stored in memory on the PC version. It turns out that only minor changes were made between this structure and what was stored in the respective console ports.

    The utilities I wrote to do this, the source code for them, and the resulting output can be found at the following link. http://hendricks266....ler_20180301.7z

    You can drop in your own copies of the input files and let the tool work, or look at the extracted CONs if you're really curious. This release is mostly about documentation.
  5. Major Stryker beta released!

    16 January 2018 - 10:07 AM



    Two days, two Major Stryker posts.

    Yesterday was the 25th anniversary of the game, and today we have a special treat. In talking to some of the developers on the actual anniversary, we discovered that we had a working beta version of Major Stryker as well that was dated August 12, 1992. We have decided to release the beta for you to check out. There was one legendary beta that we cannot seem to find - was the first beta. That one was so hard that every single beta tester complained it was too hard. That almost never happens, so it was made a bit easier to play, that is what you’re seeing here.

    The game is fairly complete, but it is not totally finished either. The music is there, but no sound effects are there. The gameplay is mostly finished, but not totally polished. Order screens are not finished, and various help is incomplete.

    Tech Stuff: This beta does require DOSBox to work - there is no shell provided for this release, nor will we give any support in getting it to work under DOSBox.

    Back in the day we used to take multiple steps to prevent our betas from leaking. For some titles we used a physical hardware dongle, and on some we made it so the games had to be played inside a specific date range AND have a specific environment variable and/or a command line parameter to run. Not all of them used all our security methods, but this Major Stryker beta used some of them. To get the game to run right, you need all the files in the directory, and have to start the game with the “PLAY.BAT” batch file inside DOSBox.

    Here is the download link: http://legacy.3dreal...r_beta_0892.zip

    Summary: We thought this would be something fun you guys would like seeing. Was a fun little surprise to discover on the anniversary day, and after some check with various folks, we’re releasing it for free on the day after. Enjoy!



Page 1 of 1
  1. Photo 07 Jul 2016 - 18:44
    First to 4000 snazzy votes, good work Hendricks.
  2. Photo 31 May 2016 - 04:11
    I wish you a Merry Christmas and Happy N... oh, I mean Happy Birthday! Never lose your BAZINGA.
  3. Photo 20 Jul 2014 - 20:32
    420 eh? hehe
    puff puff pass.
  4. Photo 26 Feb 2014 - 23:04
    Hi.Just wanted to say thanks again for the other day.Best of luck to you.
  5. Photo 12 Sep 2013 - 05:29
    I came here to donate some blood. Your blood!
  6. Photo 12 Sep 2013 - 05:28
    I came here to donate some blood. Your blood!
  7. Photo 09 Sep 2013 - 22:15
  8. Photo 31 May 2013 - 05:51
    Just thought to pop by and say happy birthday and have a good one.
  9. Photo 02 May 2012 - 08:55
    Hey, I think I know why there are some weird songs in Total Meltdown. The one with the Stalker 2 and Bar music is because I guess when you enter the bar the music changes into that (since both songs would be playing, and if you turn off music, the bar music is off too). The other one "Chemicals fuck you head" may be used as background music in a map, the variants for how far you are fro...
  10. Photo 14 Oct 2011 - 17:50
    Thanks for help with the music pack!
    My last computer manage to work HRP,Dukeplus (Didn't tried Polymer out and the music pack) back then. Now I totally forgot how they work. If you know any site or place I can refer to help me with this,that would be nice. Thanks!
  11. Photo 13 Sep 2011 - 16:38
    You have no status!!!!!!
  12. Photo 18 Jul 2011 - 21:20
    You need to get on Google/Gmail Chat or MSN more, you big dork!
  13. Photo 14 Jul 2011 - 16:22
    We need to talk to you on IRC. You've been very bad and need to be punished.
  14. Photo 31 May 2011 - 07:20
    Happy B Day!!!!
  15. Photo 31 May 2011 - 02:10
    Happy birthday Hendricks :)
Page 1 of 1

All copyrights and trademarks are property of their respective owners. Instead of reading this text, you could be playing Ion Maiden! ;) © 2018 Voidpoint, LLC

Enter your sign in name and password

Sign in options