KOTOR 1+2: Vista Fix & Windows 7 Report

[Astrotoy7]

Im stickying this here to have a permanent reference to the KOTOR Vista fix. It has been around a few months, but has not made prolific progress at making the rounds...

 

Thank you to SD Nihil for the original heads up

 

In the tech area we quite often get queries about hardware etc from KOTOR fans querying a vista upgrade. This info will stay here for any Vista user wishing to find out about KOTOR and Vista.

 

Im glad I no longer have to tell people to dual boot or try figure out Linux and WINE

 

Ive so far tested K2 on my Vista 64 bit rig and all is working well. I will be testing K1 shortly.

 

Im not sure what limitations there are, or what bugs persist for the duration of the entire game. I will attempt a summary from what I glean from obsidian etc relevant threads. Feel free to report anything as you come across it.

 

The fix is a tiny file >> mss32.dll (372kb) HERE

-Cheers to Qliveur for the updated link

 

I invite others with Vista 32 bit to chime in as well if theyve given this a go.

 

Shame on those LFN members who knew this fix and didnt spread it around better!

 

* * *

 

Source: Post by RenegadeSniper7 at

[Tutorial]Original Team Gizka thread link

 

Here's are the instructions to save you the journey/if you are lazy

 

 

The instructions describe conditions where KOTOR1/2 is not installed on your Windows Vista system.

 

 

1. Insert the install disk.

 

2. Open up "computer" , right-click the disc drive and click "Explore", so you can have a poke around what is on the disc.

 

3. Find the file called setup.exe

>Right-click> select Properties.

>Click the tab labelled, "Compatibility". > Select, "run this program in compatibility mode for Windows XP Service Pack 2(SP2)"

 

Pic For Steps 3,4(and 9)

 

4. Go farther down and also select, "Run as Administrator". In order to install KotOR II, you require admin privileges for the duration of installation to start-up. Playing it without this causes failure to launch. (Nb. if you are already logged in as an admin, this option may be grayed out.)

 

5. Run setup.exe. Select continue, and install as you normally would.

 

6. Once it is installed, you'll need to fix the mss32.dll file > this is done by simply replacing it with the fixed one from the above link

 

7. Once that file is downloaded, place it in your KotOR II's root file directory, eg: C:\Program Files\LucasArts\SWKotOR2. (or wherever you have installed it)

 

When it says, "Move and replace", select that option. This successfully fixes the "KotOR II has stopped working" bug.

 

8. Almost done! Find or create a shortcut directly for swkotor2.exe. (or kotor.exe for K1 of course) This is different from the launcher file that automatically gets created.

 

The file is located in your root file, which is where you put the mss32.dll file.

 

This is as easy as right-clicking swkotor2.exe, clicking create shortcut. If windows says, "Windows cannot create a shortcut here, would you like on placed on your Desktop instead?", click yes.

 

9. Now, the last step!

>Right-click the swkotor2.exe shortcut you created and select Properties. >Click on compatibility , then select "Run this program in compatibility mode for Windows XP SP 2". and "Run as Administrator"(if not greyed out)

 

Good luck! I'll be back with my K1 results later, but if anyone else has had a go, please report.

 

mtfbwya

[Q]

Definitive Order of Installation and Fixes for the Disk Versions of KotOR 1 & 2 - NOT the Collection DVDs! (Also Works for Windows 7):

 

THIS SHOULD ALL BE DONE USING AN ADMINISTRATOR ACCOUNT TO AVOID ANY POTENTIAL PROBLEMS WITH PERMISSIONS. IT SHOULD ALSO BE DONE IN THE EXACT ORDER AS LAID OUT BELOW IN ORDER TO AVOID POTENTIAL PROBLEMS.

 

1) Start by updating DirectX. For those that haven't yet, it's a good idea to download and install the latest DirectX Redistributable Package available here. This will install a full version of DX9.0c alongside DX10 and DX11 that will not conflict with them in any way. Vista is supposed to provide backward-compatibility with DX9, but I think that it falls short is some areas and this will fix that. The link is for the June 2010 version, so be sure to check for the latest version before downloading. First-time installers are going to want to install the entire redistributable package. Just download the file, extract it to a temporary folder and run the .exe. You can then delete both the temporary folder and the file that you downloaded after installation is complete.

 

 

2) Install the game according to Astro's instructions in Post #1, but hold off on replacing the mss32.dll and also on making the shortcut until you have patched the game and replaced the swkotor.exe (or swkotor2.exe) with the version that has been updated by SecuROM.

 

 

3) Patch the game. This is NOT NECESSARY for, and should NOT be done with, the "Best of PC" version of KotOR 1. When patching either game to the latest version, download and use the manual patches instead of the auto-updaters (KotOR 1; KotOR 2) -Note that, while KotOR 1's patch is for all versions, non-US versions of KotOR 2 require one of the international patches, found here. The international update for KotOR 2 consists of two separate patches, and you will need to install both of them; first 1.0a, and then 1.0b. Using the wrong patch will screw up your game installation, so be sure about which version you have before applying it.. Once downloaded, right-click on them, select "Properties" and set them to XP SP2 compatibility mode just like Astro described for the setup.exe and the shortcut and then run them as an administrator. If you have them, you can also install the enhanced movie (only recommended for monitors with a vertical resolution of 1200 or higher; don't bother otherwise) and music files for KotOR 2 (available on the same site as the official patches) at this time.

 

 

4) Remove the "Read-Only" property from the entire game folder (default location: C:\Program Files\LucasArts\SWKotOR). Right-click on the folder, select "Properties", deselect "Read-Only", hit "Apply", select "Apply changes to this folder, subfolders and files" and hit OK. Windows may indicate that the folder is still read-only after doing this, but if you've done the above, it has indeed worked and doesn't need to be repeated. This is a necessary step for installation of the TSLRCM mod, but it also helps with some of the remaining steps in this guide.

 

 

5) This step is for running KotOR 2 on Vista. You don't need to do this if you're using Windows 7. Backup, move or rename the mss32.dll file in the main game folder. Then download the replacement mss32.dll found here and extract that archived file to the main game folder -This is NOT NECESSARY for KotOR 1.

 

 

6) This step is for Vista only. Download the SecuROM-updated .exe's. This is NOT NECESSARY for, and should NOT be done with, the "Best of PC" version of KotOR 1. Once again, these two files are for the US versions of KotOR 1&2:

 

For KotOR 1

For KotOR 2

 

Owners of non-US versions and those of you who are experiencing problems with the new .exe, such as its accusing you of using an emulator when you're actually using an original disc, need to go to SecuROM's website and jump through their hoops in order to get a working .exe. It shouldn't take more than a couple of days. After receiving it from SecuROM, anyone who wants to post a download link to one of the updated .exes for a non-US version may do so with my gratitude and I will add it to this guide. They are not as easy to find as the patches.

 

Extract the archived file to the main game folder after either renaming the old one or moving it elsewhere. Don't overwrite the old one. You may need it later. Then right-click on it, select "properties", then under the "compatibility" tab set it to run in XP SP2 compatibility mode as an administrator. While you're at it, it wouldn't hurt to set the launcher.exe and swconfig.exe files to run in XP SP2 compatibility mode as an administrator using the same method.

 

 

7) Now you can make the shortcut as instructed by Astro in Post #1.

 

 

8) Those with multi-core CPUs (which is just about everyone these days) need to set CPU affinity to a single core. Not doing so will cause the game to randomly crash. This can be done by modifying the game's shortcut to command Windows to automatically set affinity every time the game is launched:

It's possible to alter your shortcut to automatically launch an application with the affinity you want.

 

The command I have in my target box of the shortcut is:

 

C:\Windows\System32\cmd.exe /C start "SWKOTOR" /D "C:\Users\Public\Games\SWKotoR" /high /affinity 1 "C:\Users\Public\Games\SWKotoR\swkotor.exe"

 

Obviously you'd replace the directory I have my swkotor.exe file in with the one yours is in in both places in the above line.

 

So it's a shortcut to the cmd.exe that launches what follows as a command. The command actually being executed is the start command, and the start command is what allows you to pick what CPU(s) to use for executing the game. The affinity integer is a bit flag, with the least significant bit representing the first CPU and going up from there.

 

You need to run this shortcut as administrator as well.

 

The actual game executables will run in compatability mode/as administrator since you should have set those properties already if you followed the steps outlined in the second post.

 

Since it's a shortcut to the cmd.exe, the icon will be for cmd.exe. To change it to the swkotor icon you just open the properties for the shortcut, click on the change icon button, and browse to your swkotor.exe and select the icon to change it.

 

Obviously this will work for any old game that doesn't work well on multiple cores.

Note that Windows 7 seems to do this for KotOR 2 already without any modification, but not for KotOR 1.

 

*If the above does not work for whatever reason, you're going to have set affinity to a single CPU core manually every time you launch the game. Before launching the game, open Task Manager (right-click on the Taskbar at the bottom of Windows' desktop and select "Task Manager") and click on the "Processes" tab. Check the "Show processes for all users" box if it isn't already and then launch the game. Once you get to the game's main menu, hit the Windows key to get back to the desktop and look for the game's executable (swkotor2.exe) in the Task Manager under the "Processes" tab. When you find it, right click on it, select "set affinity" and uncheck every box but "CPU 0" and hit "OK". Once you've done that, just hit the game's icon in the Taskbar and you should be good to go. Remember that you'll have to set CPU affinity like this every time you launch the game.

 

 

9) It would appear that the classic "Dantooine lag fix" for ATI video cards is now required for BOTH ATI and Nvidia DX10 and DX11 cards, as well as for Intel integrated GPUs. This should be done with both games. It should also be done when using XP with a DX10 or DX11 card:

• First, figure out where the .ini is installed. Default is "C:\Program Files\Lucasarts\swkotor(2)\swkotor(2).ini". If its not in that location, then your going to have to do some searching around on the hard drive a bit.
  
• When you find it, just double-click on the file to open it in Notepad.
  
• Scroll down the file until you find the Graphics Options
  
• Under the last line ("last line" as in the last line of the list of entries under "Graphics Options", NOT the last line of "swkotor(2).ini), add "Disable Vertex Buffer Objects=1", without the quotes.
  
• Goto File, then Save.

If, for any reason, you want to disable the fix, simply change the "1" to a "0".

 

With KotOR 2 only, make sure that Fullscreen=1 and that the Width and Height values are the same and set to a resolution that the game actually supports (800x600, 1024x768, 1280x768, 1280x960, 1280x1024 or 1600x1200) under both "Display Options" and "Graphics Options" in the "swkotor2.ini" file. After applying the changes, save and exit then go back into the file to make sure that the changes were saved. If they weren't, move the swkotor.ini file to your desktop and apply the changes there. Save it, exit, go back in to check and see if the changes were applied, then move it back to the game's main folder.

 

 

10) Those of you with an Intel GPU need to open your Intel graphics driver's control panel and Click on "3D Options". Look for "Flipping Policy" and change it to "Blit". Note that you might have to download and install Intel's drivers instead of using the ones that shipped with your laptop for the Intel graphics driver control panel to be accessible. NOTE: The newest drivers don't have this option, so if you can't do it, don't worry about it.

 

How to open the graphics properties window

 

OpenGL settings guide

 

If the game still crashes right after character creation after completing the installation, try using the the original .exe instead of the one from SecuROM. If that doesn't work, there is a link in Step #6 that will allow you to contact SecuROM and request a new .exe.

 

 

11) If the game is crashing or exiting to the desktop whenever a movie tries to play, you may need to enable support for 640x480 resolution in your graphics driver control panel to allow movies to play.

 

 

12) If the game still won't load for whatever reason, it might be a good idea to disable the intro ad movies by renaming their files. This is also handy if you just don't want to sit through them. These are located in the "movies" folder, which is in the main game folder. The files in question are:

 

KotOR 1: biologo.bik; leclogo.bik; legal.bik

KotOR 2: leclogo.bik; legal.bik; ObsidianEnt.bik

 

In each case you can just change their file extension from "bik" to "bak" and they'll be skipped.

 

 

13) If you have an AMD/ATI video card and are still experiencing problems, here are a couple of things that you can do:

Hello,

 

first some facts about the setup:

 

o Win7 x64

o KoToR via steam (so the installation guide is useless)

o HD5770

o Catalyst 10.2

 

It's rather simple, really. The game had trouble locating the OpenGL driver and I got a atioglxx.dll exception.

 

I found the workaround at guru3d and the AMD forums: Put the atioglxx.dll from Catalyst 9.12 in the game folder. So far it works in windowed mode only, but I am glad it works at all.

 

Source: http://forums.amd.com/game/messageview.cfm?catid=279&threadid=128067&enterthread=y

Thread at guru3d: http://forums.guru3d.com/showthread.php?t=315893

 

Maybe you can work this into one of the guides.

 

Thanks,

Christian

I downloaded ATI System Tools (pretty sure he means ATI Tray Tools, here), created a game profile where I set Direct3d and OpenGL settings to Auto Balanced and it worked like a charm!

 

***************************************************************************************************************************************

ORIGINAL POST:

 

My God.

 

And here I had thought that you had already known about this and still couldn't get it to work. Good to hear that you got it working.

 

OK, first and foremost:

If you are using a no-CD crack for whatever reason, you do so at your own risk. It's not our fault that it's crashing the game, so STOP PESTERING US!

In other words:

If you're using a crack, DON'T EVEN BOTHER TRYING TO ASK US FOR HELP.

 

 

EDIT: We forgot about the SecuROM Vista fixes! Make sure that their properties are set to run in XP SP2 compatibility mode as an administrator.

 

For KotOR

 

For KotOR2

 

Those of you who are still experiencing problems with the new .exe, such as its accusing you of using an emulator when you're actually using an original disk need to go to SecuROM's website and jump through their hoops in order to get a working .exe. If you're not using an original disk, well, that's your problem.

 

 

EDIT#2 VERY IMPORTANT:

For those that haven't yet, it's a good idea to download and install the latest DirectX Redistributable Package available here. This will install a full version of DX9.0c alongside DX10 that will not conflict with DX10 in any way. This should help with any DirectX 9 compatibility issues which I believe are the heart of KotOR's problems with Vista. Vista is supposed to provide backward-compatibility with DX9, but I think that it falls short is some areas and this will fix that. The link is for the February 2010 version, so be sure to check for the latest version before downloading. First-time installers are going to want to install the entire redistributable package. Just download the file, extract it to a temporary folder and run the .exe. You can then delete both the temporary folder and the file that you downloaded after installation is complete.

 

 

EDIT#3 This is not Vista-related, but it is a common problem with modern multi-core systems. This should be done with BOTH GAMES. Setting CPU affinity for a multi-core CPU:

After starting the game, press Ctrl-Shift-Esc to bring up the task manager. Right-click "Knights of the Old Republic" under the applications list and select "Go to process." Right click on the highlighted process (probably something like kotor.exe) and select "Set Affinity..." In the dialog box that comes up, deselect all but one core. Then return to the game and see what happens ^/_\^

 

Just remember that you'll need to do this every time you start the game.

Note that Windows 7 seems to do this automatically, but it wouldn't hurt to check and make sure that it's actually doing it the first time that you launch the game after installing it.

 

 

EDIT #4 This is also not Vista-related, but it would appear that the classic "Dantooine lag fix" for ATI video cards is now required for BOTH ATI and Nvidia DX10 cards, as well as for Intel integrated GPUs. This should also be done with BOTH GAMES. It should also be done when using XP with a DX10 card:

• First, figure out where the .ini is installed. Default is "C:\Program Files\Lucasarts\swkotor(2)\swkotor(2).ini". If its not in that location, then your going to have to do some searching around on the hard drive a bit.
  
• When you find it, just double-click on the file to open it in Notepad.
  
• Scroll down the file until you find the Graphics Options
  
• Under the last line ("last line" as in the last line of the list of entries under "Graphics Options", NOT the last line of "swkotor(2).ini), add "Disable Vertex Buffer Objects=1", without the quotes.
  
• Goto File, then Save.

 

EDIT #5 OMG, PATCHING! I can't believe that I missed this one. When patching either game to the latest version, download and use the manual patches instead of the auto-updaters (TSL's is broken anyway, I believe ). Once downloaded, right-click on them, select "Properties" and set them to XP SP2 compatibility mode just like Astro described for the setup.exe and the shortcut and then run them as an administrator.

 

EDIT #6 If you have an Intel GPU:

1) Open your Intel graphics driver's control panel and Click on "3D Options". Look for "Flipping Policy" and change it to "Blit".

[Astrotoy7]

Hey Q It is good news indeed. Simply out of curiousity > I want to look into that .dll a bit more closely, to see what is actually going on, and what the fix actually did. Some sleepless googling ahead

 

I just shows you the discrepancy between what we think we know and what is actually going on There were so many reports of incompatible shader models etc, the launchers own config reports - many of us(including myself), after so many tries, believed it was a no go.

 

Some even hoped that W7 would fix it!

 

Im just amazed that this news didnt spread so well. Theres some LFN members at team gizka, that didnt seem fussed with spreading it like wildfire across a prominent SW KOTOR forum... ah well, now we know. No more telling people to dual boot or "stick to xp"

 

I shouldnt be surprised though. In the htpc world, clever peeps are always pulling off amazing unsupported feats in Windows Media Center via registry tweaks and plugins. Its good that similarly clever coder types decided tho have a proper go at this.

 

We are grateful to them for that

 

mtfbwya

[jrrtoken]

Oops. >_<

 

I completely forgot about this. I've known it for awhile, but RS7 deserves all of the credit. Might want to spread the news to The Work Bench too, Astro.

[Q]

I pretty sure that it's been at least mentioned in the Vista thread there.

[Astrotoy7]

lolz... and that mischievous miltiades... he's in that very team gizka thread

 

Ah well, its all there now.

 

Ive put in a request to the smods to do some type of mirroring magic across workbench and ahto from this thread.

 

mtfbwya

[Q]

Well, I'm pretty sure that the fix that got Vampire the Masquerade: Bloodlines to work on Vista was also an ms32.dll hack.

 

Speaking of hacks: were you aware that you can now run both KotORs in widescreen, and that it looks great?

[Astrotoy7]

Speaking of hacks: were you aware that you can now run both KotORs in widescreen, and that it looks great?

 

Thats not suprising. There are a few WS hacks out there. Definitely will check it out when I test K1. Alas no 1600p hack I imagine

 

mtfbwya

[stingerhs]

wow. and here i thought most everybody knew about this one, particularly the installation bit. good thread, though, for anybody that's still clueless.

[Astrotoy7]

yes, I thought you knew about this stinger, as you'd mentioned kotor on vista a few times.

 

Did you ever have any issues or bugs that raised there head as you played? Did you run the patches and all stayed OK??

 

It is amazing that it isnt all over the place, but we'll see to that Ive titled the thread in a way that will get search engines here too hopefully

 

mtfbwya

[Q]

Thats not suprising. There are a few WS hacks out there. Definitely will check it out when I test K1. Alas no 1600p hack I imagine

 

mtfbwya

I'm not sure about KotOR1, but the patcher I use for KotOR2 supports 1600P. You'll have to Google it though because it makes use of that-which-shall-remain-unnamed. The only problem is with the way Obsidian designed the HUD. It'll probably be HUGE at 1600P and there's no way to fix it. There are custom-sized HUDs for KotOR1 available here (as well as some breadcrumbs to that-which-shall-remain-unnamed) in the TUCE.

[Astrotoy7]

that-which-shall-remain-unnamed!

 

You mean "The Scottish Play"? Yes, it is bad luck to utter its name indeed

 

1600p kotor would be awesomez

 

EDIT: Just tried K1. Games starts nicely, but getting intermittent crashes with first few minutes of playing I havent applied any of the updates etc yet.

 

>> 2nd edit >> D'oh. Hadnt applied compatibility change to the kotor shortcut > all good now It would be good if I could follow my own instructions next time

 

mtfbwya

[SD Nihil]

In an effort to spread this info around I've made posts on the BioWare K1 Official Tech Support Forums, sent a pm to Kristy Kistic for her forums, and from the TG thread it mentions someone put a thread about this on Obsidian's forum. I hope they stickied it there too. Also, I saw on KOTORFiles n the K2 section Utilities>Patches section there is a file called K2 Vista Fix. It might help too. Thought I'd pass it along. Glad I was able to help the community.

 

As for the DirectX thing I saw recently that there is a DirectX10 for both XP and Vista now. And I'm just guessing that since with compatability mode that since it's emulating in XP SP2 with K2, that it must be emulating DirectX 10 as if it was running in XP SP2 mode.

[Astrotoy7]

The XP compatbility mode deployed in vista will ensure the DX9 layer is utilised for running KOTOR. There are no components of KOTOR that were designed with the DirectX 10 SDK.

 

DirectX 10 in XP sounds paradoxical, again since the OS has not been written to integrate DX 10 functionality. It can be a compatibilty layer at best, surely! (ie. Trick DX10 games into running in DX10 mode, but not utilising full effects)

 

I want to see screenies of Crysis with all the Dx10 atmospheric effects in XP, then i'll be convinced..!!

 

Looking more into the whole KOTOR compatibilty fix, the shader models once under question are catered for in the DX9 layer in Vista. The mss32.dll fix just makes sure the game can access it better. Im having a harder time finding out if it was engineered bu fans or merely yoinked from another title where the authors put some time into fixing it

 

@SD > The fix is outlined on obsidian forums HERE. It was posted in July 2008 so I dont feel too silly for not discovering it earlier!

 

D333 has stickied this thread at workbench too ive been told. Still, thanks for help spread the word !!

 

mtfbwya

[SD Nihil]

Actually there is a DirectX 10 for XP and other O/S's: http://blogs.zdnet.com/hardware/?p=370

 

I found it in a google search by simply typing in "DirectX 10 for XP". Also, is the fix on KOTORFiles: http://knightsoftheoldrepublic.filefront.com/file/TSL_Windows_Vista_Fix;85439 the same as the file located on the TG thread?Yes I'm happy at least the K1-2 Vista Fix at least was not just on TG too.

[Marius Fett]

Astro, do you know if any of the tools we use to mod KotOR work in 64-bit Vista too?

 

I know they work under 32-bit, but i'll be going 64 soon and would just like to know beforehand.

[SD Nihil]

Have you tried running those programs in compatibility mode?

[Astrotoy7]

Astro, do you know if any of the tools we use to mod KotOR work in 64-bit Vista too?

 

I know they work under 32-bit, but i'll be going 64 soon and would just like to know beforehand.

 

Not sure Marius, I dont use em. Best bet is to ask around at the Workbench

 

@SD.. until someone posts screenies of XP running a DX10 game with advanced lighting and specular effects on, it will always remain a hacked compatibility workaround(like the KOTOR Vista fix!). I have done a *brief* search for such screenies(aka proof) and got no joy

 

oh yes, and the fact that "DX10 for XP" doesnt appear on a Microsoft page should speak volumes

 

mtfbwya

[SD Nihil]

As for my other question, is the K2 Vista Fix locatd on the K2>Utilities>Patches section of KOTORFiles, is that fix file the same file as the file located on the TG thread?

[Q]

I'm too lazy to look, but if it's an Mss32.dll file, then yes.

[Marius Fett]

Not sure Marius, I dont use em. Best bet is to ask around at the Workbench

 

Right-o. Cheers.

[SD Nihil]

I've compared the two vista fix files located on KOTORFiles and the TG thread. They are the exact same file with the exact same file size. The file on KOTORFiles was posted on January 1st, 2008. The file on the TG thread was posted in July 08. So if anything was changed to the file the most recent would be the TG posted file. So just to be safe I'd get the file from the TG thread anyway.

 

I hope the TG thread on the Team Gizka forums gets stickied. I've just checked and the TG thread has been requested to be stickied. I hope it gets stickied.

 

Yes now we need to see if these mod tools work on Vista to mod K1-2. The game now works on Vista, but its a question about the tools. I'm not sure though that we'll be able to get someone to confirm that soon in that many that have KOTOR still have XP because before this fix that's what they had to use. So I'm just guessing most of the community is using XP and very few have a second computer with Vista. I could be wrong though. I hope so.

[stingerhs]

as far as i'm concerned with the game running on my system, it runs very well. the patches run fine as long as they have administrator rights and XP compatibility mode. and, yes, i can run both games, and i do have Vistax64.

 

and give it up for raw horsepower: despite running a Radeon, instead of my framerate dropping to unplayable levels on Dantooine in K1, it still runs a fairly smooth 30fps without me running the swkotor.ini fix.

[SD Nihil]

swkotor.ini fix? Also, so you set the HQ Music patch in compatibility mode, and the HQ Movies patch Part 1 in compatability mode, but what about the other 2-6 parts that are not executables? What about the mods that use the tsl patchers? Do you also have to run them in compatibility mode? I assume the file replacements and mod files dropping in to the overide and other direcoriesare no different?

 

Finally, on the Work Bench mirror version of this thread on the KOTOR section, I saw one individual who followed all the directions, but gave a very descriptive description of how it didn't work and what happend in getting this Vista fix to work. I've been thinking though. I may not know much about computer hardware, but all the people who've used the fix and it works must have something hardware in common. And the person who didn't work must have something different if it didn't work. This information might be helpful since the guy who didn't get the fix to work has a NVIDA card. For my computer I've been wanting a NVIDA since I don't want to deal with any issues. He has a NVIDA and I plan to too. I don't want to make a mistake when I do get my computer. So this info of knowing what not to get and what to get if there is a hardware compatibility issue with the Vista Fix and this I want to know. As well as everyone else would want to know too.

[Astrotoy7]

There is some specific tweaking that seems to pull it off some for some nvidia cards. I have the details and can post them here later. I havent checked the mirror universe ()thread but imagine its the same thing >> its all lifted from Obsidians forums anyway.

 

The one irritating thing with when people say "yo it dont work" is they often dont post their full specs, output rez and driver GPU driver version. These factors are vital for us trying to help out, and for others checking to see if they may have the same issue

 

Hence to practise what I preach:

 

K1 and K2 are working (with fixes) on this rig:

 

Vista x64 Ultimate with SP1

Shuttle SN27P2 /Propietary mainboard

AMD x2 6000+

3GB DDR2 RAM

EVGA 8800GTS 640MB running 180.8 beta drivers >1600p output via DVI-D

Realtek Hi def audio drivers ALC882

Mss32.dll fix and widescreen patch

DirectX November 2008

all in XP SP2 compat mode in an admin account

 

if you have it working too/or not >> post your specs !

 

mtfbwya