In ,
Char Jackson wrote:
On Sun, 9 Sep 2012 09:37:37 -0500, "BillW50" wrote:

In ,
glee wrote:
"BillW50" wrote in message
...
In ,
glee wrote:
Bill, in this scenario you describe, are you saying you attribute
running the Linux Live CD to causing the Windows Installer pop-up
when
you started Windows? Are you implying that the Linux CD boot
caused the execution of a Windows Installer executable, even
though Linux can't run a Windows Installer file? How do you
figure that?

Windows Installer pop-ups like that are due to an incomplete or
faulty install of a program that uses Windows Installer. How do
you reconcile that with your claim?

No Glen... what I am saying that this Windows XP runs fine and
dandy for years. No problems whatsoever. I don't know if iband.dll
involves the Windows Installer every time it boots? I might, but
you never see the window. Anyway no problems whatsoever.

Now you just boot up Ubuntu Live and do nothing with it. Don't peek
into the Windows partition or anything. And just shut Linux down.
Totally harmless I would think.

Now if you boot Windows XP, it locks up. What gives? It was Linux
Live, plain and simple. I have demonstrated this a number of times
and it happened every single time. There is no excuse, Linux is
doing something to Windows. Sure whatever it is doing, most users
wouldn't know a thing. I truly believe that. But whatever it is
doing it can make some Windows unbootable.

As far as I am concern, whether Linux Live leaves Windows bootable
or not. That isn't the point. The most important point is that it
shouldn't be doing anything to Windows at all without your
permission. But it does and I caught it with my XP system (and it
is reproducible).

...yet no one else seems to have repro'd it or documented it. That
tends to point to an issue on your system, not with Linux Live CD.
As I said, we'll have to agree to disagree.

You can't be serious? It is documented for one. It is documented when
you compile the source. And how do you explain it is my system? You
can't come up with one single working theory how it can be my system!
This isn't rocket science. Any five year old can figure this out. But
you can't? Why is that?

Sorry, Bill, but the theories of Glen and philo make sense, while your
theory doesn't.

No way! Any halfwit can figure it out. It isn't that hard. Run Linux and
Windows gets trashed. Saying anything other than Linux is doing it
wouldn't make any sense. This isn't rocket science you know.

So far it's one person, you, claiming to have a
problem with one system, an old XP SP2 system with a bit of
non-mainstream software installed, and using one live distro.

It doesn't matter what OS is on the drive. The claim is that Linux Live
won't touch it. And I know for a fact that is wrong!

If you want to be taken seriously, start testing on other systems,
with other OS and software mixes, and with other live distros. One
person, one PC, and one distro is not enough to draw a solid
conclusion, but so far it looks like user error or something to do
with the obsolete system that you supposedly tested.

I haven't used any Linux Live on any Windows system since that day
except I started today. And I tried 8.04, 9.10, and 12.04.1 so far of
Ubuntu Live and every one of them were accessing the Windows drive a
number of times while Linux was booting. Philo says that doesn't happen.
Yet I bet it happens for everybody on any system. Why? What is Linux
doing with the Windows drive?

I tried the same with BartPE. And BartPE booted completely and the
Windows drive light never lit up even once. So there is no way anybody
is going to tell me that Linux Live doesn't touch your Windows drive. As
the drive's access light is saying otherwise.

I haven't got the same conditions that I did back in 2009 yet. That will
take some time to setup yet. I even still have backups from back then
too. ;-)

--
Bill
Gateway M465e ('06 era) - OE-QuoteFix v1.19.2
Centrino Core Duo T2400 1.83GHz - 4GB - Windows XP SP3