Windower Not Hooking (Windows 7 x64)

[Zirk]

Holy shit I never knew there was a x64 option for windower, I've been on Windows 7 Ultimate 64 bit and been running the same way I did for XP 32 bit and just double clicking launcher.exe

Now that I know about it, I'm afraid to try windower with 64 bit checked, what is the advantage to using windower with 64 bit enabled?

[HKR]

It makes it work.

[Pikarya]

Now that I know about it, I'm afraid to try windower with 64 bit checked, what is the advantage to using windower with 64 bit enabled?

You just performed a miracle.

[Gethsemane]

Turn UAC off. Pretty much what worked for me. The reason why it is not hooking is because of the black screen/screen fade bullshit that UAC does. I was also doing the compatibility thing, run as administrator crap but it didn't work until I turned off UAC. Let me know if it works.

[Belgaer]

Unless turning off the UAC involves more than simply sliding the UAC slider all the way down, I did that months ago. I just rechecked it and it's still slid down.

EDIT: Err, misspoke. Edited the above for clarification.

[StevenW]

I had a similar problem in Windows 7 x64 where I would luanch windower and it would show up as the normal PlayOnline window, and when I login it'd be regular FFXI with no Windower.

Turning off UAC (User Account Control) immediately fixed the problem after a restart.

UAC is that thing that darkens the screen and asks "Do you really want to do this?" every time you go to open a file or program.

-To disable the UAC, enter the Control Panel and type UAC in the search box.
-The first result returned by the search will be User Accounts – Turn User Account Control (UAC) on or off.
-Click on it and the UAC window will open. Deselect the option Use User Account Control (UAC) to help protect your computer and press the OK button.

Also, windows having to confirm with you everything you do will stop being annoying.

Edit: Wow lol I read every post but the last 2, durr... Well good to know another person knew the fix as well.

[Belgaer]

Yeah, there's no on/off in Windows 7, unless you get to it by different means. There's just the slider. It's been all the way down, set to 'do not inform' or whatever for a while now.

[ChilliSwede]

Yeah i have the exact sam problem as Belgaer. I tried using Windower 4 Alpha but i cant seem to make macros since i cant use my <> keys... I dont want to play the game if i cant use windower, so here hoping for "someone" to come to the rescue :S

[Furtwangler]

I've had a similar dilemma the past few days, just started FFXI back up again and when I used windower, it would randomly (within 10mins to an hour, depending on how much I alt-tabbed) crash. On win 7 x64. I moved my computer to a friends house, and uninstalled Logitech's setpoint software (had some issues with my wireless mouse and keyboard.) After that, windower froze whenever I alt tabbed back into the window, and the hook never properly loaded (no console.)

Windower Av4 worked for me as a temp fix. Tried all the fixes/hook files etc with 3.42 and no dice. I just reinstalled the setpoint software from logitechs site for win7, and now 3.42 is perfect. Everything loads, and as of now (I'll do some more testing later tonight) no freezes or anything out of the ordinary. Anyone else have their software installed? It's seemingly unrelated but I just tried before/after (that's ALL i changed, was the logitech software) and it works perfectly.

[Seedz]

Meh, not working for me either. I installed the "new" Hook.dll, DirectX 9 and turned UAC off. Also I ticked the x64 box on the GUI. When I click on Play button, a message saying "PlayOnline Viewer stopped working, Windows is trying to find a solution to the problem" appears....

Any suggestions?

[Seedz]

Hmm just went back to old Hook.dll and it's working. Crossing fingers.

[Kimkytaru]

I had the same problem as everyone, windower was working fine with pol but as soon as I hit "play" it wouldnt go into FF11 making it crash every time I alt-tab back to the game.
I just dl the latest ATI software and it worked, so if you have any ATI graphic card you might wanna check that too.

[Riker]

For me when I open windower it just opens the regular pol version. For the life of me I can't get it to work. I replaced the old hook files with the new ones Aikar posted, was I supposed to keep them all or something. Someone hellpp =( Need a more retard friendly version of these instructions lol

[nitsuj]

For me when I open windower it just opens the regular pol version. For the life of me I can't get it to work. I replaced the old hook files with the new ones Aikar posted, was I supposed to keep them all or something. Someone hellpp =( Need a more retard friendly version of these instructions lol

There are a lot of problems with v3 moving into Windows 7. If you don't need plugins, you should check out the v4 Alpha. It should hook properly and give you a nice windowed environment, but it's only alpha. Plugins are still being developed.

[Riker]

There are a lot of problems with v3 moving into Windows 7. If you don't need plugins, you should check out the v4 Alpha. It should hook properly and give you a nice windowed environment, but it's only alpha. Plugins are still being developed.

I can do without plugins fora while, but macro scripts are a must, is that supported? Thanks for the quick answer im pleasantly surprised

[nitsuj]

I can do without plugins fora while, but macro scripts are a must, is that supported? Thanks for the quick answer im pleasantly surprised

The format for windower v3 style scripts will be changing a little, I'm finalizing that for this week's release.

Basically, the old one was:

input /equip body "Vermillion Cloak";

It effectively in code was viewed as:

WINDOWER_COMMAND EVERYTHING_ELSE (two arguments) which is kind of messy. v3 had no idea if you typed "/equip body" or "/equip" or "/equip body bananas". v4 is a little tighter as it's designed to know the number of arguments to prevent bad data/better crash support etc.

v4 will end up something like:

input "/equip Body 'Vermillion Cloak'";

(notice the arguments to "input" are in quotes, and the arguments to "/equip" are in single quotes ('). )

This is more consistent with typical programming, and I think *should* be fairly straight forward. The only downside is the necessity to 'escape' quotes to use them as a name... i.e.

input "/equip body 'Marduk\'s Shalwar'";

I'll have some more documentation on that when it's released, but currently the command parser doesn't quite work like this, so I don't recommend remaking your macro's yet.

[Riker]

The format for windower v3 style scripts will be changing a little, I'm finalizing that for this week's release.

Basically, the old one was:

input /equip body "Vermillion Cloak";

It effectively in code was viewed as:

WINDOWER_COMMAND EVERYTHING_ELSE (two arguments) which is kind of messy. v3 had no idea if you typed "/equip body" or "/equip" or "/equip body bananas". v4 is a little tighter as it's designed to know the number of arguments to prevent bad data/better crash support etc.

v4 will end up something like:

input "/equip Body 'Vermillion Cloak'";

(notice the arguments to "input" are in quotes, and the arguments to "/equip" are in single quotes ('). )

This is more consistent with typical programming, and I think *should* be fairly straight forward. The only downside is the necessity to 'escape' quotes to use them as a name... i.e.

input "/equip body 'Marduk\'s Shalwar'";

I'll have some more documentation on that when it's released, but currently the command parser doesn't quite work like this, so I don't recommend remaking your macro's yet.

Ok I understand the differences, the extra quotes are no big deal. Thanks for the info man I just downloaded v4 about to test it.


edit: it works nicely can't wait for those scripts to come through, and spellcast lite should def be the first addon u work on getting supported XP lol

[Belgaer]

I've had a similar dilemma the past few days, just started FFXI back up again and when I used windower, it would randomly (within 10mins to an hour, depending on how much I alt-tabbed) crash. On win 7 x64. I moved my computer to a friends house, and uninstalled Logitech's setpoint software (had some issues with my wireless mouse and keyboard.) After that, windower froze whenever I alt tabbed back into the window, and the hook never properly loaded (no console.)

Windower Av4 worked for me as a temp fix. Tried all the fixes/hook files etc with 3.42 and no dice. I just reinstalled the setpoint software from logitechs site for win7, and now 3.42 is perfect. Everything loads, and as of now (I'll do some more testing later tonight) no freezes or anything out of the ordinary. Anyone else have their software installed? It's seemingly unrelated but I just tried before/after (that's ALL i changed, was the logitech software) and it works perfectly.

I don't use any Logitech products, but I tried anyway for the lulz. Didn't work. :/

I had the same problem as everyone, windower was working fine with pol but as soon as I hit "play" it wouldnt go into FF11 making it crash every time I alt-tab back to the game.
I just dl the latest ATI software and it worked, so if you have any ATI graphic card you might wanna check that too.

I'm on a laptop that uses an ATI mobility (HD 4200) card. Mobility cards are unsupported by the current Catalyst drivers. Also, the ATI MobilityModder doesn't seem to be working for me.

Hmm just went back to old Hook.dll and it's working. Crossing fingers.

Could you tell me which hook you're using? If you could provide a link, that'd be appreciated too.

[Seedz]

I'm using the default one that comes with the downloadable version of windower, nothing special.

[Riker]

I had tried all 3 Aikar posted none worked when I was using windower 3 =\