Gliding with Gold & boxing Anthology
- DarkenedRoom
- May 26
- 9 min read
A guide to running Jane's Longbow Gold and Jane's Longbow Anthology with the Glide patch in the 86Box emulator.
Since there are still issues running the Glide versions of Gold or Anthology natively in Win10, the following article looks at some other methods, using other emulators, before describing the configuration of 86Box.
Strategy
The following alternatives were also tested before settling on 86Box as a recommended solution:
BoxedWine, a limited Linux VM running Wine, taken from the Steam M1 Tank Platoon 2 release. Runs but without controller support.
Qemu with 3Dfx support. Runs but crashes to Win98 desktop once mission starts.
PCem v17, crashes to Win10 desktop once mission starts.
DOSBox-X with internal 3Dfx emulation, runs and mission can start but extremely choppy visuals, unplayable.
DOSBox-X with Glide passthrough to nGlide v2.10. Runs, mission can start successful but random crashes during mission.
DOSBox-X with Glide passthrough to dgVoodoo2 v2.86. Runs, mission can start but opens in partial 640x480 window, cannot toggle to full screen, unplayable.
DOSBox Staging is not an appropriate solution and not tested, as it does not support a Win95/98 platform required by a Glide patched Gold/Anthology install.
86Box
The heart of the solution is the x86 emulator, 86Box. The 86Box website describes it as:
86Box is a low level x86 emulator that runs older operating systems and software designed for IBM PC systems and compatibles from 1981 through fairly recent system designs based on the PCI bus.
This article assumes the latest version (at writing) will be used, v4.2.1. This version is available from 86Box.net. This website should be the first site to visit to learn more about this emulator.
An important point to note is that it is a single threaded emulator, so the single thread performance of your machine and the specs of the machine being emulated will have a major impact on the gameplay of Longbow.
Installation and configuration
86Box installation should be straight-forward although if you have the choice between SSD or mechanical drives an SSD is recommended for optimum performance.
Once installed you'll need to obtain a rom set before you can use 86Box. The 'Getting started' section of the 86Box documentation describes how. The docs are linked from 86Box.net or can be found directly at the 86Box documentation site.
Instructions should be followed to place the roms in a suitable rom folder under 86Box. This concludes the installation and configuration of 86Box.
Credit and thanks go to Miran Grča and the 86Box developers.
86Box Manager
The 86Box website recommends the use of a manager app to assist in configuration and management of multiple 86Box virtual machines (VM). A list of suitable manager apps can be found on the 86Box website for each platform. This article recommends the latest version of 86Box Manager v1.7.4.
It is available for download at the 86Box Manager GitHub repository.
Installation and configuration
86Box Manager is distributed as a zip file and only requires extracting to a suitable folder to complete installation. The few simple configuration steps are listed on the 86Box Manager GitHub page.
Credit and thanks go to daviunic/Overdoze and the 86Box Manager contributors.
Virtual machine specs
As stated previously, the single thread performance of your machine and the specs of the machine being emulated will have a major impact on the gameplay of Longbow. Therefore we want to strike a balance between a virtual machine that meets or exceeds the recommended specs of Longbow, but not excessively to the point that a Win10/11 host PC struggles to emulate the virtual machine and performance suffers.
For reference purposes my host machine uses an i7-7700K processor @ 4.2Ghz. 64MB of memory using an XMP memory profile @ 3.2Ghz (maybe, IIRC). Nvidia RTX 3060 and SSD storage. Based on comparison with your own hardware you may wish to change the virtual machine specs below.
The emulated machine is described using 86Box/86Box Manager configuration entries. Where an entry is not listed, the default setting can continue to be used. Joystick/HOTAS configuration is discussed separately.
Machine
Machine type: [1997] Slot 1
Machine: [i440BX] Gigabyte GA-686BX
CPU type: Intel Pentium Pro
Frequency: 166
Memory: 128MB
Display
Video: [PCI] S3 ViRGE/DX (375)
Memory size: 4MB
Bilinear filtering: enabled
Dithering: enabled
Voodoo 1 or 2 Graphics: enabled
Voodoo type: 3Dfx Voodoo Graphics
Framebuffer memory size: 4MB
Texture memory size: 4MB
Bilinear filtering: enabled
Dither subtraction: enabled
Screen filter: disabled
Render threads: 4
SLI: disabled
Recompiler: enabled
Input devices
Mouse: Standard PS/2 Mouse
Buttons: Wheel
Joystick: discussed later, see HOTAS config
Sound
Sound card # 1: [ISA16] Sound Blaster 16
All options left as default
Use FLOAT32 sound: enabled
FM synth driver: Nuked (more accurate)
Storage controllers
HD Controller: Internal controller
FD Controller: Internal controller
Hard disks
Select a 'New...' hard disk.
File name: choose a suitable file name
Size (MB): 3200
Cylinders, Heads and Sectors will be configured once Size is chosen
Image Format: Dynamic-size VHD (.vhd)
Speed: [1998] 5400 RPM
Floppy & CD-ROM drives
Floppy drives
First:
Type: 3.5" 1.44M
Others:
None
CD-ROM drives
First:
Bus: ATAPI
Speed: 32x
Type: 86BOX CD-ROM 1.00
Others:
Disabled
Creating the virtual machine
The virtual machine will be using Windows 98 Second Edition (Win98SE). Before creating the virtual machine it may be useful to take a look at the excellent YouTube tutorial video by PhilsComputerLab, PCem Windows 98 Setup. Even though it covers the alternative PCem emulator the steps for configuring the bios and installing Win98SE will be identical.
The virtual machine bios should be configured to boot from the CD-ROM first and then the C drive.
As usual all credit for the excellent YouTube tutorial and PhilsComputerLab website should go to Phil.
Windows 98 Second Edition
You will need to obtain the OEM full edition which allows the PC to be booted from the CD-ROM.
By following the advice provided by PhilsComputerLab and the YouTube video, PCem Windows 98 Setup you should end up with a clean Win98SE installation.
Device drivers
Now it's time to optimise the hardware using appropriate hardware device drivers, installed in the order below, for the following devices:
Intel chipset
Sound Blaster 16
3Dfx Voodoo Accelerator
It's worth remembering Win98SE does not include support for opening zip files. So it is recommended to do this with Win10/11 by following the steps:
Download copies of the device drivers.
Extract each zip file on your Win10/11 machine, into a separate folder.
Shutdown the virtual machine if it is running.
Mount the virtual hard disk in Win10/11 by opening the vhd hard disk file (created earlier when configuring the virtual machine in 86Box Manager).
Copy the folders containing the device driver and any downloaded executable (.exe) files containing device drivers, onto the mounted virtual hard disk. I would recommend copying into the 'My Documents' folder on the virtual hard disk.
Eject the virtual hard disk, unmounting it from Win10/11, otherwise you won't be able to start Win98SE on the virtual machine.
Start up the virtual machine and once Win98SE has started, begin installing the device drivers.
Intel chipset drivers
The Intel chipset drivers for the 440BX chipset can be found on the PhilsComputerLab website. The specific drivers are 2001 drivers, supporting Windows 9x, 2000 and XP (3.20.1008.zip).
As the drivers are distributed as a zip file, it should be extracted in Win10/11 first before being copied to the virtual hard disk. The executable file (infinst_enu.exe) should be run to install the drivers.
Sound Blaster 16 drivers
The Sound Blaster 16/AWE32 Driver Update for Win98 can be found on the VOGONS Vintage Driver Library.
As the drivers are distributed as a zip file, it should be extracted in Win10/11 first before being copied to the virtual hard disk. This distribution includes an installer app (upddrv95.exe) which will install the drivers.
3Dfx Voodoo Accelerator drivers
The Voodoo Accelerator drivers can be found on the PhilsComputerLab website. The specific drivers are the May 1999 - Latest Reference drivers (voodoo_graphics_driver_kit_version_3.01.00.zip)
As the drivers are distributed as a zip file, it should be extracted in Win10/11 first before being copied to the virtual hard disk. Win98SE may have already installed 3Dfx Voodoo drivers, but they should be replaced by this version. You will have to open the Voodoo device in Device Manager and upgrade the drivers.
AmnHLT driver
There is an additional virtual device driver that can be installed to increase the performance of the 86Box emulator. Quoting the VOGONS post by Jo22:
AmnHLT is a third-party VxD that issues a HLT (halt) instruction to the CPU whenever Windows 9x is idle. It's meant to avoid a 100% processor usage in VMs - and emulators. HLT is supported by late 486 processors and higher.
It can be obtained from the VOGONS post by SA1988. AmnHLT.7z is a 7zip archive. Only the amnrefr.vxd file is required from the archive.
The following installation instructions were provided in a VOGONS post by 0x6A7232:
In Win98SE, open regedit.
Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD.
Create a key named AmnHLT.
Create a binary value named Start with a value of 00 inside the AmnHLT key.
Create a string value named StaticVxD with a string of AMNREFR.VXD inside the AmnHLT key.
Shutdown the operating system and close the emulator.
Copy amnrefr.vxd driver into the C:\Windows\System folder of the virtual hard disk.
Start the Win98SE virtual machine.
Credit and thanks go to VOGONS members Jo22, SA1988 and 0x6A7232.
Preserving the virtual machine
At this point we have a clean Win98SE virtual machine (VM) using optimised device drivers. It is recommended to take a copy of the 86Box VM configuration and the virtual hard disk (vhd) file.
This provide a clean VM you can use to try out with other 3Dfx/Glide games that struggle to run natively in Win10 with Glide/DX wrappers, or with other emulators, without having to repeat the above to create the VM.
Longbow media
As usual I recommend converting physical media to images to save wear and tear on disks and drives. The Gold and Anthology cds can be ripped to an iso, data only cd image, format as there is no cd audio/music tracks on the Longbow discs.
Longbow installation
Either Gold or Anthology versions can be installed. The first cd images should be mounted within 86Box. If the cd does not auto run the installer app, it can be started manually by opening it from the 86Box emulated cd drive.
Installation should be straightforward and complete without issue. During the Gold/Anthology installation, graphics and textures options can be set to high.
Longbow Anthology will ask for a normal or custom install. Choose a custom install and only install the Longbow (not Longbow2) components. Later you will be asked if the GoldFX(A) patch should be installed, do not install the patch at this point, it will be done later.
Note: the virtual hard disk has been sized to allow the Gold or Anthology cd images to be copied to the virtual hard disk, but not both.
Longbow patches
Longbow Gold
The Glide version of Longbow Gold uses the GoldFX patch only, no other patches are required or should be installed.
This patch can be found at soggi.org as a 7zip archive or as a self extracting archive in this VOGONS post from feda, so a big thank you to both. Installation should be straight-forward and complete without issue.
Longbow Anthology
The Glide version of Longbow Anthology uses the GoldFX(A) patch only, no other patches are required or should be installed.
This patch can be found on the first Longbow Anthology cd or cd image. Installation should be straight-forward and complete without issue.
Issues
If either patch complains a suitable Voodoo Accelerator cannot be found, ensure the recommended Voodoo drivers have been installed.
Longbow fixes
For those familiar with the VOGONS post, Janes AH-64D Longbow 1 & 2 without CD inc Memory Fix (Windows) may be wondering why the memory fixes are not applied.
These fixes are required for modern machines with over 365MB of memory, however the 86Box Win98SE VM configured earlier, is only using 128MB, so is not affected. If you really want to apply them, they will not affect the game under 86Box.
CD emulation
The developers of Longbow, left in a functional cd emulation facility. If you are using cd images the performance difference will be minor/negligible, however as a convenience, it removes the necessity to mount/unmount cd images in 86Box, so is recommended.
To use it, copy the contents of each Longbow cd to a folder (e.g. C:\Janes\Lbcd1) within Win98SE. Note: for Anthology this will be the first two Longbow 1 cd/images (not the Longbow 2 cd/images)
Longbow Gold
For Longbow Gold create a file CDEmu.ini in the Longbow installation folder (in my case C:\Janes\Lbgold) and specify the folder for each of the three Longbow Gold cds, like so:
[CDEmulate]
CD001=C:\Janes\Lbcd1
CD002=C:\Janes\Lbcd2
CD003=C:\Janes\Lbcd3Longbow Anthology
For Longbow Anthology create a file CDEmu.ini in the Longbow installation folder (in my case C:\Janes\Lba\Longbow) and specify the folder for both Longbow 1 cd/images (but not the Longbow 2 cd/images), like so:
[CDEmulate]
CD001=C:\Janes\Lbcd1
CD002=C:\Janes\Lbcd2HOTAS config
Configuring axes may not be required if your HOTAS has 4 axes or less. When using devices totaling more than 4 axes, a virtual controller can be used, limited to 4 axes.
The physical axes to Windows axes were configured as follows:
Physical axis | Windows axis |
Joystick x-axis | DX_X_AXIS |
Joystick y-axis | DX_Y_AXIS |
Throttle | DX_Z_AXIS |
Rudder | DX_XROT_AXIS |
86Box configuration
The 86Box HOTAS configuration is very similar to the PCem HOTAS configuration described in Controllers and retro sims part 5: PCem. However 86Box HOTAS configuration is easier with a single 4-axis, 4-button joystick available, which is exactly what the virtual controller is configured to be and what many physical HOTAS controllers are.
To configure a HOTAS within the 86Box Manager, the following settings were used in the 'Input devices' section:
Joystick: 4-axis, 4-button joystick
Joystick 1
Device: set to the virtual controller, which was the only device present.
Axes: set to the corresponding virtual controller axes except z and zX axes (see below)
Buttons: set to the corresponding virtual controller buttons.
During creation and calibration of a custom controller in Win98SE it became apparent that the 3rd and 4th axes required swapping. This was done in the 86Box joystick config by swapping the z and zX axes (see screenshot).
Win98SE configuration
The steps to create a custom controller in Win98SE are the same as those discussed in Controllers and retro sims part 5: PCem in the section, Adding a controller to Windows 98.
Once the custom controller is calibrated the HOTAS configuration is complete in Win98SE.
Video
Here's a brief test video showing Longbow Gold running, prior to joystick setup.
Good hunting!
Comments