Pages

Wednesday, March 2, 2016

PlayOnBSD easily install and run Windows software for use with Wine

I just noticed that PlayOnBSD version 4.2.8 has been added to the FreshPorts repository. It should be allot easier and straight forward for BSD users to play Games and run productivity software on FreeBSD and PC-BSD now. So, if you need to run a Microsoft Windows Game or office application go and install the port and start testing PlayOnBSD and Wine now.


This is the adaptation of PlayOnLinux to FreeBSD. The purpose of this
program is to simplify installation of MS Windows software to run under
the Windows emulator "Wine".

The name indicates, that the program was initially developed to support
easy installation of Windows games on Linux. The range of supported
applications has long been extended to cover a wide range of windows
applications including Microsoft Office.

PlayOnFreeBSD behaves significantly different than PlayOnLinux in a
number of aspects, e.g. which version of Wine to use (only a single
version is normally installed on FreeBSD, but PlayOnLinux tries to run
each Windows application in a Wine environment that has previously been
reported to give good results and installs missing Wine versions in the
user's home directory).

Reviewed by: antoine
playonbsd Easily install and run Windows software for use with wine
4.2.8 emulators on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port
Maintainer: se@FreeBSD.org search for ports maintained by this maintainer
Port Added: 18 Feb 2016 13:24:24
Also Listed In: games
License: GPLv3
This is a port of PlayOnLinux to FreeBSD. It allows you to easily install 
and use numerous games and apps designed to run with Microsoft Windows.
The Windows emulation is provided by Wine.

WWW: http://www.playonlinux.com/
SVNWeb : Homepage : Distfiles Availability : PortsMon

To install the port: cd /usr/ports/emulators/playonbsd/ && make install clean
To add the package: pkg install playonbsd
PKGNAME: playonbsd

NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Runtime dependencies:
  1. 7z : archivers/p7zip
  2. bash : shells/bash
  3. glxinfo : graphics/mesa-demos
  4. gpg : security/gnupg
  5. gsed : textproc/gsed
  6. sudo : security/sudo
  7. xdg-open : devel/xdg-utils
  8. xterm : x11/xterm
  9. wine-gecko>=2.21 : emulators/wine-gecko
  10. wine-mono-devel>=4.5.6 : emulators/wine-mono-devel
  11. python2.7 : lang/python27
  12. wine : emulators/i386-wine-devel
  13. __init__.py : x11-toolkits/py-wxPython28
There are no ports dependent upon this port

Configuration Options
===> The following configuration options are available for playonbsd-4.2.8:
     GECKO=on: Wine-gecko HTML rendering support
     MONO=on: Mono bindings or support
===> Use 'make config' to modify these settings

USES:
python:run

FreshPorts PlayonBSD

Tuesday, March 1, 2016

ReactOS 0.4.0 has been Released

Nearly ten years ago the ReactOS Project released version 0.3.0. Today we are proud to announce the formal release of version 0.4.0. A great deal of work has gone into making this release happen and as we look back it is remarkable to consider how far the project has come since that release a decade ago. This release is both a celebration of and a testament to everything that the ReactOS team and community has achieved together. Thank you to all of you for having stood by the project for this long and we hope rewarding journey. For those of you chomping at the bit to check out the release, go to the download page to get it now.

Image

In Memoriam

It cannot be emphasized enough that ReactOS is where it is today due to the tireless efforts of the people that make up the project. Over the course of the project developers have come and gone but they have all left a mark whether it be in their code or the memories of their interactions with those still with the project. Sadly in two cases these memories are all that we shall ever receive from them. Gé van Geldorp was one of the project’s earlier developers and was heavily involved in the development of the win32 subsystem. He also helped mentor many other developers that joined afterward and is fondly remembered for his willingness to help those just getting started in the project. Brandon Mark Turner was another developer in the earlier days of the project. He worked out a variety of components and was responsible for some of the initial work to make ReactOS buildable with Microsoft’s compiler toolchain. The 0.4.0 release is dedicated to their memory and we hope that its fruition will serve to show at least some degree of our immense gratitude for the effort they put into this project.

Features

Here we document some of the highlights that separate 0.4.0 from not just the 0.3.17 release but also the cumulative achievements that the 0.3.x series achieved.
First of course the bulletpoint shortlist for those of you who don't want to wade through my giant mountain of text.

User-Centric Improvements

  • ext2 read/write and NTFS read support
  • New explorer shell and theme support
  • SerialATA support
  • Sound support
  • USB support
  • VirtualBox and VirtualPC support
  • Wireless networking

Developer-Centric Improvements

  • CMake support for GCC and MSVC compilation
  • Compilation times significantly improved
  • GDB remote debugging interface for kernel debugging
  • WinDBG support
And now onto the meat. In alphabetical order because it’s as good as any other order.

Build Modernization

Those who have been with the project since its early days will likely shudder at recollecting the means by which ReactOS was compiled back then. The first attempt to normalize the situation was in the RBuild system, a custom build specification format based on XML that was supposed to make it easy for developers to add new files and modules to the project. While impressive for its time, it suffered from structural issues that not only introduced very subtle bugs but also prevented the project from using anything but GCC to compile ReactOS.
The solution to this was a migration to the CMake platform, an effort that took many months and saw countless issues fixed. The first formal release using the CMake-based build system was 0.3.15 and since then the modernized build system has allowed developers to use not only GCC but also Microsoft’s compiler and debugging suite to build and test ReactOS, an ability that was crucial to many of the features and improvements listed here today.

Filesystems

Since its earliest days ReactOS has relied on one form or another the FAT filesystem. There was also significant interest from the community for something better, or at least something different, but a variety of technical difficulties prevented the operating system from supporting anything else. While support for ext family of filesystems progressed slowly but steadily probably the more exciting development has been preliminary support for reading NTFS volumes. While bits and pieces of the code were folded into 0.3.17, it was incomplete and 0.4.0 will be the first version to actually provide out of the box support for reading NTFS volumes.

Graphics

From 2D to 3D there were countless improvements to ReactOS’ graphics stack. Optimization work resulted in considerably faster rendering of 2D graphics, in some cases even beating performance on Windows, while support for 3D graphics has steadily advanced since work began in the 0.3.7 time period. Furthermore, architectural fixes released as part of 0.3.8 saw the ability to properly load graphics drivers, another milestone in the project’s goal of compatibility.

Memory

The memory manager, a central piece of any operating system and whose stability and correctness underpins that of the rest of the system. The memory manager that has been with the project for so many years finally saw significant parts of it retired in the 0.3.15 release. More work remains of course but a major milestone was achieved that day.

Networking

Support for networking was first formally introduced in the 0.3.0 release and since then the team has steadily improved upon the functionality and features. These range from the mundane such as simply fixing bugs to adding of wireless support in 0.3.14, affectionately known as the the PI release internally. Since the 0.3.17 release the project has also added in support for SSL, with the inclusion of the mbed TLS library.

NTVDM

A much requested feature for ReactOS was support for 16bit DOS applications. On Windows this support is provided by the NT Virtual DOS Machine (NTVDM) and the ReactOS implementation of it was first formally released in version 0.3.17. Needless to say since then the ReactOS NTVDM has seen considerable improvement to the point where many of the testers are sharing examples of old DOS games resurrected. And one of the biggest advantages to the way in which NTVDM is implemented in ReactOS is that support for it will continue on non IA-32 platforms, including AMD64 and even ARM.

Registry

Hate it or love it, the registry underpins much of the operating system’s configuration in the Windows family and like its NT-based relatives ReactOS also possesses one. The project has gone to great lengths to ensure that its implementation of the configuration manager works not only in ReactOS but is also able to correctly read and modify a registry from Windows, providing the ability for ReactOS’ own bootloader to be able to boot Windows 2003 successfully.

Shell

The explorer shell used in 0.3.0 was originally introduced all the way back in 0.2.0. When it was created ReactOS lacked the proper infrastructure to actually support a proper graphical shell, forcing the old explorer’s creator to reproduce much of the functionality, that was supposed to be provided by the operating system, in the shell itself. This worked for a time but as the OS became more complete the shell was unable to benefit from these improvements. The new explorer shell and all of its supporting infrastructure, and there was a great deal of infrastructure at that, was a cumulative effort by several people and is one of the truly new features being introduced in 0.4.0 with no previous releases possessing it.

Storage

Much as PS/2 connectors slowly fell out of use for keyboards and mice, storage devices in modern computers now use SATA instead of IDE. ReactOS added support for such devices in 0.3.10 by importing the UniATA driver and have steadily improved upon that support ever since.

Sound

What one might presume to be a rather basic piece of functionality was actually an extremely complex undertaking. Support for sound arrived in 0.3.9 and has progressively been improved upon ever since as we move towards a new normal of expecting things to work instead of being amazed that they do.

USB

In this day and age almost every peripheral comes with a USB connector. Initially the project sought to simply provide support for USB mice and keyboards, support first added in 0.3.10, but a full and proper USB stack is ultimately a necessity in this day and age. This stack was first provided in the 0.3.15 release and has seen continued work since.

Visuals

Making the shell look nicer was another oft-requested improvement and one that was a long time coming. In the course of adding that support the project encountered a few bumps of course but in the 0.3.16 release ReactOS was shipped with the Lautus theme for those that wanted to try it out.

Final Notes

More detailed technical information about the release can of course be found on the 0.4.0 wiki page with links to the changelog and other notes. Please also note that the VirtualBox image is not yet live at the time of this release.

Google Apps for Work start your free trial today

https://goo.gl/G11ts6
What is Google Apps?
 
Google Apps is a cloud-based productivity suite that helps teams communicate, collaborate and get things done from anywhere and on any device. It's simple to set up, use and manage, so your business can focus on what really matters.

Millions of organizations around the world count on Google Apps for professional email, file storage, video meetings, online calendars, document editing and more.

Watch a video or find out more here.

Here are some highlights:

Business email for your domain
 
Looking professional matters, and that means communicating as you@yourcompany.com. Gmail’s simple, powerful features help you build your brand while getting more done.

Access from any location or device
 
Check email, share files, edit documents, hold video meetings and more whether you’re at work, at home or in transit. You can pick up where you left off from a computer, tablet or phone.

Enterprise-level management tools
 
Robust admin settings give you total command over users, devices, security and more. Your data always belongs to you, and it goes with you if you switch solutions. Start your free trial

Why switch to Windows 10 or a Mac when you can use Linux

My buddy David Gewirtz recently wrote about the question of whether you should move from Windows 7 to Windows 10 or a Mac. I have another suggestion: Linux. Specifically Linux Mint 17.3, Rosa, with the Cinnamon desktop.

Linux Mint 17.3 is a great replacement for Windows 7. In fact, it's a great desktop operating system period.
Yes, I'm serious. I use all the above desktops -- yes I'm a Windows 7 and 10 user as well as a Linux guy -- and for people I think Mint 17.3 makes a great desktop.

I've been using Mint as my main Linux desktop for years now. Unlike some desktops I could name -- cough, Windows 8, cough -- Linux Mint has never had a flop. Every year that goes by, this operating system keeps getting better. The other desktops? Not so much.
Let's take a closer look.at Windows 7 vs. Linux Mint 17.3

UI Differences
 
There's really not much. While it's even easier for a Windows XP user to move to Mint than a Windows 7 user, any Windows user won't have any trouble picking up Linux Mint with Cinnamon. There's a Start Menu and settings are easy to find.

I regard Cinnamon 2.8 as the ultimate Window, Icon, Menu, Pointer (WIMP) interface. Is it ideal for tablets or smartphones? No. Is it perfect for long-time PC users? Yes.

Cinnamon does add some nice features. For example, if you mouse over the Window list, you'll now see a thumbnail for each application. It also has improved performance, system tray status indicators, and music and power applets.


What I like best about Cinnamon is that it doesn't get in the way. There's no learning curve. You may have never used Linux in your life but you can just sit down and start opening directories, running applications, and modify your PC's settings.

One small feature I like a lot, since I always run multiple work-spaces, is that the work-space switcher applet now shows a visual representation of what's running in each work-space.
Don't like Cinnamon? Unlike any version of Windows, Linux Mint comes with many different desktops. These include KDE, MATE and Xfce. Find one you like and enjoy,

Application Selection

It's true that Linux doesn't have as many application choice as Windows does. But, how many applications do you really need in 2016? I do most of my work these days on the cloud with software-as-a-service (SaaS) applications. These apps work just as well on Chrome, my favorite Web browser, on Mint as they do on any other desktop.

That said, there are many excellent Linux desktop programs. For example, instead of Microsoft Office I use LibreOffice 5. I don't use it because it's free, although most Linux desktop applications won't cost you a cent, but because it's an excellent office suite in its own right.

I also use Evolution instead of Outlook for e-mail and GIMP instead of Photoshop for my basic graphic editing needs. The bottom line is that are many great Linux programs that you can use in place of Windows appliations.

Are there some Windows programs that you can't live without? Well, you don't have to live without them.
There are two ways to run Windows programs on Linux. One is to use CodeWeaver's CrossOver Linux. This program enables you to run many popular Windows applications on Linux. Supported Windows applications include Microsoft Office (from Office 97 to Office 2010), Quicken, and some versions of Adobe Photoshop.

The application you absolutely must have won't work with CrossOver? Then run it on a virtual machine (VM) program such as Oracle's Virtual-box.

I use both methods and they work well.

Run Microsoft Windows Applications and Games on Mac, Linux or ChromeOS save up to 20% off  CodeWeavers CrossOver+ today.