Mar 112013
 

Caveat: This is what worked for me. Your mileage will definitely vary. This is also assuming you’re using a Linux distro that is set up to install via rpm and you’re using the Nautilus file manager and the Windows version you are accessing is Windows 7.

First, make sure samba is installed. Do rpm -q samba. You should get back something like: samba-3.6.4-1.fu2012.x86_64. It will be different for you, most likely. If you don’t have it, you’ll have to get it from your packages repository. Get:

samba
samba-common
system-config-samba

If it’s installed, make sure it’s running:

service --status-all | grep smbd

which should return something like:

smbd (pid 11767) is running...

Go to your firewall’s configuration app (or do this via command line if you know how) and make sure Samba and Samba Client are enabled in it.

OK, edit your config file. Do sudo gedit (or whatever editor you want to use) /etc/samba/smb.conf

The sections we need to look at are under [global]:

Look for workgroup = and put your Windows workgroup name there. 99 times out of 100, if you’re on a home Windows network, it’ll be WORKGROUP unless you’ve changed it. So if it is, make sure that line says workgroup = WORKGROUP.

Make sure there’s a ; in front of the rest of the entries here, i.e where it says NetBIOS, interfaces, hosts allow, etc, unless you have a pressing need to change them. I’ve found through trial and error, it’ll connect to your shares whether you state the interface or not, so just leave it commented out with a semi-colon.

Directly underneath where it says hosts allow add:

usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False

If you don’t want guests on your network accessing your shares, put false there. This will also grey out the guests option in Nautilus when we get to it. If you only want the owner (that is, Linux owner) of the files accessing the shares, make that line true.

Create the storage folders: Do id yourname as your non-root user and see what groups you belong to. If you belong to the wheel group (for instance) then do the following as sudo:

mkdir /var/lib/samba/usershares
chgrp wheel /var/lib/samba/usershares
chmod 1770 /var/lib/samba/usershares

If you don’t belong to the wheel group do: sudo useradd -G wheel yourname. Of course, if there isn’t a wheel group (unlikely) then do sudo groupadd wheel. Logically, you can use the above to create any group name you want and add yourself to it.

Now, create a samba password for your user. The user needs to exist in /etc/passwd for this to work. If you use your normal login name, this won’t be an issue otherwise you’ll need to do useradd or adduser and create a new user.

sudo smbpasswd - a yourname.

Now, create your shares in Nautilus.

Nautilus shares

Open up /etc/samba/smb.conf and check down the bottom. It should have added a new section to it. If not, add the following:

[Downloads]
path = /home/yourname/Downloads
read only = no
browseable = yes
valid users = yourname

Restart samba. service samba restart or rcsmb restart. Whichever works.

Go to another networked machine and connect to whatever IP address your new shares are on (do ifconfig on the shared machine to find out). It should prompt you for your user name and password. Enter them and voila! Shared files!

To share from Windows so Linux can see them, create a password for your login if you haven’t already in the Users section of Control Panel. You’ll need one for Linux to access it even if your Windows machines are joined without needing a password (pretty common occurrence). Or you can create a user specifically for Linux to connect.

Make sure sharing is enabled in your firewall and in Control Panel, and right click the folders/files you want to share. Presto. It’s as easy as that. Go to your Linux box, and connect to smb://whatever_your_Windows_IP_is and enter your credentials. Easy.

Kudos to wayne128 of the Fuduntu forums, http://tinyurl.com/aczct5h and http://www.swerdna.net.au/susesimpleshares.html for the assistance.

This tutorial is mirrored here.

Mar 112013
 

All right, first off the bat – do NOT follow any other guide you find on the Internet to getting it going other than what you find over at WineHQ. This one. Scroll down to the HOWTO section and follow that. As it says, no need for any Winetricks or special .dll files. And as it says there, you’ll probably bork your install if you do mess with Winetricks.

A couple of things extra to help with the above, things that guide doesn’t quite make clear.

Do NOT run the Wine configurator before installing Office 2007. And if you have (and you have a 64-bit install of Linux), you’ll need to specify a new wineprefix to run Office, which is 32-bit. A new what?

wineprefix screenshot

It’s where your wine config files live. So, if you need to run 32-bit Wine instance, you need a new prefix. Say, .wine32 or something.

So do WINEARCH=win32 WINEPREFIX=/path/to/wineprefix winecfg at the command line, i.e WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg.

Check your parsing in that WINEARCH statement. It didn’t work for me at first as I’d left a space between the = and ~/.wine32.

Then as the WineHQ HOWTO states, install Office 2007 and enjoy!

fuduntu desktop screenshot

Feb 072013
 

This is using the latest make of DOSBox. To avoid old hoary games playing in a tiny-assed window on my monitor, I changed the relevant lines in dosbox.conf to read:

dosconfig

You cannot resize the window (apart from alt-entering it to fullscreen), if output is set to surface. Setting it to opengl (assuming you’re using manufacturer’s drivers, not OS native ones – this is important!) allows you to resize it, which I’ve done by replacing the default window resolution setting to 1024×768. This works like a charm for Stonekeep. Alt-entering it makes it looks awful, pixellates it, and if you’re using a widescreen monitor, it stretches it unnaturally.

Stick your Stonekeep CD in the drive (this assumes you have a legal copy, right?). Install and start DOSBox being mindful of the suggestions above.

dosbox

Mount your hard drive and CD drive by doing:

mount c c:\dir where dir is the directory on your hard drive you want to mount. For the sake of this tutorial I installed Stonekeep on my D: drive (hence the line on the above screenshot). Your mileage may vary.

Mount the CD by doing:

mount d d:\ -t cdrom where d is your CD’s drive letter.

Install Stonekeep, switching to the CD by doing d: then install. Do not install it in the default location it puts there. Change it to something simple like c:\SK. Let it do its thing. The verifying copied files dialogue may take some time to get through, and it may appear it’s hung. It hasn’t – let it go – it’ll pass it. Once to the setup screen, configure digital and normal sound and movie resolution. Then exit.

Then navigate to where you installed Stonekeep (i.e c:\sk) and type SK.

Enjoy that kick-ass intro and the retro gaming.

screenshot

Jun 042012
 

It’s far from intuitive, compared to Paint Shop Pro, which is what I’m used to. Obviously this won’t work if the image doesn’t support transparency, so it needs to be a GIF or a PNG, preferably the latter, as more options are open to you.

If you haven’t done so already, add an alpha channel, or all this will be academic. Layer –> Transparency –> Add Alpha Channel

Select the fuzzy select tool by pressing U or by clicking on the tool to the right of the lasso tool.

Select the region of the image you want to be transparent, making sure the select transparent areas option is checked in the tool dialog window.

You should get the marching ants selectors around the area that’s to be made transparent. Remove the selected pixels by doing Edit –> Clear.

The now-transparent region should turn to a greyscale checkerboard pattern.

Export the image (that’s right, you don’t save it in GIMP) as a PNG, making sure the extension in the file name field is set to .png. Yes, it doesn’t always do it.

Hope this helped. I used GIMP 2.8.