Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Product Lifecycle
  3. Collaboration / Beta Testing
  4. Windows 2000 bug candidate

Windows 2000 bug candidate

Scheduled Pinned Locked Moved Collaboration / Beta Testing
helpsharepointcomtestingbeta-testing
4 Posts 3 Posters 16 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    Joaquin M Lopez Munoz
    wrote on last edited by
    #1

    I'm working for a client in a small app that automatically performs some dial-up stuff. During the development of the program, we ran into strange behaviors under Windows 2000 (and also XP): after much investigation we've come to a temptative conclusion that Windows 2000 dial-up component has the following bug: If several modems are installed on the same COM port and a dial-up connection is set to use one of them, the modem that was installed last is used regardless of the selection. Altough the problem arose as part of the execution of a program, we think we can also reproduce it manually, without interference from third parties products. SPs seem not to solve anything. Windows XP seems also to be affected by this problem. The weird thing about this bug (candidate) is that I've found nothing related to it or indicating its ocurrence in the Internet, MSDN or Usenet. This kind of strikes me, as the bug is rather severe. The client is a little suspicious about this, and a confirmation of it being a bug would save my life. What I kindly request from all of you who have some time spare and the wish to collaborate is that you try to perform the following test to determine if the bug shows in your particular OS, SP and machine scenario. The test goes as follows.

    1. In a Windows 2000 (or XP) machine, install manually two different modems on the same COM port. The modems will preferrably be chosen amongst the predefined list offered by the system. It is not important that you have any modem attached to the COM port. We will call the modem installed first and last A and B, respectively.
    2. Go to the Control Panel->Modems and click on Properties for modem A. Select the modem loggin option on.
    3. Do the same for modem B.
    4. Go to Dial-up connections and create a new dial-up entry that uses modem A. All other parameters are irrelevant, choose whatever you like.
    5. Try to connect using this dial-up entry. Of course the connection won't succeed (the modem is not even attached to the port), let it fail.
    6. Inspect the modem logs for both modem A and B. If the bug shows, you will see that it's the modem B log that has some input, instead of modem A.

    If you do this test, and the bug shows, please send me an email collecting as much info as you can about your testing scenario: OS, SP, machine, drivers chosen, you know. If the bug does not show, I'm also interested in knowing ;) If this finally happens to be a bug I'll try to report it to Microsoft: without some backup data like thi

    P L 2 Replies Last reply
    0
    • J Joaquin M Lopez Munoz

      I'm working for a client in a small app that automatically performs some dial-up stuff. During the development of the program, we ran into strange behaviors under Windows 2000 (and also XP): after much investigation we've come to a temptative conclusion that Windows 2000 dial-up component has the following bug: If several modems are installed on the same COM port and a dial-up connection is set to use one of them, the modem that was installed last is used regardless of the selection. Altough the problem arose as part of the execution of a program, we think we can also reproduce it manually, without interference from third parties products. SPs seem not to solve anything. Windows XP seems also to be affected by this problem. The weird thing about this bug (candidate) is that I've found nothing related to it or indicating its ocurrence in the Internet, MSDN or Usenet. This kind of strikes me, as the bug is rather severe. The client is a little suspicious about this, and a confirmation of it being a bug would save my life. What I kindly request from all of you who have some time spare and the wish to collaborate is that you try to perform the following test to determine if the bug shows in your particular OS, SP and machine scenario. The test goes as follows.

      1. In a Windows 2000 (or XP) machine, install manually two different modems on the same COM port. The modems will preferrably be chosen amongst the predefined list offered by the system. It is not important that you have any modem attached to the COM port. We will call the modem installed first and last A and B, respectively.
      2. Go to the Control Panel->Modems and click on Properties for modem A. Select the modem loggin option on.
      3. Do the same for modem B.
      4. Go to Dial-up connections and create a new dial-up entry that uses modem A. All other parameters are irrelevant, choose whatever you like.
      5. Try to connect using this dial-up entry. Of course the connection won't succeed (the modem is not even attached to the port), let it fail.
      6. Inspect the modem logs for both modem A and B. If the bug shows, you will see that it's the modem B log that has some input, instead of modem A.

      If you do this test, and the bug shows, please send me an email collecting as much info as you can about your testing scenario: OS, SP, machine, drivers chosen, you know. If the bug does not show, I'm also interested in knowing ;) If this finally happens to be a bug I'll try to report it to Microsoft: without some backup data like thi

      P Offline
      P Offline
      Paul Watson
      wrote on last edited by
      #2

      Just curious, but why would you want more than one modem on the same com port? Just curious... I will see if I can get our server techy to go through the steps you mentioned on a test machine and see what happens. regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Martin Marvinski wrote: Unfortunatly Deep Throat isn't my cup of tea Do you Sonork? I do! 100.9903 Stormfront

      J 1 Reply Last reply
      0
      • P Paul Watson

        Just curious, but why would you want more than one modem on the same com port? Just curious... I will see if I can get our server techy to go through the steps you mentioned on a test machine and see what happens. regards, Paul Watson Bluegrass Cape Town, South Africa "The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge Martin Marvinski wrote: Unfortunatly Deep Throat isn't my cup of tea Do you Sonork? I do! 100.9903 Stormfront

        J Offline
        J Offline
        Joaquin M Lopez Munoz
        wrote on last edited by
        #3

        I agree with you that the situation is not so common. The app is intended to work for a variety of different modems (actualliy GPRS mobile phones), so I've got all of the drivers installed on my testing machine and switch phones to check that all of them are handled properly. That's why in my world it's nor unusual to have five or more phones at my disposal to connect to the computer :) Regards Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

        1 Reply Last reply
        0
        • J Joaquin M Lopez Munoz

          I'm working for a client in a small app that automatically performs some dial-up stuff. During the development of the program, we ran into strange behaviors under Windows 2000 (and also XP): after much investigation we've come to a temptative conclusion that Windows 2000 dial-up component has the following bug: If several modems are installed on the same COM port and a dial-up connection is set to use one of them, the modem that was installed last is used regardless of the selection. Altough the problem arose as part of the execution of a program, we think we can also reproduce it manually, without interference from third parties products. SPs seem not to solve anything. Windows XP seems also to be affected by this problem. The weird thing about this bug (candidate) is that I've found nothing related to it or indicating its ocurrence in the Internet, MSDN or Usenet. This kind of strikes me, as the bug is rather severe. The client is a little suspicious about this, and a confirmation of it being a bug would save my life. What I kindly request from all of you who have some time spare and the wish to collaborate is that you try to perform the following test to determine if the bug shows in your particular OS, SP and machine scenario. The test goes as follows.

          1. In a Windows 2000 (or XP) machine, install manually two different modems on the same COM port. The modems will preferrably be chosen amongst the predefined list offered by the system. It is not important that you have any modem attached to the COM port. We will call the modem installed first and last A and B, respectively.
          2. Go to the Control Panel->Modems and click on Properties for modem A. Select the modem loggin option on.
          3. Do the same for modem B.
          4. Go to Dial-up connections and create a new dial-up entry that uses modem A. All other parameters are irrelevant, choose whatever you like.
          5. Try to connect using this dial-up entry. Of course the connection won't succeed (the modem is not even attached to the port), let it fail.
          6. Inspect the modem logs for both modem A and B. If the bug shows, you will see that it's the modem B log that has some input, instead of modem A.

          If you do this test, and the bug shows, please send me an email collecting as much info as you can about your testing scenario: OS, SP, machine, drivers chosen, you know. If the bug does not show, I'm also interested in knowing ;) If this finally happens to be a bug I'll try to report it to Microsoft: without some backup data like thi

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          Hi Joaquín, I had the same problem some time ago

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups