You cannot attach a debugger while playing Project 1999.

regatta · #1 07-28-2013, 06:39 PM

So at first I was having the WinEQ problem with EQ crashing after the update a day or two ago and now after their most recent update I am getting, "You cannot attach a debugger while playing Project 1999." Does anyone know a fix for this by chance or what could be causing it?

Norathorr · #2 07-29-2013, 02:13 PM

Also getting the exact same problem

August · #3 07-29-2013, 03:09 PM

Uninstall MQ2.

Well let me be more helpful. A 'debugger' is something that enters the process/dll being loaded in order to understand what's going on, typically.

I don't know how advanced WinEQ is but if any foreign process/object is injecting itself into your client (like MQ2) then this could register as a 'debugger'.

Or you could just be running with a debugger, but I have no idea why you would do that.

regatta · #4 07-29-2013, 09:38 PM

For one, August, I don't use MQ so your smartass comments don't help anything. Would something in the EQClient.ini file somehow enable a debugger to supposidly 'start-up' with WinEQ? Or does WinEQ somehow have a debugger option that I cannot find? Like I said it worked fine and then I tried to change my options in eqlient.ini to what Bamzal (I think his name) was saying could possibly work? It seemed those changes were only for resolution though. Any suggestions?

**Rogean** · #5 07-29-2013, 09:40 PM

Our anti cheat doesn't allow a debugger to attach to the client. This has always been the case on P99.

ansar · #6 07-29-2013, 10:00 PM

I don't think anyone is actually trying to load a debugger. It is just a symptom of the wineq update/project1999 update. They are not jiving very well.

I am getting the debugger message when I try to launch Project1999 through wineq2, and I am definitely not running a debugger.

The weird thing is that everything is working fine on my sons Windows7 machine, but my Windows8 doesn't like the two new updates.

Langrisser · #7 07-29-2013, 10:06 PM

Thats cool your server doesnt let people play anyway! /grin

regatta · #8 07-29-2013, 10:34 PM

Ansar: Same here. I can run the game fine without WinEQ except for the random glitch that happens and I can't get nilbog's command to work even with the correct file paths put in the command. Which is why I highly prefer WinEQ.

ansar · #9 07-30-2013, 08:34 AM

I prefer wineq because it recovers from UAC prompts, where as the native version will only show a black screen until I camp out.

**Rogean** · #10 07-30-2013, 08:53 AM

Quote:

Originally Posted by ansar [You must be logged in to view images. Log in or Register.]

UAC

First thing I disable on any new Windows 7+ PC.