Disabling Annoying SIM Toolkit Pop-ups on Samsung Galaxy A01 Core (Claro Argentina)

The problem

This post is a work in progress. 

If you're using a Samsung Galaxy A01 Core with a Claro Argentina SIM card, you might be frustrated by persistent pop-ups from the SIM Toolkit app appearing on your lock screen. These "flash messages" are typically promotional or service-related notifications pushed by Claro, and since can appear over the lock screen, you could "click" OK on it without noticing it (ie: if you have your phone on your pocket). The SIM Toolkit app (com.android.stk or com.android.stk2 for dual SIM devices) is a system app, meaning it cannot be uninstalled without root access. However, you can disable it or restrict its behavior using ADB (Android Debug Bridge).

 Prerequisites

• Know what are you doing: don't blame me if you manage to brick your device. I might laugh at you and make fun of you on the net if you try to do so. Of course I am posting this because I already did it on my device and it works. Also: this procedure could work on other mobiles models or even on other mobile network providers. You just need to know what to look for.
• A not too old desktop computer with Linux and adb already installed. All commands are issued by using a terminal like xterm.
• USB Debugging enabled on your mobile, ie for Samsung A01Core:
  1. Go to Settings > About phone > Software information.
  2. Tap Build number 7 times to enable Developer Options.
  3. Go back to Settings > Developer options and enable USB debugging.
• A USB cable to connect your phone to the computer.
  
• Ensure your phone is recognized by ADB:

  adb devices
  

  You should see your device listed. Not just any cable can do the trick, if you don´t see your device listed, keep trying other cables until you do.

Step-by-step solution using adb

1. Identify the package

The pop-ups are likely caused by Claro Argentina's SIM Toolkit app, which is pre-installed as com.android.stk (and com.android.stk2 for dual SIM setups). Confirm this by listing installed packages:

adb shell pm list packages | grep stk

Expected output:

package:com.android.stk
package:com.android.stk2

2. Disable SIM Toolkit

Since SIM Toolkit is a system app, you can't uninstall it without root, but you can disable it using ADB. Run these commands to disable both SIM Toolkit packages:

adb shell pm disable-user --user 0 com.android.stk
adb shell pm disable-user --user 0 com.android.stk2

Expected output:

Package com.android.stk new state: disabled-user
Package com.android.stk2 new state: disabled-user

This prevents the app from running and stops the pop-ups.

3. Force Stop (Optional)

To ensure the app stops immediately:

adb shell am force-stop com.android.stk
adb shell am force-stop com.android.stk2

4. Reboot the Device

Apply the changes by rebooting your phone:

adb shell reboot

This performs a "soft reboot," restarting the Android system and applying the disabled state.

5. Check Package Status (Optional)

To confirm the packages are disabled:

adb shell pm list packages -d | grep stk

Expected output:

    package:com.android.stk
    package:com.android.stk2

If they appear here, they're disabled. To check for enabled packages:

adb shell pm list packages -e | grep stk

If nothing appears, the packages are successfully disabled.

6. How to revert

adb shell pm enable com.android.stk
adb shell pm enable com.android.stk2
adb shell reboot

7. What if it does not work 

Not many options, really: switching to another rom like LineageOS (which atm does not fully support A01Core) and/or another mobile model/brand.

Notes for Claro Argentina users

• Phone Functionality: Disabling SIM Toolkit is unlikely to affect calls, SMS, or data, as confirmed in tests on the Samsung A01 Core. However, always test after making changes.
• Android Version: The A01 Core likely runs Android 10 (Go edition), which doesn't support the POST_NOTIFICATIONS permission (introduced in Android 13). This is why revoking notification permissions via ADB doesn't work, making disabling the app the best solution.

Script to prevent SSH attacks while allowing you to connect from dynamic IP address.

while most of the time connecting to a remote server using openvpn would be a smart choice, sometimes it's not an option. This script is for a linux behind a firewall/router. It's intended to prevent SSH attacks (by simply denying access to the SSH port) while allowing you to connect from your own dynamic DNS, that is, if you have a dynamic ip given by your ISP, otherwise you could simply use iptables.

#!/bin/bash
valor=`host yourdyndns`
OK=$?
if [ $OK -ne 0 ]; then
  exit
fi
addr=$(echo $valor |egrep "address .*" -o)
ip=$(echo $parte |egrep "[0-9\.]*" -o)

whitelist=/root/whitelist
touch ${whitelist}

exists=`cat ${whitelist} | grep "${parte2}"`

if [ $? -ne 0 ]; then
  echo $ip >$whitelist
  iptables -F   iptables -A INPUT -s $ip -j ACCEPT
  iptables -A FORWARD -s $ip -j \ ACCEPT                                                                                         
  iptables -A INPUT -p tcp --dport 22022 -j DROP                                                                                   
fi

add this to rc.local to reload iptables during bootup:

# delete whitelist

rm /root/whitelist

# run previous script

/root/bin/testso.sh

x2x on Slackware

 I had to write something. This was kinda shocking to me. I was looking for a KVM (Keyboard, Video and Mouse) software to be able to control my notebook from my PC.  Been using an old free version of Synergy, but for some odd reason seems to be compiled for 32 bits and I felt it was a terrible waste to install multilib just to run it. So I decided to look for an alternative.

As usual, went to google and discovered that Slackbuilds has Barrier but when I tried to install it, it asked for avahi, and avahi asked for something else and that something else asked for other-something-else. So I gave up. Then I came across x2x.

This particular software has a wikipedia page so I wont bother telling the story about it.

    cd

    mkdir -p install/util/x2x

    cd install/util/x2x

    wget https://slackbuilds.org/slackbuilds/14.2/desktop/x2x.tar.gz

    tar xf x2x.tar.gz 

    cd x2x

    wget https://slackware.uk/~urchlay/src/x2x-1.30_beta+20200121_ec10215.tar.xz

    su

    ./x2x.SlackBuild

    installpkg /tmp/x2x-1.30_beta+20200121_ec10215-x86_64-1_SBo.tgz

then I have to create an script to connect to my notebook, but before I get into that I had to read the man page, last section, after the examples, gives an important tip when you have multiple monitors 

Left: 1920*1080 (primary)

Right: 1366*768

So I had to do the math and write the parameters to x2x according to the man page:

#!/bin/bash
ssh -YC rudy@macabra x2x -north -to :0.0 -big  -completeregionleft 0 -completeregionup 0 -completeregionright 3286 -completeregionlow 768

I have ssh configured so it wont ask me for password. North parameter means I placed my notebook "over" my monitors and it doesn't really matter from which monitor my mouse goes up, it appears on my notebook and it's able to travel  the entire notebook screen.

What shocked me about this is the fact it's a very old proyect, but works like a charm.

 

    

Script to reconnect wan via rc.inet1

My router is a Linux PC with 2 lan boards, one for local lan and the other directly connected to the ISP router (configured as bridge). Each time my ISP disconnects me for whatever reason I had to either reboot the computer or keep running rc.inet1 restart until the connection is made.

So, even if it doesn't happen often, at one point I got bored of it and decided to write an script to force the reconnection as soon as possible:

 #!/bin/bash
while true ; do
   clear
   ./rc.inet1 restart
   ping google.com -c 1
   if [ $? == 0 ]; then
      exit
   fi;
   sleep 30
done

 

Linux: [Draft] how files should be organizaded inside $home

as the title says, this is a draft made public.

what I intend to do here is to organize my thoughts on how scripts and files should be placed inside $HOME user directory, were $HOME refers to the proper /home/yourusername directory inside the Linux filesystem, so I will simply refer  to it as "~" . And by user I mean "normal non-root user", But some of these ideas can be used as root too, specially if you run scripts as root under cron and you don' t want other to take a look at them.

At first I came up with the idea of naming each script with a prefix, like convert.mp42mp3, which is not bad by itself since it makes you easier to remember what the command name should look like or even better, tab key can hint you which is the one you are looking for.

Having all scripts inside a director ~/bin is a good thing, but if if you end up with too many scripts like me, it could be annoying each time you do "ls" inside of it trying to find out what is the script you are looking for. Specially if you don't remember the name of it. PATH variable should also point to it, so each time you want to execute them from another directory you don't have to explicit mention the path of the script you want to invoke. To this end, ~/.bashrc_profile must contain a line like this:

export PATH=$PATH:~/bin:

So I guess ~/bin should contain mostly symbolic links to the proper scripts. Where to place the scripts then? inside directories under ~/bin. Each one of those directories names should represent a category under each script belongs.

Examples of names that comes to mind:

remotes (for SSH access to specific hosts, could be ssh too)
develop (if you are a developer)
cron for scripts that are run by cron. A good example could be one to update date and time using ntpdate, but you can do that inside cron as a one line.
os: scripts that does specific things on the operating system (???)

Some programs don' t need to be installed system-wide: if you plan to keep them updated, you can always decompress them under your home dir. Firefox is a glaring example of that.  What I do is to extract the x64 files under ~/usr/local then create a symlink to ~/usr/local/firefox/firefox. And to avoid any conflict with the system-wide Firefox install, what I do is to remove it.

bash script to kill a process based on partial name

why you might need this: because sometimes some processes can't simply terminated using the GUI. And after too many years typing ps -A | grep something then kill -9 the id, I decided to write a script to avoid having to type two commands.

Be warned, this will only kill the first process found with the lowest process ID.

it takes only one argument as the partial name to be looked upon the ps -A command.

#!/bin/bash
proc=$(ps -A |grep $1 | head -n 1)
if [ -z "$proc" ] ; then
   echo Error: no processes found with the given partial name!
   exit 1
fi
echo ps -A says:
echo $proc
procid=$( echo "$proc" |grep "[0-9]*" -o |head -n 1)

echo "kill? <Y/N>"
read answer
if [ "$answer" != "${answer#[Yy]}" ] ;then
    echo Yes
    kill -9 $procid
    echo Testing if the process is still alive ...
    isdead=$(ps -A |grep "$proc")
    [ -z "$isdead" ] && echo Process has been terminated! || echo process is still alive !?
else
    echo No!
fi

you can replace the question with the actual command but I don't recommend it.

Fix for VLC 3.X video freeze during movies

A few days ago I bough new monitor, a Philco 43" FHD. Since then, VLC started to freeze during playback on H264 MKV files.

I've been searching the web for the problem mentioned in title of this post. I have tried official solution which involves setting a higher value for file and video cache among other things. I have even upgraded it to the lastest version: 3.1.8.

But the problem persisted.

So I ended up doing the most basic thing to do when an specific software doesn't work: downgrading to a working version. Uninstalled version 3 and installed version 2.0.7 and I was able to play all H264 videos with no freeze.

Be warned thou, if you want to play H265 you will need either another player  or converting the files to H264. For converting the file, I made an script with generates an h264 dir in the current directory and then output the converted files there:

rudy@madcat3:~/bin$ cat convertir.h265.sh
#!/bin/bash
mkdir 264
for file in *.mkv
        do ffmpeg  -n -i "${file}" -map 0 -c:a aac -c:s copy -c:v libx264 264/"${file}"
done

Why we shouldn't use Windows

I have been using both Windows and Linux for more than two decades. I have seen both grow, and when I see notes like this I simply can't resist the temptation to comment about it. The article is written from this viewpoint: you are a lazy/sloppy computer user and you don't care about it or you aren't even aware of it. Or perhaps you have a lot of money to spare and you don't care throwing a lot of cash to Microsoft while getting headaches in return, just because everybody uses Windows. Ok, it's almost everybody. But I think you get my point.

So, I will go one by one telling you why the editor of the article is wrong.

1. Lack of Software:

It was true at the very beginning of the Linux world back in the 90's, for the simple reason Linux was new. But at the beginning of 2000, there was a lot of software which could help you do to common task. Netscape Navigator as web browser, StarOffice as a replacement of MS Office, XMMS as replacement of WinAmp, among others. Today, most of the important software are provided for several platforms and O/S. That is: unless it comes from Microsoft or it's something specific for the Windows platform like most games, but in my scale, games aren't listed as important.

The editor also mentions Wine, it is true that not all software can run under it (perhaps a 5% of them?), specially if its new, but I have been able to successfully able to run most of the software I wanted to run under Linux. Example comes to mind: Synergy (for sharing mouse/keyboard among different machines), MySQL Administrator, Lindo, Blackmagic ATEM control software, games like Diablo 2 and Lineage 2.

When a specific software for Windows does not run under Wine, if you start it from the console it may give you clues on what happened. usually the fix involves taking an DLL and placing it on the right directory. Still YMMV. As a side note, the funny thing is: under Windows, most of the time you will never get an idea of what exactly went wrong.

2. Software updates:

First off: ask yourself this question. Do you really need a software update?  There's an old saying which goes: if ain't broke, don't fix it.

If found myself many times downgrading software just because the newer version introduced bugs (probably as a consequence of not enough software testing). LibreOffice comes to mind. Version 5 re-introduced a bug fixed in early versions related with toolbars flashing like crazy.

Another related and relevant question for you to ask yourself: How far do you want to go in  learning how to properly use the tools you have? I ask this because I want you to be aware of this point: it's not the tool' s fault if you don't care about how to properly use it. Once you can consider yourself a master on the tool usage and if you are *really* in need of something else, then go ahead and take a peek at newer versions. But if you are the typical user who doesn't know what Ctrl-C and Ctrl-V does and you think you are satisfied it with it, then don' t bother.

A note about security: if the software you use is *very* insecure (all Windows version are, I don't care about Microsoft lies) then you should either find a replacement or make a decision to stick with it until the bomb explodes. But, at least, you have been warned.

3. Distributions:

Yeah, there's a huge tree of them. A relevant question is: So what? Each  one of these are targeted for specific user and need. I decided to stick with Slackware because its the most complete and more consistent over the years (and trust me, it's been over 20 years!).


But I have also tried others: Red Hat 7 and 8 (has been using it for some years until I came back to Slackware), Mandriva, Debian and the first one I ever used: SLS (which precedes Slackware).

Oh by the way, formally speaking, "DISTRIBUTIONS" are only a few of them (Slackware, Debian, Red Hat, Suse and another one I can't remember now). "META-DISTRIBUTIONS"  are based on "DISTRIBUTIONS". For example: Ubuntu is based on Debian.

4.Bugs:

Yeah, most software has at least 1 bug lurking. The problem with Windows is: it has too many of them, namely in the form of "features". Operating System should do what you want it to do, and I don't really care if you just want to delete the entire filesystem on your hard disk, a good one will allow you even if it wont boot anymore. On the other side and as I mentioned before, if you don't know what are you doing then it's not the tool fault.

I get really angry when Windows forbids me to delete a file because its  "protected" even with Administrator privileges (happened more than once to me while dealing with viruses).

5. Support.

Let's face it: you don't know whats happening. If you do, you can fix it yourself. But as you really don't, you have no choice and have to call in "the experts". I have earned some money and I still do. There's nothing wrong with that. I have invested too much time learning both Windows and Linux, so I consider at least fair to get paid for both my time and the time I have spent learning.

Which leads me to one conclusion: if you have a problem and you want to solve it, you can either invest money and save time, or invest time learning and save money, but you can't save both and solve the problem.

And talking about Linux: if you have an specific problem, most of the time you can get an proper answer simply by looking at linuxquestions.org.

If Windows were well made as they claim, it should not need any support. But since it does a lot of thing on your back  and they keep you as much in the dark as possible, at some point you end up needing help.

6. Drivers.

Just like point 1, this is totally outdated and false. A complete Linux distro should provide you with drivers for the most hardware around. Specific cases like Nvidia Cards might require downloading a file and execute it. But again, you will need to learn a bit.

7. Games.

Kinda true. But as I mentioned in point 1, some games run just fine under Linux. Mame has both versions for Windows and Linux and its quite fun. Software companies like ID develop both versions of their games.

Main problem with games is: developers usually use DirectX which is essentially a Microsoft library. If the Linux usage increases over the years, at some point they might have no choice but to take a took at alternatives like SDL which is a cross platform library for both Win and Linux.


8. Peripherals

Also false and same as Drivers. Most of the time I connect anything into my Linux, it works. Specially HP Printers, since HP has been doing Linux support since the 90's.

Still, you might into some hardware with doesn't have Linux drivers, usually someone else developed one for it. Just Google for it and read the instructions, just like you should under Windows.

9. Complicated:

this is the most stupid argument mentioned. Do I need to ask again the question I did in point 2? Look around you. The world IS complicated. Life IS complicated. Computers are not from outside of this world nor they came from the Heavens. Computers  are just TOOLS. If you want to take a look into Linux, your goal should be to get the results you want, no matter the cost.

Sure, the editor mentioned my case: I have over 20 years of Linux and yes, to me is a lot easier to deal with things than with Windows. But the results are far different. As a normal user under Linux I have control of everything going around. As an Administrator user under Windows I may have a sightly idea. That' s because I took the time to learn, both Windows and Linux, and I assure you, I have never been as satisfied with Windows as I had been with Linux.

10. Installing Linux is Hard.

Yeah, like everything I mentioned before, if you have read so far, you should realize its also false. Why? Because if you want to do it right, understanding how to properly install any operating system is not a trivial task. It forces you to learn a lot about a lot of things and leaving Linux alone in the middle is a fallacy.

Extras:

11. Privacy.

Since main Windows source code is not open for inspection, no-one can take a deep look to say "yes, it does respect your privacy". And trust me on this: over twenty years I have learned to don't believe anything Microsoft says.


Have you ever read a Microsoft User Agreement? If you don't I will summarize it to you: They are responsible for nothing and you can't blame them for anything that goes wrong.

So if they have a hidden Trojan horse embedded with the Operating System, all three letters agencies can take a peek on your files and your activities even if you think have nothing to hide.

Under Linux, any skilled user who noticed anything suspicious would investigate and spread the word about it like they did with SSH flaw and Bash vulnerability some years ago.

12. Cost

At the time of writting this, Wind 10 Pro version cost 200 u$s on USA which is a lot for most of the rest of the world.

Some Linux Distros may charge you for the media but esencially Linux is free.

If you have a lot of money to spare and don't care about learning, then my suggestion is: go Mac and follow a few rules: get to know your tool and don't update it unless you *really* need it. High chances are that you won't regret it.

Conclusion:

So, my conclusion is: There's no shortcuts to excellence and I honestly believe Linux is taking me to that path.

How to speed up ktorrent 4.3.1 startup

this fix is to address an specific problem with KTorrent startup, since some years ago started very slowly (about a minute) and then a popup appears complaining about a missing web file in maxmind.com

At first I tried to upgrade it but I found out newest version need a newer version of KDE. Since I decided to stick to Slackware 14.2 I had to look for alternatives.

So, here it is:

simply add a line at the end of  /etc/hosts with the following content:

0.0.0.1 geolite.maxmind.com

Close KTorrent if you have it open already then next time you start it  it will load up in a flash (It will show the popup again but this time with a different error).

Eclipse PDT preventing focus stealing during test running with PHPUnit

you are writting code and at some point you press Ctrl-F11 to run the default test configuration. Thing is: both Console and PHPUnit window will steal the focus from the source editor.
theres  a bug report marked as NEW while its 4 years old and some other fixes for Mac but I ended up with the easiest solution: to do not test under Eclipse and instead use an external console. The script I made in bash is as follows:

#!/bin/bash

clear
inotifywait -m --format %w%f -q -r -e close_write $1 $2 | \
while read CUAL
do
    if [ $? == 0 ]; then
        clear
        phpunit.phar --color  $1
   fi
done

first parameter is the location of the dir containing the tests, or the test Suite. Second parameter is the directory from where inotifywait should watch for changes on filesystem.
  

PHP to UML

I wanted a tool to convert PHP classes to UML, but I also wanted to be able to modify the result.

As a (maybe positive) side effect I had to separate all PHP classes in a particular directory in order to avoid the tool to get confused with other scripts used to generate Javascript code among other things.


(this post may require some revisions)

grab php2xmi from

http://tech.motion-twin.com/php_php2xmi.html

sample script to run on project directory:

php2xmi \
--no-private \
--no-protected \
--output=/home/rudy/borrame/myresult.xmi \
`find src/class -name "*.php"`

add --path= if you need to include other project files

once you get the XMI file, you can import it with ArgoUML

http://argouml-downloads.tigris.org/argouml-0.34/

it wont generate the UML on the fly

network bonding on slackware 14.2

perhaps a first sloppy attempt I made to make bonding work in 14.2, based on this info

https://docs.slackware.com/howtos:misc:network_interace_bonding

inside /etc/rc.d/rc.M add (before rc.local section):

if [ -x /etc/rc.d/rc.bond ]; then
  . /etc/rc.d/rc.bond
fi

/etc/rc.d/rc.bond :

modprobe bonding

ip addr add 192.168.111.3/24 dev bond0
ip link set bond0 up


ip link set eth0 master bond0
ip link set eth1 master bond0

ifconfig eth0 up
ifconfig eth1 up

ip route add default via 192.168.111.13 dev bond0

chmod +x rc.bond and reboot

bash script to kill another script by pid file

the idea is to get the pid from a running script and save it to a file, so we can retrieve the id and kill the process. Also it should kill child processes

to create the file, during the script we must do (replace /home/mantener/var/run with another dir of your liking):

minombre=$(basename $0)
pidfile=/home/mantener/var/run/$minombre.pid
echo $$ >$pidfile

 
 and the script to make use of the pid file could be:

#!/bin/bash
pidfile=/home/mantener/var/run/$1.pid

if [ ! -f $pidfile ] ; then
   echo missing $pidfile !
   logger $0 missing $pidfile !
   exit -1
fi

cualpid=$(cat $pidfile)

# get child processes
resto=$(ps --ppid $cualpid -o pid --no-headers)

echo killing $1
kill -9 $cualpid

while IFS= read -r line ; do
    echo killing $line
    kill -9 $line
done <<< "$resto"

rm $pidfile

script to kill a specific process by name

This one was made specifically for VLC since the stupid program sometimes hangs and there is no way to close it by normal means (Quit command, etc)

#!/bin/bash
$(echo -n kill -9 ; ps -A |grep vlc |grep -o "^ [0-9]*")

what it does is to create a command line on the fly by extracting vlc process id and then execute it.

zeroing a disk on linux using DD

WARNING: if you don't really understand what are you doing (even if you THINK you are), then start learning/reading first or asking someone who really understands linux BEFORE doing something stupid like erasing a wrong disk by mistake.

if you need to wipe the content of a hard disk (REPLACE /dev/sda with the appropiate device !):

dd if=/dev/zero of=/dev/sda bs=1M 

last parameter (block size) makes the process a lot faster

inotifywait example

edit: modified parameter "-n 1" to the "head" command

for this example I'm assuming text files:
to avoid confusions long lines are splitted with \

#!/bin/bash

if [ $# -ne 2 ]
    then
    echo "$0 <src dir> <dst dir>"
    exit
fi

clear

inotifywait $1 -qmre CLOSE_WRITE \
--format='%f' | while read WHICHONE ; do  
   if [ $? != 0 ]; then exit; fi;
   LINESELECTED=$(head -n 1 $WHICHONE | \
grep CONDITION)

if[ $LINESELECTED -eq 1 ] then
   cp $1/$WHICHONE $2
fi

done

phpunit script

assuming theres a test directory inside a project where the source files are held:

#!/bin/bash

if [ $# -ne 2 ]
    then
    echo "testphp <test dir> <src dir>"
    echo "example: $ testphp test ."
    exit
fi

clear

inotifywait $2 -qmre CLOSE_WRITE --format='%f' | while read CUAL ; do  
   if [ $? != 0 ]; then exit; fi;
   clear
   phpunit.phar --log-junit /tmp/ultimo.txt --color -v $1
done

geany plugins for 1.33

assuming:

• have geany 1.33 installed
• you want to use geany pluings for the same version
• you have downloaded and unpacked source distribution 
• you get an error while running ./configure under slackware64 14.2 similar linux flavor

if configure complains no "geany.pc", to solve this:

find /usr |grep "geany.pc"

take note where the "geany.pc" is located and append to PKG_CONFIG_PATH

ie if the file is located under /usr/local/lib/pkgconfig

export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig

then you can run ./configure again without errors

Installing PHP 7 from source

this post assumes you are familiar with Slackware 14.2 and have php 5.6 installed

1. Donwload php from sources, and extract it
2. inside the sources, create a script with this code or copy/paste on bash:
   

   #!/bin/bash
   ./configure \
       --with-config-file-path=/etc \
       --with-config-file-scan-dir=/etc \
       --enable-mbstring \
       --enable-zip \
       --enable-bcmath \
       --enable-pcntl \
       --enable-ftp \
       --enable-exif \
       --enable-calendar \
       --enable-sysvmsg \
       --enable-sysvsem \
       --enable-sysvshm \
       --enable-wddx \
       --enable-intl \
       --with-curl \
       --with-iconv \
       --with-gmp \
       --with-pspell \
       --with-gd \
       --with-jpeg-dir=/usr \
       --with-png-dir=/usr \
       --with-zlib-dir=/usr \
       --with-xpm-dir=/usr \
       --with-freetype-dir=/usr \
       --enable-gd-jis-conv \
       --with-openssl \
       --with-pdo-mysql=/usr \
       --with-gettext=/usr \
       --with-zlib=/usr \
       --with-bz2 \
       --with-apxs2=/usr/bin/apxs \
       --with-mysqli=/usr/bin/mysql_config \
       --with-ldap \
     --with-libdir=lib64

   edit: the long line from above as one line:
   ./configure --with-config-file-path=/etc --with-config-file-scan-dir=/etc --enable-mbstring --enable-zip --enable-bcmath --enable-pcntl --enable-ftp --enable-exif --enable-calendar --enable-sysvmsg --enable-sysvsem --enable-sysvshm --enable-wddx --enable-intl --with-curl --with-iconv --with-gmp --with-pspell --with-gd --with-jpeg-dir=/usr --with-png-dir=/usr --with-zlib-dir=/usr --with-xpm-dir=/usr --with-freetype-dir=/usr --enable-gd-jis-conv --with-openssl --with-pdo-mysql=/usr --with-gettext=/usr --with-zlib=/usr --with-bz2 --with-apxs2=/usr/bin/apxs --with-mysqli=/usr/bin/mysql_config --with-ldap --with-libdir=lib64
   
   
3. make
4. make test
5. su
6. make install
7. edit /etc/httpd/mod_php.ini and comment lib_php5.so line
8. rc.httpd restart

running ATEM Software Control under Slackware

while this blog has a foolproof method for ubuntu, I believe I took a shortcut and managed to make it work under wine32 because you don't really need to install it to make it work, just like old fashioned software. Besides: installing wine64 just to install ATEM and then install win32 to run it sound more like a hack than a "propper" solution.

In case you dont have it already installed wine:
http://www.slackware.com/~alien/slackbuilds/wine/

1) on a Win setup, make a copy/compressed file of ATEM Software control
2) copy/decompress it on a Slackware box

then cd to the "Blackmagic Design/Blackmagic ATEM Switchers" and do

$ regsvr32 BMDSwitcherAPI.dll 

because if you dont the software will complain for missing DLLs.

and then you can run it:

$ wine ATEM\ Software\ Control.exe