[sebhc] Image transfer problems

[Jack Rubin]

Carroll,

The XCON manual lists 444-70 and 444-74 as "equivalent" but it would be
nice to see a ROM dump of your -74 to see if there is any difference.

Jack

> -----Original Message-----
> From: sebhc at sebhc.org [mailto:sebhc at sebhc.org] On Behalf Of 
> Carroll Waddell
> Sent: Monday, June 14, 2004 8:47 PM
> To: sebhc at sebhc.org
> Subject: Re: [sebhc] Image transfer problems
> 
> 
> TO Dwight & Jack:
> 
> I just thought of something. The XCON8 rom I've heard you 
> talking about 
> is pn 444-70.
> My XCON8 ROM is pn 444-74.
> I don't know if this makes any difference at all.
> CEW
> 
> Jack Rubin wrote:
> 
> >I'm really itching to work with you guys, but right now my 
> son is still 
> >inhabiting my "workshop". He goes back to school next weekend, so I 
> >should be back on line with the Heathkit world then.
> >
> >Jack
> >
> >  
> >
> >>-----Original Message-----
> >>From: sebhc at sebhc.org [mailto:sebhc at sebhc.org] On Behalf Of
> >>Dwight K. Elvey
> >>Sent: Monday, June 14, 2004 7:29 PM
> >>To: sebhc at sebhc.org
> >>Subject: [sebhc] Image transfer problems
> >>
> >>
> >>Hi All
> >> I'm working right now with Carroll to solve his issues
> >>with my program. I suspect that it may be an issue
> >>with his serial being a little flaky but it may also
> >>be some RAM location that I'm not setting or resetting
> >>correctly. We are working with a XCON8 and H8-5 right now, 
> >>one of the configurations that I'd not checked. I've checked 
> >>the PAM8 and H8-5 as well as the XCON8 and H8-4. I do have 
> >>some code working on my machine with the XCON8 and H8-5 that 
> >>I did over the weekend but I still am a little suspicious of 
> >>some RAM that isn't being initialized correctly. My code 
> >>depends on the H17 code heavily and there are a lot of 
> >>variables to worry about. I'll be doing some testing tonight 
> >>where I'll clear the RAM with 000's and then with 377's to 
> >>make sure I didn't miss something.  If anyone else can try 
> >>the code and report back, I'd like to hear about it. I'd like 
> >>to make the next release as robust as I can. Dwight
> >>
> >>
> >>--
> >>Delivered by the SEBHC Mailing List
> sebhc-request at sebhc.org.
> >>
> >>    
> >>
> >
> >--
> >Delivered by the SEBHC Mailing List
> >
> >  
> >
> 

--
Delivered by the SEBHC Mailing List