Ignoring md5 queries
- MuzzleTough
- Member
- Posts: 19
- Joined: March 17th, 2011, 3:26 pm
- Location: YVR
Ignoring md5 queries
I just started getting kicked for ignoring md5 queries. All discussions on the forum date back a few years. Does anyone know how to fix this so I don't get a frigging 5 min kick?
Thanks
MT
Thanks
MT
![Image](http://i54.tinypic.com/280vclx.gif)
I used to be a pacifist, then I started playing BF.
MuzzleTough
Re: Ignoring md5 queries
So, I see nobody has figured out a way to fix the Ignoring MD5 Tool Queries error. I've tried everything from:
Removed/reinstalled game.
Login as an Administrator user,
1. open Windows Explorer and browse to c:\windows\system32
64 bit, you need to browse to c:\windows\syswow64
2. scroll down and find PnkBstrA.exe - PnkBstrB.exe,
3. right-click PnkBstrA.exe - PnkBstrB.exe and choose Properties.
4. click the Compatiblity tab.
5. click the button "Change settings for all users".
6. click the checkbox for "Run this program as an administrator".
7. click the "Ok".
8.Restart your PCI've read on other forums but am also still getting kicked for the same error.
Went to virus settings and firewall to allow/exclude PB A&B and BF1942 in EA GAMES folder.
NO FIX!!!!
One thing I did notice is that I'm running Windows 7 64-bit Operating System but PnkBstrA.exe and PnkBstrB.exe files are showing up in the (Windows/System 32) folder instead of (Windows/SysWOW64). Is this right?
Removed/reinstalled game.
Login as an Administrator user,
1. open Windows Explorer and browse to c:\windows\system32
64 bit, you need to browse to c:\windows\syswow64
2. scroll down and find PnkBstrA.exe - PnkBstrB.exe,
3. right-click PnkBstrA.exe - PnkBstrB.exe and choose Properties.
4. click the Compatiblity tab.
5. click the button "Change settings for all users".
6. click the checkbox for "Run this program as an administrator".
7. click the "Ok".
8.Restart your PCI've read on other forums but am also still getting kicked for the same error.
Went to virus settings and firewall to allow/exclude PB A&B and BF1942 in EA GAMES folder.
NO FIX!!!!
One thing I did notice is that I'm running Windows 7 64-bit Operating System but PnkBstrA.exe and PnkBstrB.exe files are showing up in the (Windows/System 32) folder instead of (Windows/SysWOW64). Is this right?
Re: Ignoring md5 queries
Yeah, I've never seen or known a specific cause or solution for "ignoring MD5TOOL queries." It seems to happen just randomly to someone who is running fine most other days, and I don't know if that means MD5 checksum queries are only issued infrequently (and this person is failing them 100% of the time), or whether they are issued all the time and something is just randomly causing one of them to fail.
But the "solutions" I've seen have always just been generic reinstall recommendations, and nothing that truly investigated or pinpointed what was going wrong. Which at this point may well be impossible since we won't have Evenbalance's help.
Regarding PnkBstrA.exe and PnkBstrB.exe, there shouldn't be any need or change created by setting "Run this program as an administrator" on those two processes, because they actually run as Windows services and not as the interactive logged-on user. They are always "running as administrator" (more specifically, as "LocalSystem" which has even more rights than Administrators) even without these steps.
I do expect that PnkBstrA.exe and PnkBstrB.exe will exist in C:\Windows\SysWOW64\ on a Windows 64-bit machine. But whether they appear to be in C:\Windows\SysWOW64\ depends on what program you're using to look.
From within any 32-bit application, Windows actually "lies" and redirects "C:\Windows\SysWOW64\" to appear as though it's actually "C:\Windows\System32\" to the 32-bit application. Therefore the 32-bit application thinks "I'm accessing the SYSTEM32 directory just like I always do", but in reality he's accessing "C:\Windows\SysWOW64\".
So using the 64-bit Windows Explorer that comes with Windows, yes, you should see only 64-bit programs in C:\Windows\System32\. PnkBstrA.exe and PnkBstrB.exe and any other 32-bit application will actually exist in C:\Windows\SysWOW64\. But if you're using some other tool to browse directories, or the File | Open dialog in a 32-bit application to look at the Windows directory, everything will appear to be in "C:\Windows\System32\" because of the lie Windows is telling your 32-bit application.
-Trench
But the "solutions" I've seen have always just been generic reinstall recommendations, and nothing that truly investigated or pinpointed what was going wrong. Which at this point may well be impossible since we won't have Evenbalance's help.
Regarding PnkBstrA.exe and PnkBstrB.exe, there shouldn't be any need or change created by setting "Run this program as an administrator" on those two processes, because they actually run as Windows services and not as the interactive logged-on user. They are always "running as administrator" (more specifically, as "LocalSystem" which has even more rights than Administrators) even without these steps.
I do expect that PnkBstrA.exe and PnkBstrB.exe will exist in C:\Windows\SysWOW64\ on a Windows 64-bit machine. But whether they appear to be in C:\Windows\SysWOW64\ depends on what program you're using to look.
From within any 32-bit application, Windows actually "lies" and redirects "C:\Windows\SysWOW64\" to appear as though it's actually "C:\Windows\System32\" to the 32-bit application. Therefore the 32-bit application thinks "I'm accessing the SYSTEM32 directory just like I always do", but in reality he's accessing "C:\Windows\SysWOW64\".
So using the 64-bit Windows Explorer that comes with Windows, yes, you should see only 64-bit programs in C:\Windows\System32\. PnkBstrA.exe and PnkBstrB.exe and any other 32-bit application will actually exist in C:\Windows\SysWOW64\. But if you're using some other tool to browse directories, or the File | Open dialog in a 32-bit application to look at the Windows directory, everything will appear to be in "C:\Windows\System32\" because of the lie Windows is telling your 32-bit application.
-Trench
- =sBs=SEANY
- Member
- Posts: 29
- Joined: August 2nd, 2012, 3:58 pm
Re: Ignoring md5 queries
I'm running the game fine on 64-bit Win7, but in my explorer I see PnkBstrA.exe and PnkBstrB.exe in C:\Windows\SysWOW64\, not C:\Windows\System32\. Maybe that's part of your problem?Trench wrote:I do expect that PnkBstrA.exe and PnkBstrB.exe will exist in C:\Windows\SysWOW64\ on a Windows 64-bit machine. But whether they appear to be in C:\Windows\SysWOW64\ depends on what program you're using to look.
For reference, these are the file hashes I have (in case of corruption):
PnkBstrA.exe (md5: 3A2E85F7D90D15460C337CE80C2E3B29)
PnkBstrB.exe (md5: 13F068305D0D1BDB781D8433E364378F)
![Image](https://i.imgur.com/L10RkrL.jpg)
Re: Ignoring md5 queries
No, that, what you said, is correct, and matches what I said. Ninja said the opposite.=sBs=SEANY wrote:I'm running the game fine on 64-bit Win7, but in my explorer I see PnkBstrA.exe and PnkBstrB.exe in C:\Windows\SysWOW64\, not C:\Windows\System32\. Maybe that's part of your problem?Trench wrote:I do expect that PnkBstrA.exe and PnkBstrB.exe will exist in C:\Windows\SysWOW64\ on a Windows 64-bit machine. But whether they appear to be in C:\Windows\SysWOW64\ depends on what program you're using to look.
-Trench
Re: Ignoring md5 queries
Thanks for the info. Another question I have is do you have a folder called PunkBuster in your LogFiles folder (C:\\Windows\SysWOW64) because, like I said I have a 64-bit OS and the folder is showing up in (C:\\Windows\System32\LogFiles\PunkBuster)?
Re: Ignoring md5 queries
Went ahead and deleted the PnkBstrA.exe and PnkBstrB.exe files from the System32 folder since they're also in the SysWOW64 folder. Didn't have a PunkBuster folder in SysWOW64\LogFiles folder, so I cut it out of the LogFiles folder from System32 and pasted in SysWOW64\LogFiles folder. Gonna try and play and see what happens. How in the hell did this folder swapping even happen?????? Strange!
Re: Ignoring md5 queries
Does your pb folder look like this?
[img] [/img]
[img] [/img]
You do not have the required permissions to view the files attached to this post.
Re: Ignoring md5 queries
Do you have both a System32 and SysWOW64 folder?
[img] [/img]
[img] [/img]
You do not have the required permissions to view the files attached to this post.
Re: Ignoring md5 queries
Inside System32 folder...
[img] [/img]
[img] [/img]
You do not have the required permissions to view the files attached to this post.
Re: Ignoring md5 queries
Inside SysWOW64 folder. Should I delete the System32 folder as I'm running Windows 7 64-bit Operating System?
[img] [/img]
[img] [/img]
You do not have the required permissions to view the files attached to this post.
Re: Ignoring md5 queries
Yes, on my Windows 7 SP1 x64 machine, the .\LogFiles\PunkBuster\ subdirectory only exists under the "real" SYSTEM32 directory; it does not exist under the SysWOW64 directory's LogFiles directory. Not withstanding that the PnkBstrA.exe and PnkBstrB.exe services exist under SysWOW64, not SYSTEM32.
My game-specific PunkBuster directory does not contain a "Windows" subfolder at all, let alone a "System32" or "SysWOW64" subdirectory under that. This is the entire directory structure and files under my PB directory:
I'm guessing the difference is that you have a CD-based Battlefield 1942 installation, an original Battlefield 1.6 patch installation of PunkBuster, and then probably applied Tank's PB Update to that. My guess is that Tank's PB Update probably is what created that "Windows" subdirectory, although I'm not near a CD-based installation to actually confirm.
The way I installed PunkBuster was using the PBSETUP42.ZIP from Moongamers, as described in the "5a. Install BOTH the 'Punkbuster core services' AND the 'Battlefield 1942-specific PunkBuster files' together" section of the HOW TO: Use an Origin-downloaded Battlefield 1942 game to play on the EA117 server document.
You can actually use that same process on the CD-based installation too; it's just not "required" since PunkBuster is already offered to you during the 1.6 patch, and all you really "need" is the Tank's PB Update. But I do like using the PBSETUP42.ZIP package better, because the installation actually performs more visual tests and verifications that the services are actually working correctly.
To use the "5a. Install BOTH the 'Punkbuster core services' AND the 'Battlefield 1942-specific PunkBuster files' together" steps on your CD-based install, just provide your CD-based "C:\Program Files (x86)\EA GAMES\Battlefield 1942" path instead of the "C:\Program Files (x86)\Origin Games\Battlefield 1942" path shown in the instructions.
-Trench
My game-specific PunkBuster directory does not contain a "Windows" subfolder at all, let alone a "System32" or "SysWOW64" subdirectory under that. This is the entire directory structure and files under my PB directory:
I'm guessing the difference is that you have a CD-based Battlefield 1942 installation, an original Battlefield 1.6 patch installation of PunkBuster, and then probably applied Tank's PB Update to that. My guess is that Tank's PB Update probably is what created that "Windows" subdirectory, although I'm not near a CD-based installation to actually confirm.
The way I installed PunkBuster was using the PBSETUP42.ZIP from Moongamers, as described in the "5a. Install BOTH the 'Punkbuster core services' AND the 'Battlefield 1942-specific PunkBuster files' together" section of the HOW TO: Use an Origin-downloaded Battlefield 1942 game to play on the EA117 server document.
You can actually use that same process on the CD-based installation too; it's just not "required" since PunkBuster is already offered to you during the 1.6 patch, and all you really "need" is the Tank's PB Update. But I do like using the PBSETUP42.ZIP package better, because the installation actually performs more visual tests and verifications that the services are actually working correctly.
To use the "5a. Install BOTH the 'Punkbuster core services' AND the 'Battlefield 1942-specific PunkBuster files' together" steps on your CD-based install, just provide your CD-based "C:\Program Files (x86)\EA GAMES\Battlefield 1942" path instead of the "C:\Program Files (x86)\Origin Games\Battlefield 1942" path shown in the instructions.
-Trench
You do not have the required permissions to view the files attached to this post.
Re: Ignoring md5 queries
Well after uninstalling all my EA Games (BF1942, BF2, BF3, BF2142) I ran CCleaner to clean registry. Reinstalled BF1942 again and all was working or so I thought. Again kicked for Ignoring MD5 Queries. This is what showed up in the System32\LogFiles\PunkBuster\PnkBstrA file. Any ideas????
[12.27.2014 22:15:22] Verifying MD5 match for "C:\Windows\system32\PnkBstrB.exe".
[12.27.2014 22:15:22] Loading pnkbstrb.
[12.27.2014 22:15:22] Starting pnkbstrb.
[12.27.2014 22:15:22] packet sent [l1] 3
[12.27.2014 22:27:52] packet recv'd
[12.27.2014 22:27:52] Attempting unload of pnkbstrb.
[12.27.2014 22:28:18] packet recv'd [lC:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe]
[12.27.2014 22:28:18] loading [C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe]
[12.27.2014 22:28:18] Attempting to load "C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe"
[12.27.2014 22:28:18] SCManager Handle Opened.
[12.27.2014 22:28:18] Attempting to stop pnkbstrb.
[12.27.2014 22:28:18] Verifying signature for "C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe".
[12.27.2014 22:28:18] Copying "C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe" to "C:\Windows\system32\PnkBstrB.exe".
[12.27.2014 22:28:18] Verifying MD5 match for "C:\Windows\system32\PnkBstrB.exe".
[12.27.2014 22:28:18] Loading pnkbstrb.
[12.27.2014 22:28:18] Starting pnkbstrb.
[12.27.2014 22:28:18] packet sent [l1] 3
[12.27.2014 22:39:32] packet recv'd
[12.27.2014 22:39:32] Attempting unload of pnkbstrb.
[12.27.2014 22:15:22] Verifying MD5 match for "C:\Windows\system32\PnkBstrB.exe".
[12.27.2014 22:15:22] Loading pnkbstrb.
[12.27.2014 22:15:22] Starting pnkbstrb.
[12.27.2014 22:15:22] packet sent [l1] 3
[12.27.2014 22:27:52] packet recv'd
[12.27.2014 22:27:52] Attempting unload of pnkbstrb.
[12.27.2014 22:28:18] packet recv'd [lC:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe]
[12.27.2014 22:28:18] loading [C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe]
[12.27.2014 22:28:18] Attempting to load "C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe"
[12.27.2014 22:28:18] SCManager Handle Opened.
[12.27.2014 22:28:18] Attempting to stop pnkbstrb.
[12.27.2014 22:28:18] Verifying signature for "C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe".
[12.27.2014 22:28:18] Copying "C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb\PnkBstrB.exe" to "C:\Windows\system32\PnkBstrB.exe".
[12.27.2014 22:28:18] Verifying MD5 match for "C:\Windows\system32\PnkBstrB.exe".
[12.27.2014 22:28:18] Loading pnkbstrb.
[12.27.2014 22:28:18] Starting pnkbstrb.
[12.27.2014 22:28:18] packet sent [l1] 3
[12.27.2014 22:39:32] packet recv'd
[12.27.2014 22:39:32] Attempting unload of pnkbstrb.
Re: Ignoring md5 queries
No definitive ideas. I can say that neither my PnkBstrA.log nor my PnkBstrB.log show any MD5 verification attempts, ever. So that might be an indication that any MD5 check attempted by PunkBuster is failing, but working clients simply have no reason to attempt the MD5 check against any file, but for whatever reason your client does.
It's just a guess; as stated before, other than knowing what the MD5TOOL does, I don't know the manner in which PunkBuster employs it / the conditions that would occur to trigger it's use, etc.
Since you mentioned having Battlefield 2, Battlefield 3 and Battlefield 4 also installed, I suppose one possibility is that PunkBuster is trying to checksum the PnkBstrX.exe file images because they don't match some locally-stored criteria; maybe because the later Battlefields put down newer files or newer criteria but the files in place are from Battlefield 1942 / PBSETUP42, or vice-versa.
If you had the will to do it, I think what I would try is removing all of Battlefield 1942, Battlefield 2, Battlefield 3, and Battlefield 4 via as complete an uninstall as they offer. With those removed, I would then further ensure that all Punkbuster services and directories are removed from the machine (deleting them manually if necessary), and reboot to guarantee they are no longer in memory. Since you mentioned already having attempted CCleaner, running a pass of that again after the uninstall and reboot shouldn't hurt either, maybe catching some no-longer-in-use remnants you might have missed.
Then install just Battlefield 1942, the 1.6 with PunkBuster and 1.61 patches, DesertCombat and TanksPB to create "only" a working Battlefield 1942 + DesertCombat installation on the machine. Stop there and figure out whether playing with that configuration still gives MD5 errors or not.
If it works, then decide whether you do want Battlefield 2/3/4 also installed, and hopefully installing the "newer" PunkBuster included with Battlefield 2/3/4 onto the machine /after/ the older working Battlefield 1942 installation is already present will help PunkBuster perform a better / proper / working upgrade process when installing the later PunkBuster files.
None of the Etch-a-Sketchs installed in my machines support DirectX 10/11, so I'm not able to perform any Battlefield 4 installation scenarios myself.
-Trench
It's just a guess; as stated before, other than knowing what the MD5TOOL does, I don't know the manner in which PunkBuster employs it / the conditions that would occur to trigger it's use, etc.
Since you mentioned having Battlefield 2, Battlefield 3 and Battlefield 4 also installed, I suppose one possibility is that PunkBuster is trying to checksum the PnkBstrX.exe file images because they don't match some locally-stored criteria; maybe because the later Battlefields put down newer files or newer criteria but the files in place are from Battlefield 1942 / PBSETUP42, or vice-versa.
If you had the will to do it, I think what I would try is removing all of Battlefield 1942, Battlefield 2, Battlefield 3, and Battlefield 4 via as complete an uninstall as they offer. With those removed, I would then further ensure that all Punkbuster services and directories are removed from the machine (deleting them manually if necessary), and reboot to guarantee they are no longer in memory. Since you mentioned already having attempted CCleaner, running a pass of that again after the uninstall and reboot shouldn't hurt either, maybe catching some no-longer-in-use remnants you might have missed.
Then install just Battlefield 1942, the 1.6 with PunkBuster and 1.61 patches, DesertCombat and TanksPB to create "only" a working Battlefield 1942 + DesertCombat installation on the machine. Stop there and figure out whether playing with that configuration still gives MD5 errors or not.
If it works, then decide whether you do want Battlefield 2/3/4 also installed, and hopefully installing the "newer" PunkBuster included with Battlefield 2/3/4 onto the machine /after/ the older working Battlefield 1942 installation is already present will help PunkBuster perform a better / proper / working upgrade process when installing the later PunkBuster files.
None of the Etch-a-Sketchs installed in my machines support DirectX 10/11, so I'm not able to perform any Battlefield 4 installation scenarios myself.
-Trench
- =sBs=SEANY
- Member
- Posts: 29
- Joined: August 2nd, 2012, 3:58 pm
Re: Ignoring md5 queries
No, mine looks different. Aside from files you are missing that are generated at run-time or during certain events, one thing I noticed is that you are using the old pbsv.dll (332 kb) as opposed to the newer version (364 kb). I've uploaded the correct version if you would like to try that:Ninja2014 wrote:Does your pb folder look like this?
If that doesn't work, to rule out anything else being corrupted or different in your C:\Program Files (x86)\EA GAMES\Battlefield 1942\pb folder, try renaming the folder to pb_old and using mine:
If that doesn't work, what anti-virus do you run, if any? Try adding exceptions for PnkBstrA.exe and PnkBstrB.exe to avoid any network problems (in Windows Firewall too).
Also:
Do your file hashes match the ones I have? (You can check with a free program like HashTab, http://implbits.com/products/hashtab/)=sBs=SEANY wrote: For reference, these are the file hashes I have (in case of corruption):
PnkBstrA.exe (md5: 3A2E85F7D90D15460C337CE80C2E3B29)
PnkBstrB.exe (md5: 13F068305D0D1BDB781D8433E364378F)
Poopy
You do not have the required permissions to view the files attached to this post.
![Image](https://i.imgur.com/L10RkrL.jpg)
- =sBs=SEANY
- Member
- Posts: 29
- Joined: August 2nd, 2012, 3:58 pm
Re: Ignoring md5 queries
Just had another thought: why do you have a "Windows" folder inside your "pb" folder?
Like Trench said, this folder is not normally present. Check to make sure you actually have PnkBstrA.exe, PnkBstrB.exe, PnkBstrB.ex0, and PnkBstrB.xtr in your C:\Windows\SysWOW64 folder, and make sure they are the correct versions.
For example, in my C:\Windows\SysWOW64:
PnkBstrA.exe (76 kb), md5=3A2E85F7D90D15460C337CE80C2E3B29
PnkBstrB.ex0 (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.exe (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.xtr (284 kb), md5=43CB60CE6E345F0F097D07B85DB70F81
Poopy
Like Trench said, this folder is not normally present. Check to make sure you actually have PnkBstrA.exe, PnkBstrB.exe, PnkBstrB.ex0, and PnkBstrB.xtr in your C:\Windows\SysWOW64 folder, and make sure they are the correct versions.
For example, in my C:\Windows\SysWOW64:
PnkBstrA.exe (76 kb), md5=3A2E85F7D90D15460C337CE80C2E3B29
PnkBstrB.ex0 (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.exe (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.xtr (284 kb), md5=43CB60CE6E345F0F097D07B85DB70F81
Poopy
![Image](https://i.imgur.com/L10RkrL.jpg)
Re: Ignoring md5 queries
Poop, I went ahead and installed the zip files you sent and now I can't even connect to a game/server. Here's what I am receiving now. It won't let me checkbox the PunkBuster Enable box.
You do not have the required permissions to view the files attached to this post.
Re: Ignoring md5 queries
Don't have a fix. Just post a few things of my system. Never had any problems with the game.
I run Win7 64-bit. My game is CD-based. Did download and installed the Origin version BF1942 but never connected to any server.
My PB exe files are under Windows/SysWOW64. The pb folder has all the files as your screenshot PLUS two DAT files: pbbans (0 KB) and pbns_c (3 KB). There is a Windows folder in pb, but only a System32 under it.
Do you also have the MD5 issue on other servers?
I run Win7 64-bit. My game is CD-based. Did download and installed the Origin version BF1942 but never connected to any server.
My PB exe files are under Windows/SysWOW64. The pb folder has all the files as your screenshot PLUS two DAT files: pbbans (0 KB) and pbns_c (3 KB). There is a Windows folder in pb, but only a System32 under it.
Do you also have the MD5 issue on other servers?
Re: Ignoring md5 queries
Well, I ran Tanks PB Update and that fixed the enabling PB issue and was able to play on EA server today for a while until once again I got booted for MD5. The Windows folder also installed in the PB folder after I ran Tanks PB update. And for some reason I don't have all the PnkBstr A/B files you have (See attached pic)
PnkBstrA.exe (76 kb), md5=3A2E85F7D90D15460C337CE80C2E3B29
PnkBstrB.ex0 (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.exe (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.xtr (284 kb), md5=43CB60CE6E345F0F097D07B85DB70F81
PnkBstrA.exe (76 kb), md5=3A2E85F7D90D15460C337CE80C2E3B29
PnkBstrB.ex0 (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.exe (110 kb), md5=13F068305D0D1BDB781D8433E364378F
PnkBstrB.xtr (284 kb), md5=43CB60CE6E345F0F097D07B85DB70F81
You do not have the required permissions to view the files attached to this post.
- =sBs=SEANY
- Member
- Posts: 29
- Joined: August 2nd, 2012, 3:58 pm
Re: Ignoring md5 queries
Hmm, did this problem arise after using my pbsv.dll, or my entire pb folder?Ninja2014 wrote:Poop, I went ahead and installed the zip files you sent and now I can't even connect to a game/server. Here's what I am receiving now. It won't let me checkbox the PunkBuster Enable box.
If you look in the PB thread (http://www.ea117dcfanfavorites.com/view ... f=11&t=845), the user RoLnRoCk had a problem with ignoring MD5 queries, and fixed it by updating pb using the pbgame.htm method. I would recommend you try this method, it is quite easy:
Before doing this, I would recommend uninstalling PunkBuster for Battlefield 1942
(Goto Control Panel\Programs\Programs and Features, and uninstall punkbuster. Restart computer.)
Install PunkBuster for Battlefield 1942 (pbgame.htm method)
Step 1:
- Download pbsetup.exe from EvenBalance (http://www.evenbalance.com/?page=pbsetup.php)
- Make a folder "pbsetup", and put pbsetup.exe inside. Run pbsetup.exe, then close it.
- You will notice the program created a new file, pbgame.htm. We need to replace this with an older version that still has bf1942 as a game. I've uploaded the pbgame.htm provided by moongamers.
- Copy and replace pbgame.htm with the moongamers version. Right-click on pbgame.htm, and goto properties. Check the "Read-only" box, then click "Apply". Without this step, pbsetup will replace our pbgame.htm with newer versions.
- Run pbsetup.exe again. Click "Add a Game" and select Battlefield 1942. Then click the "Update PunkBuster" button and let it update.
You do not have the required permissions to view the files attached to this post.
![Image](https://i.imgur.com/L10RkrL.jpg)
Re: Ignoring md5 queries
Looks like that fixed it Poop! So far 3 maps with no errors. Thanks! You the POOP! ![cool 8-)](./images/smilies/Emoticon_24.png)
![cool 8-)](./images/smilies/Emoticon_24.png)
Re: Ignoring md5 queries
Here's hoping this continues to be the real fix for you. Seems like the key here could be Poopy having you pull the current PBSETUP.EXE from EvenBalance.com. Rather than the Moongamer's PB42SETUP.ZIP package which had the .HTM file already included, but was/is still including an older PBSETUP.EXE than what you would have downloaded from EvenBalance this week.
(The Moongamer's PB42SETUP.ZIP contained October 2010 versions of both PBSVC.EXE and PBSETUP.EXE. EvenBalance.com has a June 2014 PBSVC.EXE and May 2014 PBSETUP.EXE currently available for download.)
Do keep letting us know whether you get the MD5 issue, in case we don't already see it happen in-game. If it stays resolved, maybe we need to put together an updated package to use/recommend instead of Tanks's PB Update and/or Moongamer's PB42SETUP, if the latest PBSETUP and/or PBSVC is needed in order to help avoid some conflict between Battlefield 1942 and other later still-supported-by-EvenBalance PunkBuster games.
-Trench
(The Moongamer's PB42SETUP.ZIP contained October 2010 versions of both PBSVC.EXE and PBSETUP.EXE. EvenBalance.com has a June 2014 PBSVC.EXE and May 2014 PBSETUP.EXE currently available for download.)
Do keep letting us know whether you get the MD5 issue, in case we don't already see it happen in-game. If it stays resolved, maybe we need to put together an updated package to use/recommend instead of Tanks's PB Update and/or Moongamer's PB42SETUP, if the latest PBSETUP and/or PBSVC is needed in order to help avoid some conflict between Battlefield 1942 and other later still-supported-by-EvenBalance PunkBuster games.
-Trench
Re: Ignoring md5 queries
UPDATE!!! The issue came back again. Logged in first time today and was kicked again for ignoring MD5 queries. DAMNIT!! ![26 :26:](./images/smilies/Emoticon_26.png)
![26 :26:](./images/smilies/Emoticon_26.png)
Re: Ignoring md5 queries
Well, since you already used the updated PBSETUP.EXE, the additional thing that seems appropriate to rule out is running the updated PBSVC.EXE too, to update the actual Windows services used for PunkBuster. (As opposed to PBSETUP, which provides the game-specific integrations.)
You can download the updated PBSVC.EXE from EvenBalance.com, and the steps to run it appear the same as with the previous version.
-Trench
You can download the updated PBSVC.EXE from EvenBalance.com, and the steps to run it appear the same as with the previous version.
-Trench