The WineHQ Wine development release 2.17 is now available for Linux and Mac

The WineHQ Wine development release 2.17 is now available for Linux and Mac

What's new in this release:

• Better support for grayscale mode in DirectWrite.
• Per-application StartupWMClass in desktop files.
• Virtual memory compatibility improvements.
• Palette handling improvements in WindowsCodecs.
• Reply messages improvements in WebServices.
• Various bug fixes.

The source is available now. Binary packages are in the process of being built, and will appear soon at their respective download locations.

Bugs fixed in 2.17 (total 20):

  12185  Before You Know It crashes
  19177  Gorky-17 does not start in Direct3D HAL (SW Renderer is OK)
  29958  UIRibbon Framework not implemented: 926749fa-2615-4987-8845-c33e65f2b957
  38622  gdiplus should return PixelFormat32bppARGB instead of PixelFormat8bppIndexed for a grayscale PNG file
  39885  Cannot allocate more than 32gb of memory
  41370  TTM_GETCURRENTTOOL returns always FALSE when send from TTN_NEEDTEXT handler.
  41827  Wrong specular rendering with some applications
  42427  Steam application claims no internet connection
  43046  Multiple apps need api-ms-win-crt-stdio-l1-1-0.dll.__stdio_common_vfprintf_s (Civilization VI, Mafia 3, SketchBook)
  43197  5Plus: Print dialog crashes with illegal floating point operation
  43290  MyLifeOrganized crashes when mousing over tabs
  43319  Steam Store/Uplay/Epic Games Launcher no longer display text in Windows 7 mode (libcef applications)
  43476  Skyrim hardware detection spinlocks with CSMT enabled
  43519  Path of Exile: Corrupt/flickering UI textures after ~1 minute of gameplay
  43577  unit test: DBGrid inplace editor dropdown does not work and worked on version 2.0.2
  43586  Dead Space: no shadows in game
  43649  dbgeng stub DebugCreateEx causes jadesentinel crash in JADE thin client
  43658  Text in Deletion Confirmation MsgBox has wrong background colour
  43668  Terris Universal Remote UFB 234 - update database does not work
  43685  Many games fail to start, or run without audio

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

Connecting to Your AWS Linux Instance from MacOS Using PuTTY for Mac

Connecting to Your ( Amazon Elastic Compute Cloud ) AWS Linux Instance from MacOS Using PuTTY for Mac.

After you launch your instance, you can connect to it and use it the way that you'd use a computer sitting in front of you.

Note

After you launch an instance, it can take a few minutes for the instance to be ready so that you can connect to it. Check that your instance has passed its status checks - you can view this information in the Status Checks column on the Instances page.

The following instructions explain how to connect to your instance using PuTTY for Mac, a SSH client for Windows that has been ported to MacOS. If you receive an error while attempting to connect to your instance.

Prerequisites

Before you connect to your Linux instance using PuTTY, complete the following prerequisites:

• Install PuTTY
  Download and install PuTTY from the PuTTY for Mac store. If you already have an older version of PuTTY for Mac installed, we recommend that you download the latest version. Be sure to install the entire suite.
  
• Get the ID of the instance
  You can get the ID of your instance using the Amazon EC2 console (from the Instance ID column). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  
• Get the public DNS name of the instance
  You can get the public DNS for your instance using the Amazon EC2 console (check the Public DNS (IPv4) column; if this column is hidden, choose the Show/Hide icon and select Public DNS (IPv4)). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  
• (IPv6 only) Get the IPv6 address of the instance
  If you've assigned an IPv6 address to your instance, you can optionally connect to the instance using its IPv6 address instead of a public IPv4 address or public IPv4 DNS hostname. Your local computer must have an IPv6 address and must be configured to use IPv6. You can get the IPv6 address of your instance using the Amazon EC2 console (check the IPv6 IPs field). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command. For more information about IPv6, see IPv6 Addresses.
  
• Locate the private key
  Get the fully qualified path to the location on your computer of the .pem file for the key pair that you specified when you launched the instance.
  
• Enable inbound SSH traffic from your IP address to your instance
  Ensure that the security group associated with your instance allows incoming SSH traffic from your IP address. The default security group does not allow incoming SSH traffic by default.
  

Starting a PuTTY Session

Use the following procedure to connect to your Linux instance using PuTTY. You need the .ppk file that you created for your private key. If you receive an error while attempting to connect to your instance, see Troubleshooting Connecting to Your Instance.

To start a PuTTY session

1. (Optional) You can verify the RSA key fingerprint on your instance using the get-console-output (AWS CLI) command on your local system (not on the instance). This is useful if you've launched your instance from a public AMI from a third party. Locate the SSH HOST KEY FINGERPRINTS section, and note the RSA fingerprint (for example, 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f) and compare it to the fingerprint of the instance.
   

   
   
   Copy
   
   aws ec2 get-console-output --instance-id instance_id

   Here is an example of what you should look for:
   

   -----BEGIN SSH HOST KEY FINGERPRINTS-----
   ... 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f ...
   -----END SSH HOST KEY FINGERPRINTS-----

   Note that the SSH HOST KEY FINGERPRINTS section is only available after the first boot of the instance.
   
2. Start PuTTY (from the Start menu, choose All Programs > PuTTY > PuTTY).
   
3. In the Category pane, select Session and complete the following fields:
   
   1. In the Host Name box, enter user_name@public_dns_name. Be sure to specify the appropriate user name for your AMI. For example:
      
      • For an Amazon Linux AMI, the user name is ec2-user.
        
      • For a RHEL AMI, the user name is ec2-user or root.
        
      • For an Ubuntu AMI, the user name is ubuntu or root.
        
      • For a Centos AMI, the user name is centos.
        
      • For a Fedora AMI, the user name is ec2-user.
        
      • For SUSE, the user name is ec2-user or root.
        
      • Otherwise, if ec2-user and root don't work, check with the AMI provider.
        
   2. (IPv6 only) To connect using your instance's IPv6 address, enter user_name@ipv6_address. Be sure to specify the appropriate user name for your AMI. For example:
      
      • For an Amazon Linux AMI, the user name is ec2-user.
        
      • For a RHEL AMI, the user name is ec2-user or root.
        
      • For an Ubuntu AMI, the user name is ubuntu or root.
        
      • For a Centos AMI, the user name is centos.
        
      • For a Fedora AMI, the user name is ec2-user.
        
      • For SUSE, the user name is ec2-user or root.
        
      • Otherwise, if ec2-user and root don't work, check with the AMI provider.
        
   3. Under Connection type, select SSH.
      
   4. Ensure that Port is 22.
      
      
   
4. In the Category pane, expand Connection, expand SSH, and then select Auth. Complete the following:
   
   1. Choose Browse.
      
   2. Select the .ppk file that you generated for your key pair, and then choose Open.
      
   3. (Optional) If you plan to start this session again later, you can save the session information for future use. Select Session in the Category tree, enter a name for the session in Saved Sessions, and then choose Save.
      
   4. Choose Open to start the PuTTY session.
      
      
   
5. If this is the first time you have connected to this instance, PuTTY displays a security alert dialog box that asks whether you trust the host you are connecting to.
   
6. (Optional) Verify that the fingerprint in the security alert dialog box matches the fingerprint that you previously obtained in step 1. If these fingerprints don't match, someone might be attempting a "man-in-the-middle" attack. If they match, continue to the next step.
   
7. Choose Yes. A window opens and you are connected to your instance.
   
   Note

   If you specified a passphrase when you converted your private key to PuTTY's format, you must provide that passphrase when you log in to the instance.

Connecting to Your Linux Instance Using SSH

After you launch your instance, you can connect to it and use it the way that you'd use a computer sitting in front of you.

Note

After you launch an instance, it can take a few minutes for the instance to be ready so that you can connect to it. Check that your instance has passed its status checks - you can view this information in the Status Checks column on the Instances page.

The following instructions explain how to connect to your instance using an SSH client. If you receive an error while attempting to connect to your instance, see Troubleshooting Connecting to Your Instance.

Prerequisites

Before you connect to your Linux instance, complete the following prerequisites:

• Install an SSH client
  Your Linux computer most likely includes an SSH client by default. You can check for an SSH client by typing ssh at the command line. If your computer doesn't recognize the command, the OpenSSH project provides a free implementation of the full suite of SSH tools. For more information, see http://www.openssh.com.
  
• Install the AWS CLI Tools
  (Optional) If you're using a public AMI from a third party, you can use the command line tools to verify the fingerprint. For more information about installing the AWS CLI, see Getting Set Up in the AWS Command Line Interface User Guide.
  
• Get the ID of the instance
  You can get the ID of your instance using the Amazon EC2 console (from the Instance ID column). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  
• Get the public DNS name of the instance
  You can get the public DNS for your instance using the Amazon EC2 console (check the Public DNS (IPv4) column; if this column is hidden, choose the Show/Hide icon and select Public DNS (IPv4)). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command.
  
• (IPv6 only) Get the IPv6 address of the instance
  If you've assigned an IPv6 address to your instance, you can optionally connect to the instance using its IPv6 address instead of a public IPv4 address or public IPv4 DNS hostname. Your local computer must have an IPv6 address and must be configured to use IPv6. You can get the IPv6 address of your instance using the Amazon EC2 console (check the IPv6 IPs field). If you prefer, you can use the describe-instances (AWS CLI) or Get-EC2Instance (AWS Tools for Windows PowerShell) command. For more information about IPv6, see IPv6 Addresses.
  
• Locate the private key
  Get the fully qualified path to the location on your computer of the .pem file for the key pair that you specified when you launched the instance.
  
• Enable inbound SSH traffic from your IP address to your instance
  Ensure that the security group associated with your instance allows incoming SSH traffic from your IP address. The default security group does not allow incoming SSH traffic by default. For more information, see Authorizing Inbound Traffic for Your Linux Instances.
  

Purchase Putty 8.7.0 now and have Telnet SSH FTP SCP on your Mac made easy!

The WineHQ Wine development release 2.16 is now available for Linux and Mac

The WineHQ Wine development release 2.16 is now available for Linux and Mac

What's new in this release:

• Support for pasting metafiles in RichEdit.
• Better support for grayscale PNG images.
• Support for safety features in library loading.
• Better handling of transforms in GdiPlus.
• Rendering improvements in DirectWrite.
• Various bug fixes.

The source is available now. Binary packages are in the process of being built, and will appear soon at their respective download locations.

Bugs fixed in 2.16 (total 19):

  26046  comctl32/monthcal tests show some invalid reads under valgrind
  28741  Odd coordinate in hit test causes uninitialized value references in MONTHCAL_CalculateDayOfWeek()?
  35282  Multiple applications/installers need 'reg.exe' 'import' operation implementation (Muvee Reveal 8.0.x)
  35935  Enterprise Architect fails to draw basic shapes when using gdiplus
  37982  Illustrator CS6: alternate color selection does not display colours
  40025  Winrar installer fails to start
  42256  PhotoFiltre 6 and 7 don't erase the mouse selection when dragging it
  42891  Unigine Superposition needs unimplemented function KERNEL32.dll.AddDllDirectory
  43293  strange behavior- Eudora scrambles email addresses
  43328  dotnet 4.5 applications crash in factory_get_cached_fontface
  43389  valgrind shows a few invalid reads in dlls/wsdapi/tests/xml.c
  43391  valgrind shows several definite leaks in programs/regedit/tests/regedit.c
  43392  valgrind shows a couple invalid reads in programs/regedit/tests/regedit.c
  43423  Multiple applications and games need 'ProgramData' environment variable set (SteelSeries Engine SDK based games, World of Warships 0.6.9+)
  43510
 Monster Girl Quest: crashes while playing
  43536  WIC can't encode to GUID_WICPixelFormat32bppPBGRA PNG
  43603  clipboard PIXMAP regression after upgrading from 1.8.x to 2.x
  43617  [Crash] Application crash when running C:\GOG Games\Baldur's Gate\BGMain2.exe
  43632  Drop down menu for DLL override doesn't work

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

Uneeq Company Awesome Mac Bundle 7 has been Extended

The Uneeq Awesome Mac Bundle 7 has been extended until September 5th 2017

Get this incredible bundle of award-winning, diverse Mac software while you still can. 7 apps, with a combined retail value of $190.90 and this Awesome bundle will cost you only $19.95 that's a savings of 89.53% off MSRP.

Included Applications in the Awesome Mac Bundle 7 are:

Wilde - $29.99
FTP Watcher - $19.99
File Cabinet Pro - $29.99
Chronicle - $9.99
Infographics Lab - $19.99
Photolemur -$36.00
MacX Video Converter Pro - $44.95

 The Uneeq Mac Bundle is immediately available... 

About Uneeq Company Founded in 2015 as a online marketplace of unique computer hardware, software and tech gadgets. Uneeq is focused EXCLUSIVELY on technology - a place where visitors know that all they will see are carefully selected products that are a combination of quality and uniqueness.The company's goal is to help software developers and hardware/tech gadget manufacturers reach a broader audience and at the same time help users find the best or most uneeq software and hardware/tech gadgets on the planet. Uneeq is a pioneer in bringing unique products to the marketplace and in located in Minneapolis, MN and Denver, CO USA. The company is privately held.

# # #