| 21-02-2014 06:13 PM | |||
| Maxaxle |
Okay, so I'm having a *slight* problem with the game (Direct3D version). The game works fine on my old laptop, but the graphics go crazy if I run it on my much newer computer. Newer computer: -WinXP with latest updates -Newer dual-core processor (nothing impressive but hardly slow) -4? 8? GB of RAM -NOT using any emulators; Glide version works perfectly when I use nGlide but the Direct3D version's graphics go haywire, and the menu screens flicker. Using winThrottle has zero effect. Laptop: -WinXP with latest updates -Pentium 4 processor -512? MB of RAM -NOT using any emulators; Glide version works at a decent framerate but with some mild gameplay lag, and the Direct3D version works perfectly. Normally I'd be happy with the game as-is, but the Direct3D version seems prettier (or at least the shields are), and the Glide version restricts access to Championship mode for some reason (copy protection measure?). EDIT: I also seem to be incapable of playing a game between the two computers, even though they're both behind the same router and use 192.168.1.XXX IP addresses. Connecting both to, say, 192.168.1.001, and setting up one as the server and the other as the client doesn't allow the client to find the server. |
||
| 21-05-2011 02:24 PM | |||
| Japo | Ah OK I didn't know it, I haven't tested the game. | ||
| 21-05-2011 12:40 PM | |||
| Luchsen |
Quote:
|
||
| 20-05-2011 10:38 PM | |||
| Japo |
Yes we could make the script ask the user, although it would make more sense asking about the drive letter. If you think about it, now that x64 is slowly but surely replacing the legacy x86 (32-bit), quite many people will be using the former, without ever knowing the existence of the two. By the way, the script detects a CD drive, but if there are more than one, or for example the game CD is in a virtual mount different from the real CD, it may not work. It could be modified to look for a file that we know should be in the game CD. I don't know either right off the bat how to detect the OS architecture, with a cmd script only that is. There's a Windows environment variable %PROCESSOR_ARCHITECTURE% that must inform about the hardware, but oddly enough there's none that informs about the OS, which is the only thing that matters to us (since x64 processors can have a x86 OS installed, and the long mode remains always unused; actually most PC processors are x64 since long ago, even if most of them are running x86 OSes). There's also for example a %ProgramFiles(x86)% environment variable along with the usual %ProgramFiles%, that exists on a x64 Windows but not in a x86 one. But on the other hand there's no harm in writing both keys. On x86 systems the "WOW6432node" name has no special meaning--it's as if there was a program or software manufacturer named like that. Keys in that particular part of the registry are read only by the same programs that write them, so it would just stay there with no effect on the system. On x64 systems only one key is necessary, the one in HKLM\SW\WOW6432node\, because the game is a x86 program (actually from a time where x64 didn't even exist), that is run though WOW64 and sees the registry through the redirection described in the Microsoft KB article. If there were both x86 and x64 versions of the same program, each would need only one of the two registry keys. Because the purpose of this redirection and the specially named "WOW6432node" parent key (as well as the %ProgramFiles% and %ProgramFiles(x86)% folders) is to allow x86 (32-bit) and x64 (64-bit) versions of the same program to be installed on the same x64 OS side by side, and having independent registry keys. |
||
| 20-05-2011 11:59 AM | |||
| GTX2GvO |
Quote:
Quote:
"Do you have a 64bit or 32bit OS?" Also I think writing both values on a 32bit system can cause trouble. (since 32bit systems don't do 64bit) While on 64bit systems both fields are necessary to be filled if I'm correct. |
||
| 20-05-2011 03:03 AM | |||
| _r.u.s.s. | dude, i have no idea how to figure out if someone is running 64 bit. can you try it? or just write both of the registries on every system? my upload sucks and re-uploading would take another massive amount of time | ||
| 19-05-2011 06:38 PM | |||
| Japo |
 (Russ you know what to do. :P You can make the script guess if the OS is x86 or x64, although writing both registry keys on every system, x86 or x64, is perfectly fine too.) |
||
| 19-05-2011 03:15 PM | |||
| Sgt_V3n0m |
Quote:
 IT WORKS!! Thanks man, finally I get to play my favourite racing game when I was a child.
|
||
| 19-05-2011 12:14 PM | |||
| Unregistered2000k |
Quote:
Yes it works perfect now, under Win7 64Bit. thx, thx. |
||
| 19-05-2011 09:41 AM | |||
| Japo |
Quote:
Code:
HKEY_LOCAL_MACHINE\SOFTWARE\Psygnosis\Rollcage\Installer Code:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Psygnosis\Rollcage\Installer Please report back whether it works or not, so we add this to the script. |
||
| This thread has more than 10 replies. Click here to review the whole thread. | |||
