[<<]Message[>>]    [<<]Author[>>]    [<<]Subject        [<<]Thread    

Number   :  2831
Date     :  2002-09-20
Author   :  Kan Yabumoto
Subject  :  Re: Blue Screen
Size(KB) :  3


Bob:

It sounds as if you are using the XXCOPY16 program in the Win9X
environment as opposed to XXCOPY.EXE (the 32-bit program).

Although XXCOPY.EXE can produce the blue screen of death, it
is quite unlikely because XXCOPY.EXE does have a pretty robust
way to trap nearly all such incidents using the SEH (Structured
Exception Handling) scheme in the program. Instead of causing
a Blue Screen of Death which often corrupts some portion of
the system memory which results in unpredictable/unstable
operation thereafter, XXCOPY usually handles the situation
gracefully by generating the following display.

##########################################################
# #
# X X C O P Y . E X E #
# ####### #
# Error Trap #*****### #
# /~~ *## #
# A fatal situation forced XXCOPY.EXE / @ 3 ## #
# to terminate before it has finished L- 3 ## #
# all the work it set out to accomplish. > ) # #
# This message is given by XXCOPY.EXE | / #
# to replace the Blue Screen of Death! datman #
# #
##########################################################

If you have seen this, it is very likely that it is caused
by XXCOPY's bug.

Since the appearance of this screen is relatively rare,
I suspect you are running the XXCOPY16.EXE which is a
16-bit (DOS) program which cannot implement the SEH
technique. I always discourage the use of XXCOPY16
in a Win32 environment. I seldom find it necessary
to use XXCOPY16 whenever you can run XXCOPY, the 32-bit
version. Even if you are forced to use the 8.3 filename
format, the /N switch in XXCOPY will do the job as well.
In that case, you may use the /ND to use the strictly
DOS-compatible filename convention (e.g., *.* and * are
interpreted slightly differently).

To answer your question, NO. We are not aware of a
relatively simple technique to capture a fatal (and
unpredictable) error that is similar to SEH. On the
other hand, you are experiencing a Blue screen of death
using the XXCOPY.EXE (the 32-bit version), please
give us more details of the circumstance.

As I repeat myself, please add the version number
of XXCOPY. And, please describe your case in more
clear language whether you are using a DOS Box in Win9X
or the straight DOS (before the GUI starts) environment.
In such a context, please call XXCOPY16 as XXCOPY16
rather than treat both version as XXCOPY.

I gave my answer above with the assumption that
you were in a DOS Box of Win98 using XXCOPY16.

Kan Yabumoto
========================================================
At 2002-09-20 09:02, you wrote:
>I have a Windows 98 system and use XXcopy in DOS for backup. I have
>used it for several months and find it very effective. One operation
>that I have incountered that is confusing is with the Blue Screen
>display. When it has accured it has taken considerable effort to
>determine what caused the display. In a few cases no error was found
>and the error display did not return.
>If the command that caused the fault was displayed (or some other
>identification) program correction determination would be improved.
>Is something like this possible ?
>
>Thanks for a great program. Bob



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.