On Tue, 11 Sep 2012 16:35:29 -0500, "BillW50" wrote
in article ...

On 09/11/2012 09:58 AM, Zaphod Beeblebrox wrote:
On Mon, 10 Sep 2012 13:20:18 -0500, wrote
in ...

In ,
Zaphod Beeblebrox typed:
On Fri, 7 Sep 2012 15:43:51 -0500, wrote
in ...

In ,
Char Jackson typed:
On Fri, 7 Sep 2012 07:54:53 -0400, Zaphod Beeblebrox
wrote:

On Thu, 6 Sep 2012 15:55:12 -0500,
wrote in ...

Careful, I have been burned by Linux Live before. My Windows
didn't have a swapfile because I was running it on a SSD. And
Ubuntu Live doesn't care and makes it's own in the Windows
partition. I have no idea why Linux needs to touch anything it
shouldn't, but it does. And when I booted Windows after Ubuntu
Live it popped up a window saying Windows Installer and froze. I
much prefer WinPE or BartPE. As they don't play games with your
partition like Linux does.

rant

As with many other anecdotes and instances of failure from you,
this reeks of user error. I've been using various Linux Live CDs,
including Ubuntu, extensively for system recovery for better than a
decade and what you describe just doesn't happen and I'll wager has
never happened. First, Linux Live CDs don't auto-mount hard drive
partitions, they must be manually mounted by the user. Second,
Linux Live CDs don't use swap. Third, Linux doesn't use a swap
*file* by default it uses a swap *partition* so it would have
completely flattened the partition had it somehow gone off the
deep end and decided to use your drive as swap on its own.
Fourth, even if it did use a swap file, that file would have been
just that, a file on the file system separate from anything else
and Windows wouldn't have cared a whit.

Crawl back under your bridge, troll.

/rant

+1

You nailed it.

Nope you both are wrong

Without corroborated evidence to the contrary, I'd say it is you that
are wrong, not the thousands of other users who have had none of the
issues you do with Ubuntu (or other) Live CDs.

and owe us an apology.

If you are ever able to produce any evidence that an Ubuntu Live CD
has trashed any system other than yours by using a Windows swap file
when it wasn't manually configured to do so, I will. Otherwise, my
assertion and characterization stands.

Yeah I get that a lot. But I am always proved to be right in the end
even if it takes years. Like that OS/2 fiasco. For two years I was
complaining to IBM and on the newsgroups that OS/2 Warp had a stability
problem. As I was getting the OS freeze up about twice per week. I was
losing tons of work because I couldn't save anything.

And all I heard was it was just me, it's your hardware, OS/2 is rock
stable, and blah, blah, blah. Even though I knew everybody was wrong.
Then two years later IBM actually ran into it. And it affected all
machines and users. What set it off was copying and pasting back and
forth between DOS and OS/2. IBM claimed it left the OS in an unstable
state and it was just a matter of time before it would crash. Did
anybody say sorry Bill or anything? Nope! Very typical in my experience.

IBM rightly ignored your vague declaration that "omg something is
wrong" and again rightly did not give you any credit because you didn't
actually contribute anything that would help identify the problem or
provide a solution.

Among other things, I've done software quality assurance testing and
what you are doing doesn't qualify. Documentation, debug logs, screen
captures, before and after disk images / file CRCs, etc., verification
on multiple systems, systematic elimination of other variables to
determine the actual cause of a problem that was observed - those are
(some of) the things that prove a problem. Until and unless you
provide a repeatable set of steps to duplicate the issue, you are just
waving your hands and proclaiming that the sky is falling. Pick up the
acorn, Henny Penny, and recognize it for what it is. In this case, it
is a consequence of your own actions, not a flaw in the system.

How long have you been doing this?

It isn't how long you have been doing something, it is how well you do
it. Clearly, you fail that measurement of success.

You can't send in a bug report just
saying "omg something is wrong". That just doesn't fly. There are tons
of other information that you have to supply. Hardware, build, drivers,
open applications, logs, etc.

None of which matter a whit if the description of the problem is
lacking and you don't supply a repeatable set of steps to duplicate the
problem. Submitting a report that "omg something is wrong, here are my
specs" doesn't cut it.

I sent all of that in over a dozen times
over that period of time.

Then apparently what you sent was either inaccurate or insufficient or
both. Likewise, if you presented the information in the same
disorganized and anecdotal way you have here and with the same
attitude, it is likely what you submitted was dismissed out of hand.
See above: you are doing it wrong. NB: There are classes that can
teach you how, assuming you are willing and capable of learning.

--
Zaphod

Pan-Galactic Gargle Blaster: A cocktail based on Janx Spirit.
The effect of one is like having your brain smashed out
by a slice of lemon wrapped round a large gold brick.