Beta Brite Model 1036 and I-Pac registry issue

[mauldraine]

First, let me apologize if this particular model of Beta Brite, and assistance has already been covered elsewhere.  I tried performing a search on just the model number, but keep getting a "500 Server Error".

I have been a quiet reader of this forum (and others) for quite some time.  One of the best resources around.  I have plotted and planned for months.  I purchased the Ultimate Arcade II cabinet kit from Mame Room, had a superb 4 player control panel made by Arcades R Fun LLC (wired it myself, wow what a task), I'm using a ViewSonic 27" LCD, and TRYING to use a Beta Brite model 1036.  The front end is Mamewah 1.62b10.

Beta Brite --

As is with all other articles I've read here, some are just not getting their Beta Brite to work with Mamewah.  In mamewah.ini I have the following ...

lcd_com_port 1
lcd_settings    9600,n,8,1

In mame.ini I have ...

lcd_display_file_path  c:\mame\lcd

I have used Silver's LCDGen program, and the .lcd files do get created, and I can open and view them with WordPad.  I have Beta Brite Messaging Software version 1.1.1 and it can speak with the unit just fine.  I can send any text that I want to it.  I have tried using HyperTerminal to speak to it, but can't seem to get the units attention.  I have also tried opening a command prompt (as was suggested here), I have typed (mode com1 9600,n,8,1) and then from within the lcd directory have tried (copy gaunt2.lcd com1) with no results.  I know the supplied cable doesn't have any issues since the messaging software can communicate with it no problem.  Suggestions please?

I-Pac Registry Issue --

This one really has me at my whits end.  Currently when I power the machine up the I-Pac board is not seen by Mamewah.  If you go in to the Device Manager, under HID-complaint devices, there is a yellow exclamation mark next to one of the I-Pac entries.  When you view it, it tells you that there is an error in the registry.  This issue is detailed on the Ultimarc web site.  However neither the Ipacfix.reg file solution, nor manually editing the registry works.  Heck, I have even tried rebooting after each step.  No luck.  The who idea is to boot directly in to Mamewah, and not have to manually remove entries from the Device Manager and redetect them each time you power up the machine before you can play a game.  Has any one experienced this and found a solution that sticks?

My sincere thanks for any who respond.

Martin

[Hoopz]

Re: I-Pac

Is it connected via USB? If so, have you moved it to another USB port?  Is connecting it via PS/2 an option?

[mauldraine]

Yes its connected via USB, yes it has been moved a couple of times as I would not leave the control panel connected and would move the machine to my desk to work on settings, roms, etc.

I do not have the PS/2 cable but I'm sure I could purchase one.  This is definitely an option.

[Hoopz]

I would try the PS/2 route and see if you can get it to work.  If not, you may need to re-install Windows.  If so, its only a couple bucks for the cord.  Good luck.

[mauldraine]

Actually I just purchased the PS/2 cable from them and will have to just deal with the issue until the new one arrives.     Now if I could just get the Beta Brite to work correctly.   

[Hoopz]

You may also try emailing Andy.  He is always helpful.

[mauldraine]

Wow do I need to get a hold of Silver.  After playing with the messaging softare, I came upon a file called out.txt in the application directory.  So I opened it and it looked a LOT like the output of the .lcd files that LCDGen creates.  While speaking to a friend of mine here at work, he suggested that I try a little program by the name of HexEdit to take a look at both of the files and compare them.

I thought, what the hex (er heck).  So I downloaded the demo version and began to play around.  I found a really good description of the types of commands that need to be sent to the BetaBrite here ...

http://alsplace.os9al.com/txt/betaspec.txt

There are subtle differences in the output of the .lcd files and what the Beta Brite model that I have is looking for.  After 30 minutes of studying (hey, I take my time), I munged together an .lcd file that actually worked for my 1036.  I issued the command prompt command, copy c:\mame\lcd\gaunt2.lcd, and I literally jumped out of my seat when the display told me that I was playing Gauntlet II.   

Right now it's displaying fire works, and then the letters are exploding on to the display.  This is kind of fun.  Ok time to hop over to Silvers site and send him an email.

[Silver]

Hey,

not looked at this for quite a while.

Could you post/attach an LCD file that works ok for your sign so I can take a look? I may be able to knock something together.

[Silver]

Based on feedback, I've updated LCDGen which should now work with more BetaBrites correctly. It will also let you select font colour, and add extra animations into the mix if your sign supports it.

I've also corrected the Crystalfontz LCD support to work correctly (can't scroll overly long text yet though). 

I've had reports that both now work correctly, but I can't test myself. If anyone else wants to play/test/try it out, new relase is here:

http://www.silverfoxy.f2s.com/LCDGen.html