PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bob Wright <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Thu, 24 Aug 2000 11:22:55 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (79 lines)
At 11:39 PM 08/23/2000 , you wrote:
>A friend of mine is having problems with connecting to his ISP.  I've been
>trying to help him over the phone, but it's been almost impossible!
>Here's the story:
>
>He was connected thru his ISP (Concentric), browsing the internet, PC
>locked up and had to reboot.  After reboot, could no longer dial out and Windows
>gave him some type of error message about dial up networking not working (?).  He
>ended up calling the ISP, they had him look in Network Properties.  No dial up
>adapter found.  When the tech at the ISP had him delete everything there and try
>to REINSTALL the dial up adapter, the computer locked up again.  Since dial
>up networking is installed, each time he reboots windows, he gets the message
>that Windows must install the dial up adapter.  Yet, each time he tries to do
>this, the computer locks up and won't complete.  He does get a message that says
>that Windows cannot install the dial up adapter.  We eventually got to the Add/
>Remove programs/Windows Setup tab and deleted all the dial up networking
>stuff under Communications.  That cured the problem of Windows always trying to
>install the dial up adapter.  Go back and try to reinstall all the stuff
>under Communications from the Windows Setup tab again.  Still no luck installing
>the dial up adapter.  He even tried to reinstall Windows over the existing one
>but got hung up again when he got to the part where Windows Setup asks him to
>choose a Client.  It won't let him choose any of the clients (such as windows
>family logon), and won't let the install continue.  There IS a 3com ethernet card
>in this machine, but it's been disabled in Device Manager since he doesn't
>use it for anything.
>He has an IBM clone, 550 mhz, 4 GB HD, Creative ModemBlaster USB Modem,
>128 MB RAM.
>
>Could the dial up adapter files and or dial up networking files be
>corrupt?  If so, wouldn't the reinstall of Windows fix that?  Or would he have to
>reformat and reinstall??  We just can't seem to get past the installation of the
>dial up adapter.  Since he's long distance, I can't SEE what is happening, so I
>hope I've done a reasonable job of explaining the problem.  Can anyone offer
>any suggestions?



I hate giving this advice, as it rarely is the problem, but first check
the system for a virus.

Second, be sure he has run scandisk through the hard drive to correct
any errors in data on the hard drive, (but, I would assume since he has
already attempted to load Windows that was done at least once).

Third, in control panel,  under Network properties, remove all drivers listed.

Fourth, open Add/Remove software in Control panel, the Windows setup
tab.  Now, under Communications, uncheck everything to uninstall it all.

Next, remove the driver for his modem and then reinstall it, being sure
that the IRQ for both the Com port used and modem are not shared with
any other device, (check in Device Manger after the modem has been
reinstalled).

Now, after the system has been rebooted, he should be able to fresh
install Windows Dialup Networking.

I have a hunch that either his modem device drivers are in conflict, that
he still has drivers installed in Network Properties or his registry has
be altered by something on the system to conflict with his Network.

The final solution maybe above, but it also may include removing the
unused Network Card and/or formatting his hard drive with a fresh
install of Windows.  I have found when people say, "Oh...  I was just
browsing the Web and the system crashed!"  They typically have
installed some software prior to this event, that they have forgotten
to mention.  This software could have worked, sort of, for a time, only
to finally conflict enough to cause the lockup event.  That is why you
may need to go to heroic efforts to solve this issue...  sorry, I do not
have an easier solution.


     Bob Wright
The NOSPIN Group

            Do you want to signoff PCBUILD or just change to
                    Digest mode - visit our web site:
                    http://nospin.com/pc/pcbuild.html

ATOM RSS1 RSS2