Announcement

Collapse
No announcement yet.

Dell XPS "anomalies"

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

  • Dell XPS "anomalies"

    I have had a Dell XPS 710 for a couple years now. Every once in awhile I'll run across something (usually a posted program) that just won't run. Sometimes I can find out why and every once in awhile it's just mysterious. "Oh well" I say and move on to greener fields.

    One of the things I ran across that doesn't work is "Beep". And just today I found another: "#Compiler PBWin 9 ". I recall (but can't find the post) Paul Squires having an problem with something along these lines as well

    Both of my bugs seem to be limited the XPS. The commands work on other machines without problems.

    At any rate I thought it might be worthwhile to start a list of such XPS PB compatibility "bugs" so others could refer to when "puzzled" and to add to if/when they run across any others. (and me to refer to when I forget, which will be by tomorrow morning if past history is any guide. {sigh})

    1) Beep - 'doesn't work - use WinBeep instead.

    2) #Compiler PBWin 9 - 'Must be remmed. Else program won't compile or run.

    3) #Compile Exe = - 'Must be remmed. Else program won't compile or run. '

    (Note the above is with 'PBWIN 9.01 - WinApi 05/2008 - XP Pro SP3)
    Last edited by Gösta H. Lovgren-2; 26 Apr 2009, 09:46 AM.
    It's a pretty day. I hope you enjoy it.

    Gösta

    JWAM: (Quit Smoking): http://www.SwedesDock.com/smoking
    LDN - A Miracle Drug: http://www.SwedesDock.com/LDN/

  • #2
    #compile exe works on my XPS

    I have a Dell XPS 630i, just about a year old. It exhibits some flaky behavior, but as far as I can tell #COMPILE EXE doesn't cause any issues.

    I'm new to trying to use PowerBasic; I bought PBWin 9.01 and PBForms 1.51. I used PBForms to create a user interface. When I open it in PBWin IDE, I see the #COMPILE statement. I've been compiling and executing and finding things don't work the way I want and fixing and compiling and executing with no issues I can attribute to the #COMPILE statement.

    Just thought I'd mention it.

    By the way, PBForms didn't produce a #COMPILER statement so I can't say anything about that.

    Comment


    • #3
      Originally posted by Steve Frye View Post
      I have a Dell XPS 630i, just about a year old. It exhibits some flaky behavior, but as far as I can tell #COMPILE EXE doesn't cause any issues.

      I'm new to trying to use PowerBasic; I bought PBWin 9.01 and PBForms 1.51. I used PBForms to create a user interface. When I open it in PBWin IDE, I see the #COMPILE statement. I've been compiling and executing and finding things don't work the way I want and fixing and compiling and executing with no issues I can attribute to the #COMPILE statement.

      Just thought I'd mention it.
      Glad you did. As a result of your post I just tried - #Compile Exe "t.exe" - again and it compiled fine. Dunno why I had problems before (had been trying to compile C&P'ed code from the forum so maybe there was a problem elsewhere in the code. But all I had to do was rem it out and it compiled fine otherwise.) but it's fine now.

      Thanks the headsup. I'll remove the exeption above.

      {Later} Oops, no "Edit" button on the post. Must be too old to edit.

      =======================================
      Let each man exercise the art he knows.
      Aristophanes
      =======================================
      Last edited by Gösta H. Lovgren-2; 18 May 2009, 08:37 PM. Reason: Edit button gone on post #1
      It's a pretty day. I hope you enjoy it.

      Gösta

      JWAM: (Quit Smoking): http://www.SwedesDock.com/smoking
      LDN - A Miracle Drug: http://www.SwedesDock.com/LDN/

      Comment


      • #4
        Gösta, I think what you are referring to is the issue that JellyFishPro editor had when putting a comment after the #COMPILE EXE objective statement.
        For example this would cause an issue:
        Code:
        #COMPILE EXE    'this line is a compiler directive
        I posted this issue on Paul Squires forum a long time ago. The underlying issue was that the JellyFishPro editor would assume anything after "#COMPILE EXE" would be the name of the exe to compile and execute. I think Paul has probably fixed this issue.

        .
        "I haven't lost my mind... its backed up on tape... I think??" :D

        Comment


        • #5
          Originally posted by William Burns View Post
          Gösta, I think what you are referring to is the issue that JellyFishPro editor had when putting a comment after the #COMPILE EXE objective statement.
          For example this would cause an issue:
          Code:
          #COMPILE EXE    'this line is a compiler directive
          I posted this issue on Paul Squires forum a long time ago. The underlying issue was that the JellyFishPro editor would assume anything after "#COMPILE EXE" would be the name of the exe to compile and execute. I think Paul has probably fixed this issue.

          .
          Quite right, William. I remember now. The line should have read:
          3) #Compile Exe = - 'Must not have a Remark on the same line if using JellyFishPro. Else program won't compile or run. '
          ===========================
          Writing is,
          By definition,
          An optimistic act."
          Micheal Cunningham (1952-)
          ===========================
          It's a pretty day. I hope you enjoy it.

          Gösta

          JWAM: (Quit Smoking): http://www.SwedesDock.com/smoking
          LDN - A Miracle Drug: http://www.SwedesDock.com/LDN/

          Comment


          • #6
            On the subject of Dell computers, we recently got an outta sight (for us) electric bill. Okay where's it all going?

            I have a Kill A Watt "tool"(?) that measures electric usage of anything plugged into it. So I decided to actually measure our major appliances one by one to try and track down where the kw's are going.

            When I measured the Dell XPS (on 24/7), it uses 200w when in use and around 130w when "asleep". Includes a 27" LCD monitor too and a couple USB's (external hard drive, etc.) Comes out to under $18 per month (@ 15c per kw). I thought it was using way higher than that.

            The Kill A Watt is a pretty cool tool. A little bigger than a couple cigarette packs. Measures voltage, amps, watts in use, total wattage used, time elapsed. About $30 IIRC. (Miles and miles better than the big old globe type meter with all the little wheels I used to use. {laughing})
            It's a pretty day. I hope you enjoy it.

            Gösta

            JWAM: (Quit Smoking): http://www.SwedesDock.com/smoking
            LDN - A Miracle Drug: http://www.SwedesDock.com/LDN/

            Comment

            Working...
            X