VOGONS

TIE Fighter CD Setup Walkthrough (Incomplete)

Topic actions

First post, by Chris Pickett

Posted on 
User metadata

Hi,

Before anyone reads this ... I think the file I have is the TIE Fighter Collector's CD, with an executable named TIE.exe -- and from

http://www.minos.net/~sco/guide/tie-tech.html#xp

it seems that the X-Wing Collector's Edition with an executable named TIE95.exe is the better product. Not sure if it makes a difference to getting VESA support working though (my primary problem), if someone has that version and could let me know. There's so many different X-Wing / Tie Fighter packages / box sets / extensions out there, it's really hard to determine what people are talking about.

My current system:

Motherboard - IBM Thinkpad A20p 26296VU
Intel Pentium III 750 MHz
384Mb RAM
ATI Mobility Rage 128 Pro (or some similar combination of those tokens) - 16Mb
Crystal SoundFusion sound card (generic laptop crap)
W2K SP3 with all pre-SP4 fixes
Thrustmaster Firestorm Dual Power -- an AMAZING Gamepad!!! In case you need a new one.

I searched all the threads with either "tie fighter" or "x-wing" in them, and made some progress towards my ultimate goal: getting the TIE Fighter Collector's CD Edition to work in W2K with sound and VESA
support.

I thought it would be good to have a detailed walkthrough on how to
get TIE Fighter working, since it's such a great game and since
VDMSound is such a nice program. That's why a started a separate
thread -- to consolidate all the current info in one place.
So far, this walkthrough is incomplete, feel free to edit this post or
whatever. It also shows you exactly what I did and should help you to
exactly reproduce my current problem. Unfortunately, I got tired
towards the end of writing this, so it might not be so detailed at the
end. That can always be fixed.

I'm assuming you know how to use Google for something so easy to find
that it doesn't need it's own link.

1. Get or make a Tie Fighter CD.

You can find the Tie Fighter CD on kazaa pretty easily (it's about 260
megs); that's what I'm using because although I can buy the
collector's edition off somebody, I want it to work first (otherwise, what's the point?). If you
already own it, you're done.

Once you have the executable, extract it into a directory on your
harddrive. Use WinISO or some other tool to compile the files into an ISO
image (you can probably do this with just about any burner app in fact, I
just like WinISO). I named the volume TIEFIGHTER and it worked, not sure about
other names (depends on copy protection actually used).

Now, you can burn the ISO to a CD, but if you want better / less noisy
performance, use Daemon-Tools to mount the image. Either way, you're
now ready to install Tie Fighter.

2. Install Tie Fighter.

Put the CD in either in real life or with Daemon-Tools, and the
autorun installer should start. Use the maximum install (90 Mb) and
choose C:\TIECD (the default) as the installation directory. If you
choose another drive, you'll run into problems -- even copying the
TIE.CD file from C:\ to the root of whatever partition you install to
won't help (at least when I tried). Another directory is probably
fine on C:\ as well.

Don't worry about the sound card options for now, just quit after the
installation.

3. Update Tie Fighter.

LucasArts has a couple of updates available on their website.

http://support.lucasarts.com/patches/tie.htm

ftp://ftp.lucasarts.com/patches/pc/tiecdjoy.exe
ftp://ftp.lucasarts.com/patches/pc/tiesnd.exe

Save these into C:\TIECD and run them from there using the command
prompt or Explorer. WinZip will prompt you to unzip into the current
directory ... just hit OK.

I'm not sure if these patches make a difference, but I always try to
apply as many patches as possible because it's rare for something
*not* to work after an upgrade.

4. Install VDMSound + updates.

Refer to the directions in this post:

showthread.php?threadid=1226

a) install VDMSound 2.0.4 using the installer. choose 8 character
directory names with no spaces on C: for the install directory.
b) unzip vdms_update.zip, and copy the update files into the
VDMSound directory.
c) replace the launchpad DLL with version 1.0.0.9d. Uninstall
LaunchPad if you already have it, and reinstall.

Just look for vdms_update.zip posted lower down. However, I don't
think this zip includes the latest launchpad (1.0.0.9d) so you'll have
to get that from the top of the thread.

By the way ... are you guys making an updated installer? Also, why
not include LaunchPad in the installer? Off topic, I know. I think
it would be really helpful if all updates were released on SourceForge
as soon as they were available ... generally, people assume that a
project's "files" page has the latest and greatest, even if unstable.
It took me quite a bit of work to find all the updates and apply the patches.

5. Configure TIE Fighter.

Go into a command prompt and run dosdrv.exe or use LaunchPad -
whatever - and then run C:\TIECD\INSTALL.EXE. Go into the advanced
sound configuration menu and select General Midi for the music and
SB16 for the sound (choose default settings). Test it out -- you
should hear something. Now if you run the game, you should hear great
sound and be able to use your joystick too. I read in one of the
forums and on several other websites that the CD version requires a
joystick, so you're probably out of luck if you don't have one at
all. See 7e) below for a possible way to get your joystick
recognized, but I don't think this is necessary with VDMSound.

6. MY TWO BIG PROBLEMS:

a) I can't get VESA support working. I tried NOLFB.zip, enabling VESA
support from LaunchPad, and using UNIVBE that comes with Tie Fighter.
Nothing worked. If I choose the 640x480 resolution in the game, I get
a scrambled mess when I enter a flight scenario.
Note: if you encounter this problem, hit Q and then press spacebar (at
least in the training missions) to leave the mission. Then press ESC
to change the game options to use 320x240. If you hit CTRL-ALT-DEL, you'll
probably end up having to reboot.

b) I can't get Tie Fighter to recognize the second stick on my
gamepad, and so I have to program the throttle buttons manually. This
isn't actually such a big problem, but it's still annoying. Is it a
problem with VDMSound? Are there other games that require 4 joystick
axes I can test this with? How many axes does VDMSound actually
support? I know SoundFX supports 4, but it costs $$$. I tried using the different options from LaunchPad, but I get errors in "joy3.map" when I select single joystick with 4 axes. This can be fixed (sort of) by replacing the offending "T" in joy3.map with a "Z". A simple typo I suppose.

I find that if I turn *off* the analog sticks and just use the D-pad, the game runs at perfect speed (there is a little button on my joystick just like there is on the psx dual shock controller to switch from analog to digital control and back), but if not, it is quite slow. Has anybody else noticed that analog joysticks slow down emulation but digital ones do not? I suspect that this is not a problem specific to TIE Fighter, I just don't have any other games right now to test it on.

7. Other things I played around with:

a) act26.exe, available from microsoft
-- interestingly, there is an entry in the database for
x-wing alliance, and apparently tie fighter CD uses the same graphics
engine. anybody able to do anything with this information? there's
also qfixapp.exe included with it, but I don't know what settings to
apply (see section e) below.

b) There are suggestions on getting X-Wing vs. Tie Fighter to work at:

http://www.imperialcommand.net/window1.htm

but when I try adding the "ishost" command after TIE.exe at a command
prompt, it doesn't make a difference. And I cannot run the other
executables. I think that fix is only for XvT (seems like it's a
multiplayer thing specifying that this instance is the host).

c) a guest called Rela said at:

showthread.php?threadid=81&highlight=tie+fighter

that they were able to get Tie Fighter to work with VESA support by
starting it from a full screen prompt, but that didn't work for me.
I'm having the same problem that swaaye was (but he was actually
having two problems, one sound, one VESA).

I tried the ALT-ENTER trick, but I still couldn't make it work.

d) Squish said at:

showthread.php?threadid=1089&highlight=tie+fighter

that he got TF to work after either moving TIE.CD to another drive or
reinstalling to C:\TIECD (never specified), but it was unclear whether
or not he got VESA support to work. My guess is not.

Also mentioned in this thread is NOLFB.zip from Ken Silverman's
website ... I got that, tried loading it after dosdrv.exe and before
tie.exe, but I still couldn't get VESA mode to work.

e) finally, at Totally Games, there's a Tie Fighter CD thread that
says it won't work with VESA support at all (yet I refuse to believe
this ... there must be _some_ way ...)

http://pub30.ezboard.com/fofficialtotallygame … picID=103.topic

However, they do give suggestions as to how to get the Joystick
recognized. Unfortunately, I think that VDMSound already provides
this recognition, and the suggested fix there actually makes the
problem worse for me (the music and game are slowed down). So I don't
recommend using QFixApp as they suggest in that thread, but you can
try it if you like.

One final thing you can try, if you want to run QFixApp but then use
VDMSound's dosdrv.exe, is to run QFixApp with the fixes you want on
CMD.exe (preferably a copy so you can make permanent changes). Then
any commands you execute from that prompt will have the fixes. This
was sort of addressed in:

showthread.php?threadid=204&highlight=tie+fighter

when discussing how to use programs that target an executable and then
run VDMSound. Incidentally, my Thustmaster ThrustMapper app that I
use to remap buttons is similar to the WingMan Profiler but I can get
it to work with VDMSound without any problem at all simply by pointing
it to the .vlp shortcut.

===================================

Anyway, by now you should have a pretty good idea of everything I've
tried. I cannot get VESA support to work (and I know it's worth the
result from all the descriptions I've read), and I can't get Tie
Fighter to recognize my second control stick (that I want to be the
throttle). However, the second problem is really minor because I can
program the buttons to get the same result. The Thrustmaster programming software (called Thrustmapper) is really great!

Hope you don't mind my long post ... hopefully I'll save a bunch of
time for somebody else trying to get Tie Fighter to work.

Cheers,
Chris Pickett

chris.pickett@NOSPAM.mail.mcgill.ca (remove the "NOSPAM.")

P.S. Please contribute any suggestions to get VESA support working!!! Thanks!

Last edited by Chris Pickett on 2003-03-25, 08:46. Edited 1 time in total.

Reply 1 of 25, by psz

Posted on 
User metadata
Rank Newbie
Rank
Newbie

TIE95.exe is for the Windows Version of TIE Fighter (I have this, and the Windows version of X-Wing). There are no VESA problems as this uses DirectX.

To get this (and many other LucasArts Windows9x programs) to run in 2k/XP, copy the DDHELP.DLL file from the CD into your windows\system or windows\system32 directory. Otherwise you'll keep getting errors that DirectX isn't installed.

Reply 2 of 25, by Snover

Posted on 
User metadata
Rank l33t++
Rank
l33t++

I would put it in the game's directory, not the system directory, so that you can easily delete it when it isn't needed anymore.

Yes, it’s my fault.

Reply 3 of 25, by Chris Pickett

Posted on 
User metadata

Thanks for the info! I guess I wasted some time writing all that, but maybe it'll help someone get the Windows version installed. First time I've seen this information *anywhere* on the internet (believe me, I've looked) -- people have reported getting VESA support to work, but there was no explanation.

Do you have the X-Wing Trilogy boxed set? If not, do you know if this contains the Windows versions? I'm pretty sure it does but I just want to make sure.

Does the game look awesome at a high resolution? Is it the answer to my hopes and dreams? I've had the diskette version forever and just somehow passed up the opportunity to get the Windows version in stores.

Cheers,
Chris

Reply 4 of 25, by psz

Posted on 
User metadata
Rank Newbie
Rank
Newbie

That is indeed the version I have (X-Wing, TIE-Fighter, all the add-ons, and the "Mini" version of XvT (called Flight School).

At one point I had put DDHelp in the game's directory, but then I realised I had close to 10 copies of the file on my hard drive (One for each old LucasArts game (and a couple of non-LA's)), I decided to put ONE copy in the system dir (Being in XP, this dir was nearly empty ANYWAY.)

Reply 5 of 25, by Chris Pickett

Posted on 
User metadata

Hi psz,

Can you confirm the exact contents of the box? Specifically, how many CD's, and what games are on what CD's. You said you only got X-Wing, Tie Fighter, and X-Wing vs. Tie Fighter missions (Flight School) ... did you get X-Wing Alliance as well? Did X-Wing Alliance take up two discs?

I've heard some people say there are 5 CD's, some people say there are 4. I really want to make sure I'm getting a complete set, but the person who owns the box doesn't know what they're talking about (they never really played them). The version I'm looking at has 4 CD's.

Thank-you very much,
Chris

=== edit ===

I think that you might have the yet another version that I didn't know about, without X-Wing Alliance in it. If so, never mind. Sigh.

==========

Reply 6 of 25, by Schadenfreude

Posted on 
User metadata
Rank Member
Rank
Member
psz wrote:

TIE95.exe is for the Windows Version of TIE Fighter (I have this, and the Windows version of X-Wing). There are no VESA problems as this uses DirectX.

To get this (and many other LucasArts Windows9x programs) to run in 2k/XP, copy the DDHELP.DLL file from the CD into your windows\system or windows\system32 directory. Otherwise you'll keep getting errors that DirectX isn't installed.

This will get the Hi-Res DirectX rendering working in TIE95.EXE and XWING95.EXE?

This is a long-outstanding service request:
showthread.php?threadid=12

Thanks for filling it, psz! But can it be done with the Application Compatibility Toolkit and not by copying DDHelp?

OT: Which do you prefer, the DirectX rendering? or the high-res VESA rendering?

Another thing to try is to us Rob Mueller's modified univbe.drv file with NoLFB, as mentioned in this post:
showthread.php?postid=11974#post11974

No guarantees it will work, though. It didn't work for Snover, with Constructor.

Reply 7 of 25, by psz

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Chris: No X-Wing Alliance. 2CDs. X-Wing and XvT:FS on one CD, and TIE Fighter on the other.

The compilation version I have predates that by probably a year at least. AFAIK any X-Wing/TIE Fighter collection (or "Collector's Edidtions" or whatever) SHOULD include the Win9x version. The versions that were sold at CompUSA for $10 a year ago were the Windows Versions.

Schadenfreude: I take it you mean the DDHelp? This worked for all three of the aforementioned games WITHOUT using Compat Mode (as well as with, obviously ;->) as well as Curse Of Monkey Island, and a handful of other games, of which I cannot remember 😄

IIRC, I had tried the compat modes only, and I don't recall it working with CoMI, but it *MAY* have with X-Wing.

The DDHelp workaround was told to me by a member of LucasArts' Tech Support who told me it was "unofficial and unsuported, but has been known to fix quite a few of our games with the new Windows 2000 Professional and Server Operating Systems." (Old email ;->)

After getting that respones after installing the (at the time) brand new Win2K and not being able to play Lucas Games, I more or less kept the DDHelp around at all times ;->

Personally, I prefer the Direct3D Accel. version to the software render. The mipmapping rocks, and the 3D Glasses make for some REALLY cool fly by's in XvT ;->

The oldest system I did this with for XvT/XW/TF was a K6-2 350, 128MB Ram, TNT2 Ultra. Should work on any new system. No sound driver issues, no VESA issues.

Reply 8 of 25, by Chris Pickett

Posted on 
User metadata

So ... for anyone else out there trying to get these games working, this is what I have gathered in my readings on the internet, and is a summary of this thread.

1) VDMSound will work with all TIE Fighter / X-Wing versions quite nicely, and joystick support is available as well.

2) You'll have a hard (if not impossible) time getting VESA support working on newer machines running NT/2K/XP ... I went so far as to download the free UNIVBE package from SciTech Display Doctor, and still couldn't fix anything. If your games do not come with DirectX, do not expect better than 320x240 resolution (with great sound!!!)

3) If your games come with DirectX, copy the DDHELP.DLL file into your game directory and everything should work smoothly at high resolutions. I'm not sure if you need VDMSound or not for the DirectX games ... psz? Feel free to edit this post.

Cheers,
Chris

P.S. I think you can close all other TIE Fighter / X-Wing threads, unless someone sees something in them that isn't mentioned here ... and if so, just move the information here.

Reply 9 of 25, by psz

Posted on 
User metadata
Rank Newbie
Rank
Newbie

VDMSound is not needed for any DirectX program, as DirectX is Windows Native, as is whatever program you are running. Since VDMSound is only for DOS programs, you don't need it :->

Reply 10 of 25, by Snover

Posted on 
User metadata
Rank l33t++
Rank
l33t++

I think the problem with that dude's UniVBE drivers is that since Windows NT does not allow direct access to hardware it can't get the DAC information and such, which is how the UniVBE driver is configured. I'm not 100% positive about this, though.

Yes, it’s my fault.

Reply 11 of 25, by Schadenfreude

Posted on 
User metadata
Rank Member
Rank
Member
Snover wrote:

I think the problem with that dude's UniVBE drivers is that since Windows NT does not allow direct access to hardware it can't get the DAC information and such, which is how the UniVBE driver is configured. I'm not 100% positive about this, though.

Who? Mr Mueller?

Reply 12 of 25, by Snover

Posted on 
User metadata
Rank l33t++
Rank
l33t++

I guess, if that's the guy that made those special UniVBE drivers. I'm not good with names, especially of people who I only know by visiting their website once 😜

Yes, it’s my fault.

Reply 13 of 25, by Schadenfreude

Posted on 
User metadata
Rank Member
Rank
Member

Then, I suppose if somenoe could come up with a way to force video output through the proper channels and hack a univbe.drv file like Rob has, then maybe we stand a chance of getting UNIVBE games working.

OTOH, quite a few UNIVBE games have documented or undocumented switches for not using VESA.

Reply 14 of 25, by Leolo

Posted on 
User metadata
Rank Member
Rank
Member

Hi,

To psz:

Man! You managed to get 3D Hardware acceleration working with "X-Wing Windows edition" under Windows 2000???

PLEASE TELL ME HOW!!!

Thank you.

Reply 15 of 25, by Chris Pickett

Posted on 
User metadata

Leolo: re-read this thread and you'll get X-Wing working ... 😀

If you guys want to play with UNIVBE, the SciTech Display Doctor latest release is a free download. You can do lots more stuff than you can with a configuration progam for some game. There's even a built-in option to turn off LFB, so I don't really think it's necessary to use third-party hacks.

Chris

Reply 16 of 25, by Leolo

Posted on 
User metadata
Rank Member
Rank
Member

Hi,

OK, I should have been a little more explanatory:

My problem is that the file DDHELP.DLL doesn't exist in my CD. The closest file found is DDHELP.EXE.

I have put that file in the game's folder, but 3D Hardware acceleration still doesn't work.

Where do you guys find the DDHELP.DLL file?

Thanks a lot.
Best regards.

Reply 17 of 25, by psz

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hrm. I must be getting blind in my old age (I am, afterall 23!), for it is indeed DDHELP.EXE, not DLL 😜 :->

Ok, Installing X-Wing now... Step by step...

(I had it uninstalled 😄)

Ok, I hit Next through the Choose Directory (I put it into c:\games\xwing instead of wherever IT chose)...

Waiting....

Waiting....

Still waiting...

Lil more waiting...

*kicks CD drive*

Waiting a tad more...

Ok... Leaving everything Checked (links to webistes, etc)
.

Hit next... Next again...

Don't wanna read the readme...

Calibrate joystick...

It asks to set up 3D card. Hit Yes. Select Primary Display Driver.
Hit Accept.

Message saying "Once in game, you have to select Use 3D Card". Hit ok.

Back to main menu. Copy the DDHELP.EXE to the XWING dir.

Hit Play X-Wing.

Once in game, hit Escape. Go to Flight Options. Click where it says 640x480x16bit. It'll change to 640x480x3D.

You're done!

Reply 18 of 25, by psz

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Note 1: Depending on your system, you MAY need the ACT for Win2K, on XP you may need to use Win9x mode or something. THIS IS NOT NEEDED FOR XvT OR TIE FIGHTER.

Note 2: Also, you may get the problem where you get into game, choose mission, and... Dump to the desktop. This seems to be based on DirectX version, Video Driver, and dumb pure luck. Sometimes it'll work in 8-bit, sometimes 16-bit, sometimes 3D...

Reply 19 of 25, by Mr Jim

Posted on 
User metadata

I like to steal games instead of paying the people that worked so hard to produce them. Since I'm an unregistered user I probably didn't see the clause in the user agreement that forbids these kinds of inquiries. That was silly of me and I promise I'll never ever do it ever again.

Go to top of page Go to top of page
Back to VDMSound General
Close window
Close window