|
|||||||
| Memberlist | Forum Rules | Search | Today's Posts | Mark Forums Read |
| Search Forums: | Click here to use Advanced Search |
Topic Review (Newest First)
|
|
|||||||
| Memberlist | Forum Rules | Search | Today's Posts | Mark Forums Read |
| Search Forums: | Click here to use Advanced Search |
|
Topic Review (Newest First)
|
| 18-02-2015 07:00 PM | ||
| Japo | Well you seem to be right, I've checked in my normal Windows 8.1. I never noticed because 32-bit processes can see both system32 and syswow64, and you can seem to go to system32 as well as syswow64, by those separate names; but in both cases you get the same files, from syswow64. Sneaky. I thought it was only when loading DLLs or relying on environment variables or in the registry. Thanks for the info. | |
| 18-02-2015 04:41 AM | ||
| Smiling Spectre |
Quote:
 For servers, any 32-bit process automatically redirected to syswow64 in any case when it tried to access system32. I can _try_ to access system32, but in result will land in syswow64 silently. It was very confusing for me when I tried 32-bit file managers on win64, because I never was able to found 'hosts' (that exists only in real system32, of course). |
|
| 17-02-2015 07:04 PM | ||
| Japo |
On 64-bit Windows, DLLs for 32-bit processes are loaded from syswow64 instead of system32; system32 is (despite the name) for 64-bit DLLs. It's confusing but considering history it makes some sense :P Of course you can see both directories if you look via their actual paths, but that's unrelated. 32-bit processes can see true system32 too. But when linking to a DLL it's in principle Windows who finds the DLL file from a name without path. All this applies to native C DLLs. It's also possible to place a DLL in the same folder as the program that needs it, which also allows for different programs that use incompatible versions of the same DLL name. This applies to .NET DLLs as well as C ones, but not COM ones. Anyway neither COM nor .NET DLLs go in the Windows system directory for global use, only C ones. |
|
| 17-02-2015 07:08 AM | ||
| Smiling Spectre |
Oh, any 32-bit program will not ever see "true" system32 anyway. (Hmm, but Explorer is 64 by default, so it will see it right. Ok, you are right then.) |
|
| 13-02-2015 10:34 PM | ||
| Japo | On 64-bit Windows, put the DLLs in c:\windows\syswow64\ (not system32) | |
| 13-02-2015 12:05 AM | ||
| The Fifth Horseman |
A copy of the WinG libraries - along with their installer - can be found on our Programs page: http://www.abandonia.com/en/programs Guaranteed to work on 32-bit Windows versions up to XP; can't vouch for Vista and 7, never tried it with them. |
|
| 12-02-2015 11:19 AM | ||
| Unregistered2 |
Allied General on Windows XP Hi all, just copy install\wing\Wing32.dll from the CD to windows\System32. Then set winXP to 256 colors. And then AG\AG.exe should work. Works flawless here on VirtualBox. You don't have to install it. Bye, M. Quote:
|
|
| 19-03-2007 02:16 PM | ||
| The Fifth Horseman |
Using Virtual PC 2004 might just about solve the problem. There are quite a few 9x games that won't work with XP. |
|
| 17-03-2007 11:35 PM | ||
| _r.u.s.s. | Oh you can use some virtual maschine for that, if you dont have another computer | |
| 17-03-2007 11:22 PM | ||
| Sebatianos |
I had a similar problem with Allied General... Turns out I can't install it in WinXP. If I do, it won't work. But if I install it with Win9x and then just copy all the files to WinXP it works. This would mean you'd need a Win9x computer to install the game on hard-disk and then copy the installed files (and probably edit a few of them - if there are different drives, different sound and video settings), but it might do the trick (I can't guarantee though). |
|
| This thread has more than 10 replies. Click here to review the whole thread. | ||
