Terry said:
Status report:
I then thought I'd try booting to Safe Mode, prior to attempting the SR
again. I held F8 down permanently after pressing the power on button, but
presumably that was incorrect because it booted to the normal desktop, not
the 'options' screen. (Should I have inset ad repeatedly tapped the F8
key?) But the good news is that the SR succeeded this time, and I'm able
to power down properly.
It still leaves a puzzling situation though, so I'd appreciate any
thoughts please.
Background:
The issue that I'm pretty sure prompted this was somehow connected with
Microsoft .NET Framework 3.5. We had been unable to get my wife's new
Samsung Galaxy Tab 2 (7") to establish a USB connection with her PC.
Whatever route we took resulted in a message (either from the XP hardware
wizard or various programs subsequently tried) that the 'device was not
correctly configured (code 1)'.
So we downloaded yet another Samsung USB driver purporting to fix this. It
first installed .NET Framework 3.5 (about which I am 99% ignorant) but
hung with that still unfinished (although showing zero time remaining) and
we had to cancel out.
The following morning an automatic XP Windows update tried unsuccessfully
to install an update to .NET Framework 3.5, presumably just coincidence.
But that got into a dreadful mess, failing to finish, and that's when the
refusal to power down started.
Research found many problems of a vaguely similar nature concerning .NET
Framework updates, and much of the discussion is over my head.
About the only thing I can think of, to enable your Samsung Galaxy Tab 2 to
connect, would be an MTP driver. If you're attempting to connect to storage
on such a device, the paths available are USB Storage Class (for which a driver
has been installed in the OS for a dogs age) or MTP. The MTP driver, however,
is treated differently by Microsoft. At one time, it might have
accompanies Windows Media Player (because the driver also support DRM
features).
USBStor doesn't support DRM as such, and generally "just works". MTP
as a transport, allows features such as preventing you from copying
multimedia content to a portable device. On the plus side, MTP allows
both the tablet and the desktop PC, to be writing to the storage
device inside the tablet at the same time.
Generally, portable devices support USBstor or MTP, but not both.
I'm not advocating this page as a solution, merely showing that
someone had a problem with the named device and MTP.
http://answers.microsoft.com/en-us/...xy-tab-2/12326102-0d2e-4d47-8ec4-7c7b9980e479
So now, we'll ask the great Wiki, where the Media Transfer Protocol can be
found.
http://en.wikipedia.org/wiki/Media_Transfer_Protocol
"Support for Media Transfer Protocol in Windows XP requires the installation
of Windows Media Player 10 or higher."
"Windows XP supports MTP if Windows Media Player 10 or 11 (or the
Windows Media 11 Runtime) is installed."
Which to my mind, isn't a very good answer. At heart, it should just be
a stinking driver, not a "jail" for your new device.
*******
If the Samsung *Application Software* is .NET based, it may require
that some .NET file be installed. That's a possibility. The .NET should
not really be needed to make MTP work. .NET based applications, would
need .NET libraries to work.
The .NET people have a cleanup tool, with some instructions.
http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx
"* This tool is designed as a last resort for cases where install,
uninstall, repair or patch installation did not succeed for
unusual reasons. It is not a substitute for the standard uninstall procedure.
You should try the steps listed in this blog post before using this cleanup tool.
http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx
* This cleanup tool will delete shared files and registry keys used by other
versions of the .NET Framework. If you run the cleanup tool, you will need
to perform a repair/re-install for all other versions of the .NET Framework
that are on your computer or they will not work correctly afterwards.
"
The tool cannot remove versions of .NET which are "native" to the computer.
For example, on Windows 7, something like .NET 2.0 is probably already on there,
and the cleanup tool can't remove it. The cleanup tool is for removing
incrementally installed .NET. Like maybe you installed .NET 4.0 by accident
(it was in Windows Update), something went wrong, and you need an option. Then
the Cleanup tool might be a solution.
Anyway, safety first. Make sure you've got some kind of backup available,
in case things go downhill.
I don't know if that Cleanup tool, can unravel a half-installed .NET.
It's not logical that it should, since generally tool design assumes
"all or nothing" situations. Either something is completely installed,
or the install died and backed itself out (failed). Installs shouldn't
get stuck half-way, but I think you know that already. So while there
is a Cleanup tool, it probably doesn't know how to tell the MSI subsystem
to stop trying or whatever. That would take too many software skillz.
Paul
