Zdobienie

AutoStakkert! on Linux: Installation via Wine and PlayOnLinux

Zdobienie

AutoStakkert! on Linux: Installation via Wine and PlayOnLinux

AutoStakkert Linux installation

Windows is Not Required Many astrophotographers keep a Windows partition strictly for one piece of software: AutoStakkert!. This is an unjustified waste of resources. The stacking engine of this software runs perfectly in a Linux environment, often offering better RAM management than Microsoft’s native system due to the lightweight nature of the Linux kernel.

How It Works: Wine Is Not an Emulator

The key to success is Wine (acronym: Wine Is Not an Emulator). It is a compatibility layer that translates Windows API calls into POSIX (Linux) instructions on the fly. This allows the application to run with near-native performance, without the overhead of emulating an entire operating system. The PlayOnLinux (POL) tool described in this guide is used to easily manage so-called Wine “prefixes”—isolated containers with specific configurations.

Why this works?

  • AutoStakkert! is a portable app — no classic MSI installer.
  • Wine supports most API calls required by AS!3/AS!4.
  • Linux filesystems (ext4, btrfs) handle large SER/AVI files better than NTFS.

Shortened deployment Guide (Universal Method)

Since AutoStakkert! does not have a classic installer (it is a “portable” application), the process in PlayOnLinux differs slightly from the norm:

  1. Download: Get the latest stable version (AS!3 or AS!4) as a ZIP archive.

  2. POL Configuration: Select “Install a program,” then “Install a non-listed program.”

  3. Virtual Drive Creation: Choose “Create a new virtual drive” (preferably 64-bit architecture to handle large SER/AVI video files).

  4. No Installer: When POL asks for the installation file, point it to the AutoStakkert .exe. The program won’t “install” into the system registry but will be executed within the Wine directory structure.

  5. Shortcut: Finally, create a shortcut directly to AutoStakkert.exe.

Performance and Memory

When working with massive files from planetary cameras (often 50-100 GB), Linux file systems (ext4 or btrfs) handle I/O operations significantly better than NTFS. Stacking proceeds smoothly, provided that the Wine configuration has been allocated sufficient video memory access.

Warnings

  • Use Wine ≥ 6.x — older versions may cause errors.
  • Don’t copy files into system directories — keep them inside the Wine prefix.
  • Test with a small SER file before processing large sessions.

I assume that if you are already reading this description, for me it means that you are a Linux user and as a regular user, you have the ability to install the necessary programs, using the built-in tools (Muon, apt or other tool) you can install PlayOnLinux (POL) from available repositories used by you distribution.

This installation description is not closely related to the Linux Kubuntu v.18.04 LTS distribution that I use. Certainly, it will be good for almost any Linux distribution available on the Internet.

Make sure you have the “winbind” package installed in your system. It is necessary for the AutoStakkert, to be fully functional. Let’s proceed to the installation of the AutoStakkert using POL.

Detailed Installation of AutoStakkert with POL in use

Download the program from the project website, be sure to use the 32bit version and unpack the program, I’ve placed it in the ~/test/AutoStakkert/ current directory. AutoStakkert does not have an installer, it is running from the directory in which it is located. To conveniently use the program with POL, you still need to complete the installation process, so that POL creates the necessary configuration of the working environment for Wine. It’s a bit of a sandwich of different configurations, where one lie on the other and is dependent each other as shown in the table below.

Start POL and click on Install a program.

PlayOnLinux

On the PlayOnLinux install menu window, click on Install a non-listed program.

PlayOnLinux

Manual installation – click on Next.

PlayOnLinux – Manual installation

PlayOnLinux Wizard – click on Install a program in a new virtual drive and Next.

PlayOnLinux – Manual installation

Manual installation – In the text field you see, type name for virtual drive that will be created for installation process. I’ve typed „AutoStakkert_268”. Click on Next.

Manual installation – do not change anything, just click on Next button.

Obrazek posiada pusty atrybut alt; plik o nazwie image-31.png

Manual installationAttention! You should choose the 64bit windows installation version, even the program has 32-bit. This is justified by the way it handles the amount of memory available for AutoStakkert. For 32-bit, just over 3GB of RAM will be available, even your computer has more available RAM. When you choose 64-bit, we will get an additional 1 GB of RAM available to the program, which during stacking it has a very important role. During my tests, when I installed AutoStakkert on POL 32-bit while stacking a large number of images, I often saw a message from the program that there was not enough RAM. So choose 64-bit windows installation and click Next.

PlayOnLinux – Manual installation

Manual installation – Click on Browse and follow to drive location where you have a .exe file with AutoStakkert x86 (32bit) version program. Click on Next.

AutoStakkert has been run as we expected. Close the program.

POL has completed the installation and created the configuration, of the work environment we need of AutoStakkert for Wine. Do not close the Manual installation window, we will need it again.

Using the file manager or console, move the AutoStakkert directory to the ~/.PlayOnLinux/wineprefix/AutoStakkert/drive_c/Program Files/ directory. I will do it in the console using the command:

#> mv -v -i ./testowy/AutoStakkert_2.6.8 ~/.PlayOnLinux/wineprefix/AutoStakkert/drive_c/Program\ Files/

 

renamed ‘./testowy/AutoStakkert_2.6.8’ -> ‘/home/darek/.PlayOnLinux/wineprefix/AutoStakkert/drive_c/Program Files/AutoStakkert_2.6.8’
#>

Now we return to the POL installation wizard and our opened window. Select Browse from the list of available files and click Next.

Click on Browse.

Go to the directory where the AutoStakkert program is now placed (./PlayOnLinux/wineprefix/AutoStakkert/drive_c/Program\Files/AutoStakkert_2.6.8/), select the file AutoStakkert.exe and click Open.

Click on Next.

You can change the default shortcut name to something more reasonable. I’ve typed „AutoStakkert (x86) 2.6.8” and click on Next.

Installation wizard will back again to list of files. Now select the I don’t want to make another shortcut and click on Next.

The program has been installed but is not ready yet. Select AutoStakkert (x86) 2.6.8 and click the Configure button.

Go to the Display tab and set gdi for Renderer Direct Draw. Close the window.

Now we can run the program.

 

AutoStakkert v2.6.8

Enjoy 🙂

Support my work on Ko-fi

Did this guide help you?

I create these guides and projects as a hobby. If I helped you save time or money, consider supporting my work with a coffee. It keeps the energy flowing for future projects.

Categories
Newest articles
Support

Was description useful? Consider to support author, it prevents to post annoying ads for you. All you just could do is once a year, sponsor for me a coffee. The currency, amount, doesn’t matter to me. Matter to me, that you want!

Read

Similar Articles

SynScan - PCB - pads

SynScan GOTO controller – trouble with buttons

Even though this article has been around for ages, it still offers valuable insights and practical support for users of the SkyWatcher NEQ6Pro mounts. The content has been refreshed and tailored to match the current website engine, making sure everything looks and runs as smoothly as possible.     At some point while using the controller, I noticed that the ESC button wasn’t always working. I lived with it, but after a while, the left Ra button also started acting up and wouldn’t always connect. A red flag went up in my head – something needed to be done. It’s worth noting that the problems appeared right after the warranty period ended… coincidence? There weren’t many options, just two: either send the controller for service and pay a considerable amount for the repair, or try to fix it myself. My tinkering nature took over (as always), and I set about solving the problem on my own. I assumed that some dirt or substance must have gotten inside, which over time became sticky and was gripping the button. I don’t recall spilling any liquid on the controller, but I also can’t rule out a situation where rain or high humidity (fog) penetrated the controller’s interior. My recent, not-so-great experiences with electronics, especially those manufactured in China, gave me an idea of what I might find inside, so I prepared a few things for the job. Contact spray – quite a nice product for cleaning and degreasing electronics and optical devices, including removing contaminants from glass without damaging optical coatings.Cotton swabs are a must-have. Plastik 70 spray – in my electronics work, I usually reach for Plastik 70 spray (clear lacquer). It creates a thin, transparent, and, most importantly, sealed coating. It excellently protects soldering points from the tin components oxidizing and forming ‘cold solder’ joints, which stop conducting electricity relatively quickly after service work.A small, so-called artistic brush will be necessary to precisely and evenly spread the Plastik 70 over the repaired surfaces. Let’s get to work. We’re unscrewing the controller; it’s held together by 4 Phillips head screws. There are no clips, so slowly and gently, but without excessive force, we remove the housing. On the left side, carefully disconnect the white ribbon cable (signal) with the white plug and the plug with the colored wires (power). Grab the PCB board from the left side and slowly, gently turn it over to the right side. Contamination is visible at the soldering points of the white ribbon cable. Below, you can see dirty pads for the ESC button. Now I know where the problem with the uneven operation came from; it would connect sometimes and sometimes it wouldn’t – irritating. It’s not that visible in the photo, but the direction button pads weren’t exactly clean either. It was quite noticeable under the light. The opposite end of the controller, was also dirty. The soldering points of the disconnected plugs. The button pads were also dirty. I’m at my wit’s end. There’s no choice, the entire PCB will have to be cleaned. How to clean without breaking anything? Spray a little of the substance into the removed cap from the contact cleaner and dip a cotton swab in it. Lightly wipe out the dirty areas. Repeat the process until all the dirt is removed. Once you’ve cleaned all the areas, you need to protect the soldering points. Plastik 70 and a brush will be used for this purpose. The procedure is very similar to cleaning. Spray a little of the substance into the removed cap. Use the brush to apply the Plastik 70 to the soldering points. Wait 10 minutes for the applied Plastik 70 to dry.” View of the controller after cleaning the soldering points of the electronics, pads, and applying a protective plastic coating to the soldering points: I think it turned out quite decently. In my assessment, that’s everything. All that’s left is to reassemble the controller and test its operation. The problems that occurred earlier have disappeared.    

Read more...
EQDIRect for NEQ and EQ mounts

EQDIRect for NEQ and EQ mounts

    The GOTO controller is extremely convenient and practical to use, when you want to look at interesting night sky objects, with your own eye through the eyepiece mounted in the telescope’s focuser. The ability to quickly select an object using the GOTO controller, is invaluable. It’s way better using mount with PC and Here it comes the EQDIRect for NEQ and EQ mounts.     In astrophotography, however, the GOTO controller isn’t necessarily as convenient. I admit there were times when it actually got in my way. I decided to remove the controller so it would no longer intermediate the mount control; its role has been taken over by Astroberry combined with an EQDirect solution. My own implementation is based on descriptions for EQDirect available on the Internet. EQDIRect self made    The topic seemed simple, however, when it came to actually building the device myself, things weren’t so obvious anymore. Some important information is missing online. It’s easy to make a mistake that could seriously damage the mount’s electronics, as well as the Astroberry or another computer to which the EQDirect is connected. Repairing these devices can be very expensive! Once I had gathered all the necessary pieces of the “puzzle”, analyzed and double-checked the subject several times, I assembled the whole thing. Then, with a slightly trembling hand, I switched on the power to the mount. EQDIRect home made – set Luckily, nothing exploded 😉 What’s more, everything works – and it works like a charm! The mount responds to and executes all commands issued to it by the KStars+EKOS duo, along with the EQMod with INDI driver, and all of this resides together in Astroberry. EQDIRect for NEQ and EQ mounts – Astroberry configuration EQDIRect – EKOS – EQMod mount driver with setup Of course, EQDIRect will also work with ASCOM and other software that requires such a technical solution to control the Sky-Watcher EQ6, NEQ6Pro mounts. EQDIRect – EKOS – EQMod mount driver connection setup EQDirect with testing setup It works really well, even in slightly freezing conditions – tested – see the attached photos 🙂 To protect the expensive mount from damage, my EQDIRect unit is equipped with several additional electrical protections. Mount performs excellently in the field together with EQDirect when used together with PERUN II power bank. If you are interested in acquiring EQDIRect made by me, please don’t hesitate to reach out me by filling out the contact form.

Read more...
Rosette Nebula - NGC 2237 - Caldwell 49

Rosette Nebula NGC 2237 – Caldwell 49

Rosette Nebula NGC 2237.
In this article, I have gathered in one place the most interesting information about the entire nebula and its selected regions. The information contained in this content is my own compilation based on collected data.

Read more...