1 Machine With 2 OS- No Connection On 1 OS

edited February 2007 in Science & Tech
There's 2 OS installed in the same hard drive. Windows XP Pro (English) and Windows XP Home Edition (Spanish). I can browse the internet on the XP Pro OS but not on the XP Spanish OS, I can't even install the cable modem or anything. The OS works fine, I just can't get an internet connection on the Spanish OS. It's a 20GB drive on an old junky Compaq machine 1.5Ghz. Any help on why I can't browse the internet on the English OS but not the Spanish OS?

Comments

  • RWBRWB Icrontian
    edited February 2007
    When you say you're installing a cable modem to the Spanish XP, I figure you mean you're plugged into a cable modem via USB? If it's Ethernet, you don't need to install crap. On the Spanish XP, does the device manager show you an Ethernet card, or networking device? What is it called, or do you see "Unknown Device" anywhere in the Device Manager?

    Give some more specifics, because right now I have 1000 questions. Most notably, any errors you're getting, how you're connected, etc...
  • edited February 2007
    I have the modem connected via an ethernet cable and so based upon what you're telling me, I don't have to install anything else. Right now I'm on the XP Pro OS on the same machine typing back a reply, I have to get back to you in a few mins (if you're still around) and check the device manager on the Spanish OS and see if it shows an ethernet card or networking device.
  • FoldingAddictFoldingAddict Montgomery, AL
    edited February 2007
    I had this same problem with two different machines. The internet worked fine on the one running XP Pro, but the machine running XP Home couldn't get online for anything. Both machines were identical in hardware and both XP installs were a couple of hours old. The problem turned out to be fixed by service pack 2 being installed on the Home Edition computer.

    So I guess if everything else fails, download service pack 2 on the XP Pro partition and then run the install on the XP Home partition and see what happens. Unless of course XP Home is already running service pack 2, then I don't know what else it could be besides drivers.

    ~FA
  • RWBRWB Icrontian
    edited February 2007
    I'm on allllll night :p
  • edited February 2007
    Well I'm back, I checked and um... Both have SP2 so hmmm, I took a bit because I'm not familiar with the OS in another language other than english but I nailed it and for what I saw, it shows (1) 1394 Network Adapter and (1) Intel(R) PRO/100 VM Network Connection (same as this OS, just in spanish). Any ideas? :confused:
  • RWBRWB Icrontian
    edited February 2007
    OK so it sees the NIC(Intel), do this now... check in "Network Connections" and see what that "Local Area Connection" says. Does it say connected? If so, open it up, this should bring up the status window, goto the "Support" tab and check your IP and report back.

    If it says Network Cable Unplugged, or Limited or no Connectivity. It could be a bad Ethernet Cable or maybe a Duplex setting. You can check your Duplex by right clicking on the LAN connection or double left clicking which should bring up the LAN Properties window, click on "Configure" in the "General" tab, then goto "Advanced" tab. In here is a list of properties, one labeled "Link Speed & Duplex" or something of that nature, select it and report back what it's set to.
  • edited February 2007
    When I open Network Connections, NOTHING SHOWS UP!!! :confused:
  • RWBRWB Icrontian
    edited February 2007
    Like... "nothing" nothing, or nothing at all? ;D

    That sucks man, I can't say much on why that would happen except that maybe this problem is bigger than I figured.

    You could try "ipconfig" from a command prompt. You can pull a command prompt from the run command, and type in "cmd" press OK. That'll bring up a black box, just type in "ipconfig" and hopefully it has something good/useful to say.
  • edited February 2007
    RWB wrote:
    Like... "nothing" nothing, or nothing at all? ;D

    That sucks man, I can't say much on why that would happen except that maybe this problem is bigger than I figured.

    You could try "ipconfig" from a command prompt. You can pull a command prompt from the run command, and type in "cmd" press OK. That'll bring up a black box, just type in "ipconfig" and hopefully it has something good/useful to say.
    Well...
    "I'll Be Back..."
    :cool:
  • edited February 2007
    0.0.0.0
    0.0.0.0

    That's all I saw after I did the ipconfig command... nothing else...
  • RWBRWB Icrontian
    edited February 2007
    DumNDuMMer wrote:
    0.0.0.0
    0.0.0.0

    That's all I saw after I did the ipconfig command... nothing else...

    Gonna have to goto my thinking seat for this one... brb :bigggrin:
  • RWBRWB Icrontian
    edited February 2007
    OK go back into the device manager and make sure the Intel Pro 100 VM nic isn't disabled. And tell me what the icon looks like next to it. It should just be simply a green PCI card like icon. If it has a red "X" or a yellow "!" then it might need the driver reinstalled, or simply disabled.
  • edited February 2007
    Nothing, it's just green
  • RWBRWB Icrontian
    edited February 2007
    I'm spent, no idea. Probably something simple too...
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited February 2007
    Hello DumNDuMMer

    Are you using a third party boot manger? If so, which one? (or are you using Windows XP multi-boot?)

    According to your post # 8, your NIC is not showing up in Network Connections, right?

    We know that everything is ok as far as hardware goes. Otherwise it wouldn't work on the other build in your dual-boot system. So, we're down to a drivers issue. Let's approach it that way and see what happens. Please, do the following:

    If possible, configure you multi-boot manager to show the Spanish-Language build's OS partition while you're working in English-Language build.
    • (A) IDENTIFY THE NIC DRIVER
      1. CONTROL PANEL -> SYSTEM -> HARDWARE -> DEVICE MANAGER -> NETWORK ADAPTERS
      2. Right-click on the [Intel(R) PRO/100 VM] NIC
      3. Choose PROPERTIES
      4. Click the DRIVERS tab
      5. Click the DRIVER DETAILS button
      6. Make note of the driver file(s) and its path.
        • e.g. c:\windows\system32\drivers\[driverfilename].sys
      7. Cancel out of there until you've closed DEVICE MANGER
    • (B) CONFIGURE FOLDER OPTIONS TO REVEAL HIDDEN & SYSTEM FILES
      1. Open Windows Explorer
      2. Click on TOOLS
      3. Click on FOLDER OPTIONS
      4. Click on the VIEW tab
      5. Configure according to the attached pic
      6. Click OK
    • (C) NAVIGATE TO THE DRIVER FILE VIA WINDOWS EXPLORER
      1. Double-click on MY COMPUTER
      2. Double-click on the WINDOWS directory
      3. Double-click on the SYSTEM32 directory
      4. Double-click on the DRIVERS directory
      5. Click on VIEW and choose DETAILS
      6. Click on the NAME column header to sort the list in alphabetical order
      7. Find the driver you made note of earlier
    • (D) If you are able to view the Spanish-Language OS partition while in the English-Language build, please, do the following:
      1. Find the same file in the same location on the Spanish-Language build
      2. Rename the file by appending .OLD to the end of it.
        • e.g. [driverfilename].sys.old
      3. Now, copy the file from the English-Language build to that location
      4. Exit the English-Language build and boot into the Spanish-Language build.
      5. See if your NIC shows up in NETWORK CONNECTIONS now.
      6. If it does, see if you can connect to the Internet now.
    • (E) If you are unable to view the Spanish-Language OS partition while in the English-Language build, please, do the following:
      1. Right-click on the driver file
      2. Choose COPY
      3. If you have a volume (drive) that is common to both OS builds, copy the file there.
      4. If not, save the file to a pen drive or some other external media that you can access while in the Spanish-Language build.
      5. Exit the English-Language build and enter the Spanish-Language build in SAFE MODE WITHOUT NETWORKING.
      6. Configure the FOLDER OPTIONS the same as you did on the English-Language build.
      7. Navigate to the same driver file location via Windows Explorer.
      8. Rename the file by appending .OLD to the end of it.
        • e.g. [driverfilename].sys.old
      9. Now, copy the file that you got from the English-Language build to that location
      10. Reboot back into the Spanish-Language build in NORMAL MODE.
      11. See if your NIC shows up in NETWORK CONNECTIONS now.
      12. If it does, see if you can connect to the Internet now.
  • edited February 2007
    Nothing showed up and no connection yet :confused:
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited February 2007
    DumNDuMMer wrote:
    Nothing showed up and no connection yet :confused:
    • EXACTLY which steps did you follow?
    • Just refer to the steps you took by "GROUP (A-E)" and Step Numbers w/in each group. (see post # 16)
    • What was the file name that you replaced and where was it located?

    EDIT://
    Is the Intel NIC built into the motherboard or is it an expansion card that is plugged into the motherboard?
  • edited February 2007
    I did not have to do it in Safe Mode as I can browse through both drives while in 1 OS and vise-versa.

    This is the file I located
    C:\WINDOWS\system32\DRIVERS\e100b325.sys
    I renamed the old file from drive D, then
    I copied it and pasted the file from drive C on to D: drive
    Having now the old file, and the newly copied file in drive D
    D:\WINDOWS\system32\DRIVERS\e100b325.sys
    D:\WINDOWS\system32\DRIVERS\e100b325.sys.old

    The Intel NIC plugs into the motherboard, just like everything else plugs into the motherboard.
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited February 2007
    Thank you D'. Perfect!
    • (F) While in the SL (Spanish-Language) build in NORMAL mode, uninstall the NIC in device manager.
      1. CONTROL PANEL -> SYSTEM -> HARDWARE -> DEVICE MANAGER -> NETWORK ADAPTERS
      2. Right-click on the [Intel(R) PRO/100 VM] NIC
      3. Choose UNINSTALL
      4. Click OK until you have exited DEVICE MANAGER
      5. DO NOT let it reboot
    • (G) Next, boot into the EL (English language) build.
    • (H) Perform and advanced search on drive D (ONLY).
      1. (that is, include in the search of drive "D" System and Hidden files)
      2. Search for the file name: e100b325.sys
      3. Rename all instances of this file name the same way you did previously (by appending the file name with .OLD)
      4. Delete the D:\WINDOWS\system32\DRIVERS\e100b325.sys file
      5. Once again, make a copy of the file off of your EL build and place it in a common volume or on external media that you can access while in the SL build.
    • (I) Now, reboot and get into the system BIOS
      1. You can usually enter the BIOS by hitting either: DELETE or F1 or F2 or F10 right after the system is turned on.
      2. If you need help w/ this just let us know.
      3. DISABLE the ONBOARD (integrated) NIC.
      4. Save the settings and exit the BIOS
    • (J) Boot back into the SL build. (DO NOT boot into the EL build w/ the NIC disabled.)
      1. Give it time to finish booting to the desktop of the SL build.
      2. Now, reboot and get back into the BIOS
      3. While in the BIOS, re-enable the onboard (integrated) NIC
      4. Save the settings and exit the BIOS
    • (K) Boot back into the SL build.
      1. The NIC will be detected as new hardware
      2. Direct the New Hardware Install Wizard to the driver file located on the external media or on the common volume where you copied it to.
        • DO NOT direct the Wizard to your EL build partition for the driver file.
      3. Reboot - get back into the SL build.
      4. Check Network Connections to see if the NIC shows up there now.
      5. If it does, check your Internet connectivity.
  • edited February 2007
    I don't think it's INTEGRATED but still I tried every single step as described hoping to get results... but unfortunately... no... Nothing...
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited February 2007
    DumNDuMMer wrote:
    ...I don't think it's integrated...
    That does make a difference.
    1. My intention was that you boot one time to your SL build after you had uninstalled its drivers in DEVICE MANAGER and disabled it in the BIOS. If the NIC was still installed, my little trick wouldn't have been able to work.
    2. Does the NIC plug into a *slot* on the motherboard or is it part of (integrated) into the motherboard?
    3. If it plugs into a slot on the motherboard, is there also a place to plug in your ethernet cable that is "integrated" into the motherboard? (this would be the onboard (integrated) NIC)
    4. If the NIC is a card that plugs into the motherboard, then what did you disable in the BIOS?
    5. Were you able to get into the BIOS?
    6. What motherboard do you have?
    7. Do you have another NIC you can install for now?
  • edited February 2007
    1. I'm not sure about the motherboard type but crucial.com says it's a Compaq HP-Compaq 077Ch Motherboard.

    2. The NIC plugs into a slot in the motherboard (motherboard has the slot, the card plugs into the slot)

    3. In the BIOS, I disabled the NIC
    4. I have like 2 or 3 more NIC I might be able to use

    What now?
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited February 2007
    DumNDuMMer wrote:
    ... 1. I'm not sure about the motherboard type but crucial.com says it's a Compaq HP-Compaq 077Ch Motherboard....
    • So, this is an HP-Compaq computer?
    • I should have asked. Sorry about that.
    • I just assumed it was a home-built DIY (do-it-yourself) system.
    • That's my fault. You didn't say anything that would lead me to believe that.
    • I just didn't ask the right questions.
      • So, what model no. is the computer?
    DumNDuMMer wrote:
    ...2. The NIC plugs into a slot in the motherboard (motherboard has the slot, the card plugs into the slot)...
    Ok. I'm clear now. I misunderstood you b4 and I made unfounded assumptions. I apologize, D', for any added confusion that might have caused.
    DumNDuMMer wrote:
    ...3. In the BIOS, I disabled the NIC...
    You disabled the onboard (integrated) NIC which wasn't working or being detected anyway, I don't believe.
    DumNDuMMer wrote:
    ...4. I have like 2 or 3 more NIC I might be able to use
    The problem is I don't want you to lose your Internet connection on your EL build. So, let's save that as a last resort.

    Following is post # 20 modified for a plugin (expansion card) NIC rather than an integrated (built-in) NIC. Please, follow these steps.
    • (F) While in the SL (Spanish-Language) build in NORMAL mode, uninstall the NIC in device manager.
      1. CONTROL PANEL -> SYSTEM -> HARDWARE -> DEVICE MANAGER -> NETWORK ADAPTERS
      2. Right-click on the [Intel(R) PRO/100 VM] NIC
      3. Choose UNINSTALL
      4. Click OK until you have exited DEVICE MANAGER
      5. DO NOT let it reboot
    • (G) Next, boot into the EL (English language) build.
    • (H) Perform an "advanced" search on drive D (ONLY).
      1. (that is, include in the search of drive "D" System and Hidden files)
      2. Search for the file name: e100b325.sys
      3. Rename all instances of this file name the same way you did previously (by appending the file name with .OLD)
      4. Delete the D:\WINDOWS\system32\DRIVERS\e100b325.sys file
      5. Once again, make a copy of the file off of your EL build and place it in a common volume or on external media that you can access while in the SL build.
    • (I) Shut down the computer
      • Remove the NIC from the motherboard
    • (J) Restart the computer and boot back into the SL build. (DO NOT boot into the EL build w/ the NIC removed.)
      1. Give it time to finish booting to the desktop of the SL build.
      2. Now, shut down the system again
      3. Re-install the NIC
      4. Re-start the computer and boot back into the SL build
    • (K) The NIC will be detected as new hardware.
      1. Direct the New Hardware Install Wizard to the driver file located on the external media or on the common volume where you copied it to.
        • DO NOT direct the Wizard to your EL build partition for the driver file.
      2. Reboot - get back into the SL build.
      3. Check Network Connections to see if the NIC shows up there now.
      4. If it does, check your Internet connectivity.
  • edited February 2007
    I'm such a moron, I thought I was working on one of my other machines who's Ethernet Card plugs into one of those slots on the motherboard so YOU WERE RIGHT when you said it was integrated onto the motherboard, so I WAS WRONG :confused: Although for some reason I think I did something wrong upon un-installing the NIC reinstalled it with the wrong driver ej: the EL drive! Now that I ACTUALLY bothered to LOOK carefully and see that it's INTEGRATED as you originally asumed, would uninstalling the NIC, restarting the pc, then loading the driver from an external source when loaded in the Spanish OS, would that help or do I just have to try it to find out?
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited February 2007
    DumNDuMMer wrote:
    I'm such a moron, I thought I was working on one of my other machines who's Ethernet Card plugs into one of those slots on the motherboard so YOU WERE RIGHT when you said it was integrated onto the motherboard, so I WAS WRONG :confused: Although for some reason I think I did something wrong upon un-installing the NIC reinstalled it with the wrong driver ej: the EL drive! Now that I ACTUALLY bothered to LOOK carefully and see that it's INTEGRATED as you originally asumed, would uninstalling the NIC, restarting the pc, then loading the driver from an external source when loaded in the Spanish OS, would that help or do I just have to try it to find out?
    That's ok. We've both made mistakes. That's just how it goes sometimes.
    1. Ok, so you DO NOT have another NIC installed in this computer (plugged into a slot on the motherboard) - is that correct?
    2. And you DISABLED the onboard NIC in the BIOS - is that correct?
    3. If so, have you RE-ENABLED the NIC in the BIOS?
    4. Go back and look in NETWORK ADAPTERS in DEVICE MANAGER (of the SL (Spanish Language) build)
    5. Tell me EXACTLY what you see there, please.
  • edited February 2007
    This is what I see in when I open the Device Manager in Network Adapters

    Network Adapter 1394
    Intel(R) PRO/100VM

    If I uninstall one, Windows usually detects it and reinstalls it on it's own without having to do a thing or give me time to use the file from the Drive which I can browse the internet.
  • PterocarpousPterocarpous Rosie the Riveter Lives On in CA, USA! New
    edited February 2007
    DumNDuMMer wrote:
    This is what I see in when I open the Device Manager in Network Adapters

    Network Adapter 1394
    Intel(R) PRO/100VM

    If I uninstall one, Windows usually detects it and reinstalls it on it's own without having to do a thing or give me time to use the file from the Drive which I can browse the internet.
    Please, answer the questions in the previous post. It is imperative that we understand each other clearly in order to avoid any further miscommunications.

    2ndly, it is very important that you follow the instructions as I gave them to you. There is a reason that the device is being redected again before you get a chance to change the driver. Please, follow the instructions as outlined in post #20 and this will not happen.
Sign In or Register to comment.