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
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

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

Windows/2000 and CMD Line

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Windows/2000 and CMD Line

    When I enter the command line prompt and go into Alpha4, I only get half of a screen. Has anybody fixed this yet?
    Thanks
    Greg
    Tags: None
    #2
    RE: Windows/2000 and CMD Line

    Gregory,

    I have the exact same problem. I've worked on it for hours, and have been able to improve the size of the screen and the resolution by selecting "windows" on all tabs, rather than "maximize". Did you also notice that you cannot install Alpha4v6 to a Windows 2000 computer because you cannot write to the autoexec.nt file?
    Please let me know if you resolve this problem before I do. I'll do the same.

    Sam Tartamella
    [email protected]

    Comment

      #3
      RE: Windows/2000 and CMD Line

      Sam, you can edit the autoecec.nt file, thats no problem. The NTVDM.EXE is the problem. There is a registry setting some where that controls the screen and I will find it. I fixed it before but it took two days and I don't really know what I did. I have the cmd prompt set up as a windows but then the mouse does not work. I like the good old fashion DOS prompt when I have to do some work in Alpha4V6.
      If you find any thing out, please let me know. I will check technet and other areas.
      Gregory R. Zilliox, MCP,MCP+I,MSCE

      Comment

        #4
        RE: Windows/2000 and CMD Line

        1) Select Full Screen by right clicking the Icon and choosing properties, Screen.
        2) Run the app
        3) ALT-Enter back to desktop
        4) Single click on upper left corner and choose properties
        5) Select the Layout Tab
        6) Set the screen buffer height to 25 instead of 50
        7) ALT-Enter back to app and exit app
        8) open app, should be full screen 25 line

        Regards,

        Ran Hooper

        Comment

          #5
          RE: Windows/2000 and CMD Line

          Sam, have you solved the partial screen problem in Windows 2000? Has anyone else?

          I've tried all the suggestions I've found here (as of 2/26/2001), but have not yet solved the problem.

          David

          Comment

            #6
            RE: Windows/2000 and CMD Line

            Hey there, I followed the above suggestions. But when it really worked was when I deselected the 'Restore settings at startup' on the screen tab of the properties dialog of the desktop icon (you get there by right clicking on the icon). Before I discovered that, I kept changing the settings, and they would revert back as soon as I went into full screen mode. Hope this helps.
            Also, regarding the autoexec instal problem. I kept on getting a message 'unable to access boot%autoexec.bat' when I was installing. What I did was put a dummy autoexec.bat file in the root (c:autoexec.bat). The installation program seemed to be happy with this.

            Comment

              #7
              RE: Windows/2000 and CMD Line

              Thank you, Dean and Sam.

              What solved the problem for me was an MS white paper: Q272447, "Full-Screen MS-DOS-Based Program Only Visible on Top Half of Screen". This applies to Windows 2000.

              I think someone else on the message board must have referred to it, but I didn't understand the solution. Changing screen height to 25 is the secret. Read the paper for details.

              David

              Comment

                #8
                RE: Windows/2000 and CMD Line

                Try looking in the bios guys. Expand the video. I had the same problem and this fixed it.(Win 98SE)
                Good Luck
                [email protected]

                Comment

                Previous template Next
                Working...
                X