Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Keyboard buffer

  • Filter
  • Time
  • Show
Clear All
new posts

  • Keyboard buffer

    I have a different problem when using sys_shell(). I need to send keystrokes to a DOS program to operate it "remotely" using A5. Sys_shell() will likely just play a .bat file that runs the DOS program.

    What I need is some type of keyboard buffer or some other way to play stored commands as if they were coming from the keyboard into this DOS program. There will be about 6 commands, and I will need to insert a "wait" between some of the commands so they have time to finish before more keystrokes are played.

    Has anyone done this?


  • #2
    RE: Keyboard buffer


    Set brainstorm on

    if the timing is determined by processes which must be completed within Alpha Five, maybe you could set up a series of BAT files, activating each one in turn by sys_send_keys() ?

    else maybe you need to build a DOS compiled EXE to control the DOS process.

    end if

    set brainstorm off


    • #3
      RE: Keyboard buffer

      >> else maybe you need to build a DOS compiled EXE to control the DOS process.


      • #4
        RE: Keyboard buffer

        Bill, I guess my brainstorm collapsed... I was thinking you needed to run several preliminary processes, then the DOS program. You want to 'drive' the DOS program remotely. I see the difference.

        Can you configure the DOS program to accept a command line statement with arguments that cover what you need?

        Can you configure the DOS program to read a text file that contains instructions?

        Can the user run the DOS program for you, perhaps after a screenful of instructions are displayed?

        Maybe you can use sys_send_keys() if you make the DOS session current with sys_focus_put()... ???

        Having never attempted such a thing it's easy to dream up ideas, most of which are probably crazy.

        Hope they help.

        -- tom


        • #5
          RE: Keyboard buffer

          Hi Bill,

          What is the program doing? Does the program accept command line parameters? Will the program accept a file as input? I play around writing small exe's for utility stuff, but I've never done anything like this and honestly don't know how to start. I used to have a small utility program written (or sold by) parsons software. This was years ago. It was a 'safety' program basically for word processing. It would 'record' your key strokes for several minutes at a time and if your computer crashed you'd fire things back up and it would 'play' the keystrokes back into your word processor. It was a TSR. Sound kinda similar to what you are wanting.



          • #6
            RE: Keyboard buffer

            Ira sent me a tsr called Fakey. I could not get it to even play keys into a DOS edit session. (It also had a "wait" function, and I _could_ get it to wait!!) The program said it only worked if BIOS was used for keyboard processing, so maybe in 98 and W2K the system handles the keyboard input differently, or maybe I was doing something wrong.

            It sounds like this is a bigger challenge than I thought it would be.

            Currently users run the DOS program, and we are trying to get them out of the loop to reduce errors. There is no command line mode for the program.

            Thanks for the thoughts.