7 replies to this topic

[Dezwin]

UPDATE: I thought "shelling" had fixed the problem, but I was wrong. I did have success after making other changes though... see my later post in this thread.



I am running Windows 7 Professional (64bit) on my cab and have had HyperPin focus problems when first booting up the system, as well as when exiting VP tables (sometimes). I came across a thread on the HyperSpin forums that describes how to configure Windows to launch directly into HyperSpin when booting, instead of launching explorer (no desktop icons, and no task bar ever launches).


So I configured my cab to shell into HyperPin to see if there was any benefit.
I have not had any problems since the change, so it appears to have solved my focus issues.


You can still get to the taskbar and desktop by doing the following:

* Exit HyperPin
* Press alt-control-delete
* Launch Task Manager
* Select File -> New Task
* Type "Explorer" (no quotes) and press enter

If you have HyperPin in your Startup folder - you should remove it. If you don't you will go right back into HyperPin after launching explorer in this way.

Also, keep in mind that any other applications you have configured to auto-launch in the startup folder will not load when shelling into HyperPin in this way.
Perhaps those things could be launched in another way, if you need them.

Here is the link to the tutorial:
http://www.hyperspin...ght=wizard exit

Edited by Dezwin, 21 October 2012 - 02:35 AM.

[Sir Cheddar]

I have a somewhat similar approach. I kill explorer.exe on hyperpin startup and start it again when hyperpin exits.

Hyperpin settings.ini:

[Startup Program]
Executable = c:\windows\system32\taskkill.exe
Parameters = /f /im explorer.exe
Working_Directory =
WinState = HIDDEN

[Exit Program]
Executable = c:\windows\explorer.exe
Parameters =
Working_Directory =
WinState = NORMAL

Replace "c:\windows" with the path to your Windows directory, if necessary. It needs the full path to the executable, and %systemroot% doesn't work.

[mucpin]

Thanks for your tips. I gave up on Hyperpin on Windows 8 already. Maybe I'll try again sometime and use your solutions...

[Dezwin]

My focus and slowdown problems with Hyperpin soon returned, even after configuring windows as described in this thread.

However, I did have some success...
I have been running my cab without these issues for at least a week now.

The last change I made was to turn compatibility mode OFF for all my applications.
(HGlass, FPLaunch, HyerPin, etc)

I left "run as administrator" ON

I read somewhere in another thread that compatibility mode was required by an older version of FPLaunch, but it was not needed anymore.
Can anyone confirm this?


A full week without focus and slowdown problems has me convinced this is finally fixed on my cab!

Edited by Dezwin, 21 October 2012 - 02:42 AM.

[Flying Dutchman]

This is an issue I have when I exit a Table, I sometimes have to 'click' the mouse to get HyperPin back focussed .. not on all Tables though ..

Cheers,
FD.

[Zarquon]

You can still get to the taskbar and desktop by doing the following:

* Exit HyperPin
* Press alt-control-delete
* Launch Task Manager
* Select File -> New Task
* Type "Explorer" (no quotes) and press enter

 

 

I do exactly what you are trying to achieve.

I created a HyperPinExit.bat and within it I have the following:

 

@ECHO OFF
REM Turn off LEDs
CALL ledoff.bat

REM Start Explorer
START %windir%\explorer.exe

This should do what you want.

 

Adding this to the old tread as this might help someone in the future.

[shinobisan]

Here's a little app I wrote to auto single left click on your primary monitor every 3 sec(doesnt interfere with game play,just insures that the front most application VP FP HP is clicked on).

Attached Files

•  autoleftclick.rar   2.68KB   54 downloads

Edited by shinobisan, 19 March 2013 - 11:52 AM.

[blur]

All focus problems are solved with latest fplaunch (wip 10) which even has some focus tuning option in settings.ini - although this click every 3 secs cannot hurt

 

Slow downs in hyperpin on win7 are caused by memory leak in compatibility mod, runnning hp native will solve memory leak but will give you longer black and white screens (no cure for that now)

 

And in all windows - XP or 7 taskbar auto hide feature has to be off (in windows - not in settings.ini!!!), sometimes it's better to move taskbar to backglass - sometimes it works better on playfield - test it.

 

But if taskbar auto hide feature is off you will probably not have any problems with task bar any more - so no reason to really run HP shelled as most people did this only to get rid of taskbar line!

Edited by blur, 19 March 2013 - 01:37 PM.