straightman

This is with the NN build running. The Mame load bar and error descriptions box are eliminated by it (steps 1 and 2 I described above). I am trying to eliminate the region boilerplate text that is displayed for a time period before the game displays the real game graphics / coin load.

To test it I set the configuration to 30000 (30s) and it did not change the system response. Out of interest I tried running both from LB and BB with the same outcome. Is it possible to use a masking technique?, where a plain black screen image is displayed in front of the emulator output and then the black overlay is closed after a number of seconds?

Currently the time delay is set to 10s which is greater than the time during which the issue is displayed which is between 4 and 7. Based on that I would have expected the screen to be blanked out. Is it possible the autohotkey script is not working? Is there a need to install anything from the autohotkey website first or is everything setup for it in LB?

Thanks guys, this worked as described eliminating what I described in steps 1 and 2 of the originating post. I am interested to understand more how to control time delay to eliminate step 3, I see this script in the Emulator details screen under "Running Scripts" (LB V12.7 full version) the system must have pasted this in during setup: SetKeyDelay, 0, 50 return sleep 10000 ; Wait 10 seconds before pressing the key. Send, {space 3} ; Press the space bar 3 times to ensure we close all screens If not this script then I see possible options under "Startup Screen" with a Startup Load Delay slider set currently to 8s. The information that I would like to eliminate from display comes on between 4 and 7 sec. I would have thought if any of these control configuration settings where working it would have eliminated the content from display since the autohotkey has a 10s value and the slider in startup has a setting of 8s

Thanks guys, this make perfect sense now. I appreciate the information.

Referencing my original post in this thread, are there any steps that can be leveraged to do what I ask? Everything is working well enough so I would prefer if there are configuration techniques to resolve things.

Thanks, so this is a revised mame build correct? I see two versions available, 239 and 240 versions. Would these work with version 232 roms?

This applies to many mame title which after selecting play in LB have the following observed sequence of events: 1- Loading percent box is displayed which lasts for several seconds 2 - A rectangular message box from mame is displayed to tell if there are any limitations with the game (inaccurate sound or graphics for example) which requires a keypress to get through 3 - A screen of boilerplate text is displayed which disappears after several seconds without keypress 4 - Game screen is displayed asking for coin load Question: How can steps 1 thru 3 be eliminated resulting in the first displayed screen being that described in step 4?

I have been trying to run winape 20b2 in LB and having mixed results. I have LB emulator default command line parameters setup for the emulaor as /A with a sample command that shows as: WinApe.exe /A "FULL\PATH\TO\ROM\FILE" all other checkboxes in the emulator edit screen are unchecked. If I run the emulator outside of LB and perform a disk file load through the file menu I can successfully identify a .zip file for the disk file and check the auto run program checkbox and the game runs successfully. However If exit the emulator and try and play a game next through LB the emulator starts and autotypes the run command only it is using the same file reference from when I ran it manually (not loading the filename of the item associated with the LB game item). I checked to make sure that the game file reference and location in LB is good. It appears that the disk file reference is not being passed in the command string built by LB and passed to WinApe. Or possibly is not being cleared out of the emulator when I exited. Any thoughts of what to try next? It does not appear to matter whether I have the disk files stored in a the emulator folder or if they are in a separate folder (which is the state in affect during my description above, but I tested both cases with the same result)