Mouse Pointer not visible when recording a macro.

Maxx · Post by **Maxx** » Mon Jan 16, 2006 9:51 pm

Subject pretty much says it all.

The mouse pointer becomes invisible when recording a macro. It reappears once recording is stopped.

This is the only application I have run which causes this symptom. I have been able to reproduce this with the trial version on a separate computer as well. Both systems are running Windows XP Pro SP2 with all critical update applied.

Post by **Marcus Tettmar** » Mon Jan 16, 2006 10:23 pm

Hi,

I haven't seen that before. Anyone else?

I'm running XP Pro SP2 here with all latest patches and updates. So nothing to do with that. Apart from that what is the spec of these two machines? Does the problem persist after a reboot?

Rain · Post by **Rain** » Mon Jan 16, 2006 10:32 pm

I just tried recording and noticed an error when pressing shift+esc or clicking the stop button to stop macro scheduler from recording.
The error is: File not found
I have to exit it and reload macro scheduler to use it again.

I'm running version 8.0

Post by **Marcus Tettmar** » Mon Jan 16, 2006 10:37 pm

I can't duplicate that either

Does this always happen?

Rain · Post by **Rain** » Mon Jan 16, 2006 10:45 pm

Yes it happens all the time

I am not able to use the record feature at all and when I use it I first have press shift+esc to stop it. I can't even right click on the wheel in the system tray to stop recording. And on top of that while recording my mouse becomes useless no matter what or how I click the mouse is not responding, I'm only able to move it around the screen but that's all I can do. When I stop macro scheduler from recording by pressing shift+esc my mouse returns back to normal.
This has never happened with any of the older version (7.XX)

I have XP Home SP2 and all Windows updates.

JRL · Post by **JRL** » Mon Jan 16, 2006 10:49 pm

Rain,
I would not have tried stopping the record with shift+esc since the instructions say to use ctlr+alt+Z (default). But I tried it under version 8.0 and it seems to work. No error.

Later,
Dick

Post by **Marcus Tettmar** » Mon Jan 16, 2006 10:50 pm

Freaky! On the recorder dialog that pops up before you start recording - the one where you provide the name of the macro - what happens if you try selecting a different hotkey to stop the recording. The default is CTRL-ALT-S. Try selecting a different hotkey and see if it makes any difference.

Post by **Marcus Tettmar** » Mon Jan 16, 2006 10:53 pm

Another thing to try. If you have a copy of 7.4 installed, copy the file hooklib.dll from that version to your v8 directory (backup the hooklib.dll file in there first). Then see if it makes any difference. If you don't have it I can email you a copy. Be interested to see if there is any difference.

Rain · Post by **Rain** » Tue Jan 17, 2006 12:41 am

I used the hotkeys to stop it (ctrl+alt+s) and got the same error "File not found" I then installed "msfullwc74009" to a separate directory, copied the "hooklib.dll" file to the 8.0 folder and ended up with the same error again. IÃ¢â‚¬â„¢ve added all the Macro Scheduler files to my virus programsÃ¢â‚¬â„¢ allow list and added them to my firewallsÃ¢â‚¬â„¢ allow list, that didnÃ¢â‚¬â„¢t fix the problem either. Next thing I will do is uninstall 8.0 after saving my scripts and do a fresh install. That should fix the problem if the problem is on my end.

I will let you know what happened.

Thanks,

Rain

Rain · Post by **Rain** » Tue Jan 17, 2006 1:02 am

Bad news, the fresh install didn't fix the problem and the "hooklib.dll" file is in the main directory. What next?

Post by **Marcus Tettmar** » Tue Jan 17, 2006 8:32 am

Rain wrote:I used the hotkeys to stop it (ctrl+alt+s) and got the same error "File not found" I then installed "msfullwc74009" to a separate directory, copied the "hooklib.dll" file to the 8.0 folder and ended up with the same error again.

In an earlier post you said that the problem did not occur with 7.4. However, you've just tested it with the 7.4 version of the recorder dll and got the same problem. One more thing then - can you install msfullwc74009 and try recording with 7.4 again and see if you get the same problem.

Post by **Marcus Tettmar** » Tue Jan 17, 2006 8:34 am

Rain wrote:I used the hotkeys to stop it (ctrl+alt+s) and got the same error "File not found"

As you are getting file not found I wonder if there is something unusual about your setup. Where is the software installed? Does the program folder have write access or is it read only? Are you logged in as administrator or a restricted user? Where is the macro data folder?

Rain · Post by **Rain** » Tue Jan 17, 2006 11:16 am

I installed 7.4 again and get the Ã¢â‚¬Å“File not foundÃ¢â‚¬Â

Post by **Marcus Tettmar** » Tue Jan 17, 2006 11:27 am

Earlier you said that the problem didn't occur with version 7.4. Now it does. So at least we know this issue has not been caused by a code change between 7.4 and 8.0. Therefore there must have been some change to your environment/setup.

Where are your macros stored? More specifically, where is the "Recorded Scripts" group mapped to? Even more specifically, please right click on the "Recorded Scripts" group and select "Group Properties". What is "Macro Path" set to? Check that this folder is not read only.

Also check that the main Macro Scheduler program directory is not read only.

Maxx · Post by **Maxx** » Tue Jan 17, 2006 3:56 pm

The main system for MacroScheduler is a Dell OptiPlex GX620/3GHz/2GB Ram/Logitech MX1000 Laser Mouse/ATI FireGL 7100.

I have tried reboot/replacement mouse drivers/disabling temporarily of AV software.

The mouse pointer is visible for a very short period of time after clicking the "Record" button. The mouse still operates in that if I mouse-over a button in a window, the button will highlight. Of course, it is tedious to mouse-over the intended button or anything else when the mouse-pointer is invisible. Pressing Ctrl-Alt-S, terminating the recording of the macro, immediately makes the mouse pointer visible again.

mtettmar wrote:Hi,

I haven't seen that before. Anyone else?

I'm running XP Pro SP2 here with all latest patches and updates. So nothing to do with that. Apart from that what is the spec of these two machines? Does the problem persist after a reboot?