Registering

Are you having trouble registering? Read this first!

I have not received my serial number!

Please write to us, and we will provide you with your registration information immediately!

When you pay using PayPal, an e-mail with registration information is sent to the e-mail address you gave PayPal. This happens immediately after payment has been received. If that e-mail address is wrong, or if your spam filter stops the e-mail, you will not receive your registration information automatically.

In some cases we will be informed that an e-mail was not received, and in those cases we will try to contact you through other means. However, if the e-mail is stopped by your spam filter no such message is sent to us.

Daily use

These questions are the absolutely most common questions regarding MaxTo.

Why doesn’t cmd.exe resize?

Console windows are notoriously tricky to resize, and even Windows really doesn’t do it well. MaxTo has since version 2010.12 supported maximizing console windows by resizing the size of the console buffer to the closest approximation to what we want.

This will sometimes leave a few extra pixels between the console window’s border and the next region, but we believe it is a reasonable compromise. You can disable this functionality in the Options.

Why does MediaMonkey crash when MaxTo is running?

This is a problem with MediaMonkey, that Ventis Media is aware of. It is documented in their Knowledge Base (see point 4, which also applies to MaxTo).

The solution is to disable skinning in MediaMonkey. You do this by closing MaxTo completely, then starting MediaMonkey. On the Tools-menu, choose Options. Under Skin, make sure Override Skin theme with Windows System theme (requires restart) is checked, and restart MediaMonkey. Then start MaxTo.

PS! A workaround for MaxTo is coming that will disable certain features for MediaMonkey only. This workaround will be available in all version released in 2011.

Why doesn’t MaxTo work with RocketDock/other program?

MaxTo can sometimes interfere with other programs. Several people have reported that starting the interfering program and MaxTo in the opposite order than the way it is normally started fixes the problem.

I get “Failed to set hook” on Windows Server 2008. Why?

I am not sure, but the problem can be fixed by running MaxTo in Windows 2003/XP Compatibility mode. Right click the shortcut, and under the Compatibility-tab, check Run this program in compatibility mode for.

Why don’t Windows Live Messenger windows fully cover the region?

WLM windows are really a bit larger than they seem at first glance. If you have one of these windows open, try focusing on it and pressing the Alt key. This will bring up the menu, and the hidden borders around the window will become visible. I don’t know why WLM is this way, but they are not the only program behaving in this way. In WLM you can click the Show menu button (it is unfortunately unlabeled), and check the option labeled Show the menu bar to always show these borders. You will probably need to do this for both the main window and a chat window, but then it should start showing up automatically show up when you start new conversations.

Note: The latest version of WLM has fixed this.

Error messages

The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.

This error is a result of not having the .NET Framework version 2.0 or higher installed. It is necessary for MaxTo to run. The .NET Framework is installed by default on Windows Vista and Windows 7. You can get the .NET Framework through Windows Update.

Technical

The following questions are technical, and may not be of interest for most people.

How does MaxTo know when windows are maximized?

It asks Windows nicely to tell it whenever windows maximize, and is given the opportunity to change what happens afterwards. It takes control and figures out where to place things.

Why are there two processes running?

To explain this thoroughly, we have to get somewhat technical. You will only ever see both MaxTo.exe and MaxTo64.exe running on a 64-bit version of Windows. When running on a 32-bit operating system, only MaxTo.exe will ever run.

On 64-bit operating systems, there are two kinds of processes: 32-bit and 64-bit. To allow MaxTo to figure out when maximization happens, we have to set a hook, which actually involves loading code that runs in a different process.

Since you cannot run 32-bit code in a 64-bit process — or the other way around — we actually need two different processes to set the hooks, one 64-bit version and one 32-bit version.

Why are there two DLLs then?

One is compiled for 64-bit processes (Hooker64.dll), and contains the callback function for the 64-bit hooks. The other (Hooker.dll) is for 32-bit processes. The DLLs are written in unmanaged code, since managed code cannot receive callbacks from system-wide hooks. The DLLs set and release the hooks, and forwards the messages to the MaxTo process.

Why can’t I maximize any windows, even when MaxTo isn’t running?

Note! This bug should be fixed in version 1.0, as MaxTo64.exe automatically terminates if it can’t find MaxTo.exe running.

Something probably went wrong when MaxTo exited, or you forcibly exited MaxTo through task manager or some other strange means. This only happens on 64-bit systems, where the 64-bit MaxTo64.exe process is left running after MaxTo has exited. You should make sure MaxTo isn’t running, by closing it normally from the notification area.

Then open Task manager (press Ctrl+Shift+Esc), and select MaxTo64.exe, and click End process. Conrm that you want to terminate the process. You can now restart MaxTo.