Wesley said:
You can try unregistering and regisering the following files.
Paste all of the following into the Start | Run box, one at a time...
regsvr32 /u Bitsprx2.dll
regsvr32 /u Bitsprx3.dll
regsvr32 /u Qmgr.dll
regsvr32 /u Qmgrprxy.dll
regsvr32 /u Winhttp.dll
regsvr32 Bitsprx2.dll
regsvr32 Bitsprx3.dll
regsvr32 Qmgr.dll
regsvr32 Qmgrprxy.dll
regsvr32 Winhttp.dll
regsvr32 Xpob2res.dll
The first 4 modules either don't exist or can't be found in my registry
- I didn't bother with the other 2 after noting that. I had also noted
the same prob when trying 2 of them from the MS Update helpsite before
posting here. So it's obvious that problem #1 is there is missing
stuff.
Do you have the KB842773 Windows Update??
AFAIK (i.e., from the hotix list reported in the Add/Remove utility),
no. This would seem moot at present, since I can't obtain any further
updates until BITS is up & running.
Is your error 1058 maybe 1053???
No.
There may or may not be a related problem: I'm getting .Net Framework
Initialization Error
c:\Windows\Microsoft.NET\Framework\v.1.1.4322\mscorwks.dll could not be
loaded (_not_ when trying to start BITS but when clicking Help items
etc.).
I don't even _have_ a Microsoft folder & subfolders anymore (just found
out); it they were orphaned into .found files by chkdisk when I used it
as an interim fix for the previous HD which had a few bad sectors.
FWIW in replacing the HD I imaged the otherwise-fine-running
installation because it was reinstalled to a partition, whereas there
is no other way to install necessary OEM s/w except the damned "restore
CD's" which would wipe out the partitioning and the 2 other OS's which
have taken weeks to refine. I didn't notice the missing directory as I
seldom looked at the rather uninspiring XP Home tree. ;-) Naturally
all the system sounds are orphaned therein too, but I hadn't noticed
since I don't use them.
Now, I don't know that BITS is .NET Framework dependent, or even if it
requires anything from the MS directory path, but I did locate the
orphaned mscorwks.dll, and noted in its Properties that Workstation is
a dependency (even though the latter seems to be running without
complaint).
I also don't know if online Update itself is .NET Framework dependent,
but think it prudent to address this missing folder & all its files
first B4 focussing further on the BITS failure, yes? (Or pls correct me
if U disagree)
So, either this is part of the problem, or not, but I also need to
somehow restore the entire missing MS directory & wiping/a clean
install is not feasable due to the "recovery CD's" issue. It would
take weeks to rebuild the other 2 OS's from scratch.
Therefore:
Q: Can I extract the whole folder from the Recovery console (yes I
have a plain-Jane XP Home CD)? I know see how to extract individual
driver files from a .cab for example, but have no clue how to extract a
folder & it contents. And how to know exactly which .cab anything is
in, isn't anywhere on the CD.
Q: On inserting the XP CD (which also has SP1) just to browse it, it
displays a gui task menu that also lists .NET Framework, presumeably
for separate install. HWVR, clicking this item does nothing.
Q: Or alternatively(?), I have pretty much if not all of the original
MS directory contents in the orphaned (.found) folders, though it lacks
a v.1.1.4322 folder (but seems to have it's files). If I knew what the
directory structure is supposed to look like, perhaps I could patch it
together by creating the missing folder(s) & dumping the found stuff
into them.
The only other half-vast idea I've had, is to attempt a 2nd clean XP
install to an empty 2gb "shared" partition I have, copy whatever it
creates for a Microsoft folder to the original installation, then wipe
it. I'm not sure if this ploy would alter my MBR & creat other
problems.
It isn't clear from the docs (if U call them docs) whether one can
"upgrade install" XP over XP & only have it replace missing items
(assume not?).
I'm getting discouraged as I've spent 4x the time/work screwing with XP
than even with Lnx. :-( Thank God for some of you technical people. XP
is still the most efficient OS for my battery/laptop needs. None of
this is any fault of XP no matter what some of us may hate about it.
XP actually seems rather robust. IMHO it all comes down to the fault &
greed of OEM's furnishing restore CD's that cripple us & cause hundreds
of hours/dollars of losses & hassles when repair or restoration is
needed - OR give us the only alternative loss of losing the s/w.
So I am _exceedingly_ grateful for any competent guidance in patching
up my existing install in the least worst fashion, & to think outside
the box.
Much thx the read.
Rgds,
frank
