Wer kann mir was zu der obigen Fehlermeldung sagen? Tritt auf,
wenn ich Quick Time-movies im Internet anschaue. Sowohl Netscape
als auch Explorer.
Danke, Marco
Hallo Marco,
vermutlich hast Du Quicktime oder dem Browser etwas wenig RAM
zugewiesen. Hier die Erklärung des Fehlers mit weiteren Tips:
dsBusError (1)
Summary
The computer tried to access main memory (RAM) that doesn’t
exist or RAM that is reserved for another use.
Details
This error is the most common cause of crashes on the Macintosh.
It is usually caused by mistakes made by the developer in the
application’s program code. More remote possibilities are a
defective SCSI connection or a bad circuit board inside the
computer. These hardware problems are the least likely sources
of the problem and should not be considered until all other
steps to locate and resolve the problem have been tried.
However, if the crash occurs in different applications
(especially if these applications rarely crashed before) this
likely indicates a problem with the hardware.
One of the most common recommendations given to „solve“ this
error is „increase the amount of RAM (either in the computer or
given to the application)“.
In general, this is bad advice and only rarely solves the
problem. Typically, the error reported where adding RAM is a
good idea is error -108. If you get -108 errors, adding RAM (to
the computer or the application) is appropriate. Otherwise it is
a waste of time and money.
Here is the reason: Modern programming languages such as C, C++
and JAVA allow programmers to use something called a Pointer. A
Pointer is a memory cell that „points“ to another memory cell.
This is a very common thing for applications to use. Mac
Applications can use literally thousands of these „Pointers“ as
the application is exercised.
To help you understand how a Pointer can be the cause of the
Type 1 error, try to visualize the following. First, lets make a
couple of assumptions to keep the numbers simple:
- Your computer has 32 bytes of memory inside (no, not 32
megabytes, just 32 bytes). - When you start your application, it is assigned bytes 1
through 20.
These are assumptions but if you scale them to your actual RAM
size, the results will still be the same for what follows.
As your application starts, it creates a Pointer (using up cell
- and assigns a value of 6 to it. Then, the computer is told to
use the Pointer. Well, it looks at memory cell 6 (the value of
the Pointer), pulls out the contents of that cell and hands it
back to your application. Since Cell 6 is within the range of
both the computer’s memory (memory cells 1 through 32) AND
within the range of your application (memory cells 1 through
20), the application proceeds normally.
Along comes something unexpected (a programming bug) that
changes the contents of cell 1 (the Pointer) to a value of 40.
Then, the application tells the system to use the Pointer once
again. This time however, the Pointer contains a value for a
memory cell that doesn’t exist. Remember, the total amount of
memory in the system is 32 but the Pointer contains a value of
40. There is no memory cell 40. When the system tries to access
memory cell 40, an Error Type 1 occurs and your system crashes.
Can you solve the problem by adding RAM? Well, yes and no. If
you were to add another 16 bytes of RAM, the next time you ran
your application, there WOULD be a memory cell corresponding to
memory cell 40 but it would NOT contain the proper information.
Your application would no longer crash but it would produce
„strange“ results or exhibit „unusual“ behavior. Also, the
amount of RAM that you would actually need to add to „hide“ the
crash could be as much as 1000 megabytes (that’s 1 gigabyte).
This is not generally a practical or economic solution. Also,
remember that the original programming problem is still present
and the application will continue to behave „strangely“.
Virtually ALL current (and a large number of older) Mac
applications are written using one of the languages mentioned
previously and use Pointers.
As a side note, you should never see this error on a Macintosh
Plus or SE, because address references that are out of bounds
„roll over“. This means if one of these computers tries to
access one byte beyond the total bytes of RAM available, it
actually accesses the first byte in memory. If you see this
error on a Macintosh Plus or SE, it’s reporting the wrong error
or is having hardware problems.
What to do
If the problem you are having is caused by a programming bug
(highly likely), there is probably little you can do to fix the
bug yourself. You may be able to avoid the bug by using the
application where the bug showed up in a different way to do the
same thing. For example, if the problem occurred as you selected
a menu item, try using the command key equivalent to that menu
item instead. Bear in mind that this is only an example. It is
offered as an idea of what „use the application in a different
way“ means.
You should contact the company that maintains the application
for an update.
In the meantime, there are several „workarounds“ you can try
that might help you „avoid“ the bad code.
-
Attempt to run the application with the Mac’s Extensions
turned off. This may not be possible since the majority of
modern applications rely on extensions to perform some function
that they need. -
Throw the application’s defaults, settings or preferences
file in the trash. This file may have become corrupted. If so,
it will affect how the application behaves. -
Re-install the application.
-
Re-install the system. It is possible that the system
software itself could be the culprit. There are several Mac OS
releases that crash frequently, regardless of the application
you are using. You should AVOID the following Mac OS versions if
you want the best stability your Mac can offer:
6.0.5
6.0.8
7.0.1
7.5.1
7.5.2
7.6
8.n (ANY version of Mac OS 8)
If you absolutely MUST use Mac OS 8,
Mac OS 8.5.1 appears to be the most
stable version of the group.
9.n (ANY version of Mac OS 9)
Finder was totally re-written for Mac OS 8.0. That re-write
introduced MANY problems with Finder that result in the Finder
quitting. Sometimes you can get Finder to restart itself by
exiting from all of your other applications but most of the time
you simply have to restart your system. Apple is aware of the
problems with Finder. They perceive that the new features it
offers in the 8.n flavors are worth the „inconvenience“ of the
instability.
If you can use it, try Mac OS v7.6.1. All Macs made before the
introduction of the G3 systems in 1998 can run Mac OS 7.6.1. It
is the most stable of ALL of the Mac OS versions ever released.
Finder almost never quits in this version. And when it does, you
won’t really know it anyway.
Feedback
„After 6 months of generally smooth running I am having regular
‚bomb‘ crashes where I get ‚Application Switcher‘ error
messages, sometimes mentioning bus errors. I have Application
Switcher v1.0 of system 8.5 installed.“
„I’d suggest upgrading to 8.6, which fixes a bunch of bugs in
8.5. I’d also suggest deleting the AppSwitcher Preferences
file, which is in the Preferences folder in your System Folder.“
Günther
[Bei dieser Antwort wurde das Vollzitat nachträglich automatisiert entfernt]