top of page

Search Results

Search this site

221 results found with an empty search

  • DID you know? Installing & Patching EF2000 on Windows 10

    Flying the fjords Update: This guide has been superseded by ' EF2000 Updated Part 2: Installation '. This is a guide I wrote a little while ago about installing EF2000 and patching it for 3dfx and running it with EF2000 Reloaded (a custom DOSBox build). This is all done with a single Windows 10 machine, no need for a second retro pc. This guide was on the COMBATSIM forums, but these have sadly disappeared so I've added it here. It's quite an old guide and uses older versions of PCem, so with later versions it is a bit easier. At some point soon I should really update this guide. So here it is, my guide to installing, patching and running EF2000 with a single Windows 10 machine... Overview We’re going to do a completely clean install of EF2000, Tactcom and the GFX+ patch on a Windows 10 box without the need to dual boot or use another physical machine. We’ll do this by creating a virtual Windows 95 installation machine, then we’ll move our newly installed and patched EF2000 into Windows 10 before final tweaking and configuration with the Reloaded application. Now this is quite a long and involved process, as we’ll need to install PCem a PC emulator and setup a Windows 95 virtual machine. PCem more accurately emulates the hardware of an older generation of PC’s. This accurate emulation was key in successfully patching EF2000. Setting Up PCem and Windows 95 The version of PCem I used was v12 available here: https://pcem-emulator.co.uk/downloads.html Currently the latest version is v13.1 but I haven’t tried this one yet. Rather than describe the setup of PCem, I’ll instead point you to the impressively comprehensive tutorial provided by THEOLIGOPOLIST here: https://olistutorials.wordpress.com/2017/02/25/setting-up-pcem-for-windows-95-games/ You don’t need to follow the complete tutorial, once you have setup Windows 95 you can leave it there, we won’t need the 3DFX drivers, as we will use this box to create our patched installation but not for running EF2000. In order to install into PCem we’ll need to quickly cover how to mount cd’s and cd images for use with PCem. Physical cd PCem can use the host’s cd drive so for those with physical cd’s you can use them normally. Select the CD-ROM menu option and then the Host CD/DVD option. PCem physical cd option ISO cd images PCem supports iso cd images and you just need to select the iso option within the same settings menu above and then pick your iso image to mount it. PCem .iso image option Other cd images Now for those with cd images other than iso things are a bit more involved, at the time of writing PCem only supports iso images, so if you have cd images in other formats they’ll need to be converted to iso. One method is to use an imaging mounting utility, such as WinCDEmu available here: http://wincdemu.sysprogs.org/ This will mount the cd and give it a suitable drive letter. Once mounted another utility ISOcreator, can be used to create the iso image. ISOcreator can be found here: https://sourceforge.net/projects/iso-creator-cs/ Once there is an iso image, it can be used with PCem as described earlier. Installing EF2000 Mount the EF2000 cd in PCem. Open up a dos prompt in Windows 95 and select a full install to hard disk, this will automatically install it to c:\Ef2000 Installing Tactcom Mount the physical cd or an iso image of Tactcom in PCem. Once an iso image is created, mount this in PCem. Open up a dos prompt and run the tactcom executable, this will automatically find the c:\EF2000 installation directory and apply the tactcom update. Installing GFX+ The GFX+ patch can be found here (and a right pain it was to find): http://www.patches-scrolls.com/dl.php?file=gfxplus.zip The patch should be unzipped, the resulting tactpat.exe executable should be placed in a folder and an iso image created with this folder added. Mount the iso image in pcem. Copy the tactpat.exe executable to the installation folder c:\Ef2000 Run tactpat.exe from windows in PCem, it’s a 32bit windows executable. Choose the 3DFX option. GFX+ upgrade patch The upgrade occurs in two phases a dos window will appear and it will patch ef2000. Once finished close this dos window and another should open and it should patch tactcom. Once complete close the dos window and exit the Tactcom Upgrade. Extracting EF2000 from PCem Now the EF2000 installation folder needs to be extracted from PCEM. Unfortunately at present PCem only uses virtual hard disks in the img format, if it use the vhd format we could have mounted the hard disk in Windows 10 and just copied the folder elsewhere. Another utility is needed to open the virtual hard disk. One such utility is WinImage. WinImage 9.0 works with Windows 10 and is available here ( wima6490.zip ): http://www.winimage.com/download.htm Shutdown PCem otherwise the virtual hard disk can’t be opened. Start WinImage and select the virtual hard disk used by PCem. Selecting a hard disk image Select the only partition available Selecting a partition Right click on the c:\ef21000 folder and select extract. Extracting a folder Pick a folder to extract to, ensure ‘Extract with pathname’ is selected. Extract dialog box And that is a fully patched EF2000 installation folder in Windows 10. EF2000 Reloaded All that remains is to import the ef2000 folder into the reloaded application. Might be worth making a copy of the ef2000 folder (you don’t want to go through all that again!) There may be some invalid entries in the clump_3.txt file but once these are removed it should be fine.

  • Tech refresh 2025

    Over the following weeks the articles which have been produced over the year will be subject to a tech refresh. This means the DOSBox Staging configurations will be updated to the latest version. Native Windows 10 setups will be tested with updated wrappers and Mac emulation will be tested with the latest version of Mac emulators. If a particular sim does not get a tech refresh article then the existing advice will still apply.

  • Black Knight: Marine Strike Fighter

    A guide to running the F/A-18 Hornet sim, BLACK KNIGHT: Marine Strike Fighter in DOSBox Staging. The sim was developed in 1995 by SE Software and published by FormGen Inc. Versions There are primarily two editions you may encounter when trying to obtain the sim. There is a widely distributed shareware edition. This was normally released on magazine cover disks around late 1995 and 1996. It is usually named 'BLACK KNIGHT: Marine Strike Fighter SE', it's not clear whether this is a reference to the developer, SE Software or a reference to it being a Shareware Edition. These are normally distributed with an order.doc and vendor.doc text files. When compressed the sim fits on 2 x 3.5" HD floppy disks which probably helped in sharing and distribution. Some shareware editions were pre-patched to the latest v1.33 version. The CD-ROM edition was released in October 1995 and is the complete game. Differences from the shareware edition (taken from the order.doc file) include: 60 combat missions 8 training missions unlimited free flight sight range to 20 and 25 miles create your own mission scenarios more deadly AIM-7 radar-guided air-air missiles MK-82, MK-83, MK-84 bombs and bombsight avionics on-board flight instructor for in-flight training VCR-like flight recorder with advanced camera control and playback television-guided Maverick air-ground missiles with in-cockpit imaging 80 page illustrated manual includes weapons systems and combat tactics The shareware and CD-ROM version may not be obvious as the version number was not reported until the later v1.33 version, but are probably v1.x. A number of CD-ROM editions cames in a jewel case without the 80 page manual although there is a retail box edition with the manual. Retail box front Retail box back Patches There is a single official patch which upgrades any v1.x version to the latest v1.33 version. The patch (taken from the patch readme) includes: Fixed analog joystick, throttle and rudder pedal problems. Fixed waypoint error in mission 38. Changed command line switches "-1", "-2", etc., to skip intro movie as well as pilot selection screen. Improved MIDI interface for broader compatibility. Improved accuracy of roll and pitch rate/momentum to match performance data. Added INSANE! graphic detail level. Added the mission overview message on mission start. Added transonic physical effects. Added Black Knight OS initialization messages. Added debug capabilities. Added limited Surround Sound. Added support for CH Products Flightstick Pro, CH Products F-16 Combatstick and CH Products Virtual Pilot Pro. The retail box edition had this included on a single 3.5" HD floppy disk. The patch bkupd133.zip is available on The Patches Scrolls website, and from the VOGONS post ' Black Knight - Marine Strike Fighter '. However recent Windows 10 updates may incorrectly flag this as virus infected. This may have to be downloaded and extracted on another platform before being copied onto a Windows 10 machine. Scanning the extracted files and even compressing them back into a zip file with 7zip reported no issues. DOSBOX Staging settings This guide assumes the latest version of DOSBox Staging which at time of writing is v0.82. This is particularly important as with this version, persistent screen flickering has been introduced which can be avoided by using high frame rate settings, as described in this article by Omnicydle. The settings that differ from the defaults will be covered and any settings of particular interest. [sdl] host_rate = vrr vsync = off presentation_mode = vfr The host rate is set to variable refresh rate which is optimum for my display, for non vrr displays this can be left as the default, auto. Vsync is disabled and a variable frame rate is used as the presentation mode for high frame rates. [dosbox] dos_rate = 1000 The DOS rate is set to 1000hz for high frame rates. [cpu] cycleup = 1000 cycledown = 1000 The default cpu settings are suitable although changing the cycles up/down setting to discrete increments makes it easier to tweak, although a smaller increment may be required depending on your setup. [mouse] dos_mouse_immediate = true This is useful for high frame rates. [mixer] reverb = large chorus = normal Mixer default settings are suitable although these reverb and chorus settings are a personal preference. [midi] mididevice = fluidsynth # mididevice = mt32 The game supports both MT32/LAPC1 or general midi so there is a choice of either fluidsynth or mt32. The method I use to organise soundfonts and MT32/CM32L roms is described in the earlier DOSBox midi article . [fluidsynth] # soundfont = "D:\Midi\Soundfonts\FluidR3_GM_GS.sf2" soundfont = "D:\Midi\Soundfonts\Shan SGM-X48 v1.0.sf2" These are a couple of fluidsynth soundfonts that seem to work well with the game, you may wish to try others. [mt32] romdir = "D:\Midi\Versioned" This specifies the location of MT32/CM32L roms. [autoexec] mount a "D:\Games\Dos\Black Knight\fdd" # imgmount a "D:\Games\Dos\Black Knight\fdd\patch.img" -t floppy imgmount d "D:\Games\Dos\Black Knight\cd\blackknight.iso" -t iso # use '-freesize 512' at the end of this line if the installer fails mount c "D:\Games\Dos\Black Knight\hdd" c: cd bk bk exit # close DOSBox when you quit the game The folders are organised using my DOSBox game management strategy. The a: drive mounts files from the update disk, extracted to the fdd folder. This is needed to use the patch installer or patching after a cd install. If you have the patch disk as a disk image the 'imgmount a' line shows an example of mounting a floppy image. The d: drive mounts the cd-rom as an cd image file, to save wear and tear on physical devices and media. The c: drive may require the freesize option as the Black Knight installer may read the huge disk size incorrectly and fail to install. The freesize option limits the reported free space to a smaller value the installer can cope with. If you use the later patch installer the issue is fixed and the freesize option is not required. The default folder the game installs to is c:\bk. Controller settings This will cover the physical and virtual controller setup in Windows, followed by DOSBox Staging settings, controller calibration is described later. TARGET settings Like many other DOS sims, Black Knight requires a HOTAS setup limited to 4 axes. For those with 4 axes or less this won't apply. For those with a HOTAS with more than 4 axes, HOTAS profiling software will need to be used to limit axes. In my case I'm able to use TM TARGET to create a suitable profile for a virtual controller  with only 4 axes. They are specified as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder pedals DX_XROT_AXIS If you can't use TM Target or your HOTAS supplier profiling software, then other profiling software, like Joystick Gremlin may provide a suitable alternative. DOSBox settings The following changes are made to the joystick section of the DOSBox configuration file: [joystick] joysticktype = 4axis timed = false swap34 = true deadzone = 0 4axis allows the use of throttle and rudder pedals in flight. Timed false is appropriate for my setup, you may wish to change this if setting to false results in joystick drift. Again swap34 true was appropriate for my setup, however you may need to test your particular HOTAS to see if this is required. The deadzone setting is personal preference and works well for my HOTAS. My config My config is shown below, you may wish to use it as a basis for your own config or for testing any changes you may wish to try. [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] dos_rate = 1000 [cpu] cpu_cycles = 3000 cpu_cycles_protected = 60000 cycleup = 1000 cycledown = 1000 [mouse] dos_mouse_immediate = true [mixer] reverb = large chorus = normal [fluidsynth] # soundfont = "D:\Midi\Soundfonts\FluidR3_GM_GS.sf2" soundfont = "D:\Midi\Soundfonts\Shan SGM-X48 v1.0.sf2" [mt32] romdir = "D:\Midi\Versioned" [joystick] joysticktype = 4axis timed = false swap34 = true deadzone = 0 [autoexec] mount a "D:\Games\Dos\Black Knight\fdd" imgmount d "D:\Games\Dos\Black Knight\cd\blackknight.iso" -t iso # use '-freesize 512' at the end of this line if the installer fails mount c "D:\Games\Dos\Black Knight\hdd" c: cd bk bk exit # close DOSBox when you quit the game Installation, setup & patching There are two installation methods, using the patch installer to install and patch in one step, or install from cd and then update using the patch. Install with patch Installing with patch runs the installation and patching as a single step. You won't need the freesize option added to the c: mount command as it uses a fixed installer app. To install from patch you will need: An a: drive with a mounted folder containing the patch files or an a: drive mounting a patch disk floppy image. A d: drive with the cd mounted as a physical cd drive or a d: drive mounting the cd image. a: install # to run the installer readme # to view the patch readme Once the install is complete the sound and music setup will run. Install with cd-rom (or image) and patch To install and then patch, mount the cd (or cd image) and go to the DOSBox cd-rom drive and run: install Once installation is complete it will run the sound and music setup (see below). Once setup is complete go to the DOSBox drive or folder containing the patch files and run: update Once complete you may wish to run setup again to ensure sound and music settings are correct. Setup Music setup Setup will automatically run once an installation is complete, it can also be run at anytime by going to the installation folder and running the setup.exe app. There are 3 steps to setup: Sound setup. Setup should automatically find the Soundblaster settings, then just choose the Soundblaster 16 option, or whichever Soundblaster model has been configured in your DOSBox settings, if you have decided to change it. The selection will be tested and you should hear the example audio. Music setup. Setup should automatically find the Soundblaster settings again. Then you can choose Soundblaster for music, or MT32/LAPC1 if that is your DOSBox midi device. In my case I was using fluidsynth as the midi device, so I chose the General midi option. You could even try configuring a Gravis Ultra Sound (GUS) in DOSBox settings and giving that a try! The selection will be tested and you should hear the example music. Driver deletion. Setup will now ask if the unused sound and music drivers should be deleted. This was an option to save disk space, which is unnecessary today. If you keep the unused drivers you can experiment and try different options later on, so answer no. Setup should now be complete! Replacing the DOS extender This is an optional step and you may wish to skip it. Black Knight uses the older DOS/4G v1.97 extender allowing extended memory to be used. There are newer and more modern DOS extenders available. The extender is built into the bk.exe file, but can still be replaced. The process is described in the DOSBox Wiki article ' TOOLS: DOS32A ', under the Internally section. A modern DOS extender and utilities can be found at the amindlost/dos32a GitHub repository in the binw folder. Download the dos32a.exe dos extender and sb.exe utility and place them in your black knight installation folder. Make a copy of your existing bk.exe file (e.g. bk.bak) From within DOSBox, set the dos32a environment variable: set dos32a=c:\bk\dos32a Replace the extender with: c:\bk\sb /r bk.exe You should see the result of the binder utility reporting that the DOS/4G extender was found and then replaced with the DOS32A extender. You may see some warnings once you exit Black Knight but they can be ignored. If this replacement causes problems then you can always swap back to the original file. Command line options There are limited command line options but you can skip the intro movie and pre-select a pilot, as shown below: -[1-4] # skip intro and select pilot 1-4 e.g. c:\bk\bk -3 # skip intro and select pilot 3 Controller calibration Controller calibration is performed in-game, the v1.33 patch along with the DOSBox joystick settings described above will allow you to specify a 2/4 button joystick, a throttle and rudder pedals. The calibration process should be straight-forward although depending on your HOTAS setup you may need to tweak some DOSBox settings. Documentation The manual does exist! The retail box edition came with an 80 page manual which is unavailable these days. However the shareware editions did include a key reference guide, keys.doc and a limited 28 page manual, bkmanual.doc as text files. Finally... Black Knight: Marine Strike Fighter was not the most popular or well known sim, but if you've only played one or two F/A-18 Hornet sims and want to try something a little different from the well known classics, it's well worth a try and hopefully this guide will get you up and running well! Good hunting!

  • The State of the Art: Gaming with Mac Emulation

    A quick guide to the things I have discovered about Mac emulation and what it means for retro flight sim gaming. The Mac platform isn't exactly well known for a plethora of flight sims, but there are some retro classics that are worth looking up, the most noteworthy being F/A-18 Hornet Classic (Hornet v1.1.2) and Hornet 2.0 from Graphsim and A-10 Attack the prequel to A-10 Cuba and finally the Mac version of the Microprose classic F-117 Stealth Fighter 2.0. But how to play these classics? Well unless you have any old Mac's lying around the easiest way is probably going to be emulation. Creating an Emulated Mac Firstly we need to create an emulated Mac, after a lot of trial and error I've found the following to be a suitable emulated hardware/software combo for running those sims mentioned above: Quadra 800 ROM 64 or 128MB RAM 200MB - 500MB hard disk Mac OS 7.5.3 or 7.6.1 This is the emulated Mac I used to compare the various options. Mac OS 7.1.1 worked with some emulators so if you need to use a particular version anything from 7.1.1 to 7.6.1 may be suitable. Emulation Options So if we go the emulation route it's worth looking at the pro and cons of the options available. It's worth noting that the simulations were around at the time Apple had both Motorola 680x0 (m68k) and Power PC (PPC) processors and the sims above can run on either platform due to Apple fat binaries which supported either hardware. Basilisk II Sadly a common occurrence when running F-117 under Basilisk II Still considered the gold standard in m68k Mac emulation, it has a lot going for it. A fairly straightforward GUI to setup the Mac, still actively developed with releases, setup guides and forums available through the Emaculation website. On a modern monitor the graphics scale beautifully through Basilisk II. However it suffers from one serious drawback which makes it problematic for running sims, the lack of any sort of speed control. Basilisk II will run as fast as possible and without any ability to throttle its performance, this results in sims running too fast or with controls too sensitive to be able to fly properly. Earlier titles which may be speed sensitive such as F-117 Stealth Fighter 2.0 may also suffer from crashes due to the performance. In fact this is very easy to see in Stealth Fighter where switching speed in game to 'realistic' or switching to an outside view in flight will cause an 'Error of type 4' (a divide by zero error). Sheepshaver A-10 Attack! running in Sheepshaver Sheepshaver can be thought of as Basilisk II for the PPC, in fact Basilisk II and Sheepshaver share a lot of source code. Like Basilisk II it has it's own setup GUI and is actively maintained with releases, guides and forums available through the Emaculation website. Like Basilisk the scaling on a modern monitor is good. However unlike Basilisk II there is an option to throttle performance. It isn't available through the setup GUI, but the preferences file can be edited and a 'cpuclock' parameter added. Defaulting to 100Mhz which is too fast for the sims mentioned, it can be lowered. I've found going as low as 16Mhz, reduces control responsiveness to a good level while maintaining fluid framerates. F/A-18 Hornet Classic in Sheepshaver In addition it's easy to mount a host folder through the setup GUI allowing files to be transferred to the emulated hard disk easily. In fact Sheepshaver can also mount images created by Qemu m68k making it useful to have around for that reason. However it's not all good news, F-117 will still experience random lockups, although much less frequent, it still places F-117 in the unplayable category. F/A-18 Hornet 2.0 will run fine until it's time to fly, then lock up as the flight engine initializes. Qemu m68k Hornet 2.0 running in Qemu m68k Qemu is a suite of emulation and virtualisation applications but one we are interested in, is Qemu m68k as it supports the Quadra 800 and Mac OS 7. Unfortunately Qemu ppc doesn't support Mac OS 7 at present. There is no setup application for Win10 so it's command line and batch files to setup and run. Fortunately the guys at the Emaculation website maintain Qemu m68k releases, setup guides and forums. Be warned Qemu is used for serious stuff so it's all too easy to go down a Qemu rabbit hole and get overwhelmed by a daunting array of setup options, so stick to the Emaculation guides and you should be fine. There is no speed/performance controls but I've found Qemu to emulate at a suitable rate 'out of the box' so sim controls were fine on my pc, but it may depend on your own setup. There are some downsides along with the Mac setup, it's tricky to get files onto the emulated drive. It's actually easier to mount the Qemu drive image in Sheepshaver to get the files across and then run in Qemu. Although I haven't got it to crash in F-117 and the cockpit graphics are fine, unfortunately the environmental graphics are pretty messed up right from the start. It's weird to see an airbase cut across your cockpit at a 45 degree angle at 500ft. Hornet 2.0 works without issue, the scaling isn't quite up to Basilisk/Sheepshaver standard but it isn't bad at 1024x768. Mini vMac Mini vMac an older emulator but with a Win-64 release available from the project homepage reference on Emaculation website along with guides/forums. There are limited speed controls available. And unlike most of the emulations it supports the Mac specific 512x384 resolution, which is useful for older Mac software. Unfortunately it does have issues with F-117, which are almost the opposite of Qemu. While the environmental graphics are fine there are graphical issues inside the cockpit and a number of key controls are unresponsive. MAME (m68k driver) F-117 Stealth Fighter 2.0 (Mac version) running under Mame MAME is the Multiple Arcade Machine Emulator or at least it was some time ago, but it's become far more than that and in the projects own words, it's become ' a multi-purpose emulation framework '. A framework which has grown to encompass Mac emulation. In fact Mame not only emulates the CPU but controllers on the motherboard as well, requiring not just the main Mac rom but roms from other components as well. When I started writing this article I was prepared to write off MAME as unsuitable due to serious jerky mouse controls that would develop a mind of their own midway through a mission. This seems to be due to the Mac I was emulating, a Mac II ci, a known issue due to the hardware being emulated. However further investigation revealed the Quadra 800 didn't have any of these problems and can run F-117 flawlessly. Due to the accuracy of emulation the performance initially isn't as smooth as you would like, but MAME has hidden depths and the emulated CPU can be overclocked for better performance. However the performance of the Hornet sims or A-10 Attack still needs to be investigated, my subjective feeling is that it still might struggle with these titles. Controller support is excellent in MAME but again some trial and error configuration is needed. There's a huge amount that can be configured which can feel a bit daunting at first. Probably the biggest downside is hunting out the roms you need to get the emulated Mac up and running. The hard disk image is in a chd format, I didn't create this myself but found a suitable Mac 7.6.1 hard disk image for use with MAME. In order to transfer files onto the disk the recommended approach is to place files into a folder and then generate an iso image from the folder, then mount the iso onto the emulated Mac in MAME, which is a bit more involved. MAME issues a warning about sound not being fully implemented for the some of the emulated Mac machines but I had no issues in F-117 and active development means this may be resolved at some point in the future. Recommendations For games compatible with System/Mac OS 7.1 - 7.6 during the m68k/ppc period your first port of call should be sheepshaver. It's fairly easy to setup, the guides are easy to follow and it's simple to transfer files onto the hard disk image and you can throttle performance if things are running too fast or controllers are too sensitive. Make sure to get the latest build or try an experimental one. It may be all you need for a particular game. If Sheepshaver has issues then give Qemu m68k a try. It's more involved to setup but if you follow the guides it shouldn't be too difficult, and you can use Sheepshaver to mount the Qemu hard disk image to transfer files. Pick one of the latest builds, each release sees bugs fixed and enhancements. If you have an earlier title which Sheepshaver and/or Qemu has issues with you'll want to try MAME. The accuracy of the hardware emulation means MAME may succeed where others fail. However this accuracy comes with a higher processing overhead so you may want to save MAME for earlier/less demanding sims unless you have a powerhouse of a PC. Basilisk II and other Mac emulators may be recommended by others but in my opinion they've fallen behind these three when it comes to retro flight sims. Some final thoughts When I started looking at Mac emulation for retro flight sims I ran into numerous issues and it was beginning to feel like some of these classic titles would be lost to time. Each sim and emulator had it's issues and difficulties and there didn't seem to be a single all encompassing app that made these sims 'just work'. However, it's taken a lot of work but it turns out we do have the tools (and more importantly the dedicated volunteers who maintain them) to run these classic sims on modern hardware and these emulators are improving (admittedly some quicker than others) as time goes on. So on reflection we aren't in such a bad place when it comes to it and these retro classics are still playable, which in my opinion can only be a good thing. It turns out that when it comes to the art of running Mac sims, it's in a pretty decent state. You can see a quick showcase on my YouTube channel.

  • Unresponsive Thrustmaster rudder pedals in TARGET: A fix!

    An actual fix to get these pedals working! This is an update to an earlier post Unresponsive Thrustmaster rudder pedals in TARGET: A workaround , an actual fix! Firstly a huge thank you to DCS World Form member Guppy for identifying and describing the fix in this message . In my case I had to download the Advanced Calibration Tool (v2.12) from the T.RJ12 USB Adapter support page . Once downloaded, run the advanced calibration tool and follow the instructions. Since then the TFRP pedals remain active once the virtual controller is created by TARGET. Process Adding the steps of the process here in case the message or forum becomes unavailable in the future: Launch the Package Drivers installation software to uninstall the TFRP rudder pedals and their associated applications. Restart your PC. Go to Settings > Devices > Devices and printers. Right click on the T-Rudder device > Game controller settings and select T-Rudder. Then select Properties > Settings > Reset to default. Restart your PC. Launch the Package Drivers installation software to install the rudder pedals.

  • Running Wing Commander: Privateer in DOSBox Staging

    Wing Commander Privateer A guide to running Wing Commander: Privateer in DOSBox Staging. This was configured and played to completion a while ago but I've only just gotten round to writing this guide. Editions, expansions & upgrades These are the editions, expansions and upgrades available. Wing Commander: Privateer The original base game developed by Origin Systems and published in 1993 by Origin Systems and Electronic Arts. It was distributed on 6 high density (1.44MB) floppy disks. Wing Commander: Privateer Speech Pack An upgrade pack to add speech to in-flight comms. Developed by Origin Systems Inc and published in 1993 by Origin Systems and Electronic arts. It was distributed on 3 high density (1.44MB) floppy disks. Wing Commander: Privateer - Righteous Fire The one and only expansion pack, which adds a new plotline continuing from where the original game left off. Developed by Origin Systems and published by Origin Systems and Electronic Arts in 1994. It was distributed on 2 high density (1.44MB) floppy disks. Wing Commander: Privateer CD-ROM Edition A release of the original game, speech pack and Righteous FIre expansion, with further speech enhancements. Developed by Origin Systems and published by Origin Systems and Electronic Arts in 1994, released on a single CD-ROM. Wing Commander: Privateer GOG Edition Equivalent to the CD-ROM edition but distributed on-line by Good Old Games (GOG). This is the preferred version due to it being the complete Privateer package, easy to obtain and install. GOG also provides extensive documentation with this release. This is the version used in this guide. Patches There is a spaceflight music speed patch which is applicable to the CD-ROM and GOG editions, if a controller isn't going to be used. It is a file replacement patch and can be found at PCGamingWiki . Once downloaded extract into the Privateer installation directory replacing the prcd.exe file. Credit goes to HCl for producing this patch. Installation Installation on modern systems is straightforward through the GOG Galaxy app. For those with a different edition, I recommend converting any physical cds into an iso image format and especially any floppy disks into an img image format which can be read by DOSBox/DOSBox Staging/DOSBox-X. This will save wear and tear on the physical media and drives. Who knows how long those old floppies or a cd drive will last? Once you have your images, use DOSBox to install the game (and any upgrades or expansions). Once installed the patch can be applied, if applicable to the edition. Game Management I use my game management strategy described in DOSBox game management . The game itself will remain where GOG Galaxy installed it (along with a vanilla version of DOSBox), in my case D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer. The DOSBox Staging config file will be in the same parent folder as all my other non-GOG DOS games and DOSBox configurations, D:\Games\Dos. So in my case, the config file can be found in the folder D:\Games\Dos\Wing Commander Privateer\conf. If you installed a different edition with DOSBox (and followed my strategy), then in your own Wing Commander Privateer folder you might have the following folders: hdd, hard disk drive, the folder acting as a hard disk in DOSBox. fdd, floppy disk drive, the folder holding any floppy disk images. cd, the folder holding any cd images. conf, the folder storing the DOSBox config file. DOSBox Staging This guide assumes the latest version of DOSBox Staging will be used, at time of writing this was v0.81.2. This section will cover changes from the default DOSBox Staging config and any settings of particular interest, listed by configuration section. [render] aspect = auto integer_scaling = vertical viewport = 89% glshader = crt-auto The integer_scaling and glshader are default settings in DOSBox Staging but nice to include in case you want to experiment. They give a nice emulated CRT look to the game. The correct aspect rendering (4:3) will be used by default. The viewport setting of 89% corresponds to a retro CRT screen size. These settings are a personal preference but getting the game to fill a modern monitor doesn't look as good. [cpu] cycles = fixed 50000 cycleup = 100 cycledown = 100 These are good settings for my system, you may need to tweak them, but this should be a good starting point. [mixer] rate = 22050 reverb = large chorus = normal Again personal preference but I feel these settings enhance the midi music in-game. Reducing the rate seems to improve performance without affecting sound quality. [midi] mididevice = fluidsynth # mididevice = mt32 The fluidsynth midi device allows you to use of soundfonts to enhance the midi, or for a retro midi sound you could try the MT32 option (if you have the required ROMs). [fluidsynth] soundfont = "D:\Midi\Soundfonts\FluidR3_GM_GS.sf2" The soundfont is down to personal preference but I thought this one suited the game quite nicely. [mt32] romdir = "D:\Midi\Versioned" If you have MT32/CM32L ROMs this is where you can set the folder where they are located. [sblaster] irq = 5 It's very unusual to have to change any Soundblaster settings, however Privateer really didn't seem to work properly using the default IRQ 7. [joystick] joysticktype = 4axis timed = true swap34 = false deadzone = 0 This will probably be dependant on your own controller setup. I use profiling software to create a virtual controller limited to 4 axes which I then use as the basis for a game specific HOTAS config for DOSBox games, which is why I set 4axis. However Privateer will only use the 2 Joystick axes. Deadzone is a personal preference that suits my setup. The timed and swap34 are default settings, although you may need to change these depending on your controllers. [dos] ems = false Again, very unusual to have to change [dos] settings, but EMS needs to be disabled for Privateer. [autoexec] mount C "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer" mount C "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer\cloud_saves" -t overlay imgmount d "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer\game.gog" -t iso -fs iso mixer FSYNTH 33:33 c: call gog-menu.bat As the games is installed by GOG Galaxy in the 'D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer' folder, this becomes the DOSBox C: drive. Next, the overlay mount may (or may not) allow GOG cloud saving to work, if GOG Galaxy is running, but you use this at your own risk as I haven't confirmed this. 'D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer\game.gog' is the cd iso image (or equivalent) so this becomes the DOSBox D: drive. With the previous fluidsynth settings, I find the midi music can drown out the in-game speech. The mixer command reduces the volume from left and right channels to 33% which seems a better midi volume. The call command is described in the extras section below. The complete configuration [render] aspect = auto integer_scaling = vertical viewport = 89% glshader = crt-auto [cpu] cycles = fixed 50000 cycleup = 100 cycledown = 100 [mixer] rate = 22050 reverb = large chorus = normal [midi] mididevice = fluidsynth # mididevice = mt32 [fluidsynth] soundfont = "D:\Midi\Soundfonts\FluidR3_GM_GS.sf2" [mt32] romdir = "D:\Midi\Versioned" [sblaster] irq = 5 [joystick] joysticktype = 4axis timed = true swap34 = false deadzone = 0 [dos] ems = false [autoexec] mount C "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer" mount C "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer\cloud_saves" -t overlay imgmount d "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer\game.gog" -t iso -fs iso mixer FSYNTH 33:33 c: call gog-menu.bat HOTAS Config If you have a HOTAS with 4 axes or less, this won't apply. If your HOTAS setup has more than 4 axes you may wish to create a virtual controller, limited to 4 axes, through your profiling software. This is to prevent DOSBox Staging from assigning the axes oddly (e.g. assigning a throttle axis as a joystick axis). Privateer only uses the 2 joystick axes. For reference this is what I set: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder pedals DX_XROT_AXIS Game Configuration Installer/config utility To use general midi in-game you may have to run the installer, install.exe which is an installer/music and sound config utility. Once sound and music is selected use ' Install with these options ' to write the changes to the game config file. Extras If you try and use the GOG DOS menu from within DOSBox Staging, you'll find it looks odd, this is because the menu is trying to use a Codepage 437 character encoding and the DOSBox Staging config file uses a UTF-8 character encoding. This article, ' DOSBox Staging: Why do GOG menus look bad? ' goes into a bit more detail about it. As a workaround, if you copy the menu to a separate batch (.bat) file, it will use the correct character encoding and work as intended. The last line of the config file calls a separate gog-menu.bat file. call gog-menu.bat This is a zipped copy of my gog-menu.bat file, I have also added the installer/config utility as an option, to make it easier to select/switch music and sound options. It's entirely optional but if you want to use it, It should be unzipped and added to the Privateer install folder. Good hunting!

  • DOSBox game management

    DOSBox game shortcuts This is my suggested scheme for managing a large number of DOS games under DOSBox. This scheme can cover vanilla DOSBox, DOSBox-X and DOSBox Staging. This is taken from my earlier Gunship 2000 setup, which I thought covered a little too much. This concentrates on my generic scheme for managing multiple DOS games. Installing DOSBox You can get the latest version of DOSBox-X from the DOSBox-X website . Installation is straight-forward so I won't cover it here. Likewise DOSBox Staging is available from the DOSBox Staging website , again it's a straightforward installation. Once one or both are installed, remember to run each one, this will create a default configuration, which we will use later. One of the advantages of this scheme is a single installation of DOSBox, DOSBox-X or DOSBox Staging which can be used by multiple games. However each game can have a specific DOSBox configuration. DOSBox upgrades The biggest advantage of using a single installation of DOSBox, DOSBox-X or DOSBox Staging is the ease in upgrading. To upgrade you simply need to download the latest version and install it in the same location as before, overwriting the old version. As separate game config files are used, they can still be used with the new version. All that remains is to optionally tweak any existing game configurations to make use of any new enhancements or options in the new version of DOSBox-X or DOSBox Staging. How I set things up This bit is very subjective and based on my personal preference. I have a lot of DOS flight sims and this approach allows me to keep things organised while only using a single copy of DOSBox-X/Staging. Firstly I have a folder where all the DOS games live, D:\games\dos Within that folder there's another folder for the game, D:\games\dos\ The folder can contain spaces if you wish. Within the folder there are a number of sub-folders, each one has a particular purpose: hdd folder This is the folder that will be mounted in DOSBox as a hard disk drive, the C: drive in DOSBox. cd folder Stores the cd image of the game, the D: drive in DOSBox. I tend to rip my cd's to cd image files as who knows how long the cd or cd drive will last and it's generally faster. I normally use iso for data only (or cue/bin if there are audio tracks on the cd). For example .iso format is fine for Gunship 2000 as there are no audio tracks on the cd. fdd folder Stores the floppy disk images of the game (normally older games not found on cd) and acts as a floppy disk drive, the A: drive in DOSBox. We won't need this for games on cd. conf folder Stores the DOSBox-X/Staging configuration(s) specific to a game. docs folder Stores any game related documents, so manuals, reference cards, addendums, hints & tips, strategy guides, release/patch notes, etc. will be here. patches folder Stores any patches I've downloaded from the internet for a particular game. Once a patch is applied you may just want to keep the original patch .zip file here. icon folder Store an icon image (in .ico format) I use for a DOSBox shortcut for the game. I normally find the box art and convert it, giving me a very nice box art shortcut. I also use this folder to store the box art in it's original image format, eg. .jpg or .png. This is entirely optional and based on personal preference. misc folder For anything else game related I want to keep. So using Gunship 2000 as an example we'll have a minimum of: hdd, cd, conf  and docs  folders within a D:\games\dos\Gunship 2000  folder. This is all subjective and based on personal preference so feel free to use a folder/naming scheme that works for you. Initial DOSBox setup If you haven't run DOSBox-X or DOSBox Staging before, start them up, there will be a shortcut on your desktop. This will create default configuration files which we'll use next. Next we'll want to copy the default configuration to the game configuration folder. The default configuration for DOXBox-X is: C:\Users\\AppData\Local\DOSBox-X\dosbox-x-.conf While the default configuration for DOSBox Staging is: C:\Users\\AppData\Local\DOSBox\dosbox-staging.conf You may have to set the file explorer to show hidden files and folders as AppData is hidden by default. So in my case I'll be copying dosbox-x-0.83.15.conf  and dosbox-staging.conf  to the D:\dos\games\\conf  folder. I normally change the name of the config file to something more descriptive, like .conf . If you're trying DOSBox-X and Staging you might want to call them something like -x.conf  and -staging.conf . We now have a games specific configuration(s). Next we want to Copy and 'Paste shortcut' (not Paste) the DOSBox-X/Staging shortcut on the desktop, we can also change the shortcut text to , in DOSBox-X, in DOSBox Staging or whatever you prefer. Now our new shortcut will still be using the default DOSBox config, so we need to tell it to use the game specific one. We need to go into the shortcut properties and in the Target box add a -conf option followed by the game config folder and game specific config. So for me the DOSBox-X Target becomes: C:\DOSBox-X\dosbox-x.exe -conf "D:\Games\Dos\\conf\-x.conf" And for DOSBox Staging: "C:\DOSBox Staging\dosbox.exe" -noconsole -conf "D:\Games\Dos\\conf\-staging.conf" If there are any spaces in , I need to use double quotes around the config. We now have a game specific shortcut using a game specific config. If we start it up we won't see any difference because our game specific config is identical to the default one. Now it's time to make our game specific config suitable for the specific game. Installation The installation is game specific so I won't cover it in this general guide. I'll cover specific games installation in any game setup guides. Further DOSBox setup Right now if we wanted to play the game we would start DOSBox from our DOSBox game shortcut, then we'd have to go to the C drive and then we'd have to change directory to the game installation directory. Then we can start the game or run any setup utilities. Having to change drive and directory each time would get a bit tiresome after a while, so we can tell DOSBox to do this for us by adding some commands to the end of the autoexec section in the DOSBox config. After doing so my autoexec section becomes: [autoexec] mount c "D:\games\dos\\hdd" imgmount d "D:\games\dos\\cd\" -t cdrom c: cd Where c: changes to the C drive. And cd changes to the game installation folder. As DOS is not case sensitive lowercase or uppercase commands will both work. Running the shortcut now takes us to the correct drive and folder to run the game or the setup utility. If you have made a full install of the game and don't need to the cd to run it, we could remove the imgmount command, but it doesn't hurt to leave it where it is. Getting the documentation Now for something completely different. At this point it's probably a good idea to grab any documentation. This bit is entirely optional but I find it useful. The manual Depending on the release of the game you are installing the manual may be included as a document on the cd or cd image. This is normally the case for budget rereleases or compilations. Copying this to the docs folder can make referencing this manual a bit easier. If the manual is on a physical cd and you have a physical cd drive you can just copy the manual into the docs folder. You can also use Windows Explorer if it is a cd image in a .iso format. Windows Explorer doesn't support the .cue/.bin pair. So you can either obtain a 3rd party app to mount this kind of cd image and then copy it. Alternatively you can mount the cd image using DOSBox and copy the manual from the D: drive onto the C: drive. You will need to be fairly comfortable in using DOS to change drive, navigate directories and copy files. Once copied you can use Windows Explorer to copy the manual from the hdd folder (mounted in DOSBox as the C: drive) to the docs folder. An example During the installation of Gunship 2000 the manual is copied from the cd onto the hard disk. Windows Explorer can be used to copy the manual GS2000.PDF from the  D:\dos\games\Gunship 2000\hdd folder into the  D:\dos\games\Gunship 2000\docs folder. Other documents It's worth checking the installation directory for any useful documents. You can use Windows Explorer and go to the game installation folder and copy any useful .txt, .doc or README files. It's also worth checking any zipped up patch files for documents that may be useful. You can use Windows Explorer to copy these documents to the docs folder. Creating a shortcut When playing a particular sim I like to keep the docs close at hand. To do this I'd copy the D:\dos\games\\docs folder and 'paste it as a shortcut' on the desktop, making it easy to find. Open the shortcut and all the documentation is there! Shortcut icon As pretty as the DOSBox-X and DOSBox Staging shortcut icons are. I prefer to use some retro box art instead. After finding a suitable image, I use a suitable website service to convert it from it's original .jpg or .png format to a .ico format, used by Windows icons. I think it makes for a nice flight sim collection!

  • Controllers and retro sims part 2: Virtual controllers

    A virtual controller, also known as an enumerated device, is a controller which is seen in Windows as a single device which replaces one or more physical USB controllers. The virtual controller can be configured with a variable number of axes and button assignments. If you have profile software for your HOTAS device(s) it may create a virtual controller when a HOTAS profile is applied. When a virtual controller is enabled (through a profile) it becomes the sole device for the physical devices included in the profile. The physical devices are normally disabled in Windows, and you can see this if you go to the Windows Device Manager. T.A.R.G.E.T I'm fortunate enough to have a Thrustmaster throttle, stick and pedals supported by Thrustmaster's profiling software Target. With this software I can assign the 3 axes I want to use to axes across all 3 of my controllers, but I will briefly cover an alternative below. Using Target I can leave the X and Y axis assignment of my stick at it's default. Change the throttle to use a single Z axis on the main throttle axis (disabling the rest) and add an X rotation axis to my rudder pedals, as shown below. My T.A.R.G.E.T profile I have now used a virtual controller to turn 3 USB devices with many axes into a single 4 axes controller. When I run the profile, my 3 USB devices used in the profile are disabled in Windows to be replaced by a single virtual controller. This is my default DOSBox profile in Target which I can use as a basis for a more specific game profile, I have the axes, now I can copy it and add button assignments as needed! You may have you own profiling software from your HOTAS supplier which may allow you to do something similar. Joystick Gremlin If you can't use your suppliers profiling software, may be it doesn't support one of your particular device, or provide functionality to disable axes, or you are using controllers from multiple suppliers then there is an open source alternative, Joystick Gremlin . Joystick Gremlin provides similar functionality as Target but supports devices from any manufacturer, their website is definitely worth a look. Joystick Gremlin will create your HOTAS profile and then use vJoy to provide the virtual controller. Now to be honest I have dabbled very very briefly in Joystick Gremlin and there may be a bit of a learning curve and as I was starting out with Target I put Joystick Gremlin aside. So if you want to try this route I would suggest taking a look at some tutorials, websites and videos so you know what might be involved. Make sure you are comfortable in trying it out. I have seen comments where Target users have tried Joystick Gremlin and vowed never to go back! Maybe one day I'll take another run at it and become a convert, but for now I'm finding Target sufficient for my needs. One last point if you have created a virtual controller, check the calibration in Windows to make sure it is well calibrated and has all the axes you expect!

  • InstallShield freezing? It may be a Logitech issue

    If your legacy flight sim InstallShield app is freezing then it may be a Logitech Gaming Software issue and it's desire to communicate with Discord?!? Will it affect you? Task Manager Details tab The issue seems to be that the installer is waiting for a resource which never becomes free, a resource being held onto by the Logitech Gaming software. If you see this, you have the issue If your installation has frozen: Open the Task Manager and go to the Processes tab. You should see a SETUP.EXE (32 bit) entry with a status of 'Not responding'. Go to the Details tab, find the SETUP.EXE entry with the status of 'Not responding'. Right click and select 'Analyze wait chain'. If the process is logitechg_discord.exe then you have the issue. How to fix it The first thing to do is to use the Task Manager to kill off the frozen InstallShield setup.exe process. Then follow the instructions in this Logitech Gaming Software integration with Discord article. This will allow you to enable the Game Integration Customization View (which is disabled by default). You can disable the Discord applet here Within this view you can stop the Discord applet (which is enabled by default) and select the 'Never launch' option to make sure you are never bothered by it again! If you absolutely can't live without Logitech/Discord integration, stop the applet, install the game and restart the applet.

  • EF2000 Updated Part 4: Running Super EF2000 in PCem

    This article will cover running Super EF2000 (the Windows 95 version of EF2000) in the PCem emulator. Background Super EF2000 is feature equivalent to EF2000 with the TACTCOM upgrade. However the GFX+ upgrade is not compatible, as the game was rewritten as a dedicated Windows 95 application using the DIrectX libraries. It is also known as EF2000: Special Edition and is present in the EF2000 V2.0 edition as 'EF2000 for Windows 95'. For this guide the latest version of PCem v17 will be used. PCem is used in preference to native Windows 10 as there are timing issues with the game engine running too quickly on modern hardware. PCem ensures the sim will run at the correct speed. PCem setup If you're completely new to setting up PCem or need a refresher, I highly recommend the excellent YouTube tutorial video by PhilsComputerLab, PCem Windows 98 Setup . Before following the steps in the tutorial, take a look at the advice in the Sound card section below. Once you have a basic, clean Windows 98 virtual machine and hard disk image, I recommend: Taking a copy of the basic virtual machine to create a game specific virtual machine. Taking a copy of the basic hard disk image to create a game specific image. Use PCem and reconfigure the game specific virtual machine to use the game specific hard disk image. If things go badly wrong, you'll always have the basic image to try again with and it'll save a lot of time and effort if you ever want to try a different game with PCem. Sound card The sound card specified in the tutorial is the Soundblaster PCI 128, however running EF2000 with this emulated card results in distorted audio with a constant humming during gameplay. It's recommended to replace the emulated card with a Soundblaster 16 or Creative AWE 32 sound card. Drivers can be found at the PhilsComputerLab website, both for the Soundblaster 16 and AWE32 . Drivers can also be found at the VOGONS Vintage Driver Library . Once complete you may wish to take a copy of this clean Windows 98 AWE 32 or Soundblaster 16 machine and hard disk, for future games that struggle with the Soundblaster PCI 128. Installation Since it uses a fairly standard Windows installer app, installation should be straightforward and complete without issue. Once complete there is no need to run a config utility as config questions are asked during the installation. The default installation folder (on the PCem virtual machine) is c:\Program Files\Digital Image Design\EF2000. Patching There are no patches for the english language version. However there is a single patch for french and german versions of Super EF2000. It is a small file replacement patch with no associated readme so it isn't clear what this patch enhances or fixes. It can be found at the Internet Archive . Running It's recommended to run with either the physical cd in the host machine drive and configured in PCem or a bin/cue cd image pair (to preserve the red book cd audio) of the game cd, mounted in PCem (I prefer to use cd images). This will allow the selection of cd audio/midi should you wish, from within the in-game options page. HOTAS setup Take a look at my Controllers and retro sims part 5: PCem  guide for installing HOTAS controllers in PCem. Once you have a custom calibrated Windows 98 controller the hard work is done. As long as the 3rd axis is the throttle and the 4th axis is the rudder, which can be checked in the Windows 98 control panel in the Game controllers section, then the game will correctly assign the axes. Virtual controller For those with HOTAS controllers with more than 4 axes, you'll need to use your profile software to limit the total number of axes to four. The below example is how my Warthog joystick, throttle and rudder pedals were configured as a virtual controller: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder pedals DX_XROT_AXIS This virtual controller was used to set up the twin joysticks in PCem. Documentation The existing DOS manuals were converted into Windows help files for Super EF2000. However pdf versions of the manual and addendum are available on the cd and recommended reading. In addition the I feel it may be worth trying to track down the keyboard command reference as the pdf version is probably easier to use than the Windows help version, and the theater map. Good hunting!

  • EF2000 Updated Part 2: Installation

    This article covers the steps to create an installation of EF2000. It will involve, installing the EF2000 base game, installing the TACTCOM upgrade and installing the 3DFX GFX+ upgrade. It will also cover cleaning up the installation and optimising libraries. This is also an update of the previous article, ' DID you know? Installing & Patching EF2000 on Windows 10 '. This will give us a fully patched DOS installation of EF2000. As it is a DOS installation, there are no Windows registry entries or dll's to register making it a portable installation that can be copied, zipped up or moved and used with the EF2000 Reloaded app, DOSBox or PCem. I'll also cover some quicker methods using EF2000 V2.0. This article doesn't cover the Windows 95 version, Super EF2000 (or EF2000: Special Edition). That will be in a later article. The EF2000: Evolution edition isn't explicitly covered, however, since has 2 cds, one cd may contain the base game and the other cd, the TACTCOM upgrade, so the steps should be similar (if not identical). The approach A PCem virtual machine running Windows 98 will be used to create the installation. This is necessary as the GFX+ update is a 16 bit Windows installer app. The DOS based EF2000 base game and TACTCOM upgrade will be installed through a DOS command prompt. The steps required are: Create a PCem virtual machine running Windows 98. Install EF2000 and TACTCOM upgrade with a DOS command prompt. Install the GFX+ upgrade for 3DFX cards. Clean up the installation. Update the DOS/4G library. Copy the EF2000 installation onto Windows 10. CD or CD image? My personal preference is to rip my cds to cd images to save wear and tear on the disc and more importantly the physical drive. The PCem emulated cd drive supports both physical cds or cd images. The EF2000 base game cd contains red book cd music so this should be ripped to a bin/cue image pair to preserve the cd audio, allowing it to be played during gameplay, if desired. The TACTCOM upgrade cd can be ripped to an iso data only format as it does not contain cd music. Creating the PCem virtual machine If you're completely new to setting up PCem or need a refresher, I highly recommend the excellent YouTube tutorial video by PhilsComputerLab, PCem Windows 98 Setup . This guide assumes the latest version, PCem v17. As we are using PCem to create a DOS installation the graphics and sound capabilities don't really matter, although all the drivers used in the video can be found on the PhilsComputerLab website, making PCem setup a lot easier. It also means it will be a clean Windows 98 machine, that can be used for other games. Once you have a basic, clean Windows 98 virtual machine and hard disk image, I recommend: Taking a copy of the basic virtual machine to create a game specific virtual machine. Taking a copy of the basic hard disk image to create a game specific image. Use PCem and reconfigure the game specific virtual machine to use the game specific hard disk image. If things go badly wrong, you'll always have the basic image to try again with and it'll save a lot of time and effort if you ever want to try a different game with PCem. Installing EF2000 and TACTCOM Start the PCem virtual machine you want to use to create the installation. To install EF2000: Mount the EF2000 base game cd or cd image in PCem. Open up a dos prompt in Windows 95 and run the EF2000 Installer ( install.exe ), select a full install to hard disk, this will automatically install it to c:\EF2000. Once installation is complete hit enter to continue, the config utility will automatically run, simply quit out for now. To install the TACTCOM upgrade: Mount the TACTCOM cd or cd image in PCem. Open up a dos prompt and run the TACTCOM upgrade ( tactcom.exe ), this will default to the c:\EF2000 installation directory and apply the upgrade. Once complete the upgrade should quit with the message 'TACTCOM: Installation successful'. These steps should be similar (if not identical) for EF2000: Evolution. The EF2000 V2.0 release can use different steps below. Installing the 3DFX GFX+ upgrade The GFX+ upgrade can be found at the Internet Archive . To install the upgrade: Shutdown the PCem virtual machine, if it is running. Mount the virtual hard disk in Windows 10 by opening the .vhd file used by the PCem virtual machine. Unzip the GFX+ upgrade and copy the tactpat.exe file into the EF2000 folder of the mounted virtual hard disk. Once copied, eject the mounted virtual hard disk and start the PCem virtual machine. Go to the EF2000 folder and run tactpat.exe . Choose the 3DFX option, be patient, it can take a while to get started. The upgrade occurs in two phases a DOS window will appear and it will patch EF2000. Once finished, you should see a 'patch successfully applied' message. Close this DOS window and another should open, it should patch TACTCOM. Once complete, you should see another 'patch successfully applied' message Close the DOS window and exit the GFX+ Upgrade. Cleaning up the installation During the upgrade process the clump_3.txt file in the EF2000 folder was updated with a few non-existent files. If you try and run EF2000 you should see an error: clump: no file './3/paul.3' To fix, open up the clump_3.txt  file in Notepad and remove the following lines: paul paulpaul temp_83 If you try and run EF2000 this time, you should see the Intel Pentium intro movie and get to the EF2000 menu screen, there won't be any sound but it proves the installation is working. EF2000 V2.0 The EF2000 V2.0 Windows installer app can be used to combine installation of EF2000, TACTCOM and the GFX+ upgrade into a single installation step. Despite running through a Windows type install, it still installs the DOS version and the default installation folder becomes: C:\Program Files\Digital Image Design\EF2000 V2.0 for 3DFX To use this method: Mount the EF2000 V2.0 cd or cd image in PCem. If autorun doesn't open the installer, from PCem, run setup from the EF2000 V2.0 cd (or cd image). Select the 'Install for 3DFX' option. You can test the installation by running EF2000 from the Start menu. You should see the Intel Pentium intro movie and get to the EF2000 menu screen, there won't be any sound but it proves the installation is working. Updating the DOS/4G library The DOS/4G library is a 32-bit DOS extender which allows DOS apps to use memory above the 640k conventional memory limit. You can read more about it on Wikipedia . The DOS/4G library bundled with EF2000 is obviously quite old now and newer more advanced DOS extenders with fewer bugs now exist. A modern replacement is DOS/32 available from GitHub . The latest release of DOS/32 is v9.1.2. The executable is dos32ang.exe . To replace DOS/4G there are a couple of options: Mount the PCem virtual hard disk and replace DOS/4G in the EF2000 installation folder. The PCem virtual machine can be run afterwards to check the installation still works. Get the EF2000 folder into Windows 10 and then make the replacement, (you may find this an easier option). Whichever method you choose, the steps are essentially the same, once you have downloaded the file, do the following: Copy dos32ang.exe into the EF2000 folder. Rename the existing dos4gw.exe file (e.g. dos4gw.bak). It's useful to keep around in case you have issues and want to switch back. Rename dos32ang.exe to dos4gw.exe. There are other options for running DOS/32 in preference to DOS/4G but this one seems the easiest. If this version gives you trouble an alternative v9.1.2 is also available on GitHub . Getting the installation All that remains is get the EF2000 installation from the PCem virtual machine and into Windows. To copy the installation: Shutdown the PCem virtual machine, if it is running. Mount the virtual hard disk in Windows 10 by opening the .vhd file used by the PCem virtual machine. Copy the EF2000 installation folder onto a suitable Windows 10 disk (and zip up the folder if you wish). Once copied, eject the mounted virtual hard disk. Installing EF2000 V2.0 without PCem A quicker way to install EF2000 V2.0 edition only, without PCem is to replace the 16-bit Windows installer app (which is unsupported in Windows 10) with a 32-bit installer app which is still supported and then just run the 32-bit installer. This is equivalent to choosing the 'Install for 3DFX' option from the cd, so it's still a DOS version. To do so: Copy the \GFXPLUS\3DFX folder from the EF2000 v2.0 cd (or cd image) onto a Windows 10 drive. Download the generic InstallShield 32-bit installer app from PCGamingWiki . Unzip and place the setup32.exe file in the 3DFX folder. Run the setup32 installer as Administrator. Be patient it takes a little while to start. Choose an appropriate installation folder for EF2000 and complete the install. Complete the installation by updating the DOS/4G library (described above). Finally... This article has covered creating a DOS install of EF2000 for earlier EF2000 DOS releases and two alternative methods for EF2000 V2.0. This DOS install can now be used with the EF2000 Reloaded app, DOSBox or PCem and that'll be covered in the next article. Good hunting...

  • Joint Strike Fighter (Windows 10 & DxWrapper)

    A guide on running the Eidos/Innerloop classic sim, Joint Strike Fighter (JSF) natively in Windows 10 with DxWrapper. The previous article about running JSF in Windows 10, ' Running Joint Strike Fighter in Windows 10 ' concluded that the optimum settings were emulated 3dfx settings with nGlide v0.97 and a legacy 4 axis HOTAS. Using software rendering at higher resolutions caused frequent crashes to the desktop (CTD) and attempts to use a modern HOTAS setup resulted in the game crashing at startup. However, further testing with a DirectX wrapper, DxWrapper, has shown that a more stable software rendering solution is possible while using a modern HOTAS controller. Installation & patching Installation and patching remains unchanged and is identical to the process described in ' Running Joint Strike Fighter in Windows 10 '. JSF v1.12 will continue to be used. DirectX wrapper The DirectX wrapper used is the latest DxWrapper version, v1.2.7300.25. Maintained by Elisha and available from GitHub at the DxWrapper project page . Since DxWrapper is compatible with Windows 11, this solution may be workable on Windows 11 although this hasn't been tested. So firstly, a huge thank you to Elisha, the many project contributors and the maintainers and contributors of those projects that DxWrapper used source code from (you can read about them in the credits section). Without their hard work running this sim on Windows 10 would still be very problematic. If you wish to test various DxWrapper options, there is a comprehensive wiki at the Github project page. Installation Download and extract DxWrapper. The following files were copied to the JSF installation folder: dxwrapper.dll dxwrapper.ini Stub\ddraw.dll Stub\dinput.dll Note: Only the files need to be copied into the installation directory the Stub path does not need to be preserved. Configuration Each component wrapper is turned on on off in the compatibility section. The most important options will be briefly covered. The HandleException issue seems to prevent the random CTD's. Instead at very high resolutions the flight engine seems have issues handling HUD sprites which results in artifacts around the outside of the HUD (where most of the HUD sprites reside) rather than in the centre of the screen. EnableDdrawWrapper enables wrapping dx5 calls used by the game. Options within the [ddraw] section convert these calls to dx7. Dd7to9 enables conversion from DirectDraw 7 to 9. The [Dd7to9] section maintains the aspect ratio and removes scan lines from the intro movie (so you can tell the wrapper is working). The [d3d9] section has the option to run in a fullscreen window mode making it easier to close the game if it does crash. Dinputto8 converts DirectInput calls to dx8 increasing modern HOTAS compatibility. EnableDsoundWrapper enables the sound wrapper. Some artifacting seemed to occur simultaneously with sound triggers (midi music playing, wingman msgs, warnings). This may have been a coincidence but I've enabled the wrapper. Game configuration In order to run without in-game exceptions causing artifacting at higher resolutions both in-game lo-res emulation options must be enabled, big pixels and black lines, as shown in the screenshot. My configuration This is my current dxwrapper.ini configuration, the game plays without issue at 1920x1200 with a modern TM Warthog HOTAS and TFRP rudder pedals. ;; Config file for DirectX DLL Wrapper ;; ;; For details, see: ;; https://github.com/elishacloud/dxwrapper/wiki/Configuration ;; [General] RealDllPath = AUTO WrapperMode = AUTO LoadCustomDllPath = ExcludeProcess = IncludeProcess = RunProcess = WaitForProcess = 0 DisableLogging = 0 [Plugins] LoadPlugins = 0 LoadFromScriptsOnly = 0 [Compatibility] Dd7to9 = 1 D3d8to9 = 0 DDrawCompat = 0 Dinputto8 = 1 DisableGameUX = 1 EnableDdrawWrapper = 1 EnableD3d9Wrapper = 0 EnableDinput8Wrapper = 0 EnableDsoundWrapper = 1 HandleExceptions = 1 SingleProcAffinity = 1 [DDrawCompat] DDrawCompat20 = 0 DDrawCompat21 = 0 DDrawCompat32 = 0 DDrawCompatDisableGDIHook = 0 DDrawCompatNoProcAffinity = 0 [ddraw] ConvertToDirectDraw7 = 1 ConvertToDirect3D7 = 1 DdrawOverrideBitMode = 0 DdrawResolutionHack = 0 [Dd7to9] DdrawAutoFrameSkip = 0 DdrawEmulateSurface = 0 DdrawEmulateLock = 0 DdrawForceMipMapAutoGen = 0 DdrawFlipFillColor = 0 DdrawFixByteAlignment = 0 DdrawEnableByteAlignment = 0 DdrawRemoveScanlines = 1 DdrawRemoveInterlacing = 0 DdrawReadFromGDI = 0 DdrawWriteToGDI = 0 DdrawDisableDirect3DCaps = 0 DdrawLimitDisplayModeCount = 0 DdrawCustomWidth = 0 DdrawCustomHeight = 0 DdrawUseNativeResolution = 0 DdrawOverrideWidth = 0 DdrawOverrideHeight = 0 DdrawIntegerScalingClamp = 0 DdrawMaintainAspectRatio = 1 [d3d9] AnisotropicFiltering = 0 AntiAliasing = 0 EnableVSync = 0 ForceVsyncMode = 0 OverrideRefreshRate = 0 LimitPerFrameFPS = 0 EnableWindowMode = 0 WindowModeBorder = 0 SetInitialWindowPosition = 0 InitialWindowPositionLeft = 0 InitialWindowPositionTop = 0 FullscreenWindowMode = 1 ForceExclusiveFullscreen = 0 ForceMixedVertexProcessing = 0 ForceSystemMemVertexCache = 0 SetSwapEffectShim = 0 DisableMaxWindowedMode = 0 ForceDirect3D9On12 = 0 GraphicsHybridAdapter = 0 [FullScreen] FullScreen = 0 ForceWindowResize = 0 WaitForWindowChanges = 0 [dinput8] DeviceLookupCacheTime = 0 FilterNonActiveInput = 0 FixHighFrequencyMouse = 0 MouseMovementFactor = 0 MouseMovementPadding = 0 [dsound] Num2DBuffers = 0 Num3DBuffers = 0 ForceCertification = 0 ForceExclusiveMode = 0 ForceSoftwareMixing = 0 ForceHardwareMixing = 0 ForceHQ3DSoftMixing = 0 ForceNonStaticBuffers = 0 ForceVoiceManagement = 0 ForcePrimaryBufferFormat = 0 PrimaryBufferBits = 16 PrimaryBufferSamples = 48000 PrimaryBufferChannels = 2 AudioClipDetection = 0 This is the above dxwrapper.ini config file, zipped and available for download. Notes on running If you have a default system glide wrapper like nGlide or a local Glide wrapper in the JSF install folder and the splash screen is enabled, you will see it when JSF starts, even if the in-game options specify software rendering rather than (emulated) 3dfx hardware rendering. Initial joystick setup was a little problematic, when first setting up and jumping into a dogfight, keyboard controls had to be used before switching to mouse control and then finally switching to joystick control. This may have been a result of the testing I was carrying out at the time. Subsequently, I was able to use the joystick immediately. HOTAS setup Like many other sims, JSF prefers a HOTAS setup limited to 4 axes. For those with 4 axes or less this won't apply. For those with a HOTAS with more than 4 axes, HOTAS profiling software will need to be used to limit axes. In my case I'm able to use TM TARGET to create a suitable profile with only 4 axes. They are specified as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder pedals DX_ZROT_AXIS This sim seems to prefer the z rotation axis rather than the x rotation axis for rudder. Limitations Although a huge step forward in compatibility, it is not perfect. At extremely high resolutions, e.g. 3840x2160 random freezing and artifacting will occur even with DxWrapper and in-game lo-res options enabled. This seems like a limit in the in-game engine's ability to handle sprite at these resolutions, so this may not be fixable with wrappers. This is shown in the below video. Despite an increase in HOTAS compatibility the HOTAS buttons will be non-functional. Although this seems like a serious issue, it can be resolved with HOTAS profiling software (e.g. TARGET) or other joystick button mapping to keyboard software (e.g. Joy2Key, Joystick Gremlin, etc). Use of the in-game button mapping software is not recommended as will crash once button 36 is reached, this may not be an issue if you have fewer buttons. Hopefully this guide will allow you to play JSF at higher resolutions, good hunting!

Drop Me a Line, Let Me Know What You Think

Thanks for submitting!

© 2023 by DarkenedRoom.. Powered and secured by Wix

bottom of page