About | Download | FAQ | Changelog

Write the image

Instant WebKiosk boots from USB flash devices: in order to write the IMG file to a USB stick (extract it from ZIP, first), Windows users can use Win32DiskImager, while Linux users can make use of dd and Mac OS X users should follow this guide.

Help with Win32DiskImager can be found on YouTube.

Help with dd (run as root or with sudo) follows:

insert the USB stick
tail -f /var/log/messages or tail -f /var/log/syslog
locate device file, for example: /dev/sdx
umount /dev/sdx
dd if=path/to/iwk.img of=/dev/sdx bs=1M
(always refer to the whole disk, so do not use /dev/sdx1 for example)

Boot the operating system

Once you have successfully written the IMG file to a USB stick, you have to plug the USB media into the PC, reboot and choose booting from USB media (BIOS/UEFI settings for PCs and left Alt key for Macs). Newer Windows PCs have to disable the Secure Boot in the UEFI settings and enable the legacy BIOS boot.

How do I set a static IP address or use Wi-Fi?

Instant WebKiosk default network connection method is DHCP: it if finds a DHCP server in the network it will make use of if.

If you want to override this behaviour, just unplug Ethernet cable and reboot: network admin screen (image below) will show up. Once saved, network settings will persist.


Https sites refuse to work. What’s going on?

Adjust BIOS clock with current date.

Which touch screen hardware to choose for IWK?

Some people reported that EloTouch and GeneralTouch monitors work well with Instant WebKiosk.

How can I modify the operating system in order to add or remove a feature or a driver? (experts only)

Instant WebKiosk is a “live” OS whose file system is contained in a compressed read-only file called filesystem.squashfs; you can locate that file under /live directory in the USB key once Instant WebKiosk has been successfully written. In order to modify any aspect of Instant WebKiosk, you have to modify that file accordingly. Linux knowledge is required. Your workbench (host operating system) has to be a Debian Wheezy (i.e. stable, V.7) Linux i386 (not x86_64) operating system; run as root.

1. You have to use unsquashfs command (install it first in your host operating system) to decompress all files of filesystem.squashfs inside a directory you choose, say /home/chroot:

mkdir /home/chroot
cd /home/chroot/
unsquashfs /media/DEBIAN_LIVE/live/filesystem.squashfs
cd squashfs-root/

2. Then you can modify OS files inside /home/chroot chrooting inside it:

mount -o bind /proc /home/chroot/squashfs-root/proc
mount -o bind /dev /home/chroot/squashfs-root/dev
mount -o bind /dev/pts /home/chroot/squashfs-root/dev/pts
mount -o bind /sys /home/chroot/squashfs-root/sys
chroot .

Do modifies you wish, Debian-way. Clean your tracks.

cd ..
umount /home/chroot/squashfs-root/proc
umount /home/chroot/squashfs-root/dev/pts
umount /home/chroot/squashfs-root/dev
umount /home/chroot/squashfs-root/sys

3. Then you have to resquash with -xz parameters (compression):

mksquashfs squashfs-root/ filesystem.squashfs -comp xz

4. Finally replace the old squashfs.