pegram@kira.UUCP (Robert B. Pegram) (02/14/91)
From article <4824@ruuinf.cs.ruu.nl>, by avgroeni@cs.ruu.nl (Annius Groenink): > > Has any STE owner ever had the problem of two bombs (bus error) appearing > on the screen after one of the alert boxes `no disk in drive A' or > `Disk in drive A has been write-protected'? Can anyone explain this strange > behaviour of my computer (which already caused me to loose MANY files)? > > > > Annius Groenink > De Mamuchetweg 5 > 3732 AK De Bilt > The Netherlands > AVGROENI@CS.RUU Hey, I think I get it on my (homebrew connector) Tandy drive B with my ancient 520ST ('85 vintage) - it doesn't happen on drive A. No idea why - would love to fix it. I also have similar request. I recently got Spectre GCR - well, I got it before the ROM shortage 8-) and I have a mouse crashing problem. I ended up trashing my system 6.05 disks on version 2.65c of Spectre. Turns out that they're not compatible - and I didn't know it - or make backups from the Spectre menu until too late. I had assumed that the mouse crashes were due to the previously trashed and not properly installed system driver. However, I get the same problem currently running Spectre 3.0, which supports sys 6.05. I found this out when I realized that I could boot from the disk utility disk. Since I'm getting a fresh copy of everything from a local mac store soon, I want to fix this (Rats, first the NEC drive to fix, then this!). The symptom is that the mouse freezes on the screen, and I then trash my system disk, since the keyboard is not responding either, and mac menus don't have default key equivalents anyway 8-(. Do I need a new IKBD processor, or a new machine? If only TTs were class B approved! This risky store-in-memory behavior of the mac file system is souring me on the whole deal. I know, Un*x also can crash horribly when it loses power - but at least *it* has fsck! A "busy or defective" app on a mac does not seem to be fixed by the disk repair program (humph!). Bob Pegram pegram@griffin.uvm.edu or ...!uvm-gen!pegram
dodgson@sol.cs.wmich.edu (Harry Dodgson) (02/14/91)
In article <1991Feb13.201052.21311@uvm.edu>, pegram@kira.UUCP (Robert B. Pegram) writes: > From article <4824@ruuinf.cs.ruu.nl>, by avgroeni@cs.ruu.nl (Annius Groenink): > > The symptom is that the mouse freezes on the screen, and I then trash > my system disk, since the keyboard is not responding either, and mac > menus don't have default key equivalents anyway 8-(. Do I need a new > IKBD processor, or a new machine? If only TTs were class B approved! > This risky store-in-memory behavior of the mac file system is souring > me on the whole deal. I know, Un*x also can crash horribly when it > loses power - but at least *it* has fsck! A "busy or defective" app > on a mac does not seem to be fixed by the disk repair program (humph!). > > Bob Pegram If you know someone with a REAL Mac, have them install key equivalents into the Finder resources with Resedit. That may help that problem. Also, the "busy or defective" error is usually automatically reset by my Mac SE when I reboot, since it knows that the program cannot be busy. The 'Busy' bit can also be reset with Resedit or a Mac DA called DeskZap which I use a lot. I have crashed my Mac a lot and have never trashed the system files or any of the program files. I just reboot and continue on. I have lost work in progress though. For slightly buggy programs like DMCS ver 2.0, I use an autosave DA so I don't lose too much when it crashes (it doesn't handle MIDI active sensing very well). -- Harry Dodgson Jr. | Internet dodgson@sol.cs.wmich.edu -(35.132.4.2)- Western Michigan University | UUCP ...uunet!sharkey!wmichgw!wmu-cs!dodgson Computer Science Department | Voice (616) 387-5803 Kalamazoo, MI 49008 | Office 4420 Dunbar Hall