Page 2 of 2

Re: I need to make better thread titles or: .86 doesn't work

Posted: 2009-06-20 16:32
by wuschel
Megagoth1702 wrote:I just have to give my 2 cents.
Every single dude talking about the pr.exe not working missed something, it's annoying.
Delete the old shortcuts, use the new one.
Delete 0.85 if you install 86 full version, core, then levels.
If you use the patch still delete the shortcuts, but leave the 0.85 pr.

I use the "crappy" Vista 64bit and did not have a single problem with anything.


People should read the manual (what I did to kill the torrent download time), also it was just a "wtf?" when I read the title and the first post. Really, with this attitude you won't go anywhere.
Exactly.

However, I have never seen an installer with a "filter"..

Re: I need to make better thread titles or: .86 doesn't work

Posted: 2009-06-20 16:38
by amazing_retard
WilsonPL wrote:"D:\Program Files\EA GAMES\Battlefield 2\mods\pr\pr.exe" +menu 1 +fullscreen 1 +restart +szx 1680 +szy 1050

lol don't put it in that part if your computer can't handle that resolution :)

Re: I need to make better thread titles or: .86 doesn't work

Posted: 2009-06-20 16:53
by LionEyez
Megagoth1702 wrote:I just have to give my 2 cents.
Every single dude talking about the pr.exe not working missed something, it's annoying.
Delete the old shortcuts, use the new one.
Delete 0.85 if you install 86 full version, core, then levels.
If you use the patch still delete the shortcuts, but leave the 0.85 pr.

I use the "crappy" Vista 64bit and did not have a single problem with anything.


People should read the manual (what I did to kill the torrent download time), also it was just a "wtf?" when I read the title and the first post. Really, with this attitude you won't go anywhere.
Actually, there is a problem with the shortcut / and pr.exe.

I did delete the old one shortcut when i patched to .86, but I still get vBF2 instead of PR when I load through the newly installed shortcut (which btw has a correct path) or the new .exe

A re-install will fix this, I'm told, but just manually entering a command line does the same thing, and doesn't cost me a half hour ;)