LittlBUGer.info Downloads Latest Uploads

ReactOS Live CD 0.3.8

Mon, 23 Mar 2009 13:46:06 +0000

The Live CD lets you try ReactOS without installing it on your hard drive. What is ReactOS? ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system. It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not "yet another OS". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows. While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003). Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications "out of the box." This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy. ReactOS® is a registered trademark of the ReactOS Foundation. Windows® NT is a registered trademark of Microsoft Corporation. Why Reactos? A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?. We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here: * There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today). * There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT). * Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility. * Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications. * There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level. * Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family. * There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them). Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

ReactOS VMWare 0.3.8

Mon, 23 Mar 2009 13:44:40 +0000

This package contains a VMware virtual machine with a preinstalled version of ReactOS. What is ReactOS? ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system. It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not \\\"yet another OS\\\". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows. While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003). Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications \\\"out of the box.\\\" This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy. ReactOS® is a registered trademark of the ReactOS Foundation. Windows® NT is a registered trademark of Microsoft Corporation. Why Reactos? A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?. We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here: * There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today). * There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT). * Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility. * Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications. * There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level. * Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family. * There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them). Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

ReactOS Install 0.3.8

Mon, 23 Mar 2009 13:41:55 +0000

With the Installation CD, you can install ReactOS on a computer. What is ReactOS? ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system. It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not "yet another OS". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows. While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003). Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications "out of the box." This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy. ReactOS® is a registered trademark of the ReactOS Foundation. Windows® NT is a registered trademark of Microsoft Corporation. Why Reactos? A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?. We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here: * There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today). * There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT). * Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility. * Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications. * There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level. * Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family. * There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them). Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

AutoPatcher Updater v1.05

Sat, 21 Mar 2009 16:35:47 +0000

How many times did you have to leave your computer, after a format, to download the updates you had before it? How many times did you have to go do something else, leaving your friend's computer download the load of updates with their poor little dial-up modem? How many times have you wished for the updates to be portable from one computer to another and not require but a few mouse clicks to install?

If you're the \"computer guy\" of the pack, no doubt the answer to the above questions was \"I've lost count\"! And if you have one or two computers you should consider yourself lucky as well. Think of what would happen if you had to update ten or twenty computers daily!

Is there any way to avoid all this trouble?

Besides the updates one finds on Windows Update (which are not portable), Microsoft also issues special updates (called administrative updates or network install updates), which do not require an Internet connection present during the installation process. The user however will have to answer to a series of (for the most part identical) questions. Even this can be an annoyance since it requires the user's presence for quite some time.

The solution!

AutoPatcher is based on the functionality of these special updates, automating their installation process. This way, with only a few mouse clicks and two minutes of your time, AutoPatcher is able to continue with the installation of the items you selected. In short, AutoPatcher combines the advantage of both Windows Update (presentation and description of updates and automated installation), and the special administrative updates (portability and installation without the need of an Internet connection).

joomla 1.5.9 update

Sat, 10 Jan 2009 18:51:27 +0000

joomla cms 1.5.8 to 1.5.9 update

css menu creator

Mon, 29 Dec 2008 03:40:28 +0000

css menu creator

Notepad++ 5.1.2

Wed, 17 Dec 2008 01:41:37 +0000

Notepad++ is a free source code editor (and Notepad replacement), which supports several programming languages, running under the MS Windows environment.
This project, based on the Scintilla edit component (a very powerful editor component), written in C++ with pure win32 api and STL (that ensures the higher execution speed and smaller size of the program), is under the GPL Licence.

Syntax Highlighting and Syntax Folding
WYSIWYG
User Defined Syntax Highlighting
Auto-completion
Multi-Document
Multi-View
Regular Expression Search/Replace supported
Full Drag 'N' Drop supported
Dynamic position of Views
File Status Auto-detection
Zoom in and zoom out
Multi-Language environment supported
Bookmark
Brace and Indent guideline Highlighting
Macro recording and playback

Digsby Beta (build 43)

Wed, 17 Dec 2008 01:37:28 +0000

Digsby, IM, email and Social networks in one easy to use application.
Instant Messaging - digsby is a multiprotocol IM client that lets you chat with all your friends on AIM, MSN, Yahoo, ICQ, Google Talk, and Jabber with one simple to manage buddy list.

Email Notifications - digsby is an email notification tool that alerts you of new email and lets you perform actions such as 'Delete' or 'Report Spam' with just one click.

Social Networking - digsby is a social networking tool that alerts you of events like new messages and gives you a live Newsfeed of what your friends are up to.

Version 38 onwards is a stub installer that includes numerous toolbars etc., we recommend you do not install these.

CuteFTP 8.3.2 Home

Wed, 17 Dec 2008 01:33:43 +0000

Cute FTP Home is a utility for transferring files between your computer and a remote File Transfer Protocol (FTP) server anywhere on the Internet.
It offers the perfect blend of ease-of-use and performance for the home or personal FTP user. Whether publishing a Web page, downloading the latest digital images, music and software or transferring large files between your home and office. Cute FTP Home will get the job done quickly and easily, even if you are a beginner.

ReactOS Install 0.3.7

Thu, 20 Nov 2008 19:32:20 +0000

With the Installation CD, you can install ReactOS on a computer.

What is ReactOS?

ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.

It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not "yet another OS". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows.

While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003).

Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications "out of the box." This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy.

ReactOS® is a registered trademark of the ReactOS Foundation.
Windows® NT is a registered trademark of Microsoft Corporation.

Why Reactos?

A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?.

We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here:

* There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today).
* There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT).
* Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility.
* Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications.
* There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level.
* Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family.
* There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them).

Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

ReactOS Live CD 0.3.7

Thu, 20 Nov 2008 19:27:02 +0000

ReactOS VMWare 0.3.7

Thu, 20 Nov 2008 19:22:10 +0000

This package contains a VMware virtual machine with a preinstalled version of ReactOS.

What is ReactOS?

ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.

It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not \\\"yet another OS\\\". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows.

While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003).

Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications \\\"out of the box.\\\" This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy.

ReactOS® is a registered trademark of the ReactOS Foundation.
Windows® NT is a registered trademark of Microsoft Corporation.

Why Reactos?

A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?.

We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here:

* There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today).
* There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT).
* Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility.
* Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications.
* There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level.
* Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family.
* There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them).

Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

ReactOS VMWare 0.3.5

Mon, 14 Jul 2008 13:47:37 +0000

This package contains a VMware virtual machine with a preinstalled version of ReactOS.

What is ReactOS?

ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.

It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not \"yet another OS\". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows.

While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003).

Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications \"out of the box.\" This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy.

ReactOS® is a registered trademark of the ReactOS Foundation.
Windows® NT is a registered trademark of Microsoft Corporation.

Why Reactos?

A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?.

We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here:

* There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today).
* There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT).
* Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility.
* Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications.
* There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level.
* Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family.
* There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them).

Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

ReactOS Install 0.3.5

Mon, 14 Jul 2008 13:45:57 +0000

With the Installation CD, you can install ReactOS on a computer.

What is ReactOS?

ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.

It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not "yet another OS". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows.

While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003).

Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications "out of the box." This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy.

ReactOS® is a registered trademark of the ReactOS Foundation.
Windows® NT is a registered trademark of Microsoft Corporation.

Why Reactos?

A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?.

We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here:

* There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today).
* There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT).
* Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility.
* Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications.
* There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level.
* Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family.
* There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them).

Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

ReactOS Live CD 0.3.5

Mon, 14 Jul 2008 13:43:21 +0000

The Live CD lets you try ReactOS without installing it on your hard drive.

What is ReactOS?

ReactOS is a free and open-sourced operating system based on the Windows NT architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.

It would be perhaps important to start by saying what ReactOS -isn't-. It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past. ReactOS is also not "yet another OS". It does not attempt to be a third player, like SkyOS or any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows.

While ReactOS' source availability and current usage is mostly intended for programmers to expand and improve on, you don't need to be a rocket scientist to use it, and in its final state will be a consumer friendly OS. If you've used Windows before, you'll find yourself in a familiar environment with ReactOS. The learning curve, if any, should be minimal, since ReactOS duplicates many of the Windows graphical environment applets, control panels and dialogs (Windows 2000/XP/2003).

Focus at present is on developing ReactOS to a stage where it is capable of running most Windows drivers and applications "out of the box." This does not mean that ReactOS will stop there, however; as new features are added to Windows, our developers be striving to incorporate such new features in future versions of ReactOS. Once the compatibility level has been reached, we may even choose to improve ReactOS beyond its Windows roots. These changes would be external from the main OS, and totally compatible with Windows, but they would add an extra advantage. For example, one of our goals is to have built-in POSIX compatibility, much like Windows Services for Unix. It could also be as simple as natively supporting multiple desktops however, instead of requiring a powertoy.

ReactOS® is a registered trademark of the ReactOS Foundation.
Windows® NT is a registered trademark of Microsoft Corporation.

Why Reactos?

A lot of people in popular discussion forums keep asking why should I use ReactOS or why would someone need ReactOS or why not help develop Wine instead? or why not use Linux with Wine?.

We have an answer for all these questions, but it's not some simple magic word. Let's name a few key issues here:

* There are plenty of *nix operating systems out there, this is very good. However they have different targeting (they perfectly fit server market, but desktop still isn't conquered, and several factors work against most Windows alternatives out today).
* There is currently no operating system which implements the kernel architecture design of MS Windows NT family (GNU/Linux is the best for comparison here: Linux was started as clone of Minix and Unix (eventually going on to be a Unix replacement), and ReactOS was started as clone of Windows NT).
* Linux+Wine is never going to be a complete replacement for a full Windows system. It's not only because Linux (despite there are some really user-friendly Linux distros out there), and not only because many users might find a transition to Linux/BSD difficult, but it's due to design and implementation decisions of Linux and Wine architectures, which prevent 100% compatibility.
* Even though Linux supports many types of hardware, Windows is still the dominant platform for device manufactorers. There are attempts to overcome this situation (like NDIS Wrapper for NT network card drivers, there are rumours about supporting NT video drivers, Captive NTFS for NT filesystem support), but ReactOS solves them from the first day by its design be compatible with existing drivers and existing applications.
* There are many people who do not like how *nix systems behave or dislikes the conventions used. For them, Linux, BSD, and Mac OS X are not options, even before application compatibility and hardware support come into play. An operating system should give the consumers what they want instead of demanding the consumer conform. Even with WINE, you are still running an operating system that behaves quite differently from Windows, at a user and system level.
* Backwards compatibility. This is something vital for many people and companies, but the development philosophy of Linux and the GNU project do not consider it a priority. The Windows family has always went out of its way to ensure a stable API and backwards compatibility. By its design, ReactOS will also follow the philosophy of backwards compatibility with existing and future applications designed for the Windows NT family.
* There are no plans for Windows to become released under a GPL-compatible license (at least, ReactOS team is not aware of them).

Finally, ReactOS offers a third alternative, for people who are fed up with Microsoft's policies but do not want to give up the familiar environment, architectural design, and millions of existing software applications and thousands of hardware drivers.

Fakefactory's Cinematic Mod V8.0 (Part 6/6) (Beta 1)

Tue, 17 Jun 2008 15:18:02 +0000

Cinematic Mod's anticipated port to the Orangebox Engine is here! Bear in mind this Beta 1 of V8.0 are there will be some known and unknown issues as depicted below. If you would rather wait for the complete version, that will available as soon as everything is polished out.

THIS VERSION BRINGS THE ORANGEBOX ENGINE TO OLD HL2 AND EP1. IT INSTALLS INDEPENDENT FROM CM7 OR OLDER VERSIONS. TO PLAY THIS MOD, YOU MUST OWN HALF-LIFE 2 / EPISODE ONE / EPISODE TWO FULLY INSTALLED AND UNLOCKED (= started at least one time)! YOU CANNOT PLAY THIS MOD WITHOUT EPISODE TWO CONTENT!

Please note this download is 5.53 GB in size and is split up into 6 .rar files for convenience & easier downloading.

Make sure you download ALL 6 parts and extract with WinRAR: - Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6

Features:

* Updated engine to the Orangebox for improved graphics and gameplay
* Raise the quite outdated graphical appearance to a state-of-the-art level
* Give the HL2 trilogy a more stressed, darker and minatory look
* Complement the atmosphere with a emotional cinematic music soundtrack that fits the action on the screen
* Replace the low-resolution textures with high resolution counterparts and more detailed environments
* Complement the storyline with the unused content from the original games
* Refresh the look and feel with optional new HD models
* Add more replay-value to the game
* Give the facepunch monkeys something to complain about

The following issues are known and currently unfixed in V8.0 Beta 1:

* At the first teleport-sequence out of Kleiners Lab, during the "visit" at Breens office: Breen cannot stand up
* The teleport rings at Kleiners Lab are not rotating & have been disabled completely as a temporary workaround
* The Valve-Alyx/HD-Body hybrid model is far from finished
* The CM7 and older models aren't included
* New dynamic shadows are disabled by default on some systems
* Remember to set the shadow settings to high for activating the new effects.
* The new Valve-style Mossman/Eli/Breen/Barney HD-models aren't included, because they are too far from a usable stage.

Please ensure you READ the info given below in the readme section before installing or playing the mod. Feel free to report any bugs or glitches and post your comments or suggestions below. Fakefactory does tend to read these over time. Enjoy!

------------------------------------------------- README----------------------------------------------

FAKEFACTORY CINEMATIC MOD V8 ORANGEBOX Build 8.0 beta1

for Half-Life 2 / Half-Life 2: Episode One / Half-Life 2: Episode Two
--------------------------------------------------------

THIS VERSION BRINGS THE ORANGEBOX ENGINE TO OLD HL2 AND EP1.
IT INSTALLS INDEPENDENT FROM CM7 OR OLDER VERSIONS

TO PLAY THIS MOD, YOU MUST OWN HALF-LIFE 2 / EPISODE ONE / EPISODE TWO FULLY
INSTALLED AND UNLOCKED (= started at least one time)!
YOU CANNOT PLAY THIS MOD WITHOUT EPISODE TWO CONTENT!

--------------------------------------------------------
Remember to activate "High Quality" model and graphic settings in the options dialog.
--------------------------------------------------------

HOW TO INSTALL:

Unpack FAKEFACTORY_CM8.part1.rar with Winrar after you have all 6 parts downloaded to the same location.
WinRar will unpack the following parts 2-6 automatically. Start the installation with setup.exe.
DON'T UNPACK THE ZIP-FILES IN INSTALLER FILES FOLDER.
SETUP.EXE WILL DO THIS FOR YOU.

CHANGES SINCE CM 7:
-------------------------------------------------

- Orangebox engine for HL2 and EP1 (new particle and dynamic shadow effects for HL2 + EP1)
- Enhanced Alyx HD-model (VALVE style face) -> still not finished
- Enhanced Alyx HD-model (Adriana Lima face)
- Enhanced Civilian HD-models (now its the time to give them a try)
- hacked all HL2 levels for Orangebox compatibility
- fixed all known texture errors
- fixed the "hopping mossman" bug in novaprospect
- tweaked the HDR/BLOOM effects on HL2 maps (less blooming) -> still not finished

CHANGES SINCE CM 4/5/6:
-------------------------------------------------

- Reworked sounds and music
- Almost all textures reworked or updated
- Added Hires-Detail-Overlays
- Added HDR to HL2 (See below)
- Fixed two potential crash-bugs
- One pack for all episodes

HDR for HL2
-------------------------------------------------

Not all HL2 maps are true HDR, because not all sources are available. For all other maps i used a technique, that i call "Entity injection". Technically i've used clientcommand entities and tonemapcontrollers to achieve a hdr-like type of blooming on those maps. This type of bloom is much more realistic than the old bloom mini-mod, because the effect is controllable inside the map for different settings at certain locations. You can call it HDR V0.5 or Bloom V2. Its some kind of super-ehanced bloom that gives a near-HDR look on the old HL2 maps. Some of the map-settings aren't final (i'm still at the fine-tuning phase)

CHARACTER PIMPER:
--------------------------------------------------

You can use the "Character Pimper" to switch between HD models andoriginal VALVE models.

The Alyx HD-model was built from scratch, all other models are based on massive modified POSER7 models and compiled with a rewritten studiocompiler, that is allowing a much higher polycount than VALVE's original compiler. The facial animations were build with 3DS MAX and exported with Cannonfodders VTA -exporter.

USING OLD CM6.x Alyx Hires models in this version
--------------------------------------------------

The V8 Alyx models are completely reworked with enhanced skeletton and facial animations. The older CM6 models are not longer used. If you want the older models from your CM6 installation, make a copy of the CM6-Characterpimper "repository" folder and the CM6 "hl2\materials\models\Adriana" folder before you uninstall it.

After installation of CM8 is completed, you can copy the old content to the V8 directory, BUT DON'T OVERWRITE V8 FILES! I strongly recommend to use the new CM8 models. They are optimized for the Orangebox engine. I will release recompiled V6 models as a update-patch in the near future.

SOUND DROPS OR CRACKLING:
-------------------------------------------------

If sound crackles occures, you can fix this by setting the snd_mixahead value in the autoexec's of CM's subdirectories. You will find the autoexec.cfg in the

FAKEFACTORY_CM8\hl2\cfg
FAKEFACTORY_CM8\episodic\cfg
FAKEFACTORY_CM8\ep2\cfg

directories. Try different value like snd_mixahead "0.2" or snd_mixahead "0.4" for increasing the buffered time of soundsamples. This will fix crackling or dropouts, but can lead to slightly asynchronous or delayed sounds.

MICROSTUTTER AND HEAPSIZE
--------------------------------------------------

If you encounter microstuttering ingame (animations), try the heapsize command.
Add -heapsize {bytes} to the shortcuts, i.e.:

Shortcut: Cinematic Mod EP2
Target: "....\Launcher_EP2.exe" -heapsize 512000.

But NEVER set the heapsize above [YOUR INSTALLE RAM / 3] or 512MB

SETUP.EXE AND VIRUS-WARNING
--------------------------------------------------

Setup uses a tool called SetACL for setting write permissions to the mods screenshots / cfg / SAVE directories. Some antivirus software could warn about possible malware. This is a false positive.

TECHNICAL INFO:
--------------------------------------------------

Thi mod's binaries are modified for memory allocation beyond 2 GB. To prevent STEAM from overwriting this binaries with its own copies on each start, the mod ist using a little launcher, that reroutes STEAM's original binaries to >NIL.

Start this mod only with the shortcuts in your start menu (that were created during installation)!

HARDWARE REQUIREMENTS:

- DX9 capable graphics hardware with minimum 256 MB VRAM. (512 MB recommended)
- 3 GB RAM (4 GB recommended)

SOFTWARE REQUIREMENTS:

- Fully installed STEAM Client; You can't start the mod without STEAM running.
- Fully installed and unlocked HL2 / EP1 / EP2; Make shure, you have started those games in the past.

32 BIT WARNING:
--------------------------------------------------

This mod was developed and tested on 64 Bit Windows. It is NOT supported on 32 Bit Windows, because of the limited Userspace with 32 Bit systems. You can try it on 32 Bit, but prepare for crashes.

On some 32 Bit systems it is possible to overcome this limitation with some boot.ini switches for raising the userspace limit. I'm not going into detail here, because those tweaks are dangerous and should only
be done by people, who are knowing exactly, what they do.

ADDENTUM FOR VERSION 7 and 8:

V7 of this mod uses much more Hires textures than the previous versions. This means: The engine has to cache a peak-value of >2GB texturedata at runtime. It's almost impossible to play this mod crash-free on 32 Bit systems
without lowering the graphics settings.

USED SOFTWARE FOR THIS MOD:

Adobe Photoshop CS2
3DS MAX 8
E-Frontier Poser 7
Microsoft C++ Visual Studio 2005
Powerbasic 8
VALVE Source SDK
Sony Soundforge 7
Sony Vegas 7
Crazy Bump 5
Cannonfodders SDK tools
entspy
vmex
Autoplay Mediastudio Pro
Setup Factory

USED TEXTURE RESOURCES:

Majang.com
3d.sk
Dosch
environmenttextures.com
Own photos

USED MODEL RESOURCES:

contentparadise.com
efrontier.com
daz3d.com

Fakefactory's Cinematic Mod V8.0 (Part 5/6) (Beta 1)

Tue, 17 Jun 2008 15:16:36 +0000