View Single Post
  #47  
Old September 10th 12, 12:39 PM posted to microsoft.public.windowsxp.help_and_support
BillW50
external usenet poster
 
Posts: 5,556
Default Undeletable file. I'm stumped.

In ,
glee typed:
"BillW50" wrote in message
...
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?


You apparently don't understand the meaning of "documented" in this
dialog. It has nothing to do with compiling, that statement doesn't
make sense. I stated no one else has reproduced your issue, it is not
documented as being an issue anywhere I have seen other than in your
posts about it.


The people who you claim has never seen my issue, also has never
compiled Linux either. People who has compiled Linux before knows
exactly what I am talking about. You can compile it many different ways.
If it can use the Windows swapfile or not, how much RAM can it use,
whether it uses a swapfile at all, etc.

I already gave you a working theory... it's some issue with your
system. How can I explain what, when I am not on your system? As you
seem to be the only person in the world reporting this, on one
computer, that points pretty clearly to it being that system's issue,
not the Linux Live CD boot. I say once again, we will have to agree
to disagree on this.


Look Glen. I get that a lot, that it is just your system and nobody else
sees it. But what always happen later? Here is one. While running OS/2,
I noticed that OS/2 was locking up about twice a week. I reported it on
the newsgroups. Yes I got it's just your system, you are the only one
that sees it, etc. Being an engineer, I know my system was just fine.
But nobody believed me still.

Two years later IBM stumbled on the bug. Not only did it affect systems
like mine, but all machines. It had to do with pasting between OS/2
applications and DOS applications. And the bug would leave the whole OS
in an unstable condition and the whole thing could lockup at any time.
So did anybody apologize for harassing me for two years? Nope. Did
anybody mention that I found it two years earlier? Nope! It doesn't
matter, just so it got fixed is all I cared about.

I've been investigating computer problems since the 70's. And I know the
difference between user error, hardware fault, and something much bigger
than either. And I am usually right every time. And there is something
big here going on that needs to be investigated. We can do this as a
group or I can do it solo and report my findings. It really doesn't
matter to me.

Casting aspersions on those who doubt your conclusion is just
silly.... your disparaging comments about "any five year old", "not
rocket science" and so forth, are just examples of using insults when
evidence is not available. It's a very sorry way to discuss something.


You bet! And so is the harassment I often receive that it is just you
and nobody else, it's just your machine, etc. when I know far better
than that. People rather harass others instead of doing the logical and
right thing.

"Condemnation without investigation is the height of ignorance." ~
Albert Einstein

--
Bill
Gateway M465e ('06 era) - OE-QuoteFix v1.19.2
Centrino Core2 Duo T5600 1.83GHz - 4GB - Windows XP SP2




Ads