Bugs in Trial Version 1.0.0.5

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • WPhyer
    Forum Member
    • Nov 2002
    • 3

    Bugs in Trial Version 1.0.0.5

    I've been trying to evaluate TrueUpdate Version 1.0.0.5 trial and I'm running into some "bugs".

    The first:
    In the Client Configuration Utility, when building the Build Status dialog box appears. After it's finished, I have the option to Save. This options fails. It appears that your program things the file name I'm saving to, i.e., Build.txt is a directory. When running my file monitor, I get a FAILURE when ClientConfig.exe tries to open directory c:\temp\build.txt. I decided to create the Build.txt file using notepad to see what happens. Your program deletes the file.

    The second bug is a bit more serious. I'm testing on my local machine using a local web server (IP: 127.0.0.1). In the client setup, I've set the Server File Location Properties: HTTP URL to: http://127.0.0.1/trueupdate/QW-TrueUpdate.uif Port: 80

    When I run the Update.exe, it's trying to access IP: 207.46.230.220. NSLOOKUP sees this address as microsoft.com, which I blocked. I could only get the update to work once I unblocked that IP. Why is your software accessing microsoft's web site?
  • Brett
    Indigo Rose Staff Member
    • Jan 2000
    • 2000

    #2
    Re: Bugs in Trial Version 1.0.0.5

    It does that to make sure that you are connected to the Internet since you gave it a URL to update from. The only reliable way that we could detect an internet connection is to try to connect to some Web site on port 80. We chose Microsoft because if their Web site is down it probably means that the world has ended and there is no point in trying to update your software [img]/ubbthreads/images/icons/smile.gif[/img]

    Seriously, though, that is why we do things that way. If you give it a local path to check, it will not try to check the Internet connection at all.

    As far as the save bug goes, we will look into that.

    Comment

    • WPhyer
      Forum Member
      • Nov 2002
      • 3

      #3
      Re: Bugs in Trial Version 1.0.0.5

      That's twisted (and flawed). Why would you go to a 3rd party web site to check for the internet connection, especially Microsoft's? Are they aware that you have embedded their domain name into your distributed program and you're using their site as an "acid test"?

      As a programmer your logic boggles the mind. If I gave a URL to update from, why not test for a connection to THAT URL instead? Or at the very least, if you're going to hard code, why not hard code the indigorose.com URL? Why not look for the DNS server? There's plenty of other options available and yet you took the lazy way out (which will and has caused problems).

      Essentially, you've hard-coded your program to rely 100% on the hopes that Microsoft's web server is up and running. If it's not (and no the world has not come to an end...) , then it doesn't matter whether the URL I'm trying to connect to is there or not, you're program will fail the attempt. So, humor me... why is this a good method?

      Anyway, I find this rather ironic. Your FAQ says you don't have any external run-time dependencies and yet, you've coded your software to be dependent on microsoft.com.

      If I was in your position, I'd probably dissasemble the InternetGetConnectedState API call from wininet.dll and take the chunk of code that determines the connection state, thus removing any dependency on wininet.dll or IE4+.


      Comment

      • Brett
        Indigo Rose Staff Member
        • Jan 2000
        • 2000

        #4
        Re: Bugs in Trial Version 1.0.0.5

        First of all, thanks for having a sense of humor. That's fantastic to see [img]/ubbthreads/images/icons/smile.gif[/img]

        I was looking at the source code today and we do run a quick check on microsoft.com as I mentioned before just to make sure a connection is there. I think a better idea would be to first check for a connection to the cite you are downloading from. I will make sure that gets changed for the next version.

        From your message I take it that you are quite a programmer. Please do pass along any source code that you think would improve our product.

        Comment

        • WPhyer
          Forum Member
          • Nov 2002
          • 3

          #5
          Re: Bugs in Trial Version 1.0.0.5

          You can't be a serious coder all the time... and I have comments to prove it [img]/ubbthreads/images/icons/smile.gif[/img]

          I'm glad you agree that it'd be better to check the site you're downloading from as a better method to determine your net connection. As you've could of guessed, I'm not a fan of Microsoft. It's just that my livelyhood (read: paycheck) depends on writing code that uses their OS.

          I can see that the humor runs deep at your place. Do you really think I'd just "donate" my source code? Tell ya what... When I finish my own proprietary internet updating program, I'll send ya a screen-shot. [img]/ubbthreads/images/icons/smile.gif[/img]

          Seriously though, your product was almost on the mark. There were just a few things that I needed more control over that TrueUdate couldn't offer.

          Comment

          Working...
          X