Free trend micro pc cillin software for linux

Micro CMS project combines a search-engine-friendly WYSIWYG GUI with a simple, AJAX-based content management system, making the management of a static Web site easy and fast.
A typical session starts with the administrator loggin in via a simple form and then visiting the page which needs to change.
The administrator then clicks a button which is not present for normal readers and an interface for editing is presented, with a button for saving the changes. An easy installer program is included.
Main features:
- Micro CMS uses a WYSIWIG that is as search engine optimized as WYSIWYG gets!
- AJAX-based page editing makes making changes to your site nearly instantanious.
- Edit the content in-line. No need to fish around in some other interface for the right database entry, you can edit the content right where it is.
- Amazingly simple interface that anyone can understand. Setting up a site using Micro CMS only takes a few minutes.
- Support for CSS styling for extra search engine optimization.
- Easily preview changes before you commit to them.
- Supports versioning, so you can roll back changes with the click of a button. You set the number of versions you want to be able to save through the admin area.
- Comes with installer for easy database setup and configuration.
- Cross-browser compatibility. For real! If youre an Internet Explorer user, you have the added benefit of spell checking.

Trend is a general-purpose, efficient trend graph for "live" data. Data is read in ASCII form from a file or continuously from a FIFO and displayed in real-time into a multi-pass trend (much like a CRT oscilloscope). trend can be used as a rapid analysis tool for progressive or time-based data series together with trivial scripting.
Main features:
- OpenGL graphics
- Automatic or fixed graph scaling
- Two graph scrolling and shading modes
- Configurable colours/grid
- Flexible input
- Interactivity

OpenDMTP is a protocol and framework that allows bi-directional data communications between servers and devices (clients) over the Internet and similar networks.
OpenDMTP is particularly geared towards Location-based information (LBS) such as GPS, as well as temperature and other data collected in remote-monitoring devices. OpenDMTP is small, and is especially suited for micro-devices such as PDAs, mobile phones, and custom OEM devices.
We saw a need for a communications protocol that allowed high-latency, low-bandwidth (HL/LB) devices to transmit location data to monitoring-systems. Because these devices often have limited network connectivity, the protocol needed to be small and efficient.
Example devices include mobile phones, PDAs, OEM micro-devices (alarm systems, temperature monitors, etc.), and more.
There are many mobile GPS tracking devices on the market today with their own closed proprietary protocols. Searching the web for open protocols revealed only a few available for transferring data (including GPS information) between devices.
However these solutions are generally designed for non-mobile applications and lack some of the low-bandwidth, configurable, and extensible features that mobile applications require.
Main features:
Small Footprint: Mobile devices typically have limited resources on which to run client code (ie. memory, processor speed). An open protocol designed with this in mind should be optimized to allow efficient implementation and should support devices such as PDAs, mobile phones, GPS monitoring devices, and other OEM micro-devices.
Network Efficient: Because mobile devices typically have limited network connectivity, the protocol needs to be efficient in its dialog between the client and server. The communication needs to be optimized such that the necessary information can be conveyed with a minimum number of bytes in the least amount of time.
Bi-directional: Some devices can support two-way communication (ie. GPRS, or other socket based connections), while others may only support one-way communication (ie. some satellite communication systems). With this in mind, a protocol should be designed to support both duplex (two-way) and simplex (one-way) communication.
Transport Media: Differrent mobile applications will have their own unique way of communicating data back to the server. Some may use GPRS, or socket based communication, others may use satellite communication, while still others may use other forms of wireless communication, such as BlueTooth. The design of the protocol should be able to encompass all such transport media types, regardless of the type of transport in use.
Flexible Data Encoding: Most types of transport media allow for the transmission of binary encoded data. However, there may be some forms of media for which an ASCII encoded data packet is much better suited. A protocol designed with this in mind should be able to support both types of data encoding.
Configurable Messages: Due to the broad range of data types used in mobile applications, the protocol should be flexible enough to define standard messages, yet still allow custom messages within the framework.
Extensible: Not every mobile application is the same. Some require special handling and may have various types of inputs and outputs. A protocol designed for mobile applications should insure that the framework can be easily extended to incapsulate the specific needs of the device.
Industry Compatibility: Having an open protocol insures better compatibility between different client devices and service providers.
Reference Implementation: Having a reference implementation that showcases the major features of the protocol provides an easy starting point on which developers can add their own features and platform specific implementation without having to worry about how data gets from the client to the server.
Enhancements:
- Added additional logging for any errors returned by closedir, fflush, fclose.
- Additional changes made to facilitate dual transport support.
- Property PROP_COMM_HOST no longer uses localhost as a default. Also, if this property remains undefined during deployment, no events will be queued.
- When Geozone arrival/departure delay is in effect, the generated event will be the time and GPS fix of the moment that the geozone boundary crossing was detected.

UWG is a lightweight gadget/windowing toolkit for C and X11. Interfaces are described using XML and are turned into C code using the ubuildinit utility. Currently, only a small percentage of the planned gadgets are implemented.

Micro WG is a C `version of WG. In general, UWG is somewhat more light-weight than WG. Firstly because its written in C and not C++. Secondly because it does not yet provide all the features of WG. Also, it should be significantly easier to `connect UWG to KRoC.

Why UWG ? Its now the case that there are many `widget libraries for programmers to choose from. The traditional X11 widget libraries (X Toolkit Intrinsics), GTK, QT, Motif, wxWindows, TK, etc.. GTK and QT are probably the most common for an average users desktop system -- as the graphics libraries of Gnome and KDE respectively. C++, used by WG, provides a largely type-safe environment for gadget programming -- i.e. the structure/nature of gadgets fit neatly into the C++ type (class) heirarchy.

However, C++ ultimately suffers from the same problems as some other `object-orientated languages -- namely leaky encapsulation. When writing WG, some of the limitations (maybe features) of C++ caused significant problems, particularly in the function-pointer department. Object-orientation is a fine model for data, but it does not work well when `bolted-on to sequential languages -- C++ and Java in particular.

Forcing a sequential flow-of-control through something that we tried to break into objects only leads to problems. E.g. when executing inside the method of one object, is it safe to delete another object ? -- well, only if that other object wasnt involved (and still is involved) in the flow-of-control. And this you cannot easily tell. Furthermore, in many cases, `delete may be substituted for any object interaction (method-call).

Also, a lot of modern GUI toolkits seem unnecessarily bloated. C++ (and other `frilly languages) can be blamed for some of this, but not all of it. WG isnt bloated yet, but its not far off. UWG is therefore an attempt at a lightweight (size and speed) gadget toolkit for X11, programmed in C.

Libqrencode is a C library for encoding data in a QR Code symbol, a kind of 2D symbology that can be scanned by handy terminals such as a mobile phone with CCD. The capacity of QR Code is up to 7000 digits or 4000 characters, and is highly robustness.
Libqrencode supports QR Code model 2, described in JIS (Japanese Industrial Standards) X0510:2004 or ISO/IEC 18004. Currently the following features are not supported:
- ECI and FNC1 mode
- Structured Append Feature
- Micro QR Code
- QR Code model 1

Pocket PC System Controller is a client-server package that will allow you to use your pocket pc as a remote controller for your desktop by sending voice commands.

Installation:

This is the server part of the software which you can install on a linux system.
See the INSTALL file in the ppc-system-controller-linux directory for more information.

Viralator is a Perl script that virus scans HTTP/FTP downloads request on a UNIX server after passing through the Squid proxy server.
Even when I implemented virus protection for my network email server we still continued to get the odd virus. Most of the viruses came from people using free webmail accounts like Hotmail or Yahoo and downloading the infected attachments to their machines or through downloading junk.
Rather than block access to the users I decided to look at how we could better protect the network. I looked at a couple of different products both comercial and free but they were either too expensive or did not meet my needs.
That is how Viralator was born. Viralator Proxy Virus Scanner is licenced under the GPL.
Viralator should work in any UNIX system that uses Apache and Squid servers. We have reports about successful instalations on:
- RedHat Linux
- Mandrake Linux
- SuSe Linux
- e-Smith Linux
- Slackware Linux
- Conectiva Linux
- Debian Gnu Linux
Supported Redirectors:
- Squirm
- SquidGuard
- Jesred
Supported Virus Scanners
- AntiVir
- AVP
- RAV
- Inoculate
- Sophos Sweep
- McAfee
- Trend
- Clamav
- Bit Defender (free edition)
The original concept for Viralator came from the Viromat project. Without Viromat the Viralator project would not have had a starting point. We can also thank Ralph Meyer for badgering me into releasing the script under the GPL.
Enhancements:
- Parenthesis are included on the regular expression used to validate URLs.
- The character set checking step, which was not working before last patch released, has been fixed.