Overtkill

Hi Mindy, In my experience, you cannot run a client on any left display. It has something to do with the negative screen coordinates. I experienced this issue about 6 years ago myself. The only real solution is to run it on a right or top display, keeping the client in positive coordinates. I got around this by configuring my left display to an input sharing application, and setup a KVM on the left display to toggle to another machine, or 3 machines in my case. The input sharing app runs keyboard and mouse functions over the LAN, and the KVM toggles the left display to which ever machine I'm after. This setup works well for far more than E&B, but the game was the initial "mother" reason behind it, being that I would field a full group of Jenquai at times. I hope some of this helps a bit. -( )vert.

Also make sure Compitability is enabled for WindowXP SP2. Mine wasn't enabled after install, so yours probably isn't.

Mobs put in game to irritate and slow us down.

Those of you experiencing client window selection issues under Windows 10, should note that in setting compatibility mode to a previous windows version on a game or app, can cause certain software not not find the window or task properly. I believe that Win10 is isolating the process a further layer, maybe a container when doing so. Setting the client.exe to normal operation under Win10 was the only way that I have found to correct these selection issues. Others trying to access multiple windows at once should also remember that as an operating system, Windows (all versions) are only designed to take UI input from a single window at a time. In other words, the keys and mouse clicks you send can only access 1 window at a time. If you need to send commands to another window, you will need to select it, thus making it the foreground window, prior to sending anything. The only way to access different windows in a truley simultaneous manner, would be with additional machines. Be they virtual (VMWare) or actual machines and sending commands over the LAN to the other computers.

My experience is that the client does not like the display to the left of the main one. Something to do with negative pixel coordinates. Consider the clients age as the reason. Because of this, my setup uses that monitor on a KVM to other boxes, and possible VM's on those boxes. Local stuff, I run on the main, and right display. I also have an upper, smaller monitor, that is used mainly for tools and small apps.

\Program Files (x86)\EA GAMES\Earth & Beyond\Data\client\output\login.ini This file contains the last login name.

Nice job!

lol cool.

My apologies. My intention was merely to make you aware of the issue by posting in that thread, as I am well aware that you'd get the alerts. No one from staff had replied about it at the time of my posting. With no one being able to login, the SysAdmin in me saw the server as effectively down.

You guys should also be posting in the Server Status thread in general discussion. IIRC, Zack will get a message if posted there, which I have already done.

Server keeps popping INV 300 Errors at login on peeps Zack. Same with me. Posting here to alert you.

The dragon drops from the freighter at Huston Resource Field, in Grissom. I cannot recall the name of the resource field in Shep, but it is there is also a dragon figurine drop near the gate to Grissom, also from the Freighter there. I have 3. I had a rat figurine drop a few weeks back, but can't recall where. Probably another CL30 something freighter or elite RD mob. I'll check again soon. I couldn't find him today so far. I'll keep burning them down until I do.

Karu's idea is correct, in that ESET is breaking this by injecting its own stuff into the connection. Unfortunately, this is common practice for most security softwares available. Another way around this issue, might be to create rule exceptions in your security software. I do this for my own stuff, in Kaspersky. Both the folder paths to the EnB game folders, and the net-7 folders, should be added to general AV exceptions to exclude them from any security activity. On the firewall side, create a rule to "allow always:" Game: client.exe Net-7: LaunchNet7.exe, net7proxy.exe

Perhaps they should've moved the hull upgrades to Mars during the invasion.

Welcome Back.

Another app like AutoSizer, could help as well. On another note, make sure the screen coordinates are positive. The client doesn't like it when Windows maps a monitor in negative pixels.

Most of the time, this can be solved by checking the option "Prototype Re-order" in the Net-7 Launcher.

Okay, I'll bite again. The rotation served its purpose when there were huge numbers of players in the Big 3. Since the numbers have shifted to the majority being in public or other guilds, including Damage Inc, I'd argue that its currently only serving a few multi-boxers at this point, and their respective guilds. If this is indeed the case, and triggers are being left up, you guys need to rally and go take them down as Gunney has suggested. I supported the rotation (and help design it as part of Static) as a method of dealing with large numbers of players, including getting the public a spot. My motives and views then were to simply make the situation more fair for everyone who are able to raid. If the dynamics have changed that much, and those guilds no longer have this majority, then the rules should change or be tossed altogether in favor of the majority of players who can and actually want to raid. I would hope the leaderships of these guilds would acknowledge this difference, and make this change on their own. -Not give into the greed of the situation. But since this does not seem to be the case, nothing will change until those with the greater numbers choose to act and make it a regular thing to do these raids. Until then, this issue is like beating the proverbial dead horse. Hence the fizzle in discussion.

Odd, I was able to login normally just now. Maybe reboot some equipment like your puter, router, and modem, then give it another try.

For starters: Ruby Disruptor, Black Razor, Pitbull 8's, Soulfires Curse, Harvester of Souls, Jaguars, Stone Cleaver, Bl3nd3ngStr3ke. Quite the poo-poo platter of beams available.

I'd suggest a better branded router. Check out smallnetbuilder.com for some ideas in their router listings.

Your outgoing IP address information should all be provided by your ISP. In most cases, the range is dynamic (ISP assigned by a DHCP server). I don't understand why you are trying to manually route traffic, when this process should be working automatically. My setup uses a single router, like most. I don't assign any of the address information to the outside, as the ISP does this for me. And that router also handles IP addressing for my internal machines through its DHCP capabilities. Nothing special required to connect to the game server. Why is yours any different?

/group refuse IIRC...

Sorry to inject this somewhat off topic thought, but I figured this was worth mentioning to anyone running a VM: Using VMWare Workstation 12 myself in my own full group configuration, I run 4x Windows 7 32bit OS's, on VM's. The key to not wasting disk space is to create 1 actual VM with an actual OS disk image. From there (After fully configuring said VM), right-click on that VM, move to Manage, then select Clone. This will start the Clone wizard. Click next, and you will see that you can create a "Linked Clone" of the other. A linked clone allows you to make a copy of the VM created, that also uses the image of the original VM for OS on the cloned copy. It stores the differences in data to the cloned VM's directory/folder. The result is that it doesn't require another-second copy of the original disk image, as it uses the first as it's base source for it's OS data. (I repeat this on the second machine.) Windows 7 also has the advantage of having a hardware accelerated desktop, compared to XP. I simply disable and uninstall everything that is unnecessary within the OS, and have little problem running 2 VM's on each of my 2 machines, which are also running clients in the main OS on each rig, giving me access to 6X ships at once, without the need to switch between them very often. If you have gating issues or odd crashes, remember to go through your host computer's network config, turn off IPv6. If you have a newer motherboard with 2 Ethernet adapters, disable the VMWare bridge protocol on the first adapter, but leave it enabled on the second. Start the local client session, and make sure its using the 1st adapters IP in the launcher. This will keep the VM's on the second NIC, allowing you to dedicate the 1st to the group's driver. This helps a butt-load in terms of stability. Hope this helps some people. Feel free to PM me if there are any further questions.