#WB2.0
6 messages in this thread
#3127-#WB2.0 — declared parent_msg_num=3127, resolved parent_id points to #(none)
Bill,
I don't know what to tell you. Right now, I've got a 640×400 CLI
up in the background (and thus in interlace) and in the foreground I'm
running a terminal program in 640×200 (thus non-interlace). I just jumped
back and forth between the screens a bunch of times…no problem.
A few minutes ago, I was running the same background, and a
different terminal program that runs in 640×400. I jumped to the CLI and
did a few things, jumped back to the terminal and did an upload…and while
it was running, went back to the CLI and did a few more things.
No problems at all.
Now…my hardware is probably a bit different than yours, I've got
a 2 Meg Agnus and the ECS Denise installed. But I've never noticed the
problem even with the original 512K Agnus and original Denise. Same goes
when I moved to the 1 Meg Agnus, then added the ECS Denise and now moved to
the 2 Meg Agnus…..I've just never seen the problem.
Who knows…maybe I do have a magic machine.
Don
#3171-WB2.0 — declared parent_msg_num=3171, resolved parent_id points to #3171
Don;
I am inclined to think so….. Most of the gurus that I have seen in
recent years have all occured when switching screens. I am running conman
and wshell. I have recently started trying MachIII and it MAY have
increased the frequency slightly but I'm not sure. I do know that on
several occassions I have had one of the interlaced screens be displayed in
non-interlace (with the bottom half of the screen going off of the crt).
73, bill
#3201-WB2.0 — declared parent_msg_num=3201, resolved parent_id points to #3201
Bill,
Ok…there's obviously some difference…I've never seen the
problem, and last night…I specifically tried to re-create it. I had 3
screens overlapping on the CRT. 2 interlaced, one non-interlaced. I
switched back and forth between them, "fronted" them in rotation and so
forth. No problems.
Yes, part of each screen was off the bottom of the CRT.
One thing…I don't use conman or wshell or any other shell
except the CBM shell. Same with all my C: command files…they're 1.3
(with 1.3.2 upgrades where appropriate) thru and thru.
Don
#3171-WB2.0 — declared parent_msg_num=3171, resolved parent_id points to #3171
Don,
The problem is CBM's and is demonstrable. Have 2 interlaced screens and
1 non-interlaced screen up — then flip 'em – you'll guru. Thre is a PD
program available that fixes the problem (I forgot the name but it's been
in my startup-sequence for a couple of years. I believe the problem is
fixed in 2.0x.
-sja
#3218-#WB2.0 — declared parent_msg_num=3218, resolved parent_id points to #3218
Steve,
I'm not saying the problem isn't CBM's…I'm saying I can't
duplicate it. Harry left me a message earlier saying he thinks that WB
must be up and running for the problem to show up. I'll try that later and
see what happens. I don't normally have the WB up…so that may be why I
don't see it.
Don
#3251-WB2.0 — declared parent_msg_num=3251, resolved parent_id points to #3251
Workbench has nothing to do with it. Have 2 interlace and 1 non-interlace
screen up… and you'll duplicate the problem.