Try this with XP (all patched)

HTML
BODY
IMG SRC="./sweetydead.jpg" width="9999999" height="9999999"
/BODY
/HTML

The image does not need to be that large, a very small one is sufficient
Just the /declaration/ of the size is enough to trigger the bug

Save your data before. The machine will BSOD

Try this with XP (all patched)

HTML
BODY
IMG SRC="./sweetydead.jpg" width="9999999" height="9999999"
/BODY
/HTML

The image does not need to be that large, a very small one is sufficient
Just the /declaration/ of the size is enough to trigger the bug

Save your data before. The machine will BSOD

Save your data before. The machine will BSOD

Tried it. No BSOD. No crash. IE simply doesn't display the image with a
width and height of 9999999. Dropping a digit (999999) shows the image
but it's very slow. Dropping another digit (99999) shows the image and
scrolling is sluggish but usable.

Nice FUD though. BSOD... now that would be a lie.

Your error message says that "the display driver for RADEON IGP 320M
seems to be responsible for the system instability."

I have a different graphics card/driver (Nvidia) which doesn't have
this problem.

I'll recant my original post that this can't happen since this appears
to be a driver issue.

Your error message says that "the display driver for RADEON IGP 320M
seems to be responsible for the system instability."

I have a different graphics card/driver (Nvidia) which doesn't have
this problem.

I'll recant my original post that this can't happen since this appears
to be a driver issue.

begin Error Log for Thu, 09 Jun 2005 06:16:51 -0700 - lqualig@uku.co.uk
caused an invalid page fault at address
1118323011.742032.307010@g43g2000cwa.googlegroups.com>, details as
follows:

Save your data before. The machine will BSOD

Tried it. No BSOD. No crash. IE simply doesn't display the image with a
width and height of 9999999. Dropping a digit (999999) shows the image
but it's very slow. Dropping another digit (99999) shows the image and
scrolling is sluggish but usable.

Nice FUD though. BSOD... now that would be a lie.

How is it a "lie" when it has been confirmed by other people? Perhaps it
depends on the amount of total memory you have on your system as to
whether it actually crashes or not.

The point here is that a friggin WEB BROWSER has the capability of
potentially crashing a Windows system simply because the platform will
allocate all available memory to trying to display this massive graphic,
even to the point of taking away memory from its core components.

And yet you wintards have the audacity to call this platform stable and
secure. What a fsckin joke! Now, for an ancore performance, let's see
how long it takes for M$ to get up off it's ass and fix this little bug.

The point here is that a friggin WEB BROWSER has
the capability of potentially crashing a Windows system
simply because...

Running XP fully up2date.
...Remote Desktop doesn't allow reboot .

From reading your claims I have serious doubts regarding your claimed
proficiency on Windows.

HTML
BODY
IMG SRC="./sweetydead.jpg" width="9999999" height="9999999"
/BODY
/HTML

The image does not need to be that large, a very small one is
sufficient Just the /declaration/ of the size is enough to trigger
the bug

Save your data before. The machine will BSOD

XP SP2 here and nothing happened with either Firefox or IE, just a
broken graphic image with very large vertical and horizontal scroll.

did you try shutdown.exe? Command prompt:

C:\> shutdown /?

Not sure if it works or not... But, I have been able to do it through
the menu on the task manager in the past :)

It's a driver issue. No different than the recent bug where sometimes
running 'tar' to archive a file causes a kernel panic in linux. Last I
checked 'tar' was even more rudimentary than a web browser so why is
tar bringing down a Linux system?

It's a video driver error - it has nothing to do with memory. It works on
my little 64MB nVidia card that's in this box. Sure, it slows things
down, but it doesn't crash. The problem is crappy video drivers - which,
as we all know and have discussed, run in kernel space. So, if the driver
craps out, so does the system. It appears that nVidia drivers (at least
the latest) don't have this problem.

Try this with XP (all patched)

HTML
BODY
IMG SRC="./sweetydead.jpg" width="9999999" height="9999999"
/BODY
/HTML

The image does not need to be that large, a very small one is sufficient
Just the /declaration/ of the size is enough to trigger the bug

Save your data before. The machine will BSOD

--
Longhorn error#4711: TCPA / NGSCP VIOLATION: Microsoft optical mouse
detected penguin patterns on mousepad. Partition scan in progress
to remove offending incompatible products. Reactivate your MS software

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason Bowen wrote:


HTML
BODY
IMG SRC="./sweetydead.jpg" width="9999999" height="9999999"
/BODY
/HTML

The image does not need to be that large, a very small one is
sufficient Just the /declaration/ of the size is enough to trigger
the bug

Save your data before. The machine will BSOD

XP SP2 here and nothing happened with either Firefox or IE, just a
broken graphic image with very large vertical and horizontal scroll.


Broken graphic image? You mean it didn't really point to an image file?
If not, try it.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCqIQOd1ZThqotgfgRAtBCAKCMauOU1C7NM26SdhwUo6EAw4XHZACfRkRy
2dp6r3aIYnsAMMi2yNB8GiY=
=gxvL
-----END PGP SIGNATURE-----