>
> If the problem can be worked around by patching a byte or two in the
> .oex file, a simple patching program (DOS or Win32 .exe) could be
> written in a few minutes. I'd do it right now if the necessary
> information was made available. It would let those with deadlines
> get on with their work.
>
And apparently it only affects C.1.1 because V6 does produce proper
event code for B.2.2+. Or, at least it seems to work...
The real difference must be in the C.1.1 firmware for events and the
compiler output wasn't changed to accomodate the new firmware.
A workable solution would be to have the chips reprogrammed with
B.2.2+ firmware. There would be a mail turn-around issue. Perhaps
the chips could be ordered direct from SavageInnovations.
With Priority Mail, the delivery could be quite fast. I order from
Digikey in Minnesota on Monday and receive the parts in California on
Wednesday.
There is never anything good that comes from being on the bleeding
edge. If C.1.1 works today, it will still work in a year or so. Same
with V6 vs V5. There's no hurry to upgrade; better the devil you know...
Richard
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment