 | | Announcing BricxCC release 3.3.5.6
|
|
(...) I was updating the website earlier today which may have caused some disruption. The link worked for me a few minutes ago. This is as good a time as any to post about my new release of BricxCC. Version 3.3.5.6 fixes an Access Violation during (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) Thanks for conducting the test... being 200+ miles away from my RCX this was bugging me :). My sources (gcc-2.95.2) have the same #define... but with the following about 120 lines earlier: /* Make int's 32 bits. */ #define TARGET_INT32 (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Gutting an optical mouse - Part I
|
|
(...) Gee, that's too bad. That means there are only three states that can be distinguished. It seems like they could have easily increased the resolution by 1/3, without any cost. (23 years ago, 12-Jul-02, to lugnet.robotics)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
John A. Tamplin, Jason Clark, Jochen Hoenicke and Michael J Ash: Thank you all for addressing these issues! It all make sense after reading the preceeding messages. I appologize for causing confusion. I am glad, however, to get it straight. ??So (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | detecting memory leaks
|
|
In the thread "anyone know how to check free space on RCX?" the issue of checking for memory leaks was raised. I wanted to mention that I have some code that may help in that area. I wrote a function for the memory manager called mm_defrag() It (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Gutting an optical mouse - Part I
|
|
(...) I thought this was an error to, so I spent about an hour triplechecking my findings. Bear in mind that the scroll wheel doesn't need 7.5-degree-per-step accuracy, which is what that extra bit would give. This is a chart of the data I collected (...) (23 years ago, 12-Jul-02, to lugnet.robotics)
|
| |
| | Re: MIBO Kits, Any interest?
|
|
(...) ...or at least if you looked at 100 people who might have the desires, abilities and budget to build the beast, you'd see 100 different inventory needs. Some might have one RIS, others two, others one - plus a bunch of ad-hoc parts. I think (...) (23 years ago, 13-Jul-02, to lugnet.robotics)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) The header is ok, but int is 2 bytes = 16 bit. You can check this with this highly optimized program: #include <conio.h> int main(int argc, char *argv[]) { lcd_int( sizeof( int ) ); for(;;) ; return 0; } And in the kernel sources, mm.c says (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) This can't be right. I'm about 99% sure that all of the ints I've used with my legOS programs have been 2 bytes. When using LNP to send RCX ints to a PC, for example, you have to use short on the PC end of things to make it all work right. (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Gutting an optical mouse - Part I
|
|
(...) It appears to me there is a slight mistake here. According to this, there is no way to distinguish between the first row and the second. I assume the second should be 10, so it would go 00 10 11 01. Steve (23 years ago, 12-Jul-02, to lugnet.robotics)
|
