Announcement

Collapse
No announcement yet.

I'm not complaining, but.....

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • I'm not complaining, but.....

    I just got around to noticing. Under windows xp, my screen is
    set to 1024x768 (24-bit hi color). When I run a program from
    F8 or the dos prompt, the screen goes to 80(columns)x50(lines).

    Now I'm not complaining about this but I thought PB/DOS (3.5)
    defaulted to 80x25 and one had to use the SCREEN function to
    switch modes.

    Someone shed some light on this?
    Cheers


    ------------------
    There are no atheists in a fox hole or the morning of a math test.
    If my flag offends you, I'll help you pack.

  • #2
    Check the default pif for dos and see what the screen size is set at.
    KS

    ------------------

    Comment


    • #3
      Well, the "command prompt properties" gives me an 80x25. Okay,
      I'm confused.


      ------------------
      There are no atheists in a fox hole or the morning of a math test.
      If my flag offends you, I'll help you pack.

      Comment


      • #4
        If the console is changing size only after you run the program, it's
        likely to be the program that is changing the console size. Check for
        a WIDTH statement in the source code.

        ------------------
        Tom Hanlin
        PowerBASIC Staff

        Comment


        • #5
          Wrote a test program. It works perfectly. Again, I'm using xp/pro
          and the display adapter is set to 1024x768 24-bit hi-color. The
          monitor is a Dell M781s being driven by Intel(r) 82810E Graphics
          controller. The screen buffer size (right-click DOS icon > properties >
          Layout) is 80x300 and the window size is 80x25.
          Code:
          	$lib all off
          	color 14,1
          	cls
          
          	c = 64
          	for row = 1 to 50  ' <-- Please note # of rows
          	for col = 1 to 80
          	incr c
          	if c = 91 then c = 65
          	print;chr$(c);
          	next col
          	next row
          	end

          ------------------
          There are no atheists in a fox hole or the morning of a math test.
          If my flag offends you, I'll help you pack.

          Comment


          • #6
            I've had this problem with XP and some of my DOS programs (written
            with PDS, not PB).
            I never change the screen resolutionin my program, but sometimes it switches
            to 80x50. I have no idea why. It happened so much at one place
            in the program that I actually had to manually set the screen to
            80x25 there. My customer was running it in full screen mode, and it
            would all of a sudden switch to the windows desktop in a 80x50
            window. It is weird and I think an XP thing.


            ------------------

            Comment


            • #7
              In NT/2000/XP, the default console is 80x300. When a DOS app is launched, the closest "standard" console mode that is supported by the driver will be selected automatically, typically 80x43 or 80x50. When the DOS app end, the console is usually switched back to the original size again.


              ------------------
              Lance
              PowerBASIC Support
              mailto:[email protected][email protected]</A>
              Lance
              mailto:[email protected]

              Comment


              • #8
                Originally posted by Lance Edmonds:
                In NT/2000/XP...the closest "standard" console mode...will be selected automatically
                Oh, okay. Thanks.


                ------------------
                There are no atheists in a fox hole or the morning of a math test.
                If my flag offends you, I'll help you pack.

                Comment


                • #9
                  If you change the screen buffer size from 80x300 to 80x25, the results
                  may be more the way you expect.

                  ------------------
                  Tom Hanlin
                  PowerBASIC Staff

                  Comment

                  Working...
                  X