TCP/IP CP reported error 31

[Ace Fekay [MVP]]

In

That's easy for *you* to say ;-)

Hokay - I've purchased a licensed version of UltraISO and although
I've managed to burn five new copies of my original W2KPro disc, I
haven't been able to figure out how to get the i386 folder to update
using ROLLUP 1 FOR WINDOWS 2000 SP4 file:
C:\703e7a1af4906c3f23\update.

What I'm doing is this:

Using UltraISO to "Make A CD/DVD Image" from the original W2KPro disc
and putting it into the default directory on my C drive. Then I'm
saving it.

Then I'm extracting the "i386" folder directly onto my C drive without
first creating a new folder so that i386 and all its folders & files
are now located in C:\i386.

Then I'm using UltraISO to delete "i386" from the folder I've
transferred to my hard drive from the original CD.

Then I'm going into C:\703e7a1af4906c3f23\update, opening the "update"
folder, launching "update.exe" and following all the prompts.

After the update is completed, I use UltraISO to "add" i386 from the C
drive, save, ask UltraISO to "Burn" the changed image onto a blank CD
using Nero and cross my fingers.

Then I launch the CD and get the same message telling me that I can't
update SP4 with an earlier version.

Since this isn't what I'm trying to achieve I've gone back and
compared the dates/times the i386 files were created. It appears that
the SP4 update isn't integrating the update into the folder I've ISO'd
and replaced on the copied CD. So I must be leaving out a step or two
along the way.

In any event, I've learned one hell of a lot, but obviously have
further to climb on this particular learning curve. As always, any
suggestions would be appreciated. Cheers, b

You can't use that C:\703e7a1af4906c3f23\update folder, unless you didn't
provide the right switches for update.exe. What I do with the service pack,
is I will download the service pack, put it somewhere, then i run the
service pack executable as such
w2k2p4.exe /x
The /x will just extract the files into a location that you choose. From
that location, in a command prompt, run:
update /s:c:\
That will look for the i386 folder and then integrate it. Once done, you
would rt-click on the iso name in UltraISO and paste it. It will then copy
the i386 folder off your C drive and paste it into the actual ISO image of
your cdrom. THen click on save to save the new image.

Here's a more specific updated steps:

1. Use a tool such as UltraISO to ISO the current CD.

2. Once the ISO is complete, open the ISO with UltraISO.

3. Copy the i386 folder out of the ISO to a location on your drive, such as
C:\i386.

4. Then delete the i386 folder from the ISO image in UltraISO. Deleting it
will remove the i386 from the ISO. Keep UltraISO open.

5. Then download SP4 (or whatever service pack for whatever operating
system), and save it somewhere, such as c:\sp4 (or whatever sp it is).

6. We now need to extract the service pack files from the downloaded service
pack executable. To do that, open a cmd prompt, navigate to the location
where you saved the service pack you just downloaded, and then run:
servicepackname.exe /x
It will then ask you where to extract it. Provide c:\sp4 (or where you like
to send it).

7. Then run SP4's update as such (assuming i386 is located at c:\i386):
update /s:c:
In the aboce command I provided, the updater will look for an "i386" folder
under the C: drive and will proceed to integrate the service pack into it.

8. Once the integrationg is completed, then rt-click the i386 folder from
c:\i386, choose copy, then go to image in UltraISO that you still have
opened, and choose to paste it on C: drive in the image. It will now copy
the the newly integrated i386 into the ISO in it's original location.

9. Choose Save in UltraISO to save the altered image.

10. Then burn it.

I hope that's better.

Ace

 

[Bob Feigel]

OS: WIN2000Pro
Pentium III & plenty of system resources to spare
No hardware conflicts

Problem: After I've accessed my dial-up connection more than four or
five times in one session, I get the following error message:

"Checking network protocol connections...

TCP/IP CP reported error 31: A device attached to the system is not
functioning."

Thanks for all your help, Ace. But the problem seems to have
disappeared (fingers crossed).

When I said earlier that I hadn't installed any new software before
the problem started, I'd forgotten that I'd just updated my ZoneAlarm
Pro firewall software. The problem disappeared after I updated it
again a couple of days ago. So it could be that something in the
previous version caused the problem. I also think I may have simply
updated the previous version, while this time I did a clean install.

Live and learn ... bob

"Only two things are infinite, the universe and human
stupidity, and I'm not sure about the former." - Albert Einstein


Wax-up and drop-in on surfing's Golden Years: http://www.surfwriter.net

 

[Ace Fekay [MVP]]

In

Thanks for all your help, Ace. But the problem seems to have
disappeared (fingers crossed).

When I said earlier that I hadn't installed any new software before
the problem started, I'd forgotten that I'd just updated my ZoneAlarm
Pro firewall software. The problem disappeared after I updated it
again a couple of days ago. So it could be that something in the
previous version caused the problem. I also think I may have simply
updated the previous version, while this time I did a clean install.

Live and learn ... bob

Wow, that's a very *minor* oversight.

If I knew it was ZA, I would have mentioned it's not a recommended software,
especially if the machine is part of an AD network. It's a known issue. And
when you try to remove it, it doesn't uninstall properly leaving numerous
files behind and a service running that *will* hinder a machine's
functionality. ZA is NOTORIOUS for this. You wouldn't believe how many folks
have problems due to ZA.

Cannot Access Share or Files When ZoneAlarm Is Installed:
http://support.microsoft.com/?kbid=302951

And what's funny, removing it in Add/Remove doesn't completely remove it and
you have to follow this article to manually remove it:
http://nh2.nohold.net/noHoldCust25/Prod_1/Articles55646/CompleteUninstallNonNT.html

I hope that helps for future reference.

Ace

 

[Bob Feigel]

In

Wow, that's a very *minor* oversight.

If I knew it was ZA, I would have mentioned it's not a recommended software,
especially if the machine is part of an AD network. It's a known issue. And
when you try to remove it, it doesn't uninstall properly leaving numerous
files behind and a service running that *will* hinder a machine's
functionality. ZA is NOTORIOUS for this. You wouldn't believe how many folks
have problems due to ZA.

Cannot Access Share or Files When ZoneAlarm Is Installed:
http://support.microsoft.com/?kbid=302951

And what's funny, removing it in Add/Remove doesn't completely remove it and
you have to follow this article to manually remove it:
http://nh2.nohold.net/noHoldCust25/Prod_1/Articles55646/CompleteUninstallNonNT.html

I hope that helps for future reference.

Ace

Thanks for those references. I had a real runaround with ZAP a couple
of years ago and ended up phoning the guy who ran the whole show,
Gregor Freund, and complaining. That got the results I'd been trying
to get from their hopeless online support team (although he
flogged-off the company to someone else shortly after that).

Bottom line - I had to manually remove all those pesky files that
uninstall doesn't touch. Since I'd paid for a three year license I'm
still using ZAP (which also has its good points) until the license
expires.

Fortunately, I also have a file with ZAP's step-by-step manual
uninstall procedure somewhere. Cheers, Bob





"Only two things are infinite, the universe and human
stupidity, and I'm not sure about the former." - Albert Einstein


Wax-up and drop-in on surfing's Golden Years: http://www.surfwriter.net

 

[Ace Fekay [MVP]]

In

Thanks for those references. I had a real runaround with ZAP a couple
of years ago and ended up phoning the guy who ran the whole show,
Gregor Freund, and complaining. That got the results I'd been trying
to get from their hopeless online support team (although he
flogged-off the company to someone else shortly after that).

Bottom line - I had to manually remove all those pesky files that
uninstall doesn't touch. Since I'd paid for a three year license I'm
still using ZAP (which also has its good points) until the license
expires.

Fortunately, I also have a file with ZAP's step-by-step manual
uninstall procedure somewhere. Cheers, Bob

So you've had the ZA experience. Intgeresting.

Cheers!