Re: hp49g+ -- Problem with bad libs in second port
- From: "awilpert" <awilpert@xxxxxx>
- Date: 23 Jul 2005 11:21:20 -0700
Thousand thanks, Jean-Yves, this finally solved the problem. I will
keep this small program for the future.
Regards and thanks again,
Alexis
Jean-Yves Avenard wrote:
> awilpert wrote:
> > Thanks for the clarification Jean-Yves, I knew PINIT was used to solve
> > some port problems, but I did not know exactly which, that is why I
> > reported that PINIT was not working in my case.
> >
> > I did what you adviced ( 1 4046 + 1 ->TAG DUP DETACH PURGE ), but
> Sorry it should be:
> 1 4096 + 2 ->TAG DUP DETACH PURGE
>
> In fact this should work for any library with a number < 256:
> [lib_number] 4096 + [port_number] ->TAG DUP DETACH PURGE
>
> JY
.
- References:
- hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- From: Veli-Pekka Nousiainen
- Re: hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- From: Veli-Pekka Nousiainen
- Re: hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- From: Jean-Yves Avenard
- Re: hp49g+ -- Problem with bad libs in second port
- From: awilpert
- Re: hp49g+ -- Problem with bad libs in second port
- From: Jean-Yves Avenard
- hp49g+ -- Problem with bad libs in second port
- Prev by Date: hp48g don't work properly?
- Next by Date: Re: hp49g+ -- Problem with bad libs in second port
- Previous by thread: Re: hp49g+ -- Problem with bad libs in second port
- Next by thread: HP33s First impressions
- Index(es):