Re: [aprsisce] Printer Lock up -Resolved
I'm glad to know it's fixed and it really didn't have anything to do
with APRSIS32 (seemingly), but actually COM port activity. If this
turns out not to be the case, by all means, let me know and we'll keep
trying to figure out what's going on. As I've said before on this list,
for everyone that reports a problem or requests a feature, I figure
there are 5-10 others that need / want the same thing but not badly
enough to say something.
So speak up when you want / need something. I give great weight to your
requests. I might not get to it soon (or at all), but I do want to
implement what people want and I can't think of everything (although the
range circle and expanding yellow progress indicator is pretty unique, I
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
Michael A. Kelly wrote:
> Hello everyone,
> Just a follow up to my earlier printer problem. I ended up changing
> the Kam Plus from Comm 1 to Comm 2 changed nothing else and my problem
> appears to be solved after hours of running and printing.
> Thanks Lynn ...
> On Sat, Jun 12, 2010 at 10:25 PM, Michael A. Kelly <mkellync@...
> <mailto:mkellync@...>> wrote:
> The version is what was released today - 06-12-10 and as such, it
> is the development version .... and I just rebooted and it is
> still printing after 5 minutes with APRSIS32 running ... I will
> try it again in 20 minutes ... wonder if I could switch printer
> port number from 1 to 2?
> On Sat, Jun 12, 2010 at 12:15 PM, Lynn W. Deffenbaugh
> <kj4erj@... <mailto:kj4erj@...>> wrote:
> Also, is it the released version or the development version
> that you're
> running (What's the date on About)?
> Lynn (D) -KJ4ERJ
> kb4mk wrote:
> > Howdy everyone,
> > Does anyone have an issue with the printer not responding
> after aprsis32 runs an hour or so? My printer seems to quit
> communicating with the computer and anything I try to print
> (perhaps from MSWord) will not until I completely re-boot.
> Once I do re-boot, then the document that is in cue goes ahead
> and prints ....
> > I do not have this issue with UI-View, with same
> communication settings to the TNC - which is a Kam Plus ver
> 8.2 and I mention this only to clarify I do not think I have
> an interrupt problem - that is unless I am unaware of something.
> > Thanks,
> > Michael N4MAK