32 bit windows memory limit
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3412
The Linux Memory Game 0.6c
The Linux Memory Game project is a childrens (and adults) game based on the card game. more>>
The Linux Memory Game project is a childrens (and adults) game based on the card game.
The Linux Memory Game is an X11 game using GTK+ library for children ages 3 and up. It is a lot more than the card game "Memory".
It has five skill levels, the higher ones are challenging to adults as well. Additionally, one can choose from the menu to match 2 cards or 3 cards, or match different cards.
This last "different card" mode can be a very good teaching tool for teaching languages, concepts, or association.
Main features:
- Extensible - add new images yourself without having to make changes to the program.
- Five skill levels appropriate for the youngest and the ones with the best brains.
- Can play two card matching or three card matching (more challenging!)
- Can set to match different cards. This can be used with apropriately designed pictures to teach children (or adults) words, concepts, or another language.
Enhancements:
- Fixed overflow bug in pixmaps_jump.
<<lessThe Linux Memory Game is an X11 game using GTK+ library for children ages 3 and up. It is a lot more than the card game "Memory".
It has five skill levels, the higher ones are challenging to adults as well. Additionally, one can choose from the menu to match 2 cards or 3 cards, or match different cards.
This last "different card" mode can be a very good teaching tool for teaching languages, concepts, or association.
Main features:
- Extensible - add new images yourself without having to make changes to the program.
- Five skill levels appropriate for the youngest and the ones with the best brains.
- Can play two card matching or three card matching (more challenging!)
- Can set to match different cards. This can be used with apropriately designed pictures to teach children (or adults) words, concepts, or another language.
Enhancements:
- Fixed overflow bug in pixmaps_jump.
Download (0.10MB)
Added: 2006-11-15 License: GPL (GNU General Public License) Price:
1073 downloads
Martian Memory 1.2
Martian Memory project consists of a simple memory game. more>>
Martian Memory project consists of a simple memory game.
Martian Memory is a simple memory game oriented to kids, featuring the Pachi el marcianos world characters.
The goal of the game is to pick up two identical chips from a board that contains 32. The game contains very nice visual effects, sounds, and very nice music composed by Jonne Valtonen.
Installing
Just do:
./configure
make
make install (as root).
Enhancements:
- Added the -f or --fullscreen switch.
- Changed some chips (removed bloody ones) the game is now "child safe".
- program exits if close window or press [F10].
- if two scores are equal they are ordered by minor time.
- time stops during a combo FX.
- the hiscores screen displays a "press right mouse button to return" sign.
<<lessMartian Memory is a simple memory game oriented to kids, featuring the Pachi el marcianos world characters.
The goal of the game is to pick up two identical chips from a board that contains 32. The game contains very nice visual effects, sounds, and very nice music composed by Jonne Valtonen.
Installing
Just do:
./configure
make
make install (as root).
Enhancements:
- Added the -f or --fullscreen switch.
- Changed some chips (removed bloody ones) the game is now "child safe".
- program exits if close window or press [F10].
- if two scores are equal they are ordered by minor time.
- time stops during a combo FX.
- the hiscores screen displays a "press right mouse button to return" sign.
Download (MB)
Added: 2006-12-26 License: GPL (GNU General Public License) Price:
1034 downloads
Gnome Memory Blocks 0.2
Gnome Memory Blocks project is a concentration game for GNOME. more>>
Gnome Memory Blocks project is a concentration game for GNOME.
This is GNOMEs version of the `memory blocks game originaly come from Semantec game pack for Win-3.11
<<lessThis is GNOMEs version of the `memory blocks game originaly come from Semantec game pack for Win-3.11
Download (0.42MB)
Added: 2006-12-05 License: GPL (GNU General Public License) Price:
1062 downloads
Zero Memory Widget 0.2.0
Zero Memory Widget is a widget library without a single bit of storage per widget. more>>
Widget libraries have now been developed and used for years. In all these libraries, widget instances require computer memory. But this memory is not really required, We have implemented a widget library to prove that it is possible to use zero bytes of memory per widget.
In such a library, there is no widget reference, so widget programming is easier even in a low level language such as C. Programs are more robust because they do not use pointers, make no memory management and do not translate data between application and widget.
To set the attributes of a widget, it is not possible to use the widgets pointer so a current state is used as in OpenGL. Most classic widgets were integrated into the library, and it is possible to integrate widgets of all kinds without any problem.
This library license is the GNU GPL. Beware: it is alpha software. It works but the API is not yet stable.
Main features:
Base widgets:
- text, text_editable, int, int_editable,
- anchor,
- button, tearoff, button_with_accelerator,
- image, image_from_file,
- scrollbar2, scrollbar_vertical, scrollbar_horizontal,
- toggle (bit or int or char) with or without label. Same for radio button. Really easy to use.
Container widgets:
- window, window_drag, window_popup_right, window_popup_bottom
- anchor_box,
- box_horizontal, box_vertical, box,
- decorator,
- notebook,
- scrolledview (can contains billions of children)
- viewport
- table, table_with_width,
- void, if, popup : base system to make transient widgets. The menu are constructed with "popup"
Composite widgets:
- alert (container),
- message (container),
- filechooser,
Widget attributes:
- Choice of the focus group.
- Width: padding, border, focus
- Expand: vertical, horizontal
- Alignment: vertical, horizontal
- Font: family, size, weight, style
- Geometry: x, y, width, height
- Window auto resize
- Sensibility (to overide the value computed automaticaly)
- Debug level
Other features:
- a drag and drop working only inside the application.
- fully working text cut and paste (UTF8 or not).
- simple animation possible.
- the library runs a web server allowing to debug.
- accelerators. If a modifier key is pressed, a list of short-cut with this key is displayed in a bubble tip.
Enhancements:
- Complete rewrite of the kernel API, in order to have :
- The library can now be updated without recompiling external code
<<lessIn such a library, there is no widget reference, so widget programming is easier even in a low level language such as C. Programs are more robust because they do not use pointers, make no memory management and do not translate data between application and widget.
To set the attributes of a widget, it is not possible to use the widgets pointer so a current state is used as in OpenGL. Most classic widgets were integrated into the library, and it is possible to integrate widgets of all kinds without any problem.
This library license is the GNU GPL. Beware: it is alpha software. It works but the API is not yet stable.
Main features:
Base widgets:
- text, text_editable, int, int_editable,
- anchor,
- button, tearoff, button_with_accelerator,
- image, image_from_file,
- scrollbar2, scrollbar_vertical, scrollbar_horizontal,
- toggle (bit or int or char) with or without label. Same for radio button. Really easy to use.
Container widgets:
- window, window_drag, window_popup_right, window_popup_bottom
- anchor_box,
- box_horizontal, box_vertical, box,
- decorator,
- notebook,
- scrolledview (can contains billions of children)
- viewport
- table, table_with_width,
- void, if, popup : base system to make transient widgets. The menu are constructed with "popup"
Composite widgets:
- alert (container),
- message (container),
- filechooser,
Widget attributes:
- Choice of the focus group.
- Width: padding, border, focus
- Expand: vertical, horizontal
- Alignment: vertical, horizontal
- Font: family, size, weight, style
- Geometry: x, y, width, height
- Window auto resize
- Sensibility (to overide the value computed automaticaly)
- Debug level
Other features:
- a drag and drop working only inside the application.
- fully working text cut and paste (UTF8 or not).
- simple animation possible.
- the library runs a web server allowing to debug.
- accelerators. If a modifier key is pressed, a list of short-cut with this key is displayed in a bubble tip.
Enhancements:
- Complete rewrite of the kernel API, in order to have :
- The library can now be updated without recompiling external code
Download (0.56MB)
Added: 2005-07-06 License: GPL (GNU General Public License) Price:
1573 downloads
Monkeys Memory 0.1.2
Monkeys Memory is an implementation of the classic game om memory. more>>
Monkeys Memory is an implementation of the classic game of memory. Classic Game of Memory written in mono where you can play against other people (on the same computer, network game is not implemented jet) or against Computer (there is 2 type of computer player).
There is more level of game from tiny level to very big one.
<<lessThere is more level of game from tiny level to very big one.
Download (0.18MB)
Added: 2007-06-28 License: GPL (GNU General Public License) Price:
854 downloads
Running Unix Memory Test 0.2
Running Unix Memory Test is a tool to check the memory without interrupting the service. more>>
The goal of RUMT is to check the memory of a computer over a long period of time and almost-real load conditions without having to interrupt the services.
RUMT exploits the possibility of some Unix kernels to selectivly disable some memory areas while still accessing them through the /dev/mem device. The principle of RUMT is to write pseudo-random data in these disabled memory areas, and later check them. This principle and the original code for the deterministic pseudo-random generator are from David Madore.
This distribution contains another variant on the same theme: URUMT allocates a large chunk of memory, locks it in memory using the mlock(2) system call, and scans /dev/mem to find where in physical memory the allocated area is. Then it continuously runs the same tests in that memory.
URUMT can not be used to test a particular area of memory: the kernel will give it whatever physical memory it feels like. But URUMT can be restarted now and then, hopefully getting different physical memory each time.
This is perfect if you suspect you have bad bits, but do not know at all where they are. Once you have sighted the bad bits, you can use a plain RUMT to test more extensively the neighborhood.
<<lessRUMT exploits the possibility of some Unix kernels to selectivly disable some memory areas while still accessing them through the /dev/mem device. The principle of RUMT is to write pseudo-random data in these disabled memory areas, and later check them. This principle and the original code for the deterministic pseudo-random generator are from David Madore.
This distribution contains another variant on the same theme: URUMT allocates a large chunk of memory, locks it in memory using the mlock(2) system call, and scans /dev/mem to find where in physical memory the allocated area is. Then it continuously runs the same tests in that memory.
URUMT can not be used to test a particular area of memory: the kernel will give it whatever physical memory it feels like. But URUMT can be restarted now and then, hopefully getting different physical memory each time.
This is perfect if you suspect you have bad bits, but do not know at all where they are. Once you have sighted the bad bits, you can use a plain RUMT to test more extensively the neighborhood.
Download (0.015MB)
Added: 2005-04-11 License: GPL (GNU General Public License) Price:
1663 downloads
Guarded Memory Move 0.6
Guarded Memory Move tool is useful for studying buffer overflows and catching them together with a good stack image. more>>
Guarded Memory Move project gets handy when you have to study buffer overflows and you need to catch them together with a "good" stack image. When a stack overflow has been exploited, the back trace is already gone together with good information about parameters and local variables, that are of vital importance when trying to understand how the attacker is trying to work out the exploit. The GMM library uses dynamic function call interception to catch the most common functions that are used by attackers to exploit stack buffers.
The GMM library uses the LD_PRELOAD capability and offers two services to the user. First of all, it avoids buffer overflow to allow the attacker to execute shell-code on your machine. Second, in case where an exploit is detected, the stack content is saved and a segmentation fault is triggered. The resulting core dump will then have all the necessary information to debug the exploit and fix the software. Internally, the library insert itself between the application and the glibc library and intercept functions that might lead to buffer overflow exploits. Before calling the glibc core function, the GMM layer saves part of the stack frame above the caller to a temporary location in its frame.
It also stores the previous three return addresses in its local storage before calling the glibc core function. When the core function returns, the GMM code samples again the previously recorded return addresses and, if they differ, it restores the previously saved stack frame and issue a segmentation fault. This with a clean stack frame, so that it can be inspected with a debugger. While other solutions exist to detect buffer overflow exploits, like for example StackGuard and StackShield, those differs from GMM in many ways. They live as gcc patches and do require you to rebuild your application to use their functionalities. The good of this approach is that every single function is protected against buffer overflows.
The bad of this solution is that every single function is protected against buffer overflows. That is, performance regression on the whole application, even if this is not really a huge problem when hunting for buffer overflows. Another solution similar to GMM is LibSafe, but it does not save and restore the stack frame by making it unusable for debugging. But lets see how GMM differs from the above listed solutions. First of all, GMM works everywhere there are stack frames and the gcc and glibc duo. That means that it is not limited to i386 only. And now the real reason for the GMM existence.
Enhancements:
- GCCs __builtin_return_address and __builtin_frame_address seems to return garbage instead of NULL at the last frame. This release fixes the problem.
<<lessThe GMM library uses the LD_PRELOAD capability and offers two services to the user. First of all, it avoids buffer overflow to allow the attacker to execute shell-code on your machine. Second, in case where an exploit is detected, the stack content is saved and a segmentation fault is triggered. The resulting core dump will then have all the necessary information to debug the exploit and fix the software. Internally, the library insert itself between the application and the glibc library and intercept functions that might lead to buffer overflow exploits. Before calling the glibc core function, the GMM layer saves part of the stack frame above the caller to a temporary location in its frame.
It also stores the previous three return addresses in its local storage before calling the glibc core function. When the core function returns, the GMM code samples again the previously recorded return addresses and, if they differ, it restores the previously saved stack frame and issue a segmentation fault. This with a clean stack frame, so that it can be inspected with a debugger. While other solutions exist to detect buffer overflow exploits, like for example StackGuard and StackShield, those differs from GMM in many ways. They live as gcc patches and do require you to rebuild your application to use their functionalities. The good of this approach is that every single function is protected against buffer overflows.
The bad of this solution is that every single function is protected against buffer overflows. That is, performance regression on the whole application, even if this is not really a huge problem when hunting for buffer overflows. Another solution similar to GMM is LibSafe, but it does not save and restore the stack frame by making it unusable for debugging. But lets see how GMM differs from the above listed solutions. First of all, GMM works everywhere there are stack frames and the gcc and glibc duo. That means that it is not limited to i386 only. And now the real reason for the GMM existence.
Enhancements:
- GCCs __builtin_return_address and __builtin_frame_address seems to return garbage instead of NULL at the last frame. This release fixes the problem.
Download (0.41MB)
Added: 2007-04-24 License: GPL (GNU General Public License) Price:
914 downloads
The Golly Game of Life Simulator 1.2
Golly is an open source, cross-platform Game of Life simulator. more>>
Golly project is an open source, cross-platform Game of Life simulator currently under development by Andrew Trevorrow and Tomas Rokicki.
Our goal is to write a world-class Life simulator, solicit ideas and help from the planets best Life hackers, and share some of our excitement.
Main features:
- Unbounded universe (limited only by memory).
- Fast, memory-efficient conventional algorithm.
- Super fast hashing algorithm for highly regular patterns.
- Responsive even while generating or garbage collecting.
- Reads RLE, Life 1.05/1.06, and macrocell formats.
- Can paste in patterns from the clipboard.
- Auto fit option keeps patterns sized to the window.
- Full screen option (no menu/status/tool/scroll bars).
- Built-in HTML help system (thanks to wxWidgets).
Enhancements:
- The X11 version of Golly has a number of bugs and limitations, so use the GTK version if you can (it requires GTK+ 2.x).
- If you want to build Golly from the source distribution then to avoid various bugs use wxGTK 2.7 or later.
<<lessOur goal is to write a world-class Life simulator, solicit ideas and help from the planets best Life hackers, and share some of our excitement.
Main features:
- Unbounded universe (limited only by memory).
- Fast, memory-efficient conventional algorithm.
- Super fast hashing algorithm for highly regular patterns.
- Responsive even while generating or garbage collecting.
- Reads RLE, Life 1.05/1.06, and macrocell formats.
- Can paste in patterns from the clipboard.
- Auto fit option keeps patterns sized to the window.
- Full screen option (no menu/status/tool/scroll bars).
- Built-in HTML help system (thanks to wxWidgets).
Enhancements:
- The X11 version of Golly has a number of bugs and limitations, so use the GTK version if you can (it requires GTK+ 2.x).
- If you want to build Golly from the source distribution then to avoid various bugs use wxGTK 2.7 or later.
Download (2.8MB)
Added: 2007-04-15 License: GPL (GNU General Public License) Price:
929 downloads
lx_lib structural memory library 20060226-1
lx_lib handles memory allocations as structures, keeping important information such as the remaining allocated space. more>>
lx_lib handles memory allocations as structures, keeping important information such as the remaining allocated space and the length of the used string internal to each variable (or descriptor).
Much of it was initially inspired by Dan Bernsteins stralloc library, but the two are not compatible, nor has there ever been any intention to make them compatible.
Main features:
- strings need not be scanned to determine their length
- the amount of allocated string remaining is easily determined
- promotes more secure programming practices
- if used correctly, lx_lib can offer a significant speed increase over traditional methods
- easy-to-use methods for manipulating strings
- generic descriptor support for buffered i/o
- generic descriptors enable fast scanning of input for specific characters (e.g. a newline)
Enhancements:
- Bits of the lx_map() interface have been updated for use with the 20060228-1 release of libnaw.
<<lessMuch of it was initially inspired by Dan Bernsteins stralloc library, but the two are not compatible, nor has there ever been any intention to make them compatible.
Main features:
- strings need not be scanned to determine their length
- the amount of allocated string remaining is easily determined
- promotes more secure programming practices
- if used correctly, lx_lib can offer a significant speed increase over traditional methods
- easy-to-use methods for manipulating strings
- generic descriptor support for buffered i/o
- generic descriptors enable fast scanning of input for specific characters (e.g. a newline)
Enhancements:
- Bits of the lx_map() interface have been updated for use with the 20060228-1 release of libnaw.
Download (0.024MB)
Added: 2006-04-13 License: GPL (GNU General Public License) Price:
1292 downloads
SigBrowser 0.4
SigBrowser is a small tool to display large signals (up to 2 GB filesize / 1-6 channels / 16 bit integer). more>>
SigBrowser is a small tool to display large signals (up to 2 GB filesize / 1-6 channels / 16 bit integer).
SigBrowser allows you to smoothly browse in a large signal. It can load 16 bit signed integer data with up to 6 interlaced channels.
Unfortunately theres no large-file support, so the limit is at 2 GB. You cant do much except looking at the signal with various zooming factors.
But if youre searching for certain artefacts in a signal then its probably quite useful for you.
It can visualize large signals with filesizes of up to 2 GB. Currently only 16 bit signed integer signals with up to 8 interlaced channels can be loaded.
Using a P4 @ 1.8 GHz with 512 MB RAM and a GeForce 4 graphics card you can scroll and zoom quite smoothly through the whole signal. On a Sun Ultra 1500 its a bit slower but you can still work fine with it.
By using something which I call block-reduction (BL). BL uses the fact that todays screens only have a limited amount of pixels. That means to display the whole signal at once, the worst case regarding performance restrictions, you would have to display thousands of samples on one pixel coordinate in x (horizontal) direction.
Assuming we plot lines between each pair of following samples the user will see a colored area which borders in vertical direction are the minimum and maximum value of all samples falling on the same x-coordinate.
Using this fact we let the user create a so called signal profile. Besides storing the sampling rate, file format info, number of channels to visualize and similar things its main purpose is to contain min/max pairs each of which calculated from a block of N samples per channel. N gets specified by the user, usually 10..50, depending on signal size and computer beeing used.
By visualizing these min/max blocks instead of the real signal as long as the user doesnt zoom into the signal to much we dont loose any information on the screen. But we get a nice performance boost as the signal profile has a much smaller size (signal_lengh_in_samples / N * 2) than the original signal has. Unfortunately we cant do this anymore when the user zooms into details. Then SigBrowser switches to direct display of the signal but it loads only about 1 MB of the original signal at once, which would result in a width of usually several screens.
Example:
* C = number of channels in origianl signal
* V = number of channels to visualize
* S = original signal length in samples per channel
* B = block size
I have a signal of 1.1 GB, C = V = 8 channels, 16 bit integer samples which in my case contains S = 73298610 samples per channel. Using a block size of B = 10 samples per min/max block (really smooth interaction on a P4 3.2 GHz) you get a signal-profile of S / B * 4 / (1024*1024) = 84 MB which you have to keep in memory.
<<lessSigBrowser allows you to smoothly browse in a large signal. It can load 16 bit signed integer data with up to 6 interlaced channels.
Unfortunately theres no large-file support, so the limit is at 2 GB. You cant do much except looking at the signal with various zooming factors.
But if youre searching for certain artefacts in a signal then its probably quite useful for you.
It can visualize large signals with filesizes of up to 2 GB. Currently only 16 bit signed integer signals with up to 8 interlaced channels can be loaded.
Using a P4 @ 1.8 GHz with 512 MB RAM and a GeForce 4 graphics card you can scroll and zoom quite smoothly through the whole signal. On a Sun Ultra 1500 its a bit slower but you can still work fine with it.
By using something which I call block-reduction (BL). BL uses the fact that todays screens only have a limited amount of pixels. That means to display the whole signal at once, the worst case regarding performance restrictions, you would have to display thousands of samples on one pixel coordinate in x (horizontal) direction.
Assuming we plot lines between each pair of following samples the user will see a colored area which borders in vertical direction are the minimum and maximum value of all samples falling on the same x-coordinate.
Using this fact we let the user create a so called signal profile. Besides storing the sampling rate, file format info, number of channels to visualize and similar things its main purpose is to contain min/max pairs each of which calculated from a block of N samples per channel. N gets specified by the user, usually 10..50, depending on signal size and computer beeing used.
By visualizing these min/max blocks instead of the real signal as long as the user doesnt zoom into the signal to much we dont loose any information on the screen. But we get a nice performance boost as the signal profile has a much smaller size (signal_lengh_in_samples / N * 2) than the original signal has. Unfortunately we cant do this anymore when the user zooms into details. Then SigBrowser switches to direct display of the signal but it loads only about 1 MB of the original signal at once, which would result in a width of usually several screens.
Example:
* C = number of channels in origianl signal
* V = number of channels to visualize
* S = original signal length in samples per channel
* B = block size
I have a signal of 1.1 GB, C = V = 8 channels, 16 bit integer samples which in my case contains S = 73298610 samples per channel. Using a block size of B = 10 samples per min/max block (really smooth interaction on a P4 3.2 GHz) you get a signal-profile of S / B * 4 / (1024*1024) = 84 MB which you have to keep in memory.
Download (0.12MB)
Added: 2005-07-21 License: GPL (GNU General Public License) Price:
1557 downloads
Zile is Lossy Emacs 2.2.41
Zile is Lossy Emacs is an Emacs clone. more>>
Zile project is a small Emacs clone. Zile is a customizable, self-documenting real-time open-source display editor. Zile was written to be as similar as possible to Emacs; every Emacs user should feel at home.
Main features:
Small
- It is very useful for small footprint installations (like on floppy disk) or quick editing sessions. A typical binary is about 100Kb.
8-bit clean
- Zile can operate with binary files.
Looks like Emacs
- Most Zile key sequences and function names are identical to Emacs ones.
Multi buffer editing with multi level undo
- The number of files and undo operations that Zile can handle is limited only by memory.
Multi window
- Zile can display multiple windows on the screen.
Killing, yanking and registers
- The standard killing, yanking and register features of Emacs are available under Zile.
Minibuffer completion
- Zile can complete commands and filenames in the minibuffer.
Auto fill (word wrap)
- Zile automatically breaks the lines when they become too wide (if the Auto Fill Mode is enabled).
Enhancements:
- This release stops long file names from causing problems with the modeline.
<<lessMain features:
Small
- It is very useful for small footprint installations (like on floppy disk) or quick editing sessions. A typical binary is about 100Kb.
8-bit clean
- Zile can operate with binary files.
Looks like Emacs
- Most Zile key sequences and function names are identical to Emacs ones.
Multi buffer editing with multi level undo
- The number of files and undo operations that Zile can handle is limited only by memory.
Multi window
- Zile can display multiple windows on the screen.
Killing, yanking and registers
- The standard killing, yanking and register features of Emacs are available under Zile.
Minibuffer completion
- Zile can complete commands and filenames in the minibuffer.
Auto fill (word wrap)
- Zile automatically breaks the lines when they become too wide (if the Auto Fill Mode is enabled).
Enhancements:
- This release stops long file names from causing problems with the modeline.
Download (0.34MB)
Added: 2007-08-10 License: GPL (GNU General Public License) Price:
807 downloads
MCP2510 Bit Timing Calculator 1.0
MCP2510 Bit Timing Calculator project is a bit timing calculator for the MCP2510. more>>
MCP2510 Bit Timing Calculator project is a bit timing calculator for the MCP2510.
It is a bit timing calculator which is very easy to use.
All you have to do is to choose the baudrate and the oscilator-frequency.
Sure you can edit and change all setting. You will see a graphical bit timing diagram which show you your current options.
At the end you will get a detailed report of your choosen options. See an example here: mcp2510btn
HowTo
On the first step you have to choose your wished baudrate and the oscilator-frequency.
Second you will get a great table with all avaible baudrate for you oscilator-frequency. The are already choosen some baudrates if your baudrate equals with some on the table. Otherwise you have to select them manually, but you will get deviations to you choosen baudrate. You will the the deviation in percent at the right table.
When you are ready you can go forward to step three.
Here you have first to select your wanted Nominal Bit Time Screenshot 2 [Step 3]and then you can edit/change to values for the single segments of a bit timing.
<<lessIt is a bit timing calculator which is very easy to use.
All you have to do is to choose the baudrate and the oscilator-frequency.
Sure you can edit and change all setting. You will see a graphical bit timing diagram which show you your current options.
At the end you will get a detailed report of your choosen options. See an example here: mcp2510btn
HowTo
On the first step you have to choose your wished baudrate and the oscilator-frequency.
Second you will get a great table with all avaible baudrate for you oscilator-frequency. The are already choosen some baudrates if your baudrate equals with some on the table. Otherwise you have to select them manually, but you will get deviations to you choosen baudrate. You will the the deviation in percent at the right table.
When you are ready you can go forward to step three.
Here you have first to select your wanted Nominal Bit Time Screenshot 2 [Step 3]and then you can edit/change to values for the single segments of a bit timing.
Download (0.017MB)
Added: 2006-11-03 License: GPL (GNU General Public License) Price:
640 downloads
Bit::Vector 6.4
Bit::Vector is an efficient bit vector, set of integers and big int math library. more>>
Bit::Vector is an efficient bit vector, set of integers and "big int" math library.
CLASS METHODS
Version
$version = Bit::Vector->Version();
Word_Bits
$bits = Bit::Vector->Word_Bits(); # bits in a machine word
Long_Bits
$bits = Bit::Vector->Long_Bits(); # bits in an unsigned long
new
$vector = Bit::Vector->new($bits); # bit vector constructor
@veclist = Bit::Vector->new($bits,$count);
new_Hex
$vector = Bit::Vector->new_Hex($bits,$string);
new_Bin
$vector = Bit::Vector->new_Bin($bits,$string);
new_Dec
$vector = Bit::Vector->new_Dec($bits,$string);
new_Enum
$vector = Bit::Vector->new_Enum($bits,$string);
Concat_List
$vector = Bit::Vector->Concat_List(@vectors);
OBJECT METHODS
new
$vec2 = $vec1->new($bits); # alternative call of constructor
@veclist = $vec->new($bits,$count);
Shadow
$vec2 = $vec1->Shadow(); # new vector, same size but empty
Clone
$vec2 = $vec1->Clone(); # new vector, exact duplicate
Concat
$vector = $vec1->Concat($vec2);
Concat_List
$vector = $vec1->Concat_List($vec2,$vec3,...);
Size
$bits = $vector->Size();
Resize
$vector->Resize($bits);
$vector->Resize($vector->Size()+5);
$vector->Resize($vector->Size()-5);
Copy
$vec2->Copy($vec1);
Empty
$vector->Empty();
Fill
$vector->Fill();
Flip
$vector->Flip();
Primes
$vector->Primes(); # Sieve of Erathostenes
Reverse
$vec2->Reverse($vec1);
Interval_Empty
$vector->Interval_Empty($min,$max);
Interval_Fill
$vector->Interval_Fill($min,$max);
Interval_Flip
$vector->Interval_Flip($min,$max);
Interval_Reverse
$vector->Interval_Reverse($min,$max);
Interval_Scan_inc
if (($min,$max) = $vector->Interval_Scan_inc($start))
Interval_Scan_dec
if (($min,$max) = $vector->Interval_Scan_dec($start))
Interval_Copy
$vec2->Interval_Copy($vec1,$offset2,$offset1,$length);
Interval_Substitute
$vec2->Interval_Substitute($vec1,$off2,$len2,$off1,$len1);
is_empty
if ($vector->is_empty())
is_full
if ($vector->is_full())
equal
if ($vec1->equal($vec2))
Lexicompare (unsigned)
if ($vec1->Lexicompare($vec2) == 0)
if ($vec1->Lexicompare($vec2) != 0)
if ($vec1->Lexicompare($vec2) < 0)
if ($vec1->Lexicompare($vec2) Lexicompare($vec2) > 0)
if ($vec1->Lexicompare($vec2) >= 0)
Compare (signed)
if ($vec1->Compare($vec2) == 0)
if ($vec1->Compare($vec2) != 0)
if ($vec1->Compare($vec2) < 0)
if ($vec1->Compare($vec2) Compare($vec2) > 0)
if ($vec1->Compare($vec2) >= 0)
to_Hex
$string = $vector->to_Hex();
from_Hex
$vector->from_Hex($string);
to_Bin
$string = $vector->to_Bin();
from_Bin
$vector->from_Bin($string);
to_Dec
$string = $vector->to_Dec();
from_Dec
$vector->from_Dec($string);
to_Enum
$string = $vector->to_Enum(); # e.g. "2,3,5-7,11,13-19"
from_Enum
$vector->from_Enum($string);
Bit_Off
$vector->Bit_Off($index);
Bit_On
$vector->Bit_On($index);
bit_flip
$bit = $vector->bit_flip($index);
bit_test
contains
$bit = $vector->bit_test($index);
$bit = $vector->contains($index);
if ($vector->bit_test($index))
if ($vector->contains($index))
Bit_Copy
$vector->Bit_Copy($index,$bit);
LSB (least significant bit)
$vector->LSB($bit);
MSB (most significant bit)
$vector->MSB($bit);
lsb (least significant bit)
$bit = $vector->lsb();
msb (most significant bit)
$bit = $vector->msb();
rotate_left
$carry = $vector->rotate_left();
rotate_right
$carry = $vector->rotate_right();
shift_left
$carry = $vector->shift_left($carry);
shift_right
$carry = $vector->shift_right($carry);
Move_Left
$vector->Move_Left($bits); # shift left "$bits" positions
Move_Right
$vector->Move_Right($bits); # shift right "$bits" positions
Insert
$vector->Insert($offset,$bits);
Delete
$vector->Delete($offset,$bits);
increment
$carry = $vector->increment();
decrement
$carry = $vector->decrement();
inc
$overflow = $vec2->inc($vec1);
dec
$overflow = $vec2->dec($vec1);
add
$carry = $vec3->add($vec1,$vec2,$carry);
($carry,$overflow) = $vec3->add($vec1,$vec2,$carry);
subtract
$carry = $vec3->subtract($vec1,$vec2,$carry);
($carry,$overflow) = $vec3->subtract($vec1,$vec2,$carry);
Neg
Negate
$vec2->Neg($vec1);
$vec2->Negate($vec1);
Abs
Absolute
$vec2->Abs($vec1);
$vec2->Absolute($vec1);
Sign
if ($vector->Sign() == 0)
if ($vector->Sign() != 0)
if ($vector->Sign() < 0)
if ($vector->Sign() Sign() > 0)
if ($vector->Sign() >= 0)
Multiply
$vec3->Multiply($vec1,$vec2);
Divide
$quot->Divide($vec1,$vec2,$rest);
GCD (Greatest Common Divisor)
$vecgcd->GCD($veca,$vecb);
$vecgcd->GCD($vecx,$vecy,$veca,$vecb);
Power
$vec3->Power($vec1,$vec2);
Block_Store
$vector->Block_Store($buffer);
Block_Read
$buffer = $vector->Block_Read();
Word_Size
$size = $vector->Word_Size(); # number of words in "$vector"
Word_Store
$vector->Word_Store($offset,$word);
Word_Read
$word = $vector->Word_Read($offset);
Word_List_Store
$vector->Word_List_Store(@words);
Word_List_Read
@words = $vector->Word_List_Read();
Word_Insert
$vector->Word_Insert($offset,$count);
Word_Delete
$vector->Word_Delete($offset,$count);
Chunk_Store
$vector->Chunk_Store($chunksize,$offset,$chunk);
Chunk_Read
$chunk = $vector->Chunk_Read($chunksize,$offset);
Chunk_List_Store
$vector->Chunk_List_Store($chunksize,@chunks);
Chunk_List_Read
@chunks = $vector->Chunk_List_Read($chunksize);
Index_List_Remove
$vector->Index_List_Remove(@indices);
Index_List_Store
$vector->Index_List_Store(@indices);
Index_List_Read
@indices = $vector->Index_List_Read();
Or
Union
$vec3->Or($vec1,$vec2);
$set3->Union($set1,$set2);
And
Intersection
$vec3->And($vec1,$vec2);
$set3->Intersection($set1,$set2);
AndNot
Difference
$vec3->AndNot($vec1,$vec2);
$set3->Difference($set1,$set2);
Xor
ExclusiveOr
$vec3->Xor($vec1,$vec2);
$set3->ExclusiveOr($set1,$set2);
Not
Complement
$vec2->Not($vec1);
$set2->Complement($set1);
subset
if ($set1->subset($set2)) # true if $set1 is subset of $set2
Norm
$norm = $set->Norm();
$norm = $set->Norm2();
$norm = $set->Norm3();
Min
$min = $set->Min();
Max
$max = $set->Max();
Multiplication
$matrix3->Multiplication($rows3,$cols3,
$matrix1,$rows1,$cols1,
$matrix2,$rows2,$cols2);
Product
$matrix3->Product($rows3,$cols3,
$matrix1,$rows1,$cols1,
$matrix2,$rows2,$cols2);
Closure
$matrix->Closure($rows,$cols);
Transpose
$matrix2->Transpose($rows2,$cols2,$matrix1,$rows1,$cols1);
<<lessCLASS METHODS
Version
$version = Bit::Vector->Version();
Word_Bits
$bits = Bit::Vector->Word_Bits(); # bits in a machine word
Long_Bits
$bits = Bit::Vector->Long_Bits(); # bits in an unsigned long
new
$vector = Bit::Vector->new($bits); # bit vector constructor
@veclist = Bit::Vector->new($bits,$count);
new_Hex
$vector = Bit::Vector->new_Hex($bits,$string);
new_Bin
$vector = Bit::Vector->new_Bin($bits,$string);
new_Dec
$vector = Bit::Vector->new_Dec($bits,$string);
new_Enum
$vector = Bit::Vector->new_Enum($bits,$string);
Concat_List
$vector = Bit::Vector->Concat_List(@vectors);
OBJECT METHODS
new
$vec2 = $vec1->new($bits); # alternative call of constructor
@veclist = $vec->new($bits,$count);
Shadow
$vec2 = $vec1->Shadow(); # new vector, same size but empty
Clone
$vec2 = $vec1->Clone(); # new vector, exact duplicate
Concat
$vector = $vec1->Concat($vec2);
Concat_List
$vector = $vec1->Concat_List($vec2,$vec3,...);
Size
$bits = $vector->Size();
Resize
$vector->Resize($bits);
$vector->Resize($vector->Size()+5);
$vector->Resize($vector->Size()-5);
Copy
$vec2->Copy($vec1);
Empty
$vector->Empty();
Fill
$vector->Fill();
Flip
$vector->Flip();
Primes
$vector->Primes(); # Sieve of Erathostenes
Reverse
$vec2->Reverse($vec1);
Interval_Empty
$vector->Interval_Empty($min,$max);
Interval_Fill
$vector->Interval_Fill($min,$max);
Interval_Flip
$vector->Interval_Flip($min,$max);
Interval_Reverse
$vector->Interval_Reverse($min,$max);
Interval_Scan_inc
if (($min,$max) = $vector->Interval_Scan_inc($start))
Interval_Scan_dec
if (($min,$max) = $vector->Interval_Scan_dec($start))
Interval_Copy
$vec2->Interval_Copy($vec1,$offset2,$offset1,$length);
Interval_Substitute
$vec2->Interval_Substitute($vec1,$off2,$len2,$off1,$len1);
is_empty
if ($vector->is_empty())
is_full
if ($vector->is_full())
equal
if ($vec1->equal($vec2))
Lexicompare (unsigned)
if ($vec1->Lexicompare($vec2) == 0)
if ($vec1->Lexicompare($vec2) != 0)
if ($vec1->Lexicompare($vec2) < 0)
if ($vec1->Lexicompare($vec2) Lexicompare($vec2) > 0)
if ($vec1->Lexicompare($vec2) >= 0)
Compare (signed)
if ($vec1->Compare($vec2) == 0)
if ($vec1->Compare($vec2) != 0)
if ($vec1->Compare($vec2) < 0)
if ($vec1->Compare($vec2) Compare($vec2) > 0)
if ($vec1->Compare($vec2) >= 0)
to_Hex
$string = $vector->to_Hex();
from_Hex
$vector->from_Hex($string);
to_Bin
$string = $vector->to_Bin();
from_Bin
$vector->from_Bin($string);
to_Dec
$string = $vector->to_Dec();
from_Dec
$vector->from_Dec($string);
to_Enum
$string = $vector->to_Enum(); # e.g. "2,3,5-7,11,13-19"
from_Enum
$vector->from_Enum($string);
Bit_Off
$vector->Bit_Off($index);
Bit_On
$vector->Bit_On($index);
bit_flip
$bit = $vector->bit_flip($index);
bit_test
contains
$bit = $vector->bit_test($index);
$bit = $vector->contains($index);
if ($vector->bit_test($index))
if ($vector->contains($index))
Bit_Copy
$vector->Bit_Copy($index,$bit);
LSB (least significant bit)
$vector->LSB($bit);
MSB (most significant bit)
$vector->MSB($bit);
lsb (least significant bit)
$bit = $vector->lsb();
msb (most significant bit)
$bit = $vector->msb();
rotate_left
$carry = $vector->rotate_left();
rotate_right
$carry = $vector->rotate_right();
shift_left
$carry = $vector->shift_left($carry);
shift_right
$carry = $vector->shift_right($carry);
Move_Left
$vector->Move_Left($bits); # shift left "$bits" positions
Move_Right
$vector->Move_Right($bits); # shift right "$bits" positions
Insert
$vector->Insert($offset,$bits);
Delete
$vector->Delete($offset,$bits);
increment
$carry = $vector->increment();
decrement
$carry = $vector->decrement();
inc
$overflow = $vec2->inc($vec1);
dec
$overflow = $vec2->dec($vec1);
add
$carry = $vec3->add($vec1,$vec2,$carry);
($carry,$overflow) = $vec3->add($vec1,$vec2,$carry);
subtract
$carry = $vec3->subtract($vec1,$vec2,$carry);
($carry,$overflow) = $vec3->subtract($vec1,$vec2,$carry);
Neg
Negate
$vec2->Neg($vec1);
$vec2->Negate($vec1);
Abs
Absolute
$vec2->Abs($vec1);
$vec2->Absolute($vec1);
Sign
if ($vector->Sign() == 0)
if ($vector->Sign() != 0)
if ($vector->Sign() < 0)
if ($vector->Sign() Sign() > 0)
if ($vector->Sign() >= 0)
Multiply
$vec3->Multiply($vec1,$vec2);
Divide
$quot->Divide($vec1,$vec2,$rest);
GCD (Greatest Common Divisor)
$vecgcd->GCD($veca,$vecb);
$vecgcd->GCD($vecx,$vecy,$veca,$vecb);
Power
$vec3->Power($vec1,$vec2);
Block_Store
$vector->Block_Store($buffer);
Block_Read
$buffer = $vector->Block_Read();
Word_Size
$size = $vector->Word_Size(); # number of words in "$vector"
Word_Store
$vector->Word_Store($offset,$word);
Word_Read
$word = $vector->Word_Read($offset);
Word_List_Store
$vector->Word_List_Store(@words);
Word_List_Read
@words = $vector->Word_List_Read();
Word_Insert
$vector->Word_Insert($offset,$count);
Word_Delete
$vector->Word_Delete($offset,$count);
Chunk_Store
$vector->Chunk_Store($chunksize,$offset,$chunk);
Chunk_Read
$chunk = $vector->Chunk_Read($chunksize,$offset);
Chunk_List_Store
$vector->Chunk_List_Store($chunksize,@chunks);
Chunk_List_Read
@chunks = $vector->Chunk_List_Read($chunksize);
Index_List_Remove
$vector->Index_List_Remove(@indices);
Index_List_Store
$vector->Index_List_Store(@indices);
Index_List_Read
@indices = $vector->Index_List_Read();
Or
Union
$vec3->Or($vec1,$vec2);
$set3->Union($set1,$set2);
And
Intersection
$vec3->And($vec1,$vec2);
$set3->Intersection($set1,$set2);
AndNot
Difference
$vec3->AndNot($vec1,$vec2);
$set3->Difference($set1,$set2);
Xor
ExclusiveOr
$vec3->Xor($vec1,$vec2);
$set3->ExclusiveOr($set1,$set2);
Not
Complement
$vec2->Not($vec1);
$set2->Complement($set1);
subset
if ($set1->subset($set2)) # true if $set1 is subset of $set2
Norm
$norm = $set->Norm();
$norm = $set->Norm2();
$norm = $set->Norm3();
Min
$min = $set->Min();
Max
$max = $set->Max();
Multiplication
$matrix3->Multiplication($rows3,$cols3,
$matrix1,$rows1,$cols1,
$matrix2,$rows2,$cols2);
Product
$matrix3->Product($rows3,$cols3,
$matrix1,$rows1,$cols1,
$matrix2,$rows2,$cols2);
Closure
$matrix->Closure($rows,$cols);
Transpose
$matrix2->Transpose($rows2,$cols2,$matrix1,$rows1,$cols1);
Download (0.13MB)
Added: 2007-05-17 License: Perl Artistic License Price:
890 downloads
Network Pipemeter 0.40
Network Pipemeter is a tool for measuring available bandwidth between hosts. more>>
Network Pipemeter is a tool for measuring available bandwidth between hosts. nepim is also useful to generate network traffic for testing purposes.
nepim operates in client/server mode, is able to handle multiple parallel traffic streams, reports periodic partial statistics along the testing, and supports IPv6.
nepim has been tested under Linux, Solaris and FreeBSD, though it should work under other platforms as well. If you manage to build nepim for different systems, please send the patch.
- nepim is useful to assess the throughput at the transport layer (TCP or UDP) as seen by applications.
- nepim runs single-threaded and should impose very light burden on your CPU. Unless, of course, your testing hosts have relatively high network bandwidth compared to low CPU power.
- One single server can service multiple clients simultaneously.
- As of nepim 0.11, one single client can interact simultaneously with multiple servers. For instance, suppose you want to test, from a single client, two remote servers, one located at 10.0.0.1,2000 and another at 192.168.0.1,3000:
- nepim -c 10.0.0.1,2000/192.168.0.1,3000
- The server listens to both TCP and UDP sockets. The client by default uses TCP sockets. Use the "-u" client option to switch the client operation to UDP.
- By default, only the server sends traffic towards the client. Use the "-s" client option to reverse the behavior, then only the client will send traffic. Use the "-d" client option to make both client and server to send traffic.
- Use the "-r" client option to establish an upper bit rate limit. Without a rate limiting option, nepim sends as fast as possible. See also "-R" below. Please notice the rate is specified in bps (bits per seconds); for instance, the following example states a rate limit of 100,000 bps (100 Kbps):
- nepim -c 10.0.0.1 -r 100000
- Use the "-R" client option to establish an upper "packet" rate limit (outbound rate limit for transport layer segments). Without a rate limiting option, nepim sends as fast as possible. If both "-r" and "-R" are given, nepim limits the sending rate at the lower of those bounds.
- Use the "-n" client option to run multiple parallel traffic streams.
- Use the "-b" server option to make the server to listen on specific local addresses.
- Use the "-6" option to disable IPv6 support.
Enhancements:
- Support for randomizing the UDP destination address/port has been added in order to put stress on routers with on-demand (dynamic) forwarding table caches.
<<lessnepim operates in client/server mode, is able to handle multiple parallel traffic streams, reports periodic partial statistics along the testing, and supports IPv6.
nepim has been tested under Linux, Solaris and FreeBSD, though it should work under other platforms as well. If you manage to build nepim for different systems, please send the patch.
- nepim is useful to assess the throughput at the transport layer (TCP or UDP) as seen by applications.
- nepim runs single-threaded and should impose very light burden on your CPU. Unless, of course, your testing hosts have relatively high network bandwidth compared to low CPU power.
- One single server can service multiple clients simultaneously.
- As of nepim 0.11, one single client can interact simultaneously with multiple servers. For instance, suppose you want to test, from a single client, two remote servers, one located at 10.0.0.1,2000 and another at 192.168.0.1,3000:
- nepim -c 10.0.0.1,2000/192.168.0.1,3000
- The server listens to both TCP and UDP sockets. The client by default uses TCP sockets. Use the "-u" client option to switch the client operation to UDP.
- By default, only the server sends traffic towards the client. Use the "-s" client option to reverse the behavior, then only the client will send traffic. Use the "-d" client option to make both client and server to send traffic.
- Use the "-r" client option to establish an upper bit rate limit. Without a rate limiting option, nepim sends as fast as possible. See also "-R" below. Please notice the rate is specified in bps (bits per seconds); for instance, the following example states a rate limit of 100,000 bps (100 Kbps):
- nepim -c 10.0.0.1 -r 100000
- Use the "-R" client option to establish an upper "packet" rate limit (outbound rate limit for transport layer segments). Without a rate limiting option, nepim sends as fast as possible. If both "-r" and "-R" are given, nepim limits the sending rate at the lower of those bounds.
- Use the "-n" client option to run multiple parallel traffic streams.
- Use the "-b" server option to make the server to listen on specific local addresses.
- Use the "-6" option to disable IPv6 support.
Enhancements:
- Support for randomizing the UDP destination address/port has been added in order to put stress on routers with on-demand (dynamic) forwarding table caches.
Download (0.038MB)
Added: 2007-08-18 License: GPL (GNU General Public License) Price:
802 downloads
Memory Structures Library 4.0
Memory Structures Library (MemSL) is a complete data structures/collection classes library with memory tracing. more>>
Memory Structures Library (MemSL) is a complete data structures/collection classes library with memory tracing, memory debugging, entry/exit tracing, exception handling, definable memory handlers, built-in thread support, and much more.
The project supports single, double, and circular linked lists, AVL balanced and threaded binary trees, dynamic hashing tables, stacks, queues and dequeues (using arrays or linked lists), sets (Pascal implementation, with union, difference, intersection, etc.), bags, tables and dictionaries, priority heaps, priority search queue, and more.
<<lessThe project supports single, double, and circular linked lists, AVL balanced and threaded binary trees, dynamic hashing tables, stacks, queues and dequeues (using arrays or linked lists), sets (Pascal implementation, with union, difference, intersection, etc.), bags, tables and dictionaries, priority heaps, priority search queue, and more.
Download (0.82MB)
Added: 2007-07-04 License: GPL (GNU General Public License) Price:
846 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above 32 bit windows memory limit search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed