#WB2.0
8 messages in this thread
#3122-#WB2.0 — declared parent_msg_num=3122, resolved parent_id points to #(none)
Hey Don… try one non-interlace, and two interlace. My memory is prodding
me that that's how one wakes that particular insect up.
BBS->Williams.Ben[AA7AS]
#3188-#WB2.0 — declared parent_msg_num=3188, resolved parent_id points to #3188
Ben,
Ok…did that too…while on-line here. I've got the 640×400
terminal running, behind it a 640×400 CLI and then opened a PCWindow
(640×200). I flipped between them…no problems, I moved them each down a
bit so all 3 were visible at once and clicked between them. Popped the
non-interlace screen on top and when back and forth between it and the
other two screens underneath and finally just kept "backing" them one at a
time.
I'm still on line, no GURU, no problems.
Not that it matters (or perhaps it is what really does matter),
I've still got the 1.2 ROM in this beast and run SetPatch 1.34. 2 Megs of
CHIP RAM in this beast…no other RAM.
I'm not saying the problem doesn't exist…I've seen it reported
before by others…I'm just saying that whatever it is…I personally have
never been able to get my machine to exhibit that behavior. Maybe it's
because I don't use non-Commodore system software. NO idea if you do or
don't. Just for clarity, I define system software as things like the C:
commands, the shell and various libraries and drivers.
Don
#3196-WB2.0 — declared parent_msg_num=3196, resolved parent_id points to #3196
Don –
I _think_ the screen-to-front bug (with on non-IL and two IL) is a bug
in Workbench, which you wouldn't see as you don't use it. I use Workbench
and I see it whenever I'm not careful enough 8^). I _have_ found that I can
have that one-and-two setup and change successfully if I pull down the
non-IL screen and use the flip buttons on the other two.
Harry
#3216-WB2.0 — declared parent_msg_num=3216, resolved parent_id points to #3216
Harry,
That's very possible…I'll try it later on and see if having WB up
makes a difference.
Don
#3216-WB2.0 — declared parent_msg_num=3216, resolved parent_id points to #3216
Harry,
I tried it…having the WB up didn't make any difference.
Don
#3196-WB2.0 — declared parent_msg_num=3196, resolved parent_id points to #3196
Ok, you dont' have the problem. :^) Good! <grin>
BBS->Williams.Ben[AA7AS]
#3188-WB2.0 — declared parent_msg_num=3188, resolved parent_id points to #3188
Ben,
Oh…again for clarity..that PCWindow runs on it's own screen in 8
colors.
Don
#3197-WB2.0 — declared parent_msg_num=3197, resolved parent_id points to #3197
Gotcha
BBS->Williams.Ben[AA7AS]