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

Alpha4 under 64 bit Windows

  • Filter
  • Time
  • Show
Clear All
new posts

  • Alpha4 under 64 bit Windows

    Some of those looking for a method to run Alpha4 under newer 64 bit versions of windows (for example Windows 10) have tried using vDos. vDos is a DOS emulator designed to run business applications under the newest Windows Operating Systems. Originally vDos would not run many version of Alpha4 because it did not supply math co-processor emulation.

    The author of vDos has released a new version of vDos 2017.08.01 that added a FPU (Floating-point unit) to the emulated CPU.

    I have tested vDos version 2017.08.01 and it will run Alpha4 Version 6 under windows 7 64 bit quit well. It should support Alpha4 version 7 and 8 as well.

    What a walk down memory lane.

    Learn about vDos at

  • #2
    Re: Alpha4 under 64 bit Windows

    I'll add that, in my experience, vDos indeed seems to work well with A4V8 in Windows 10. I have one application that I haven't yet translated to A5, so I've had to jump through a few hoops to continue to use it. I can even print with vDos - something that wasn't possible with DOSBox.

    There's a version of vDos with more functionality, called vDosPlus: However, although A4V8 displayed with the original colors, it hung, which I attribute to a problem with how it handles memory. (Just a guess and I could be wrong.) I haven't taken time to tinker with it further since vDos seems to do the trick.

    I can even run WordStar - and those old control-key commands came right back, just like riding a bike.



    • #3
      Re: Alpha4 under 64 bit Windows

      The latest release (09/16) also works with a4 networked data. Multi-user shared database and file locking is now supported. We are running alpha4v7 in Windows 10, 64 bit without issues.


      • #4

        Has anyone had any recent experience with vdos? In my case, I need to migrate about 40 users on XP to Windows 10 64bit, so I'm looking, mainly, for information (good and bad) of this setup in networked environments with lots of activity, but anything would help.

        The database's main tables are in the 500MB to 1GB range and it's mission-critical, so we can't afford to find out that something's not working two weeks after the change and no matter how much though we've given to the problem, we can't come up with a reasonable way to test this thoroughly without seriously disrupting the client's operations.

        My preferred option was to set up a Win2008 server and have the users run instances of alpha4 via rdp as opposed to running something like vdos (or virtualbox) on each workstation, but this is no longer an option because both, Window 2008 nor XP (running in virtualbox), are discontinued products.

        Thank you!!!



        • #5
          We are running vDos on 5 windows 10 stations without any issues. Our databases are 400 MB. Why can't you introduce a couple of windows 10 PCs on the network and run vDos to access the data? In the past we had some users on XP and others on windows 7 with virtualbox and windows 10 with vDos. The dbf files don't care what os you are running as long as it's setup correctly on each station. Of course always have a backup.


          • #6
            Hi, and thanks for replying to a rather old thread admin@dci,

            In an ideal world, I'd have the users work on parallel systems until we feel confident that the solution works and no weird side-effects surface. I'm pretty sure that alpha4v8 behaves normally in a virtual environment (vDos, virtualbox, etc.) but I've seen my share of weirdness after doing this for 30 years.

            I am grateful for your sharing some of the details of your setup, which despite being somewhat smaller than mine has a configuration quite similar to what I'll be seeing until we migrate everybody to Win10.

            If you have any tips or caveats, I would be much obliged.