«

"Andrew" <> wrote in
news:%U5fb.5912$:

> Howd you paste that message into here?
>





taken by DSC then used OCR

"Myname" <> wrote in message
news:Xns9409838F97121namemynet@203.109.252.31...
> can anyone help!?

Ok, when you get a stop screen the first thing to do is check whether it is
listed on MS's website. Lo and behold,
http://support.microsoft.com/default...b;en-us;281428
details a stop error of this nature if you are using a Zip drive. Now, it
doesn't apply to XP (the fix is for 2k) but it does give you some insight
into what may be causing the problem.

In this case it appears to be Ppa.sys or Ppa3.sys. You may want to start
with these system files, and check that they are the latest versions for XP.
You may also want to check that you have the latest service pack.

Do you have a Zip drive on your machine? Does it have the latest drivers,
and is it listed on the HCL (hardware compatibility list).

If the answer to these is no, check your eventlog Start -> Run, type in
eventvwr. Check the application log for errors especially around the time of
the dump.

While this isn't an exhaustive list of fixes, it should set you going in the
right direction.

If none of this throws up any answers, then perhaps you could google:
http://www.google.co.nz/search?q=sto...8&oe=UTF-8&hl=
en&btnG=Google+Search&meta=

which would probably bring you to:
http://aumha.org/win5/kbestop.php

From here you're on your own.

--
Mr Scebe
Give someone a fish and you feed them for a day
Teach them to fish and you feed them for a lifetime

On Fri, 3 Oct 2003 01:38:05 +0000 (UTC), Myname <> wrote:

>"Rider" <> wrote in news:blij4e$lo0$1
>@lust.ihug.co.nz:
>
>> Have you installed the security updates to block the Blaster and Welchia
>> worms?
>
>yep, the system is currently up to date... sp1 also installed... no new
>patches in my windows update.
>
>the system now is newly installed with all patches applied.
>
>thanks

Didn't go on the net naked at all did you?

"Mr Scebe" <> wrote in news:%hdfb.166741$JA5.4143903
@news.xtra.co.nz:

> http://aumha.org/win5/kbestop.php



thanks mate!
i did another search...in which i found another thing

318988 Stop 0x000000B8 Error Occurs in a Windows 2000 Cluster Security
http://support.microsoft.com/default...b;en-us;318988

CAUSE
This problem may occur if the Clusnet.sys driver is loaded when the
computer starts, which is at the wrong time. The load time may have been
changed by a third-party vendor.

it's also for win2k, but i did try to fix according to their solutions...
well, turns out that the registry stated doesn't exist in WinXP.



still wondering if the sharing/conflict thing(PCI bus, DMA controller)
is involved in all this.


thanks again!


p.s i don't have zip drive.

> i'm getting this msg
> =-=-=-=-=-=-=-=-=-=-=
>

You don't tell us what you did before this message appeared.

However, I have had the same problem, and it was self-inflicted.

I am using an alien (Acorn RiscPC) to share the same Iomega ZIP drive, and
somehow or other I reverted to a filing zystem for the ZIP drive that cannot
handle long file names - something else to sort out. The result is, long
file names generated on the native RiscPC harddisk get trunkated when
transferring to the ZIP drive, which results in lots of files with the same
name. WinXP then throws a wobbly when trying to read those ZIP disks. The
short term solution was to rename, on the Acorn RiscPC, all the files with
names that fit into eight characters. Windows XP now reads those disks quite
happily.

No Microsoft operating system was designed to be stable. They were all
designed to be commercially viable, ie to generate repeat business. The
Acorn Risc PC, with its Riscos system, is stable, so it did not generate
enough repeat business, and it was eventually killed from within its own
organisation. Yet the machines keep working still.

Henry Falkner

On Sun, 5 Oct 2003 10:01:17 +1300, "Henry Falkner" <>
wrote:

>> i'm getting this msg
>> =-=-=-=-=-=-=-=-=-=-=
>>
>
>You don't tell us what you did before this message appeared.
>
>However, I have had the same problem, and it was self-inflicted.
>
>I am using an alien (Acorn RiscPC) to share the same Iomega ZIP drive, and
>somehow or other I reverted to a filing zystem for the ZIP drive that cannot
>handle long file names - something else to sort out. The result is, long
>file names generated on the native RiscPC harddisk get trunkated when
>transferring to the ZIP drive, which results in lots of files with the same
>name. WinXP then throws a wobbly when trying to read those ZIP disks. The
>short term solution was to rename, on the Acorn RiscPC, all the files with
>names that fit into eight characters. Windows XP now reads those disks quite
>happily.
>
>No Microsoft operating system was designed to be stable. They were all
>designed to be commercially viable, ie to generate repeat business. The
>Acorn Risc PC, with its Riscos system, is stable, so it did not generate
>enough repeat business, and it was eventually killed from within its own
>organisation. Yet the machines keep working still.
>
>Henry Falkner
>
Congratulations on this post, particularly the last para. You have entered the
Hall of Fame... and not the kill file. Thanks Henry,

nof