|
<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
|
Rtfm !!!
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 " !!!
*****************************************
|
C'mon Mister_e, you can do better than that! - show us all some of your "real" java skills, like scrolling some 3D text with user definable parameters.Originally Posted by mister_e
<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>
|
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 two
|
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.
|
LMAO nah i don't have as this much of COM port. I only have 13. But you know, some USB-Serial (if not all) default value will be higher than COM15 - 16... which is the MSComm limit. Sure there's a way to do it with old VB version (5-6). Maybe one day i'll do a deeper API/DLL search.
I'm afraid, i will need to move to .NET soon
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
Veering off topic....
Don't most folks have 2 monitors? I couldn't imagine life otherwise. If I had more desk space I would move up to 3 or 4! (I still swear by CRTs, but am starting to consider a move towards LCD as $ goes down and image quality/size goes up), It would be an interesting poll to see how many monitor folks on this forum have and would like to have.
Steve
|
To handle higher ports, use "\\.\COMnn" (where nn is the port number, in decimal) when you define the port using the API.it's just too bad that it doesn't allow to open COM port > 15 or 16
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.
|
Yeah i saw the piping method a few times here and there... just never have the real requirment andd time to experiment it. Sure i keep the info handy.
one thing is sure VB.NET handle all available COM.. i know i have to move on that one... Not sure how good and how long VB6 will work with Vista... which i still don't want to have
i'd downloaded VbExpress today... and
Visual Studio is on the 'stuff to buy one day.. but ASAP' list. I'm waiting for 2007 release... Orcas, or something like that.
Visual Studio 6 did a nice job... already paid few times
PS an API call always work better... Mscomm seems to be erratic on lower baudrate on some machine, while an API call seems to solve most problems. But... who use low baudrate in 2007? ;-)
yeah indeed.. over 10 there's no problemj, over 16.. you have a problem. There's some OCX available here and there, i don't think they worth as long you can deal with API.My memory has faded but I think some early versions of the OCX worked above COM10
unfortunately, and as far as i'm aware of, there's no 'real' API guide. Those i know are just outdated.
Last edited by mister_e; - 17th May 2007 at 01:58.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks