Gotta get new glasses.
@nap
Did not work![]()
Gotta get new glasses.
@nap
Did not work![]()
Dave
Always wear safety glasses while programming.
<body onload="setInterval('blinkIt()',1000)">
<script type="text/javascript">
function blinkIt() {
if (!document.all) return;
else {
for(i=0;i<document.all.tags('blink').length;i++){
s=document.all.tags('blink')[i];
s.style.visibility=(s.style.visibility=='visible') ?'hidden':'visible';
}
}
}
</script>
<blink>@ NOP</blink>
@nap will just define a label
nap without the @, is a PBP function, and it's not the same as ASM
<blink>@ NOP</blink>![]()
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
A half hearted compile of your code (Alian) for the 16F873A gave an error with DEFINE INTHAND _Blink.
I changed it to DEFINE INTHAND Blink and it did not come out of sleep (I presume) the same code compiles OK for the 16F628A.
I am sorry , I was busy with some other job, but today I shall try your code for the intended chip and post results.
Thank you for all your help,
regards
Hi, Charudatt
See chapter 9.3 ...
your device ( 16F873 ) has two mem. pages ... 16F628 only has ONE.
What does PbP for ASM Interrupts ???
What do you have to reserve as variables room ???
TWO beers now !!!
Cheers
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
euh... sorry i don't have any Java skills... i just copy/paste some script here and there.![]()
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I'm about to start a Java unit soon - maybe I'll teach you a thing or twoOut of interest, I've just found some good code for VB that allows serial comms without MSCOMM.ocx !!! http://www.thescarms.com/VBasic/commio.aspx No probs in XP either.
it's just too bad that it doesn't allow to open COM port > 15 or 16![]()
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Heh, how many comm ports do you have? I won't be terribly surprised if you tell me a 100 or so since I already know you have 2 monitors.
To handle higher ports, use "\\.\COMnn" (where nn is the port number, in decimal) when you define the port using the API.
You can patch the MSCOMM32.OCX control to allow ports >COM10. Use a hex editor to search for 3D 10 00 and change it to 3D xx 00 (where xx is the new upper limit, in hex) - e.g. 3D FF 00. NOTE: This may not work with all versions of the OCX.
CAUTION: Make a backup copy before patching.
My memory has faded but I think some early versions of the OCX worked above COM10.
Bookmarks