#Probs with 3.1
6 messages in this thread
Steve,
if the problem moves as you change things, you have an interaction
problem, not just one program at fault. These are beasts to fix as
removing any one element will completely transform the problem. You may
want to try paired removal instead of just removing one program or line at
a time.
I'm sorry, but these are the hardest to troubleshoot. Suggestions are,
pay attention to any program dating back from 2.04 or 1.3. They are
farthest from most recent revision. Also think of backing up and
reformatting, if you are using any disk utilities/caches. That may help.
You may want latest version of Enforcer as a check (ENFORC.LHA from
AmigaTech). Lastly, a prayer followed by a threat of complete disassembly
of offending computer may help. Yes, I'm serious, mostly.
The Four Seasons of Southern California:
Fire, Flood, Earthquake, and Riot.
Brian (and anyone else who will comment),
I have installed 3.1 in my nearly vanilla A3000/25 and it "seems" to be
ok, so far, tho I do have some 'cleaning up' to do.
An item of interest which probably should be dealt with – with this SCSI
setup, the address of the SCSI drive is 0 instead of 6. I would like to
change the address, but can't figure a way.
Help, please. Thanks.
Dick:
Did the SCSI drive address change when you installed 3.1, or did you add
something to the system and re-number it? I have a "vanilla" A3000/25
also, and my drive has always been address 6.
You can change the address by running a program here in the library called
SCRAM3.LHA. It is intended to test static column RAM, but also has many
other features. If you download this program and run it, it opens a small
window with gadget options. Click on "Battmem Bits" and another window
will open showing you the status of the bits… one of them is SCSI Host
ID, which you can change by a cycle gadget. That should do it for you.
Please refer to the program's documentation (in AmigaGuide format) before
you change anything, though!!
BTW, I just got the 3.1 upgrade kit for my 3000… how did your upgrade
go? Any problems or odd things? I'll be doing it myself soon….
Hope this helps!
— Dave
You have to change the hardware jumpers on the drive. There is no software
which will do it. Some external drives will put a switch on the outside.
Otherwise, you have to get to the controller board and move the jumpers….in
your case to go from 0 sounds like will have to add some jumpers. You might
need to get the tech info on your drive to do this.
Regards,
Norm
Brian,
Thanx for the responce and concern. Yes this beast is kicking my @$$.
It is the stangest thing. I thought I was pretty computer literate (might
not be able to fix what was wrong but able to track it down).
I am running enforcer but at this time can only output to a window, as
when it crashes the whole machine locks up. No hints there. I have run
through all my files for any type of file virii, again no luck. Checked
all my ram, went through my WBStartup one program at a time, my
Startup-Sequence and User-Startup one line at a time, with strange
results.
I started noticing strange hapenings shortly after the install of 3.1,
normally stable games (on the hard drive) would act strange ie menu
actions not working, sluggish response ect. I had a hd crash shortly
afterwards that wiped the drive. (Had a timely backup!) My thinking at
the time was some differences in the file systems between 2.04 and 3.1, so
I formatted all my drives. Problem cleared up for a while. Then slowly
more problems developed; sluggish behavior, random crashes ect. Last week
I noticed there may be a pattern to the randomness.
Typical troubleshooting session, cold boot, boot is successful, try to
access Final Writer from Tool Manager, system lock-up. Warm boot, comment
out all addbuffers commands, reboot, Final Writer loads OK. Try to access
Phasar, system lock-up, go to Startup-sequence comment out burst mode from
CPU command, reboot, access Phasar OK, try AVM, system lockup, ed
user-startup uncomment addbuffer command, reboot, Final Writer now works,
AVM now works, Phasar now works, Directory Opus (or JrComm or SuperBase or
something else) locks up system. ect. I am pulling my hair out!!! It
seems to me something is trashing memory at a particular location and when
a program tries to load in that area BOOM!
Next ploy is to install virgin workbench onto DH0 and slowly (1 or 2 a
week) add my custom programs and commands.
What is strange is the addbuffers commands effect. It does not have to
be to the partition that is being accessed, that will effect things. I am
NOT running anytype of disk caching or compression programs. Oh well, the
kicker is I am now working about 70 hours a week (not with the computer)
and do not have time for this crap!
Again thanx for your ear and suggestions.
…Steve
Cruising on Autopilot
from beautiful Coastal South Carolina
Steve,
this is beginning to sound like a problem with a memory chip or one of
the other chips in the system. Have you run a memory tester, several are
available in the libs here, on the system? Next, when you have the system
open again, ground yourself on the metal case an reseat _all_ of the chips
inside. One may have worked its way loose.
Aside from a flaky intermittent, I can't think of anything else. Umm,
one thought. Have you tried yanking ToolManager and/or DirOpus out of the
system? A common thread seems to be problems with tools.
The Four Seasons of Southern California:
Fire, Flood, Earthquake, and Riot.