Announcement

Collapse
No announcement yet.

win2000 mouse with PBDOS

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

  • win2000 mouse with PBDOS



    Having a problem with a mouse routine that has been working in
    every DOS and Win vsn up to ME incl NT4 (I still use pb3.00c )

    The routine comes from Eric Olsen's DRAW application.

    My latest installed user happens to have WIN2000 (nt5?) and the
    mouse seems to have expired.

    My mainmenu .exe is called directly from a desktop shortcut icon
    and after a 7.0 second delay appears to run as designed except
    for the mouse. (it is using the command.com that came with w2k
    that I copied into my working dir. This eliminated any delays
    within my application when using my secondary menus.)

    Thanks in advance.

    James Gillem (www.magnumsoft.com)


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

  • #2
    sounds like the infamous quickedit gotcha:

    http://www.powerbasic.com/support/pb...ad.php?t=14666

    ------------------
    tom hanlin
    powerbasic staff

    Comment


    • #3
      Thank you: TOM HANLIN

      The QuickEdit ON default was the problem..

      The greatest support in the world - I now have a happy win2000
      user in Athens Ga. (I am in Walnut Creek Ca.)

      I assume that any problem of this type will also be in XP ?

      Now, if I could eliminate the 7.0 second delay
      (in the w2k desktop) using a std shortcut icon to my dos app
      via command.com..

      I think the cmd.exe may be the answer ?

      James Gillem


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

      Comment


      • #4
        The delay should be a one-time thing as Win2k loads its monstrous DOS emulation files.
        These are left in memory after the first load, unless you explicitly terminate it. Due
        to how the NT memory manager works, "left in memory" does not actually reduce the amount
        of memory available to your programs, so it is not an issue in that respect.

        Using CMD.EXE instead of COMMAND.COM will not help the load time, but does give you
        access to a more modern 32-bit command shell (with LFN support and other improvements).


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

        Comment


        • #5
          AGAIN, THANKS TOM.

          THE SERVER "WIN2000 BOX" SHOWS FREE MEM OF 605 BUT I WOULD LIKE
          TO DO A DOS TYPE MEMMAKER TO MAKE SURE EVERYTHING POSS IS IN
          HI-MEM. I HAVE SEEN 630 ON NT4.X SERVER/WORKSTATION.IS THIS POSS
          IN NT5 (W2K) ?

          THE ONE TIME LOAD OF THE DOS EMULATION FILES SEEMS LOGICAL BUT
          UNTIL I ACTUALLY STUFFED THE FILE COMMAND.COM MY DIR THE MOVEMENT
          FROM ONE .EXE OR .PBC SEEMED TO TAKE 6-7 SECONDS - WITH IT IN
          PLACE THE WAIT IS ZERO TIME.GO FIGURE..

          THANKS

          JAMES GILLEM




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

          Comment


          • #6
            I've noticed that occasionally Win2K takes a long time to close files in *any* DOS application, but I've never been able to find a pattern to it.

            In my K6/266, the delay is usually around 1-2 seconds per file - certainly not 6-7 seconds (unless this *is* the problem you have and you are closing multiple files).

            However, this occasional delay when closing a file is not a PowerBASIC issue - it is the O/S close function that is taking its time...

            If anyone else has any theories on this, I'd be interested in discussing it further.

            Thanks!

            PS: James - please do not shout! (posting in capital letters is considered by many to be equivalent to "SHOUTING!"). Thanks!

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

            Comment


            • #7
              I don't believe MemMaker agrees with the NT-based OSes. You may be able
              to tweak the CONFIG.NT and AUTOEXEC.NT files to remove functionality you
              don't need.


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

              Comment


              • #8
                I am not completely familiar with how the DOS Emulation in NT works, but I would guess that the extra time could be 2000 Journalizing the write. This is just a guess, but it is slightly educated, since it is a well know n fact that Journalizing slows down file systems (ReiserFS, ext3, bfs issues)

                As for how long it slows down, my guess would be that 2000 has to send the filr through the DOS Manager to Windows, which then saves the file using it's own method...thus causing a delay.

                Unfortunately, I tend not to see slowdown on my system so I can't take anymore guesses.


                ------------------
                Amos
                DosOS.com
                mailto:[email protected][email protected]</A>

                Comment


                • #9
                  Thanks for the info Amos!

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

                  Comment

                  Working...
                  X