Announcement

Collapse
No announcement yet.

PB35 freezes under win2k

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

    PB35 freezes under win2k

    Any help woulf be appreciated here...

    I open pbdos in a windows under win2k, everything looks good and I write a little test program and run it and all is fine then when I hit a key and drop back to the IDE I'm fine for a little while (2-5 secs) then everything freezes. I'm suspecting the mouse but I'm still testing that. By small program I mean like:

    Code:
    Dim x As Integer
    
    For x = 1 To 10
        Print Str$(x) & " Hello"
    Next
    
    
    End
    Are there any win2k issues I need to be aware of?

    Thanks

    ------------------
    Paul Dwyer
    Network Engineer
    Aussie in Tokyo

    #2
    It's the Mouse!!!

    I can use the mouse untill the first time I run the program then even if I've hit alt-enter and am full screen everything freezes. Infact when I use full screen I can't not have the mouse over the IDE so it always freezes. The software seems fine if I stick to the window mode and keep the mouse away from it. I can use it okay now that I know this but it's a bit annoying not being able to use full screen mode.

    Any ideas? I have downloaded a mouse driver from MS to be able to run the scroll mouse properly in the PBDLL6 IDE. It wasn't installed on this system and I was having this trouble so I installed it a couple of minutes ago and after a reboot nothing has changed

    Regards

    ------------------
    Paul Dwyer
    Network Engineer
    Aussie in Tokyo

    Comment


      #3
      In the DOS window Properties, do you have Quick Edit Mode disabled?

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

      Comment


        #4
        It's not enabled.

        In the pb35 software I have the mouse disabled now and all works fine, but it would be nice to be able to use the mouse



        ------------------
        Paul Dwyer
        Network Engineer
        Aussie in Tokyo

        Comment


          #5
          I had a mouse conflict with DOS a couple of years ago. If your mouse is hooked to
          the Serial Port, You have to make sure that the mouse driver points to the correct
          port (the one the mouse is plugged into) or it will freeze a DOS PB program.
          I don't know about a Bus mouse though.

          Regards,

          ------------------
          [email protected]
          :) IRC :)

          Comment


            #6
            seems odd though that it works untill I do a run or compile and that I have no trouble in other applications...

            I have the mouse turned off in the IDE now



            ------------------
            Paul Dwyer
            Network Engineer
            Aussie in Tokyo

            Comment


              #7
              It does seem odd... I've never seen or heard of the problem, so I (have to) suspect it has something to do with your system or O/S...

              And yes, we run Win2K all the time...

              Anyone got any ideas for Paul to try?

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

              Comment


                #8
                In humor here, your mouse may be a, "Mouse of very little brains!"
                Curiously, all mice have brains! Some have less or more or
                different brains than others! It's true!

                It is a know fact that some brands of mice have brains which are
                incompatible with some drivers, at least in OS/2 .. grin. There
                are even know incompatibilites with various serial number runs
                in mice (Logitec!) for example. in the same model number! Not
                all mice with certain "firmware" in them on a model wide basis
                are created equal! I'm not kidding..

                That discussion can be made worse, if, for example, you are using
                a system switcher, such as a Rose unit, like I do, to provide for
                toggling back and forth between many systems in a relay rack so you
                can use one keyboard, one mouse, and one video monitor between a
                number of different systems.

                The reason for that is that switcher must provide the ability to
                cross-interface the mouse the systems! There appear to be some
                motherboards of the very latest type with power-on capability,
                so I've now seen, which grunge the keyboard and mouse operations
                on at least the boot run, if the actual hardware device isn't
                there *ALL* the time during the boot run! Why? Well, the Rose
                switcher knows enough to present a phantom "I'm here!" during boot
                time for the monitor, mouse and keyboard .. for the older units.

                But maybe not these new mothers!

                I have a suspicion, based on problems with a brand new MB I'm now
                debugging here of this type, that this problem with low level mouse
                snooping may show up, at some time, later as well, if the MB is
                going to intercept the mouse, for idle and power reset snooping,
                at all times. Yes, I have it turned off as to that choice, but,
                based on the current failures in the boot runs, at times, using
                the Rose switcher, I'm leery! I can start the boot run, swap to
                another unit, come back and either the keyboard or the mouse, or
                both will be dead on arrival even though the system desktop is up
                and running!

                That's not nice to have to push the power button hard off to get
                the box rebooted.

                As long as the switcher is set to the actual booting box, I don't
                see the problem!

                Of course all this is related to drivers, too, as has been already
                said!

                You asked for suggestions! Please don't shoot the messenger! He
                just brought you more possibilities than you'll ever likely want!

                But since, all mice have brains! Thus, as a small suggestion, switch
                mice for testing any, "Mouse of very little brains!" It probably
                won't make any difference, but then, again, it might!

                ------------------
                Mike Luther
                [email protected]
                Mike Luther
                [email protected]

                Comment


                  #9
                  Well,

                  I do have a mouse/keyboard switch at home so I have disconnected it and there is no change (even after a couple of reboots)
                  I tested on my work system and the mouse can select text from the dos but the mouse can't select menus. If I bring the dos winder full screen then I can select and everything is fine but when I run something, just like at home, PB freezes.

                  grrrrrr




                  ------------------
                  Paul Dwyer
                  Network Engineer
                  Aussie in Tokyo

                  Comment


                    #10
                    Paul, it still sounds like the settings in Mouse section of the Misc tab in the Properties dialog of the DOS window have the Exclusive Mode and/or Quick Edit modes are disabled.

                    Please try enabling both settings and retry in Windowed mode...


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

                    Comment


                      #11
                      Lance,

                      Those setting do effect whether the mouse can effect the menu's or not but not the crash.

                      I have done a couple of more tests, after I run a test app then hit a key to return to my source code I'm fine even if I move the mouse. It's when I click the mouse somewhere like to put the curser somewhere) that it freezes and I have to kill the cmd prompt process.

                      has this not happened to anyone else?

                      ------------------
                      Paul Dwyer
                      Network Engineer
                      Aussie in Tokyo

                      Comment


                        #12





                        ------------------
                        Paul Dwyer
                        Network Engineer
                        Aussie in Tokyo

                        Comment


                          #13
                          Does this happen with any app loaded into the IDE, or just a specific app?

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

                          Comment


                            #14
                            Any app,

                            The last one I tried was...

                            Print "Hello"

                            that was enough to kill it after a RUN then a mouse click once the source code reappeared.

                            ------------------
                            Paul Dwyer
                            Network Engineer
                            Aussie in Tokyo

                            Comment


                              #15
                              How are you launching PB.EXE? From the command-line? If so, which command interpreter is running (CMD.EXE or COMMAND.COM)? Are you using the default AUTOEXEC.NT and CONFIG.NT files? If so, try disabling the DPMI and other drivers/services in those files and try again.

                              (The .NT files are usually located in \WINNT\SYSTEM32)

                              IHTH.

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

                              Comment

                              Working...
                              X
                              😀
                              🥰
                              🤢
                              😎
                              😡
                              👍
                              👎