Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: nubbles526 on May 17, 2007, 01:33:26 pm
-
A few days ago, I bought a new comp with all the nice gfx cards and etc. It is a Vista Ultimate I really appreciate it. However, after trying to reinstall FS2, nothing happens. When I click the setup.exe, nothing happens. However, when I checked the task manager (under Processes) I see two processes which definetly associate with this installation:
csrstub.exe (Description: Allows lua to launch 16-bit applications. It's obvious because it FS2 setup.exe is a 16bit)
NTCDM.exe (Shows up after clicking the setup.exe)
I install via CD.
Does anyone have the same problem? Is there a solution?
Please let me know.
P.S. Please move this post to the appropriate section if this post is in the wrong location.
-
I was expecting to see a few more of these popping up. As you suspect it's a problem with running 16-bit applications in vista that is scuppering you.
To be honest I'm not certain what the best solution is. If you still have the old PC then I'd suggest networking them/yanking out the old HD and sticking it in the new PC. Then all you have to do is click on the launcher or move the files to your new HD (Or just move the retail files. I can give you a list of what you need if you want).
-
ok you could try setting the setup.exe file on your computer to run as Windows XP or maybe even Windows 98 (compability modes) dont know if this will solve the problem with 16-bit program but for some other old games this worked for me.
/Dice
-
ok you could try setting the setup.exe file on your computer to run as Windows XP or maybe even Windows 98 (compability modes) dont know if this will solve the problem with 16-bit program but for some other old games this worked for me.
/Dice
This is pure speculation, but I'd reckon not. In Windows XP Professional x64 Edition, Microsoft completely removed 16-bit support bar running a VM. I think the reason was something like "at some point, you've got to move on."
-
If you can extract .cab files, you should be able to get a lot of the data off of the disks. That should save you a lot of bandwidth.
-
In Windows XP Professional x64 Edition, Microsoft completely removed 16-bit support bar running a VM. I think the reason was something like "at some point, you've got to move on."
...which is simply because they want people to get new stuff and not to play old games over and over.
We don't actually *need* to move on, the corporates need us to "move on". Some choose to make better new stuff, some choose to prohibit the use of old stuff. I would prefer the former, but obviously the corporates prefer the latter by default because it costs a lot less, as they don't actually need to improve their products, the hardware improvements take care of making them appear cooler and better. :rolleyes:
But anyhow, Turey's suggestion of extracting the information from the installation disks is one choice and probably theoretically the simplest, but not necessarily easiest. Easiest would probably be downloading a readily installed version of FS2_Open, like the one in ShivanSPS' torrent, but that's a big download, something like 1.5 GB IIRC...
If you go for extracting the data from the disks and doing a manual installation, I think 7-zip is able to extract cab files for example.
-
But anyhow, Turey's suggestion of extracting the information from the installation disks is one choice and probably theoretically the simplest, but not necessarily easiest. Easiest would probably be downloading a readily installed version of FS2_Open, like the one in ShivanSPS' torrent, but that's a big download, something like 1.5 GB IIRC...
If you go for extracting the data from the disks and doing a manual installation, I think 7-zip is able to extract cab files for example.
Certainly, but from a bandwidth standpoint, the best way to do it would probably be to copy all the .vp files (inside the .cab files, IIRC) from the disks into C:\Games\FreeSpace2\, then follow the instructions for installing over retail FS2 here (http://www.hard-light.net/forums/index.php/topic,47045.0.html), ignoring the first step under "Retail Install" where it tells you to install from disks.
-
As I had posted in another thread, I have Freesapce SCP installed and runing under Vista Ulitmate Edition with no issues at.
You can have my exact install for your own by downloading the Freespace SCP DVD or the Freespace SCP Installer from the links in my sig :)
and don't forget the patch ;)
hip63 :p
-
I think I have to trash the CD, they are useless on my Vista. I just use Turey's Installation instead.
Thanks for your advice, at least it did teach me something more about computers
-
use a dual boot?
-
Turey's online installation is meant for upgrading retail FS2 to FS2_Open.
EDIT: Old information, scratch that. Sorry. But if you still want to use the CD's, the rest of my message should work all right... at the very least, it will reduce the run time of the online installer, bu the amount of the Retail stuff included in the download.
The CD's are not useless for you, you just have to do manually what the installer executable would be normally doing - that is, opening the data*.cab files on the disks, extracting the content, and saving it into a directory. It probably isn't as hard as it may sound, although I have never had to do it.
The directory/file structure is pretty in a functional FS2 install. On most basic level, you can just find the following files from the CD's:
root_fs2.vp
smarty_fs2.vp
sparky_fs2.vp
sparky_hi_fs2.vp
stu_fs2.vp
tango1_fs2.vp
tango2_fs2.vp
tango3_fs2.vp
warble_fs2.vp
I don't know what *.cab files contain these files, but you should find the data<number>.cab files on the CD's root directory, and a program named 7-zip (http://www.7-zip.org/) says it's able to unpac data from *.cab files, and it's jolly useful utility anyway so grab it anyway. :)
Once you find the files in the list form those pesky cabinet files, copy-paste these files into Freespace2 directory that you have created.
*
After this, to confirm compatibility with your system, download and install FS2_Open Launcher and executable - current versions for Launcher is 5.5a and executable is version 3.6.9, they are found on this thread (http://www.hard-light.net/forums/index.php/topic,44291.0.html) in an archive file (http://fs2source.warpcore.org/exes/3.6.9.rar)... simply extract the Launcher.exe and fs2_open_3_6_9.exe to your newly created Freespace2 directory.
You also need to take care that you have latest OpenAL (http://developer.creative.com/articles/article.asp?cat=1&sbcat=31&top=38&aid=46) installed and have no residual files on your system (unlikely, since you're running Vista, but you never know)... the specific files are nvopenal.dll and some other file, but those only become relevant if the game doesn't work after installing latest (version 1.1) OpenAL from the link.
Now, believe it or not, you actually should have all you need to start playing FS2 with the FS2_Open engine as far as file structure and required other stuff go... with retail graphics at this stage, however. That is where Turey's installer comes in more than handy if you don't want to set everything manually (which is also a viable option, since installing mod directories to FS2 is really easy and teaches a lot of how the game works...)
Since you are running Vista, though, you will need to make sure that you make the Freespace2 directory fully open, like in traditional Windows style, so that users (and executables run by users) have read, write and execute permissions to the directory. Otherwise, there will be problems with stuff like saving a pilot file and soforth, which makes it impossible to get past the sign in screen.
Once you have taken care of this nuisance, start the Launcher.exe. Select thefs2_open_3_6_9.exe file to be executed when you press run, then get yourself to "Video" tab and set rendering device to OpenGL, colour depth preferably to the same as your desktop resolution (32 bit depth most likely by default), and you may as well set the anisothropic filtering to 16x, most of the current graphics cards can afford it easily.
Now you're ready to hit the Run button for the first time. Do so. You should be prompted to write a callsign. Do so. When you do this, the game creates a config file and a directory named "data" onto your Freespace2 directory. This directory contains all the pilot files and caches and stuff, so usually you should just let it be and commit possible modifications via mod directories.
Fire up the first mission of the campaign, just to make sure graphics and sounds and everything works all right at this stage. If it does, great, you should have no problems with improved graphics since you are already using the FS2_Open engine. If it doesn't work... well, troubleshooting ahead.
Assuming everything works fine, you may now quit the game and run Turey's online installer at this time. This utility will automagically download and install latest MediaVP files and quite a deal of mods as well, as long as you have a functional install directory as a basis, which you should now have assuming you didn't have any unforeseen difficulties with hardware acceleration or drivers or stuff. Since it's Vista, these really are pretty much that, unforeseen. :ick:
* I am not certain, you need to ask this from Turey, but it is possible that he has already implemented the OpenAL set-up phase to his online installer. In this case, you would be able to run the online installer immediately after pasting the retail VP's to Freespace2 directory.
I would prefer more manual approach since it gives a better picture of what's going on, and installing FS2_Open really isn't that complex ordeal after all. After doing it manually you will have much easier time troubleshooting later when problems occur...
Dual boot is certainly a possibility and seeing how Vista is kinda raw at the moment with especially device drivers being partially non-functional, having a dual-bootable system is kinda sensible as of now... but just to make one game to work it's like killing mosquitoes with a 155 mm field artillery howizer... It may work, but it also flattens a lot of forest and other stuff where it hits. :p
Godspeed, pilot. :D
-
Turey's online installation is meant for upgrading retail FS2 to FS2_Open.
Ahm....no? That's the old version you're thinking about. The one in my sig does that just fine. (Installs everything you need.)
-
Thanks for correction. Post edited accordingly. :)
-
Since I got Vista intalled on my new spec, I didn't intall Fs 2 within the original CDs. Instead, I copy/paste all my Freespace 2 folder (SCP included with other mods) and that's all. SCP work great, so, you don't really need to intall Freespace 2. Since, It doesn't need to be in your windows register to be running.
-
The directory/file structure is pretty in a functional FS2 install. On most basic level, you can just find the following files from the CD's:
root_fs2.vp
smarty_fs2.vp
sparky_fs2.vp
sparky_hi_fs2.vp
stu_fs2.vp
tango1_fs2.vp
tango2_fs2.vp
tango3_fs2.vp
warble_fs2.vp
Grrr...have everything BUT stu_fs2.vp!!! $^%$#^@ :mad: :hopping:
-
ok you could try setting the setup.exe file on your computer to run as Windows XP or maybe even Windows 98 (compability modes) dont know if this will solve the problem with 16-bit program but for some other old games this worked for me.
/Dice
This is pure speculation, but I'd reckon not. In Windows XP Professional x64 Edition, Microsoft completely removed 16-bit support bar running a VM. I think the reason was something like "at some point, you've got to move on."
I don't like the way that sounded at all... :doubt: I haven't been impressed by a single new game release other than the coming UT3 or Starcraft II.
What was that one space simulator called...engine's a bit like X3: Reunion's...Infinity: Quest for Earth?
I think that's it...Command And Conquer 3 actually looks pretty cool for a change.
I'm just three oranges short of a basket when it comes to new games. :doubt: Get rid of the ability to play older games and I'd probably turn into one of those MySpace obsessed freaks... :lol: