VOGONS


First post, by exofreeze

User metadata
Rank Member
Rank
Member

When trying to install this add-on pack it hangs during the update process of Falcon 3.0

The message returned is:
Neither command line parameter returned is an existing directory

This seems to be when it calls:
gopatch /NOI c: epatch.rtp

If I type that command line I get the same error message. However if I type it without the "c:\" it seems to run and begins patching.

The install process refuses to recognize the game has been patched however, and attempts to rerun this, so it always hangs and it never proceeds to the actual expansion installation.

In the readme, there are instructions for a manual update/install of the program:

To install MiG-29 with Falcon 3.0 only already
installed:

- Insert Disk 1 in drive A.
- At the A: prompt, type the following:
COPY GOPATCH.EXE C:\FALCON3 <Enter>
COPY EPATCH.RTP C:\FALCON3 <Enter>
- Insert Disk 2 in drive A.
- At the A: prompt, type the following:
COPY 302PATCH.RTP C:\FALCON3 <Enter>
COPY MIGPAT2.RTP C:\FALCON3 <Enter>
COPY 302ARM.RTP C:\FALCON3\ARMSDATA <Enter>
COPY MIGMUSIC.RTP C:\FALCON3\MUSIC <Enter>
- Insert Disk 3 in drive A.
- At the A: prompt, type the following:
COPY MIGPAT1.RTP C:\FALCON3 <Enter>
COPY MIGPAT3.RTP C:\FALCON3 <Enter>
C:\FALCON3 <Enter>
- You will now be at a C: or C:\FALCON3 prompt. Type
the following to start the MiG-29 install:
GOPATCH <Enter>

However typing gopatch at the end simply causes it to state it can not find the patch.rtp file. So I attempted to run the gopatch on each rtp file I copied over (ex: gopatch epatch.rtp)

This worked on about half the files. However MIGPAT1, MIGPAT2, and MIGPAT3 don't seem to unpack.

I also tried gopatch with the /noi commands I saw it try to use in the installer, but I got the same issue. My guess is the files have to be combined somehow before it can be run.

also worth noting, is even after extracting the eptach and 302patch files, checkver still reports Falcon as being version 3.0. So that makes me think the update isn't applying properly either.

Last edited by exofreeze on 2012-08-15, 13:43. Edited 1 time in total.

Reply 1 of 5, by exofreeze

User metadata
Rank Member
Rank
Member

Just a note that I am still working on trying to figure this out, but have had no luck so far.

Reply 2 of 5, by exofreeze

User metadata
Rank Member
Rank
Member

I finally solved this problem.

After copying each file to the proper directory, I simply ran gopatch by itself. It then prompts for the name of the patch file.

I did this for each file.

by typing the name of the patch file *after* gopatch on the same command line, it refused to extract half the files properly.

I also had the cputype set to 386_prefetch this time. I'm not sure if that was why it worked this time or not, but it sure didn't hurt.

Reply 3 of 5, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

I applaud your stubborn testing of games with DOSBox 😀
Are you "recording" your (or Ripsaws 😀) findings in the wiki or in the compatibility list?

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 4 of 5, by exofreeze

User metadata
Rank Member
Rank
Member

I had been documenting elsewhere, however your right, I ought to document here as well. I will have to pull up a list of all my topics and make sure the info gets copied over to the games respective compatibility page.