ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (02/06/89)
Since I have been using Kickstart 1.3, I have been having a problem I never had with 1.2. Sometimes when a program crashes the machine, I do not get any GURU message. Instead, I am faced with a blank screen that just sits there. (I think it is white or greenish... I forget.) So, I press CTRL-AMIGA-AMIGA and the red LED blinks a bit as usual. Then the Amiga just sits there for a few seconds, and finally I get the Kickstart picture on the screen. Before you ask... YES, I am using c:SetPatch as the first instruction in my startup-sequence. My configuration: A1000 with 512K, 2 floppies, 2Meg StarboardII, 50-meg C.Ltd. hard drive running SCSIDOS 3.0. I use ConMan 1.3, Rez, DMouse 1.10, RAD: with FFS, and a few scattered ARP commands (*not* "Mount"). This configuration does NOT exhibit the problem when running Kickstart 1.2. I also use "KFont" to replace my Kickstart Topaz font, but I already had this problem before I started using KFont. Any help appreciated! Dan -- Dan Barrett ins_adjb@jhunix.UUCP UUCP barrett@cs.jhu.edu (128.220.13.4) ARPA Dept. of Computer Science, Johns Hopkins University, Baltimore, MD 21218
rickf@pnet02.cts.com (Rick Flower) (02/07/89)
I also get this same occurrance on my A1000!! Usually it happens when I'm
programming in assembly (most of the time!) and forget some minor (at least I
think so!) instruction and KABOOM! Next thing I know it looks like it has
completely hung.. Sometimes it will Guru then just hang (press Ctrl
Amiga-Amiga) and other times it will just plain hang (mouse freezes) and when
I do press Ctrl-Amiga-Amiga, it throws up the kickstart screen...
Amiga A1000 w/ Amigados 1.3 (modified for NoClicking df1:)
512k w/ 2 Meg Comspec Memory
No memory resident programs...
Oh well, such is life..
P.S. Anyone want to comment on whether the Supra or C-Ltd SCSI i/f is better??
===============================================================================
I Thought So...
UUCP: {ames!elroy, <backbone>}!gryphon!pnet02!rickf
INET: rickf@pnet02.cts.com
===============================================================================lphillips@lpami.wimsey.bc.ca (Larry Phillips) (02/08/89)
In <11722@gryphon.COM>, rickf@pnet02.cts.com (Rick Flower) writes: >I also get this same occurrance on my A1000!! Usually it happens when I'm >programming in assembly (most of the time!) and forget some minor (at least I >think so!) instruction and KABOOM! Next thing I know it looks like it has >completely hung.. Sometimes it will Guru then just hang (press Ctrl >Amiga-Amiga) and other times it will just plain hang (mouse freezes) and when >I do press Ctrl-Amiga-Amiga, it throws up the kickstart screen... One of the main reasons for resetting back to KS is a bad checksum on the KS disk. > Amiga A1000 w/ Amigados 1.3 (modified for NoClicking df1:) This could have been the culprit, though I thought it checksummed the disk after applying the patch. Perhaps it has become corrupted since. Try another KS disk (patched or not) next time you get a GURU that takes you back to KS. Then try the same program/GURU after reloading KS from the new disk. -larry -- Frisbeetarianism: The belief that when you die, your soul goes up on the roof and gets stuck. +----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca or uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 | +----------------------------------------------------------------------+
ejkst@cisunx.UUCP (Eric J. Kennedy) (02/09/89)
In article <11722@gryphon.COM> rickf@pnet02.cts.com (Rick Flower) writes: >I also get this same occurrance on my A1000!! Usually it happens when I'm >programming in assembly (most of the time!) and forget some minor (at least I >think so!) instruction and KABOOM! Next thing I know it looks like it has >completely hung.. Sometimes it will Guru then just hang (press Ctrl >Amiga-Amiga) and other times it will just plain hang (mouse freezes) and when >I do press Ctrl-Amiga-Amiga, it throws up the kickstart screen... This has been happening to me chronically since I installed 1.3 on my A1000, and I've heard other complaints of the same problem. It seems that I almost never see a "normal" crash anymore. Naturally, a lot of this is due to the fact that over time I've weeded out the programs and techniques that cause problems for me. Still, when I do have problems, (most recently with chip memory fragmentation caused by two programs that didn't like topaz 11) I almost always see the above symptoms rather than a 'task held' requester or even an immediate guru. Any clues as to what might be causing these problems? -- Eric Kennedy ejkst@cisunx.UUCP
jim@syteke.UUCP (Jim Sanchez) (02/09/89)
I have almost exactly the same setup except for a Supra 4X4 adaptor
and their scsidisk.device. I have noticed the same thing happening
as well. If the net has a solution(or even explantion) for this I
would like to see it.
--
Jim Sanchez {sun,hplabs}!sun!sytek!syteke!jim OR
Sytek Brussels mcvax!prlb2!sunbim!syteke!jimarmhold@topaz.rutgers.edu (George Armhold) (02/10/89)
Could someone briefly explain what is meant by a "bad checksum", especially in regard to the Kickstart disk? I kinda get the idea that it means that certain pieces of data are either missing or extra data has been added to the disk. If this is true, how does kickstart even load into WCS w/ bad data?? -GEA PS: How does a "bad checksum" even occur? Is it caused by the same gremlins that make disks go bad/unreadable?? (ie magnets, etc...)
ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (02/10/89)
In article <11722@gryphon.COM> rickf@pnet02.cts.com (Rick Flower) writes: >I also get this same occurrance on my A1000!! Usually it happens when I'm >programming in assembly (most of the time!) and forget some minor (at least I >think so!) instruction and KABOOM! Next thing I know it looks like it has >completely hung.. Sometimes it will Guru then just hang (press Ctrl >Amiga-Amiga) and other times it will just plain hang (mouse freezes) and when >I do press Ctrl-Amiga-Amiga, it throws up the kickstart screen... I have found a little consistency in WHEN this happens. Some PD programs (such as Hack) will crash if they are trying to find a file that does not exist. When I accidentally removed all my Hack icons, the program would crash all the way back to Kickstart every time I tried to Save my game. Hack couldn't find an icon for my type of character. -- Dan Barrett ins_adjb@jhunix.UUCP UUCP barrett@cs.jhu.edu (128.220.13.4) ARPA Dept. of Computer Science, Johns Hopkins University, Baltimore, MD 21218
ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (02/11/89)
In article <2215@van-bc.UUCP> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >One of the main reasons for resetting back to KS is a bad checksum on the KS >disk. >In <11722@gryphon.COM>, rickf@pnet02.cts.com (Rick Flower) writes: >> Amiga A1000 w/ Amigados 1.3 (modified for NoClicking df1:) >This could have been the culprit, though I thought it checksummed the disk >after applying the patch. Perhaps it has become corrupted since. I was the original poster of this problem. Larry, your explanation make sense... but why would the Amiga crash all the way to Kickstart only *sometimes*? With a corrupted Kickstart disk, I would think that every crash would go back to Kickstart. I also have a modified Kickstart (with KFont3 replacement font), but I have had this problem even with a totally unmodified Kickstart disk. -- Dan Barrett ins_adjb@jhunix.UUCP UUCP barrett@cs.jhu.edu (128.220.13.4) ARPA Dept. of Computer Science, Johns Hopkins University, Baltimore, MD 21218
alj@bilver.UUCP (arthur johnson) (02/11/89)
When KickStart is initially loaded into the machine, the Amiga does NOT
check to see if the checksum is correct. It does do this whenever you
warmboot. Therefore, you can happily boot with a KickStart that the Amiga
will later choke on.
If you modify KickStart in any way (like patching for noclicking, or
KickFont, etc.), you MUST re-do the KickStart checksum stored on the disk.
There are programs (sumkick) out there that do this. Otherwise, you will run
into the warmboot, guru med, etc. problems of 'Insert KickStart'.
--
Arthur Johnson Jr. -=> {uiucuxc, hoptoad, petsd}!peora!rtmvax!bilver!alj
-=-=-=-=-=-=-=-=- -=> alj@bilver.UUCP
-=> PLink: DUNG
-=> GEnie: A.JOHNSONJRltf@killer.DALLAS.TX.US (Lance Franklin) (02/11/89)
In article <716@jhunix.HCF.JHU.EDU> ins_adjb@jhunix.UUCP (Daniel Jay Barrett) writes: > I was the original poster of this problem. Larry, your explanation >make sense... but why would the Amiga crash all the way to Kickstart >only *sometimes*? With a corrupted Kickstart disk, I would think that every >crash would go back to Kickstart. Just a thought, but you don't, by any chance, have a Dallas Semiconductor SmartWatch clock chip in your Amiga, do you? These required a boot-rom swap to work, and disabled the write-protect on the Kickstart Ram. Or perhaps the write-protect on your Kickstart Ram has, for some other reason, failed to work...or maybe you just have a marginal chip in the KickStart RAM. Has anybody ever come up with a RAM checkout program for the KickStart RAM, by the way? I assume it would have to run from the KickStart prompt, since you'd have to get in before the RAM was write-protected...of course, you could always read each RAM word, NOT it, then try to write it to the word and check to see if the word had changed... Lance . -- +-------------------------+ +-----------------------------------------------+ | Lance T Franklin | | I never said that! It must be some kind of a | | ltf@killer.DALLAS.TX.US | | forgery...I gotta change that password again. | +-------------------------+ +-----------------------------------------------+
lphillips@lpami.wimsey.bc.ca (Larry Phillips) (02/12/89)
In <Feb.9.13.25.48.1989.29158@topaz.rutgers.edu>, armhold@topaz.rutgers.edu (George Armhold) writes: >Could someone briefly explain what is meant by a "bad checksum", >especially in regard to the Kickstart disk? I kinda get the idea that >it means that certain pieces of data are either missing or extra data >has been added to the disk. If this is true, how does kickstart even >load into WCS w/ bad data?? The KS disk has a checksum embedded in it that tells you if the data is good. It is not checked when the KS is loaded, but the data in WCS on a reset is checked, and if the checksum is wrong, it is assumed that a reKick is required. A wild guess atthe rationale for doing things this way is that it makes it easy to test new KS code without having to mess with checksums. ie. a patched KS will load regardless of checksum. A disk of type 'KICK' does not have any checksums on a sector by sector basis, so it will load whatever it finds out there. >PS: How does a "bad checksum" even occur? Is it caused by the same >gremlins that make disks go bad/unreadable?? (ie magnets, etc...) Yes, magnet, dirt, phyical damage, etc. are the main causes of a KS disk going bad. -larry -- Frisbeetarianism: The belief that when you die, your soul goes up on the roof and gets stuck. +----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca or uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 | +----------------------------------------------------------------------+
lphillips@lpami.wimsey.bc.ca (Larry Phillips) (02/12/89)
In <716@jhunix.HCF.JHU.EDU>, ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) writes: > I was the original poster of this problem. Larry, your explanation >make sense... but why would the Amiga crash all the way to Kickstart >only *sometimes*? With a corrupted Kickstart disk, I would think that every >crash would go back to Kickstart. > I also have a modified Kickstart (with KFont3 replacement font), >but I have had this problem even with a totally unmodified Kickstart disk. Right. Well, let's look at what's common. A good place to start might be WCS, the memory that the KS loads into. One or more bad bits could easily cause the same problem. memory, unfortunately, does not always fail solid, but can have a 'weak bit'. Even one bit in the checksummed area of WCS could cause a reset back to KS. Here's a little experiment you might want to try. Write a program that checksums WCS ($F80000 - $FFFFFF). The algorithm need not be the same as the one the reset routine uses. For best results, you might want to do it in both words and longwords, in case you have multiple bit failures that cause one of the methods to 'come out right'. Write it to simply print the result to the screen, then when you have the values, modify it to check for these values and tell lyou 'OK' or 'Whoops'. Before each test of a program you are running, run your checksum program. The two easiest ways to do this are either using an entry in 'make' to run it, or by launching your program via a script which first runs the checksum. Writing it in assembler will make it acceptably fast. -larry -- Frisbeetarianism: The belief that when you die, your soul goes up on the roof and gets stuck. +----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca or uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 | +----------------------------------------------------------------------+
osvenblad@abo.fi (02/14/89)
In article <2215@van-bc.UUCP> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >One of the main reasons for resetting back to KS is a bad checksum on the KS >disk. From what I have heard ( from Bitnet ) you can kick out the KS if you do a processor RESET followed by a write to $f80000-$ffffff (might be $f000000-$f800000 also) . The RESET enables you to write to the "write protected" RAM . Then again I may be completely wrong. Ove. #ifdef DEBUG ------------------------------------------------------------------------------- Ove Svenblad < 'I apologise for the inconvenience' osvenblad@abo.fi Internet > God's final message to his creation OSVENBLAD@FINABO Bitnet < (Hitchikers guide) ]bo Akademi > Finland < #endif DEBUG
jac@ssibbs.UUCP (James Crotinger) (02/15/89)
In article <2224@van-bc.UUCP>, lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:
. [stuff about rebooting to kickstart, and bad WCS memory]
I don't know about everyone else, but for me the problem (warm booting
back to kickstart) started precisely when I got 1.3, and has happened
on both my A1000's. Also, I doubt it is a bad kickstart disk since I have
usually 3-4 warm boots that succeed per one that fails.
Jim
--
Jim Crotinger
crotinger%mit.mfenet@nmfecc.arpains_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (02/17/89)
In article <15700@cisunx.UUCP> ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy) writes: >In article <11722@gryphon.COM> rickf@pnet02.cts.com (Rick Flower) writes: >This has been happening to me chronicallysince I installed 1.3 on my >A1000.... [And lots of other people have written similar things since I posted my original message about the problem.] Could somebody from CATS please *comment* on this problem? We've been discussing it for a few weeks. In case you don't recall: since installing KS1.3, some machine crashes go all the way back to the Kickstart prompt instead of the GURU. The problem never occurred under KS1.2, with otherwise identical hardware and software configurations. Thanks CATS! -- Dan Barrett ins_adjb@jhunix.UUCP UUCP barrett@cs.jhu.edu (128.220.13.4) ARPA Dept. of Computer Science, Johns Hopkins University, Baltimore, MD 21218
scott@applix.UUCP (Scott Evernden) (02/17/89)
In article <15700@cisunx.UUCP> ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy) writes: >In article <11722@gryphon.COM> rickf@pnet02.cts.com (Rick Flower) writes: >>.... and other times it will just plain hang (mouse freezes) and when >>I do press Ctrl-Amiga-Amiga, it throws up the kickstart screen... > >This has been happening to me chronically since I installed 1.3 on my >A1000, and I've heard other complaints of the same problem. Me too! I've hesitated to say it's something about 1.3, but I seem to find myself looking at the KickStart screen more than I remember these days. I can't figure it out. -scott
ksp@anuck.UUCP (p.s.kasten) (02/18/89)
In article <15700@cisunx.UUCP>, ejkst@cisunx.UUCP (Eric J. Kennedy) writes: > This has been happening to me chronically since I installed 1.3 on my > A1000, and I've heard other complaints of the same problem. It seems > > Any clues as to what might be causing these problems? > > Eric Kennedy > ejkst@cisunx.UUCP I may have determined the cause of this. I kept crashing back to kickstart until I removed the SetPatch line and the PatchWB line from my startup-sequence. I haven't had problems since (I still crash, but not to Kickstart). phil kasten AT&T Bell Labs !att!mvuxj!ksp
armhold@topaz.rutgers.edu (George Armhold) (02/25/89)
Add me to the list of 1000 owners that have had trouble with kickstart
requests since upgrading to 1.3. I NEVER had a kickstart request after
a crash or warm boot until I got 1.3. The first week I got it I had
crashes like crazy. Then a few weeks later it just stopped happening.
Haven't had one in over a month! Strange, heh?
-GEA
--
------------------------------------------------------------------------------
Save a bunny- stop the Draize. |armhold@topaz.rutgers.edu
|
"We saw the wrong and the right. We were for life |Careful with that axe,
and we would never concede it." |Eugene...
-T. Scholz |
-------------------------------------------------------------------------------andrews@cos.com (Andrew R. Scholnick) (02/25/89)
I've had the problem once or twice only when a program GURU'd. I also get a flaky system when my SCSI (C-Ltd) cable is twisted!?!
chas@gtss.gatech.edu (Charles Cleveland) (02/26/89)
In article <Feb.24.16.01.13.1989.24133@topaz.rutgers.edu> armhold@topaz.rutgers.edu (George Armhold) writes:
)Add me to the list of 1000 owners that have had trouble with kickstart
)requests since upgrading to 1.3.
Add me to the list of 1000 owners that have never had a kickstart request
since upgrading to 1.3 (except on a cold boot, of course).
--
- It is better for civilization to be going down the drain than to be -
- coming up it. -- Henry Allen -
Charles Cleveland Georgia Tech School of Physics Atlanta, GA 30332-0430
UUCP: ...!gatech!gtss!chas INTERNET: chas@gtss.gatech.edupeter@sugar.uu.net (Peter da Silva) (02/26/89)
Just adding a datapoint. Have been using 1.3 with both 1.3 and 1.2 kickstart for months now. *no* problems. -- Peter "Have you hugged your wolf today" da Silva `-_-' Hackercorp. ...texbell!sugar!peter, or peter@sugar.uu.net 'U`
bryce@cbmvax.UUCP (Bryce Nesbitt) (02/26/89)
In several articles <> several.net.posters wrote: > > [Since installing V1.3 I have noticed something strange. If the > machine ever crashes, it sometimes goes back to the Kickstart hand > instead of the Workbench hand.] > Thank you all for noting and reporting this bug. I have located the cause; a code mistake causes the Kickstart protected memory to be left open open for writing during some types of system Alert. This problem will be addressed in the next version of "SetPatch" (no date or distribution details are available at this time). Please note that some types of bug reports can be sent directly to Commodore. Before reporting, please verify the accuracy of your statements. Try removing any special programs or hacks you may be running (booting from your unmodified master Workbench disk is a good way to guarantee this). Submitted reports must include a TELEPHONE number. Reports must be CLEAR, COMPLETE and CONCISE. Based on your bug report alone, we must be able to repeat the bug. Bugs that we can repeat in-house GET FIXED. -Bryce Nesbitt, Commodore-Amiga, Inc. ----------------------------------------------------------------------------- Here is a sample bug report form: BUG REPORT ---------- Date: Name: Phone: Company: EMail: ### Bug Location (Hardware, Documentation, Software, Other): ### Your Configuration (Model, number and type of disks, memory, ### add-on equipment): ### Other software running or resident at the time of the bug (should be ### "none"): ### Revisions (Kickstart/Workbench revision numbers, etc.): ### Brief Bug Description: ### Bug Generation Procedure (remember that someone else will be trying to repeat this bug based on your description): ### Related bugs: -- |\_/| . ACK!, NAK!, EOT!, SOH! {O o} . Bryce Nesbitt (") BIX: bnesbitt U USENET: cbmvax!bryce@uunet.uu.NET -or- rutgers!cbmvax!bryce Lawyers: America's untapped export market.
ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (02/27/89)
Since I posted the original message for this topic, I have seen maybe a dozen responses from other people who have the same problem. Bryce Nesbitt of CBM has been in contact with me, and I have described the problem (and a consistent method for recreating it, which I posted here) to him. I would like if everyone who is experiencing this problem of crashing all the way to Kickstart, instead of getting a GURU, on an A1000 with KS1.3, to SEND ME MAIL. Please tell me your complete hardware and startup-sequence software configuration. Maybe we can help Bryce track this down. One weird thing I have noticed about the postings is that many of you have C.Ltd. SCSI controllers... hmm.... And everybody probably upgraded to C.Ltd. SCSIDOS 3.0 about the same time that KS1.3 came out... but I'm just guessing. Send mail to any of the addresses below, preferably the "cs.jhu.edu" address.
ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett) (02/27/89)
Our stupid "rn" program didn't include my .signature file for my last posting. Here it is... sorry! ############################################################################# # Dan Barrett barrett@cs.jhu.edu (128.220.13.4) ARPANET # # ins_adjb@jhuvms.bitnet BITNET # # ins_adjb@jhunix.UUCP UUCP (unreliable) # # Dept. of Computer Science, Johns Hopkins University, Baltimore, MD 21218 # #############################################################################
ksp@anuck.UUCP (p.s.kasten) (02/27/89)
In article <Feb.24.16.01.13.1989.24133@topaz.rutgers.edu>, armhold@topaz.rutgers.edu (George Armhold) writes: > Add me to the list of 1000 owners that have had trouble with kickstart > requests since upgrading to 1.3. I NEVER had a kickstart request after > a crash or warm boot until I got 1.3. The first week I got it I had > crashes like crazy. Then a few weeks later it just stopped happening. > Haven't had one in over a month! Strange, heh? > > -GEA I mentioned this a few weeks ago, but I'll restate it: Once I removed the PatchWB and SetPatch lines from the vanilla WB1.3 startup-sequence, I no longer crash back to kickstart. Try it! phil kasten at&t bell labs !att!mvuxi!ksp
peter@sugar.uu.net (Peter da Silva) (02/28/89)
In article <1491@anuck.UUCP>, ksp@anuck.UUCP (p.s.kasten) writes: > Once I removed the PatchWB and SetPatch lines from the vanilla WB1.3 > startup-sequence, I no longer crash back to kickstart. Well, I have never had the 'kickstart crashing' problem, and I still have SetPatch in my Startup-Sequence. What I don't have is PatchWB. I have never heard of PatchWB. It's not on *my* vanilla 1.3 Workbench disk. I just went back and checked. What's going on? -- Peter "Have you hugged your wolf today" da Silva `-_-' Hackercorp. ...texbell!sugar!peter, or peter@sugar.uu.net 'U`
dan@ivucsb.UUCP (Dan Howell) (03/02/89)
In article <340@gtss.gatech.edu> chas@gtss.UUCP (Charles Cleveland) writes: |In article <Feb.24.16.01.13.1989.24133@topaz.rutgers.edu> armhold@topaz.rutgers.edu (George Armhold) writes: |)Add me to the list of 1000 owners that have had trouble with kickstart |)requests since upgrading to 1.3. |Add me to the list of 1000 owners that have never had a kickstart request |since upgrading to 1.3 (except on a cold boot, of course). etc. etc.... CATS, where are you? -- Dan Howell <...!pyramid!ucsbcsl!nessus!ivucsb!dan> -- <nessus!ivucsb!dan@hub.ucsb.edu> -- * Adress path subject to change without notice. Good luck replying. *
bryce@cbmvax.UUCP (Bryce Nesbitt) (03/07/89)
|||Add me to the list of 1000 owners that have had trouble with kickstart |||requests since upgrading to 1.3. ||Add me to the list of 1000 owners that have never had a kickstart request ||since upgrading to 1.3 (except on a cold boot, of course). | |etc. etc.... CATS, where are you? We already responded. It's a real bug and will be addressed in the next version of "setpatch". -- |\_/| . ACK!, NAK!, EOT!, SOH! {O o} . Bryce Nesbitt (") BIX: bnesbitt U USENET: cbmvax!bryce@uunet.uu.NET -or- rutgers!cbmvax!bryce Lawyers: America's untapped export market.
fnf@estinc.UUCP (Fred Fish) (03/15/89)
In article <6088@cbmvax.UUCP> bryce@cbmvax.UUCP (Bryce Nesbitt) writes:
<< [Since installing V1.3 I have noticed something strange. If the
<< machine ever crashes, it sometimes goes back to the Kickstart hand
<< instead of the Workbench hand.]
<<
<
<Thank you all for noting and reporting this bug. I have located the
<cause; a code mistake causes the Kickstart protected memory to be
<left open open for writing during some types of system Alert. This
<problem will be addressed in the next version of "SetPatch" (no
<date or distribution details are available at this time).
< ...
< Based on your bug report alone,
<we must be able to repeat the bug. Bugs that we can repeat
<in-house GET FIXED.
Outstanding work! A bunch of vague reports of the form "my machine
crashes all the way back to kickstart" that indicate a trend that
there is a real problem and you guys go and find the cause. Your
support for this machine is simply amazing. Most companies won't
even bother looking for a problem until they have several written
bug reports documenting repeatable bugs, and even then may not do
anything about it until it looks like it might impact their sales.
Kudos also for finding the fix for the trackdisk bug that was so
elusive!
-Fred
--
# Fred Fish, 1835 E. Belmont Drive, Tempe, AZ 85284, USA
# 1-602-491-0048 asuvax!{nud,mcdphx}!estinc!fnfdan@ivucsb.UUCP (Dan Howell) (03/17/89)
In article <6088@cbmvax.UUCP> bryce@cbmvax.UUCP (Bryce Nesbitt) writes:
<< [Since installing V1.3 I have noticed something strange. If the
<< machine ever crashes, it sometimes goes back to the Kickstart hand
<< instead of the Workbench hand.]
<Thank you all for noting and reporting this bug. I have located the
<cause; a code mistake causes the Kickstart protected memory to be
<left open open for writing during some types of system Alert. This
<problem will be addressed in the next version of "SetPatch" (no
<date or distribution details are available at this time).
< ...
< Based on your bug report alone,
<we must be able to repeat the bug. Bugs that we can repeat
<in-house GET FIXED.
This is great! I'm glad to see that the people at Commodore-Amiga respond
to these bug reports over the net and fix them. Would it be possible
for you to distribute the SetPatch over the net when its finished?
--
-- Dan Howell <ivucsb!dan@anise.acc.com>
-- <...!(pyramid|ucbvax)!ucsbcsl!nessus!ivucsb!dan>
-- "What? TWO buttons? I don't know if I can handle that!" -- a Mac user