Megatouch Help Please

Geoffers08

Newbie
Credits
4CR
Hi obcd

Mmm I think finding the manual for this device is my priority. The sound related error only happens if I return to "FAIL SAFE " Bios settings. The optimised default option gives no such problem, but I will definately look at the oboard BIOS setting for inbuilt sound.

No, my mobo has pci slots, I did wonder about sticking a USB to serial adapter on the unit, and seeing if that helps any? - I know using these at work, they don't seeeeeeem to need a driver (note to self, I will try this tonight).

Sorry I am a little vague on some points, of all the mobo's I have (4 including this), they all seem different versions of hardware - and at present, other than looking at the BIOS splash screen, I am a little lost at which is identified as which.

Cheers.
 

obcd

Active member
Credits
3,830CR
I understand. Just be carefull. If you have 2 much spares, it's easy to exchange stuff and finally loose track of what works and what doesn't work. Most USB2serial adapters use an ftdi chipset, and the drivers for that might already be in the kernel or might be loadable by the kernel. The problem is that the device will likely be seen as a different comport. There might be a configuration file somewhere on the harddrive telling on which comport the touchscreen is connected.

In that case, it won't work. The isa adapters could be set to an io range and an interrupt. For instance io 0x3f8 and interrupt 4 are the typical settings for com 1.

Maybe your mobo is having another 10 pins connector that can be connected to a DB9 for an additional comport. In such case, you usually can set in the bios which connector is which comport.

So, besides finding the manual of the machine, the one of the mobo could be uefull as well. If you have a link where you can find it, you can post it here so we can check it out as well. I have no idea if Merrit had some custom mobo's build for these machines or if they used of the shelf available mobo's. The bios splash screen looks customised, but that can be done by flashing another bios as well. If you set the bios settings again 2 "optimised default", does everything revert to the situation as before? (The touchscreen controller error..)
 

Geoffers08

Newbie
Credits
4CR
Hi obcd,

Cheers for all the advice... I will have a rummage tonight.. I just heard from my mate who seems to have a link for the version of hardware manual. I will post it once I check it out as being correct.

Mmm maybe ill give the USB to Serial a miss. There is a second wider interface on the back - which I do recognize as a second serial, I will see if I can get hold of a converter for that.

Cheers.

Geoffers082014-10-10 15:11:02
 

obcd

Active member
Credits
3,830CR
As you say wider, I assume it's a DB25?

If it's a female connector, it's an LPT port instead of a COM port, which can't be used.

If it's a DB15, that's likely a joystick port. The headers I am talking about are on the mobo pcb. They are 10 pin's, 2 rows of 5. There exist pc brackets with a DB9 connector and a flatcable that can be connected to that mobo 10 pin connector. If you have such, you will find the settings for 2 comports in your bios setup. The mobo header will probably have the word com written next to the header. The manual of your mobo might help to locate such connector (if there is one.)
 

Dazzzzz

User
Feedback
7 (100%)
Credits
77CR
Geoffers08 said:
Hi Dazz,

I think tonight I will have to really try and get to grips as to what version this machine is - and what it is "trying" to load.

To be honest, all I really know, is the Flash on top of the machine, the BIOS splash screen, and then the software loading screen... I think the Flash on the top of the cab has never been changed, so this may well give me a good idea of what it was originally.

I am a bit confused about why suddenly the key is invalid, I definitely know this machine was running without issue original - using the current software, without key issue.

To be honest, I am not really too fussed what version I run - as I said I do have some other motherboards, complete with drives and keys (I think)... again, over the weekend I will look and report back, maybe I could re-sue some of this? I will also have a chat with my mate who I got this from, as he should know what "is / was" running.

Cheers for all the ideas - and I may well be very pleased on the drive / drive image.

Theirs nothing wrong with the Key mate, the HDD contains software for the Force and MAXX machines, the correct one loads depending on what Hardware the boot software encounters during startup.

Your HDD is detecting a MAXX machine when your running on Force Hardware (which is causing the key error) - this is where the invalid key error message is appearing from

Your Hard Drive should be loading the Force software, if this loaded then the key would be verified as correct, but since its loading the MAXX software (which is expecting a different version of the key) its failing
 

Geoffers08

Newbie
Credits
4CR
Hello again... yes, if I go back to "Optimised Defaults", I loose the error referring to the script, and sound card, and the "invalid key" error - but get the original touch screen controller error back.
 

Dazzzzz

User
Feedback
7 (100%)
Credits
77CR
oh and USB to Serial would not work as their would be no way to configure it or tell the software to look for it, unlike Windows is wont go off searching for drivers etc.
 

Geoffers08

Newbie
Credits
4CR
Hiya, no I know the Parallel port (LPT port), it was probably the "old" style joystick port I had spotted.

Mmm I think the mobo manual is definitely going to be the thing i look for!
 

Geoffers08

Newbie
Credits
4CR
Hi Dazz,

cheers for the explanation on why the wrong key message is appearing - so, basicly, by me having set the BIOS to "fail safe" default, it is changing the hardware profile enough, that it is loading the wrong software up... Mmmm seems me finding the manual and getting the right BIOS setting in is key (again) then?
 

Dazzzzz

User
Feedback
7 (100%)
Credits
77CR
Geoffers08 said:
Hi Dazz,

cheers for the explanation on why the wrong key message is appearing - so, basicly, by me having set the BIOS to "fail safe" default, it is changing the hardware profile enough, that it is loading the wrong software up... Mmmm seems me finding the manual and getting the right BIOS setting in is key (again) then?

i dont think its the bios settings mate as it was showing MAXX software on your original video i think?
 

obcd

Active member
Credits
3,830CR
The force mobo's listed on ebay have a 9 pin header between the cpu and the LPT COM connectors which could be a second serial port connector.
 

obcd

Active member
Credits
3,830CR
Dazzzzz is right. Even in the first video it's starting Maxx software.

The bios splash screen shows Force...

In linux, it's searching for a Maxx modem...

So, would the "touchcontroller not responding" error come before the Invalid key message?

Would be interesting to know what it is using to determine which software to run?
 

Geoffers08

Newbie
Credits
4CR
Hi Dazzz and Obcd (cheers both for sticking by me through this!).

yeah, the hardware comes up as FORCE (on the BIOS splash), and loads up as MAXX on software. Thing that really confuses me, is that it was working.......

I will check tonight re the 9 pin header on the board.

Ahhhhhhh this machine is in my spare bedroom on the first floor... at this rate it may just go out the window!
 

Geoffers08

Newbie
Credits
4CR
Well...... now that has me wondering! I rang my mate earlier, and asked him if he could remember what software the machine "use to" boot up into when it worked.... he felt pretty sure it wasnt Maxx.....so why is it trying to now?

When I get home tonight... I am going to check the key number...all the connections..and see if it sheds any light!
 

Dazzzzz

User
Feedback
7 (100%)
Credits
77CR
I've had the same issue before mate and when i did some digging i found out the Force and Maxx Hard Drives are the same and the touchscreen controller determines which software is loaded, the point is that somewhere along the way your megatouch is reporting the wrong touchscreen controller or the software has become corrupt

if you have another Force HDD and Key then swap them out

If that doesnt work i might have a board that you can test it with if you dont have a working spare one

Edit:

I believe the Touchscreen controller error comes up before the Invalid Key error message

If the Linux boot screen is reporting a touchscreen controller error then its usually something like the cable is loose etc. however if the error is shown once the software gui has started to load then the touchscreen is reporting that its there (since its booted this far) but its not reporting something correctly.

if yours is loading into the gui when the error is showing then the error is correct since its looking for a MAXX touchscreen controller and finding a Force one

Hope that makes sense (it did in my head!)

Dazzzzz2014-10-10 20:40:18
 

Geoffers08

Newbie
Credits
4CR
AHHHHHHH1 well cheers Dazz and obcd.....right.. now here is a question... ahem.

OK...both the invalid key message (on fail safe bios defaults), and the no response from screen controller (post safe bios optimised defaults), appear when the gui start - not during the linux boot process. Either error message appears just after the "Mega touch loading" screen appears.

I also have a spare "older style" white controller.... is it wirth me attaching this and seeing what happens?
 

obcd

Active member
Credits
3,830CR
Was that white one the controller original in the system, or was it a black force one?

Isn't microtouch having software you can use to identify the type of touch controller when you connect it to your (windows) pc? If it would be a comport problem on your mobo, do you have another comport (header) on the mobo? Maybe you don't have a bracket with a db9? Is it possible in the bios to select which comport is which?
 

Geoffers08

Newbie
Credits
4CR
Hi Dazzz / Obcd,

the original controller connected to the mobo, is a Black "Force" controller.

Speaking to my friend, he has said he is pretty certain it was a force 2005.

I have just powered up and gone into BIOS again, it now seems the battery for the BIOS must be on the way out, as the time has reset since yesterday. I am wondering if that is what is happening. I notice when in the Linux boot up, when it detects the controller, and loads the driver, it writes a line "saving changes to BIOS".

Could it be... it finds the right controller, writes the necessary changes to BIOS for the mobo, this isn't getting saved, so on the following boots, the right settings aren't there.. the software finds wrong settings, thinks it is a MAXX... it carries on loading, and of course then finds "oh no it's not a MAXX as the hardware doesn't match" and there is the problem.

My friend sent me a PDF he had of the manual - this is a FORCE manual.

I am going to pull the board out tomorrow, clean it completely, unplug and re plug everything. Make a note of any MOBO model number, and the software key code... then see what this matches in the manual. My hope being I will then find out what the BIOS settings should be for this board.

One question, is it safe to change the BIOS battery on these? I hear in some places that once the battery goes completely, or gets removed, these boards sometimes never power up again.

Cheers.

Geoff.
 

Geoffers08

Newbie
Credits
4CR
UPDATE,

I'm just going through a Megatouch document, as sent to me by my mate who orignaly owned this machine. The doc is entitled "Megatouch Tech 2013".

In it, it describes each of the major motherboards used, and lists, what appears to be mine under the FORCE hardware.

It goes on, and talks about the important of having the correct BIOS settings, it goes on to say:

ECS (FORCE)

1 - Plug the keyboard into PS2 (purple) port or the USB port on the motherboard.

2 - Power the game on. Press Del to enter SETUP.

3 - Arrow over and down to Load Fail-Safe Defaults.

4 - Press Enter, and then select Y for Yes.

5 - Arrow over and down to Load Optimized Defaults.

6 - Press Enter. Then press Y for Yes.

7 - Arrow back over to Standard CMOS features, then press Enter.

8 - Adjust the date and time, then press Esc.

9 - Press Enter. Press F10 and then press Enter.

10 - The system will reboot. Unplug the keyboard.

Instructions to change the date and time are normally explained on the actual display screen.

Keyboards: Both the USB port or PS2 port (purple port) will work with Force and Ion version motherboards.

TechTip: DIP switch 8 (DS8) should be tried first before doing a keyboard CMOS.

TechTip: Do not connect a PS2 keyboard to the motherboard when it’s powered up.

So by this, it seems that BOTH sets of defaults need to be loaded up... I am off now to try just that!

Fingers crossed! I'm going in.
 
Top