Budge4

Sorry about spelling email address wrong in first post Taipan74.

Have you tried freeing up licence from main machine so that you have 1 usable licence then install game again to laptop. Licence game then Unlicence it again from the games Start Menu shortcut (from the Windows Start Button), after its unlicenced go to Windows add\remove programs and when you click on remove to uninstall TOW the Licence screen comes up again so you can click on unlicence game again. I had this happen where i lost a licence (hd crash) but unlicenseing the game 2 times (as written above) on comp where i lost it originally gave me both licences back. It may be worth a try. Otherwise guess you will have to email elicence@battlefront.com to try and retrieve lost licence. [ February 26, 2008, 02:48 AM: Message edited by: Budge4 ]

Lol, same here Stoppelhopser saves a lot of problems. Also put into a txt file and burnt to disk with the game.

Yea guess Man U will be wearing crash helmets and shouting Hut,Hut everytime they go on the pitch soon then.

I found with my system and a 7950gt that the 100 series nvidia drivers gave quite a few graphical probs with this and some other games i own so i went back to the 90 series drivers (93.71). Im sure the 100 series drivers are geared more towards the 8 series graphics cards. Guess some people probably run an Nvidia 7 series card and the 100 series drivers no problem, but on my sys with the 7950gt the 90 series drivers are definately better.

Have you tried installing from your digital download then Uber patch. Also noticed in another post that people were having probs with a corrupted Uber patch downloaded from strategy informer, maybe you have a corrupted patch? [ January 29, 2008, 12:34 PM: Message edited by: Budge4 ]

Glad you got it sorted out henriksultan, Can understand the problem you had with all the different latest versions from the different publishers, easy done. Happy Battles. ps: When the big 1.2gig patch comes out shortly get the kalypso one

Yea buy direct from this site, i bought the download copy of CMSF plus the hard copy which took about a week to arrive by air mail. Paradox version was in local shop at the time but i had read here about people (probably Meach) having problems with getting Paradox version running. Another plus with the BF version is that game patches generally are available days before the Paradox one gets released.

Otrex have you checked your "Data Execution Prevention" (DEP) settings, if its switched on which i think it is as default in 64 bit Vista Ultimate this can stop the game running by blocking programs running that use certain parts of computer memory.It seems to affect only certain programmes that try to use certain parts of memory, when i switch DEP on certain games i have still run ok but others dont, TOW was one that would'nt run. Check the TOW troubleshooting guide about DEP or do an internet search for DEP Vista. Think settings are in your windows system\maintenence section? Its a bit beyond me but know it can stop programs running. Had tried switching DEP on in my Xp pro 32 bit and it stopped TOW running until i added certain TOW executes into the DEP exceptions tab. Like i said above i think DEP is switched on as Default in 64 bit Vista for all programms (not just the vital windows progs) so that could be your problem. The DEP section in TOW troubleshooting guide tells you which Executes etc to add to the DEP exceptions tab if you can work out how to do it. Or better still turn DEP off if its possible in 64 bit Vista. [ January 03, 2008, 07:40 AM: Message edited by: Budge4 ]

Before you install patch henriksultan you say the game works ok, have you checked the game version at that stage (before patch), you may already have the latest version 1.3.0.56 (english version) and not need to patch it. If your TOW is in a different language you may already have latest version or you may be using the wrong patch also. [ January 03, 2008, 07:57 AM: Message edited by: Budge4 ]

Yea sure thats the right patch you've just got

Sounds like you have the wrong patch or something then seeing as the game worked before you patched it.

If your using xp runservice.exe is in your windows dir not the game dir. I just tried switching the DEP on and game would'nt run until both runservice.exe and tow.exe were added to DEP tab. If you have'nt DEP switched on its irrelevent anyway i guess. The tow2 file was apparently an error with early patch as far as i know, thats why it had to be renamed to elicen40.dll. If elicen40.dll is in your game dir it should be ok. My installation of game does'nt have the tow2 file in either but has the elicen40 one and game works fine. Does your towsetup.exe run ok, maybe its set a res or refresh rate to high that your monitor cant handle. [ January 02, 2008, 01:21 PM: Message edited by: Budge4 ]

Just a thought because someone else had a similar problem. They had turned on "Data Execution Prevention" for all programmes installed in windows (xp i think, but may be same in vista as well?) which stopped the game from running. Think once they added runservice.exe which is in c:\windows dir and tow.exe in your game dir to the DEP tab it worked ok. [ January 02, 2008, 12:36 PM: Message edited by: Budge4 ]

Ok will try that, thanks Rune. Budge4

Hi Would like some info from anyone at Battlefront please. The Giga-byte sata2 raid array crashed on my ga-p35-ds3r mb causing me to lose all data on hd's, i have just partitioned and set it up again but this time im trying the ich9r ports instead. At the time it crashed i had CMSF and TOW installed and licenced, is there anyway to get those licences back or are they gone for good. I have a written record of both game licence numbers (no email order conf now though) and still one licence left for each but obviously im a bit worried that if anything similar happens again i end up with both games being unusable. Both games have only ever been installed on the one same computer and were ordered direct from BF as download+hard copies. Thanks Budge4 [ December 21, 2007, 03:21 AM: Message edited by: Budge4 ]

Not all the bugs introduced in v1.05 of CMSF were known by Steve and Charles, the low wall line of sight being one of them that accidently crept into the patch code by mistake shortly before it was released. It has quite a big impact on the gameplay in CMSF when your units (troops and vehicles) cant fire over a 4 or 5ft wall. The low wall los was'nt a problem in earlier versions of the game and guess it will be fixed fairly quickly, seems sometimes fixing one bug can cause another so the longer they test the TOW patch the better it will probably be. Hopefully BF will release the patch when its good and ready and not before.

Take it 163.79 is a beta driver, not a lot you can say then really. Im using 169.21, also beta, works ok with CMSF but gives minor probs with other games. Dont think there will ever be a driver made that will work 100% with everything.

Thought it was more fun in v1.04 when you faced up headon to a tank only to find you had forgotten to get a missile. Holy Cr*p!! [ December 18, 2007, 05:42 AM: Message edited by: Budge4 ]

Try e-mailing support with details of cd-key you have, maybe they can help.

Seems to be the odd problem with infantry then, i was playing "Follow the Euphrates" battle and one man in a squad got sort of stuck on the left stone wall of the long avenue that leads up to the intersection, approx in area where set of 3 buildings are on the right (he was continually jumping over wall backwards and forwards) Someone else that posted earlier had units stuck in that set of 3 buildings too, he tried splitting units, tried all the different move commands, all to no avail. Dont think he tried shelling em though, friendly fire and all that lol.

Microsoft can release a directx update every couple of months and still call it 9.0c so BF can release updates and still call it 1.05 as far as im concerned, 1.051, 1.052 etc just gets too confusing.

When i gave order to assault the building that was next to the one i was in (no interconnecting doors but other buiding joined to one my squad was in)) i thought maybe the squad would exit out of the building they were in then assault into building next door through that buildings own door, but they would'nt move. Trying to explain it as best as i can, sorry if you dont understand what i mean.

I had a squad on the ground floor of an 8 storey building, gave them assault order to go into ground floor in 8 storey building that was joined to first one, they just got up then lay back down again, thought they might have gone out of door then into building to be assaulted but they did'nt. I then breached the wall between the 2 buildings and the assault order worked ok then. Seems like you have "not" to be inside of a building to give the assault order to enter another building or you have to have a direct route such as the breached wall or a door between them. The assault order does'nt seem to work if it means squad actually going outside of a building then assaulting back into another. Move out of the building then order assault on 2nd building and it works ok. [ December 16, 2007, 06:10 AM: Message edited by: Budge4 ]

Yep its the low wall los bug that apperently crept into the patch code shortly before release, BF are gonna address it in the next patch.