Stange Screen Controller Issue... any help really appreciated.

[geoffers2013]

Hi All from the UK (and a newbie to the site),

ahhh now I know the Megatouch doesn't get much love, but after converting a few to some multi touch emulator machines, I now have one that I would like to keep in my games room as an "Original" (I actually want to do a full restoration series on it).

Sooo...

All was going fine with this machine - happily playing on it, when suddenly...

I would Boot it up and all seems fine.  It goes all through the BIOS - fine.

It shoots through the post BIOS, starting up LINUX fine, detecting the Microtouch touch screen controller fine (it shows "OK" when detecting, and when loading up the driver)... but as the actual Megatouch software finishes loading, I get

"touch screen controller not responding".

I am a bit at my wits end.. I have tried connecting the touch screen controller (the 3M black model), to a PC - and it all works fine.

I have tried swapping in 2 "spare" controllers, and even a different screen overlay - all working fine on a normal PC, but all resulting in the same message on the Megatouch machine.

I have tried flipping DIP switch 6 on the I/O board, in order to put the board into hardware detect board... and... as it should, it goes into diag, detects the controller, reboots twice (re-initializing the drivers).. but still... nada!  "touch screen controller not responding".

Any ideas are really gratefully received...

Here is a video showing what happens.




Cheers in advance all!

[mahkeymike]

There is some weird stuff going on with your megatouch. Its loading the Maxx splash screen. Which suggests your using either a maxx hard drive, or a maxx key. This is why your getting the touchscreen error because its expecting a maxx controller. (white smt3 case)

Just so you know, your using a Force Motherboard and a Force touchscreen controller, Force IOboard and Maxx key or hard drive with maxx software loaded. This is most likely your problem and is a conflict of hardware/software.

What does it say on the sticker on the key? should be SAxxxx-xx-r00

[ed12]

ya he's running max with fource firmware
thats a no no
also that overlay need's alot of love
ie clean it
when u bind it back down just go around the edge and maybe 1/32 in on edges
enough to fold
or u will cause the touch to error out

ed

[mahkeymike]

ya he's running max with fource firmware
thats a no no
ed

No, he is using a legit Force mobo. He could even have a Force key, but the hard drive might have Maxx software loaded, or vise versa. Older versions of maxx did not have motherboard checks. If it detected a motherboard with a i810 chipset it would load Force driver modules along with touch screen driver modules. Then the software would take over and expect a Maxx touchscreen controller but the Force controller and driver modules were already loaded so it errors out.

I dont have a maxx mobo to test but in theory you could run 2005 force software/key on a maxx system with a simple patch.

[ed12]

i seen all that
guess it just came out wrong

ed

[mahkeymike]

dude makes a video pleading for help, posts video here where help is given, and a week later no responce. 

[lilshawn]

dude makes a video pleading for help, posts video here where help is given, and a week later no responce. 

checked the user, he signed in today. he may come back tonight with the results of his investigation.

 

[mahkeymike]

dude makes a video pleading for help, posts video here where help is given, and a week later no responce. 

checked the user, he signed in today. he may come back tonight with the results of his investigation.

 

Guess he gave up. I was just curious what version key he is using. If it was a 2005 or later Force key, all he would need to do is download the software (if he doesnt have the discs) and reinstall it.

Oh well, 

[Dazzzzz]

Hi Guys,

Just to let you know that I actually helped Geoff out with this problem (i guess he forgot to come back and update you all).
I sent him a spare 2006 Force HDD and Key that I had and once he popped these into the machine it worked
So the problem was a corrupt Hard Drive, he was using a Force one HDD but for whatever reason it was defaulting to load the MAXX software due to corruption on the drive