#WB 3.1
18 messages in this thread
Since installing 3.1 on my REV6.2 A2000 a minor problem has come to light.
Using the scroll bars on programs that open text windows can cause corruption
of the windows borders and contents. Horizontal lines appear within the window
when the scroll gadget is used, these lines are at a slight angle and extend
into the windows border area. The worst offender is Multiview using either
Amigaguide ot ASCII datatypes.
The problem also occurs when scrolling DirOpus file lists. Shell and Ed windows
also suffer from corrution to the frame, particularly if the windows are moved
around the WB screen. Oddly the problems go away on 16 colour screens.
I had minor problems with Amigaguide under WB 2.X corrupting window borders but
no other trouble. This leads me to belive that 3.1 is throwing up a previously
hidden hardware fault.
Any one got any ideas on this one? I can supply screen grabs this would help
diagnosis.
Heres hoping,
Robert.
Robert,
see my reply to Steve, but have you tried running the system with no
tools such as ToolManager, DirOpus, etc?
This one has me curious. I don't use them here, but a thread seems to
be developing.
The Four Seasons of Southern California:
Fire, Flood, Earthquake, and Riot.
Brian,
Will WB 3.1 work with an enhanced A2500 with a 2.04 ROM chip? Or is it
only for the A4000/A1200?
Dom Fontana
–> Sent from NY via AP <–
WB 3.1 works great in an A2500, but only if you replace the 2.04 ROM, not
"with a 2.04 ROM chip."
Dale,
What exactly do I need to get to use 3.1 in my A2500? Is there an
Upgrade Enhancer Kit that includes a new ROM chip plus new software?
Originally I thought that 3.X could only be used with AGA machines, but
then I saw some messages to the contrary.
So what do I need to do?
Thanks.
Dom Fontana
–> Sent from NY via AP <–
Call Expert Services and order their $125(?) 3.1 kit for the 2000/2500.
Dom,
You need to update the ROM to use OS3.1
It runs on my B2000 with GVP 3001 '030 fine except for some strange
characters in some title bars like SnoopDOS and WSHell2.0.
Also a rexx script that starts up when I load TurboText has been causing a
guru (or whatever it's called now), which I can suspend and keep on
working.
I can't find the d!@m turbotext startupscript that I edited a long time
ago to use this script. Arrghh! (Anyone reading this who knows where to
look please drop me a note, OK?) I can't find me manual around here, got
to check my storage spot or it.
Christopher
I've got 3.1 running on my A2000.
Robb
Robert,
> I've got 3.1 running on my A2000.
Do you have any problems or caveats to report?
Dom Fontana
–> Sent from NY via AP <–
Dom,
Other than the preferences problem, I haven't had any trouble, yet.
Robb
Robb,
> Other than the preferences problem, I haven't had any trouble, yet.
Thanks for the info. What preferences problem did you have?
Dom Fontana
–> Sent from NY via AP <–
Dom,
Sorry, I've seen quite a few messages about mouse pointer color problems
around here. I thought you'd know what I meant.
I installed 3.1 on top on my existing 2.1 SYS:, against my better
judgement, but I did it none the less. Afterward, the pointer colors
looked awful and I'd go into the pointer prefs and simply save and
everthing would be fine. When I booted the strange mouse colors were back.
I think the right thing to do would be to delete all your old prefs (or
install to a formatted drive) and then go through and set them all to your
liking. I just re-installed Magic Workbench and it re-set the mouse back
to normal.
Robb
Robert,
> I just re-installed Magic Workbench and it re-set the mouse back
to normal.
Okay, that's good to know. I'll keep your tips in mind when I install
3.1.
Do you have the phone number for Expert Services? I decided to order
the 3.1 upgrade.
Thanks.
Dom Fontana
–> Sent from NY via AP <–
Dom,
It looks like QuarterBack doesn't like 3.1 (crahses and makes the HD
unavailable without a disksalv run, or so it would seem from preliminary
tests with 6.0).
wmc – via Autopilot!
Wayne,
> It looks like QuarterBack doesn't like 3.1…
I believe New Horizons is out of the Amiga market, so it looks like
that won't get fixed. Do you know how Ami-Back works with 3.1?
Thanks.
Dom Fontana
–> Sent from NY via AP <–
IMHO, AmiBack has no advantage over HDBackup supplied with ADos. And
though I have it, I have never used it aside from one trial run on ADos
2.04 – in fact I never registered it… And since they are not going to
release the promised 3.0 unless the Amiga product line is picked up again,
I feel that if I am going to abandon Quarterback, I might as well bit the
bullet and go with HDBackup. Compatibility won't be that big an issue
then even though the UI sucks and the log files are rediculously large
(though you do get 90% compressions of the log files with lha.)
wmc – via Autopilot!
Brian,
The window corruption problem occurs even on a clean system, booting from the
original WB 3.1 floppy and all prefs deleted from ENVARC on the hard disk.
I have a feeling that this is a hardware (blitter?,timing?) problem.The
corruption only occurs when text windows are scrolled quickly, using the scroll
bars. Some border corruption can occur if the window is dragged around the
screen. These problems appear to be random in their frequency and intensity but
never crash the computer.
Very occasionaly there is disturbance around WB icons and window borders, but
these can be fixed with Redraw All. All of these problems disapear on a 16
color screen, not ideal but a solution.
Thanks,
Robert.
I don't run ToolManager on my 3.1 A2000, but I do run DirOpus and I've had
no such problems.
Robb