Packet Logger/Proxy

Bone,

to those with the problem that says "The application failed to start because the configuration...."


I've been lookin into it half the stuff I find is no help because a lot of people have no idea what the hell causes it.


Either we all don't have .NET 2.0, I don't, but this is C++ so as far I as know .NET is not needed, but rather the Visual C++ runtime library is.

However, it would appear as though you are giving us a Debug executable, according to MS's system event log, "Resolve Partial Assembly failed for Microsoft.VC80.DebugCRT. Reference error message: The referenced assembly is not installed on your system.", Dependent Assembly Microsoft.VC80.DebugCRT could not be found and Last Error was The referenced assembly is not installed on your system."

MS says in short to either redist those manifests, which I don't think is legal under the EULA, or to release to us the Publish exe files that wouldn't require the Debug DLLs.

Hope that helps, and I'm assuming anyone it does work for has VS2005 installed.

Let me know if I'm right or if I wasted my time.

-Andy
[img]text2schild.php?smilienummer=1&text=This took me a while to find ' border='0' alt='This took me a while to find ' />

Actually, the first few releases were in Release mode and that's when people started complaining so I tried to give out debug mode. It appears to still do it.. and as for what's causing it, as far as I know it's those stupid manifest files. I got that error on my VMWare setup. I went and removed the manifest from the build and then it worked fine. Problem is I also removed it from the last two releases I put on here so I don't know why it does it. It's ONLY happened when using vs8.0 though. I'm about ready to revert back to 7.0 for this. What I don't get is why no one has a problem using my emu when it was essentially the same project with a name change lol.

Also I learned that hard way about using the DLL version of the CRTs lol. I compile everything with the libs built into the exe hence the bloated size (damn crt files increased heavily in size since 7.0). Without it compiles to a measily 80kb or so. :D even in debug mode.


Actually, after I did that last paragraph I went to check. My debug exe is 96kb (oops? :D) I had release set to nondll but not debug. meh.. I'll try ONE last time. If this doesn't work I'll try it in 7.0.

grr.. I just went to compile "embedding manifest" God.. it's a constant battle with VS. It like resets it every time I load it even though it shouldn't. That might be one of the reasons it doesn't work. Who the hell thought of doing that anyway? What good does it do to NOT run on some computers >.>

Ok. I found the issue.. Both of my computers recently experienced mass harddrive failures and this one got the heavy hit so I went to move all the data off when I got it back online. I've been copying from the old source folder (that hasn't changed every time I compile x.x) which is why it hasn't been working rofl. I've just been giving out the same file. OK then. THIS time it should work fine ;/ sorry for the stupidity there :D

Yes, VS never seems to want to work with everything.

It just sucks.

Boo MS!


Well, anyway, you said it should work, but have you uploaded a new version yet?


Also, I think it might not work for everyone because not everyone has the C++ runtime(haha?), and I saw a post on MSDN stating that if, in release mode, it works after copying the MSVCR80.DLL and some others to the system 32 dir then....Yeah I'll look it up sometime later.

So now my outlook is: Blame VS.

Also, if you want you can just send me the release version, we can see if the problem relies in the users or if it is still something wrong with VS.

i don't think he uploaded the new versi0n, because it still doesn't work and its the same size too :eek: . I've had vs2k5 already and still didn't work.

Quote:

.... I've been copying from the old source folder (that hasn't changed every time I compile x.x) which is why it hasn't been working rofl. I've just been giving out the same file...

it happened to me the other day... i was pulling out my hair

I did reupload it. The rar is the same size but the binary is around 185kb. I still don't get why my emu runs and the proxy doesn't. Damn MS to hell. I guess when I get a chance I'll downgrade the project to vs7.0 and try that... I never had any issues with 7.0. I only got 8.0 for it's x64 compiling anyway :D

Winrar still shows that xproxy.exe is 98,304 bytes.


Did you not update the link?

Quote:

Originally posted by andyd123@Jun 9 2007, 16:53 Winrar still shows that xproxy.exe is 98,304 bytes. Did you not update the link?

Sorry... rough day xD I started messing with my emu and suddenly half of the things broke. Was running to everything trying to figure out why. Kinda screwed with my head. I actually only updated the zip one I had hosted, and not the rar. hah. It's updated now >.<

works like a charm ;)

=x

What the hell, It's still showing 98kb.


I dunno I need to find out why its doing this to me =[

<hr>Append on Jun 10 2007, 03:15<hr> Works with the zip file, not the rar :D

Quote:

Originally posted by andyd123@Jun 9 2007, 21:13 =x What the hell, It's still showing 98kb. I dunno I need to find out why its doing this to me =[ <hr>Append on Jun 10 2007, 03:15<hr> Works with the zip file, not the rar :D

Might be your browser cache :P

Awesome, it works, even with 4343.

I loaded it up and used SV version made by fallenstar, since that stopped working -- it worked, and I could bot.

Problem - It is so laggy it dced me 2 mins after being logged in.

Any idea why?

Which is laggy? Your ping, or the proxy? I only use it to login because I hate that new font and always use an older client. I've never d/ced on it and was just on it now in market.

When I log in, it appears to be fine, I jump and NPCs etc are not loaded, it waits for a few seconds or minutes then dcs me after I achieve some 25k-100k ping.

That's an awesome client issue sometimes, though it's never happened to me outside TG. When it does that, go into the proxy and try typing. If the text displays instantly it's not the proxy lagging itself. In that case it'd be TQ servers, the client, or just a poor connection to the server. I assume it works fine though outside the proxy so I'm not sure what the issue is.

Can you fix the link?