begin Error Log for Thu, 09 Jun 2005 15:28:04 -0400 - "DFS"
nospam@dfs_.com> caused an invalid page fault at address
7L0qe.895$1v7.364@fe04.lga>, details as follows:

Then Linux stinks to high heaven. I recently installed an ATI 9600
card, and when I next booted Linux it installed the driver and booted up
fine and I thought everything was working OK. It even seemed a bit
snappier, and it ran some of the [suck-ass] 3D games it previously
wouldn't run with the onboard video (Intel 865G Extreme Graphics).

And Linux stinks because it automagically recognized and setup the new
video card without any interaction from you?

Yet when XP does this, it's a good thing, right?

But when I went into harddrake to change the screen resolution, it
filled the screen with mumbo-jumbo. The mouse was working, but there
was nothing but a mess on the screen. So I had to hardboot.

Linux does resolutions different than Windows does. Windows resizes the
screen to fit within the specified video resolution, it doesn't actually
change the video resolution per se. Linux, OTOH, has screen size AND
resolution, so when you change one, you are not necessarily changing the
other. If you push the actual video resolution beyond what the
capabilities of the hardware (vid card and/or monitor) are, you will get
garbage.

And you didn't *have* to cycle the box to fix this, of course this is the
first resort of a trained wintard.

I'm sure some cola nut reader will blame me, or the ATI driver, or
anything but the OS.

The OS was simply doing what you told it to do, the fact that you told it
to do something that was not possible with your existing hardware +
settings is not the fault of the platform.

This kind of thing is exactly why Linux is not ready for the desktop -
and probably never will be.

ITYM *you* are not ready for a Linux desktop - and probably never will be.
Stick to Windows, where at least you can pretend you have a clue.

Kier wrote:

I get you.
True.
I agree.
I'm glad you do.
I like it too.

Like I said, unless talking to a "Wintroll", cola is just one big "I agree"
lovefest.

Tom Shelton wrote:
In fact, I've been looking a lot into the freedesktop
standards lately, as well as the xdg python libraries. I'm not a python
guru - but, I've sort of been giving my self a crash course in
converting those libraries to C#. It helps me to see understand the
standards somewhat better when I can look at an implementation of it :)

Kier said:

I wish I had that kind of knowledge. Still, there's plenty of time for me
to learn :-)

If you want to learn programming for Linux, start with 'Learning Perl' or
'C++ in 24 Hours' or a 'Python for Absolute Beginners' book. That's if
you're going to stay in the... shudder... Linux environment.

All three will probably put you to sleep.

If you want to learn something interestinga and useful in Windows, check out
Visual Basic/VB for Applications. Those are easy to use and powerful.
Linux morons scoff at them, while millions of programmers and businesses
run on them.

Many databases have their own programming languages that are valuable to
know: Oracle PL/SQL and MS SQL Server T-SQL are two big ones.

And your's didn't crash. Neither did mine and it is running an nVidia
card. As for rebooting - I did think about it, but decided to wait it
out. Once, the image loaded I had no problem shuting down IE and the
system returned to normal. You just got impatient

On Thu, 09 Jun 2005 14:33:42 -0500, Linønut <linønut@bone.com> wrote:

No, in my case, I initiated the reboot. On purpose, so I could get back
to having a usable machine.

Why didn't you simply close IE, as I just did?

Linux has hardware support. And sometimes, it even has ok support. But,
other then my video card and printer, it's support hasn't been above ok.

1) My Kodak digital camera - works ok. gphoto2 is able to recognize it
2) My older hp digital. It no worky at all. To be fair, it barely
3) My card reader. This works ok on both - but it was slightly more
4) Muvo. Works well, but I haven't figured out udev well enough yet (my
5) Scanner. HP5370C. Doesn't work on Linux at all. I had it close to
6) I have no complaints on my printer. It works well on both, though

So, most of the hardware works - but I still have to figure out how to
make it hotplug. I don't have to figure that out on Windows. It just
happens. To be fair, the figure out part on Linux may have something to
do with the fact that I am using Gentoo. Gentoo, doesn't do a whole lot
for you like some of the more "user friendly" distributions. But, I
like it that way, it gives me a feel for how things "really" work.

I can't think of a single time I've had a user app crash 2K or XP... In
fact, like I said before - video drivers are the only driver I've ever
seen do this, and we all know why that is...

OK poked his little head through the XP firewall and said:

On Thu, 09 Jun 2005 14:33:42 -0500, Linønut <linønut@bone.com> wrote:

No, in my case, I initiated the reboot. On purpose, so I could get back
to having a usable machine.

Why didn't you simply close IE, as I just did?

You are pretty stupid.

I couldn't close it. At all. After many
attempts and many minutes.

Idiot.

rapskat wrote:

begin Error Log for Thu, 09 Jun 2005 15:28:04 -0400 - "DFS"
nospam@dfs_.com> caused an invalid page fault at address
7L0qe.895$1v7.364@fe04.lga>, details as follows:

Stick to Windows, where at least you can pretend you have a clue.

I have a bit of a clue,

first of all, if you read the entire thread,
you would see that the reported issue
was not necessarily related to any
kernel mode drivers.

Keep in mind that Windows is the operating system. It will allocate
as much memory as the application (which is a browser in this case)
asks it to allocate.

In article <26qdnb2zH72GPTXfRVn-oA@ctc.net>,
robert <root@wheel.invalid> wrote:
The odds that everyone who has had this problem is using the same
video driver are probably pretty long. Did you test with multiple
src's as suggested

How so? There are only a handful of video drivers nowadays.


Here's some of the nvidia, ati and matrox drivers available for
XP/2000. It's tad more than a "handful":

Not really. Take the NVidia driver(s), for example. First, many people
will be using the latest version. Most of the rest will be using a
recent version. Furthermore, all the different releases will share a
lot of code. A bug like this will likely be in several versions before
the one it is finally discovered in.

Same goes for the other drivers.

So, for this kind of thing, basically people fall into only three or
four groups (NVidia driver users, ATI driver users, etc).

The fact remains that some ATI users are getting the BSOD; some are not.
Some NVIDIA users are getting the BSOD; some are not. Some with the same
driver are getting it, while others are not.

first of all, if you read the entire thread,
you would see that the reported issue
was not necessarily related to any
kernel mode drivers.

So in other words a non-priviledged application like TAR is able to
bring down the entire OS. That's some robust kernel you got there !!!

robert wrote:


The fact remains that some ATI users are getting the BSOD; some are
not. Some NVIDIA users are getting the BSOD; some are not. Some
with the same driver are getting it, while others are not.

I wish you M$ people would stop wetting your pants over this and stop
blaming everyone under the sun including your grandmother for a
problem that is *absolutely* yours alone to fix.

A web page should not reboot the XP "professional operating system"
(POS, right?).

The fact that it can and could probably do the same for production
servers which cannot be run headless indicates that Windos is a total
abject failure and should not be used by anyone, anywhere at any time.

first of all, if you read the entire thread,
you would see that the reported issue
was not necessarily related to any
kernel mode drivers.

So in other words a non-priviledged application like TAR is able to
bring down the entire OS. That's some robust kernel you got there !!!

robert wrote:


The fact remains that some ATI users are getting the BSOD; some are not.
Some NVIDIA users are getting the BSOD; some are not. Some with the same
driver are getting it, while others are not.

I wish you M$ people would stop wetting your pants over this and stop
^^^^^^^^^^^^^