Creb

Don't wanna let you down,but I am sure it doesn't work(2CD Version) on my X64.I wonder if there is someone else who have tested it on win7x64.
In fact,it doesn't matter as Ion(Nvidia 9400M) doesn't cause much compatible trouble during playing.

I run windower and Torment just fine on win7x64.

Anyways, just wanted to thank Ghostdog for this. Playing Torment again after a decade or so was unbearable without this fix.

Also, I use autohotkey to remove the window border/title so you don't have to play around with the resolution to accommodate your taskbar. Aka 'full screen windowed mode' as found in modern games. The script is:

^f::
WinSet, Style, -0xC40000, A
WinMove, A, , 0, 0, 1920, 1200
;WinActivate, A
return

Once you load it, pressing cntrl + f will work the magic. Replace 1920, 1200 with whatever your desktop resolution is.

Now, the only issue(s) I've had are a few crashes when the game goes to load a cutscene. Sometimes it'll work if I delete the cache and restart the game with the last autosave, though I had one instance when you are leaving the the alley where your body was found to go to the lower ward where the cutscene trigger crashed about 10 times in a row before I gave up and ran it without windower. Coincidentally or not, I had no problem loading the cutscene. Of course I returned to using windower after this workaround so I could use spell effects without wanting to kill myself. ;p I have no idea if that was related to windower, but it was a strange, seemingly coincidental workaround, so I thought I'd mention it.

The other minor problem I have which is not related to windower at all (happens regardless of using it or not), is the rare and seemingly random crashing on zoning. Restarting and reloading one's last autosave works, though I had one incident in which I could reproduce this almost 100% of the time. If I zoned into the midwife's hut (after I had already zoned in and out once successfully; so basically every time I returned to turn in a quest), it would crash. However, one of those crashes didn't occur till a few seconds after successfully zoning. In that instance, I clicked on the midwife to initiate dialog and she ignored me. Several seconds later, it crashed. Whether this sheds any light on the cause of these zoning-related crashes, I don't know. I have read that crashes tend to be associated with the widescreen mod, but my understanding is that those are related to not starting a new game, which is not the case here. I'm assuming something gets corrupted randomly. Thank goodness for all the autosaving on zoning so you loose nothing.

Again, ghostdog, thanks for all your work!