I was going through adtpro and showing the wife how to work it and all that. And I came across the black-screen-on-the-Apple bug when everything is connected up and the pc running but not having started the server yet.
Additional notes -
No settings in device manager make a difference.
This is on a genuine legacy serial port.
ADTPRO client version 1.3.0 does not exhibit this.
Pressing the ESC key on the Apple //e makes a bleee-blooop noise while the screen is blank.
Starting the server allows the client to continue.
No complaints - just trying to make a fine program 1% better than before (in a complete-ist sense).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I fixed that in 2.0.1 with respect to the GS, which is the only place I
knew it happened - are you (still) seeing it in this context, or in another?
David
On 3/22/2015 9:56 PM, Keatah wrote:
I was going through adtpro and showing the wife how to work it and all
that. And I came across the black-screen-on-the-Apple bug when
everything is connected up and the pc running but not having started the
server yet.
Additional notes -
No settings in device manager make a difference.
This is on a genuine legacy serial port.
ADTPRO client version 1.3.0 does not exhibit this.
Pressing the ESC key on the Apple //e makes a bleee-blooop noise while
the screen is blank.
Starting the server allows the client to continue.
No complaints - just trying to make a fine program 1% better than before
(in a complete-ist sense).
Note if I disconnect and reconnect the serial cable, it gets past the black screen. OR, if I start the server while the screen is black - that prods it along too.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Note if I disconnect and reconnect the serial cable, it gets past the
black screen. OR, if I start the server while the screen is black - that
prods it along too.
Ok, then it is behaving the same way as the GS... it hangs until it gets
some kind of acknowledgement from the other side. I'm between a rock
and a hard place here: I need/want to send a "I'm home" signal to the PC
side whenever everything resets (also the first time the client starts
up). The GS and your hard serial port hang unless/until there's
something to "hear" it on the other end. Not a lot I can do about that
except avoid the check; but that runs the risk of not sending the "abort
whatever else was going on" in case something else was going on. So you
see the dilemma... just connect it and off you go. ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was going through adtpro and showing the wife how to work it and all that. And I came across the black-screen-on-the-Apple bug when everything is connected up and the pc running but not having started the server yet.
It is #2 in this thread:
https://sourceforge.net/p/adtpro/discussion/support/thread/19d41ed8/#5e53
I also read your comment about the nullness and stuff here:
https://sourceforge.net/p/adtpro/discussion/support/thread/19d41ed8/#db76
I'm asking if you'll be revisiting this issue?
Additional notes -
No settings in device manager make a difference.
This is on a genuine legacy serial port.
ADTPRO client version 1.3.0 does not exhibit this.
Pressing the ESC key on the Apple //e makes a bleee-blooop noise while the screen is blank.
Starting the server allows the client to continue.
No complaints - just trying to make a fine program 1% better than before (in a complete-ist sense).
I fixed that in 2.0.1 with respect to the GS, which is the only place I
knew it happened - are you (still) seeing it in this context, or in another?
On 3/22/2015 9:56 PM, Keatah wrote:
Yes still see it. Platinum //e + SSC..
Note if I disconnect and reconnect the serial cable, it gets past the black screen. OR, if I start the server while the screen is black - that prods it along too.
On 3/23/2015 6:42 PM, Keatah wrote:
Ok, then it is behaving the same way as the GS... it hangs until it gets
some kind of acknowledgement from the other side. I'm between a rock
and a hard place here: I need/want to send a "I'm home" signal to the PC
side whenever everything resets (also the first time the client starts
up). The GS and your hard serial port hang unless/until there's
something to "hear" it on the other end. Not a lot I can do about that
except avoid the check; but that runs the risk of not sending the "abort
whatever else was going on" in case something else was going on. So you
see the dilemma... just connect it and off you go. ;-)
Maybe do something with/after a timed interval? IDK.. Well do what you think is best for the project. That's all we can ask for.
Last edit: Keatah 2015-03-24