import math

def cycle(centre, range):
        theta = 4.71
        speed = 0.1
        for i in range(0,80):
                theta = theta + speed
                value = centre + (range * math.sin(theta))
                print value

I got the following error which confused the hell out of me:

Traceback (most recent call last):
  File "cycle2.py", line 11, in 
    cycle(0.0,10.0)
  File "cycle2.py", line 6, in cycle
    for i in range(0,80):
TypeError: 'float' object is not callable

Can you see it? It took me a while. I’d assigned a variable called range and then tried to call the range() function. I’d overloaded a built-in function. Duh!

I just had to rename my variable and it was good.

Now you can get the same level of simplicity using inpout32.dll and Python. Go here to download the DLL and you can access it from Python just as easily as it used to be under DOS. The following example writes the number 5 to the parallel port:

import ctypes

ctypes.windll.inpout32.Out32(0x378, 5)

=if(A1<=6000;0;if(a1<=35000;.15*(a1-6000);if(a1<=80000;4350+(.3*(a1-35000));if(a1<=180000;17850+(.38*(a1-80000));55850+(.45*(a1-180000))))))

My goal here was to compile a new kernel for a Debian 4.0 (Etch) system. You can download pre-built kernels but I wanted to modify some drivers before building it.

Anyway, you will firstly need the source code. Go to the Debian Backports Repository and grab the latest linux-source package. Before installing it, you will need to install some tools:

sudo apt-get install kernel-package fakeroot libncurses5-dev

Now we can install the source:

sudo dpkg -i linux-image-2.6.26_dvc.1.2_i386.deb

cd /usr/src

tar jxvf linux-source-2.6.26.tar.bz2

ln -s linux-source-2.6.26 linux

cd linux

Next you need to configure the kernel. A good way is to simply copy the current kernel configuration:

cp /boot/config-2.6.18-6-686 ./.config

Finally, launch the make-kpkg utility. This will configure, compile and package the kernel in a DEB package.

fakeroot make-kpkg --revision=mycustomkernel-1.0 --config menuconfig --initrd kernel_image

This will launch the kernel configuration menu first. You can make any configuration changes here but usually the defaults are fine. When it is all done you will have the completed package file in /usr/src.

char c;
cin >> c;
cout << "You pressed " << c << endl;

But it doesn't work! The user has to press ENTER before the cin function will complete.

I read all sorts of crazy solutions on the web to fix this, most of which involve using NCURSES but I think that is total overkill. I have found a simpler way.

Now it's not the fault of std::cin or even C++. It's the operating system which buffers the keyboard input, only releasing it to your app when the user whacks ENTER. So what you need to do is tell the OS not to buffer keystrokes. You can do this with the termios functions in Linux. Here is an example:

// Example for inputting a single keystroke in C++ on Linux
// by Adam Pierce <adam@doctort.org>
// This code is freeware. You are free to copy and modify it any way you like.

#include <iostream>
#include <termios.h>

using namespace std;
main()
{
// Black magic to prevent Linux from buffering keystrokes.
    struct termios t;
    tcgetattr(STDIN_FILENO, &t);
    t.c_lflag &= ~ICANON;
    tcsetattr(STDIN_FILENO, TCSANOW, &t);

// Once the buffering is turned off, the rest is simple.
    cout << "Enter a character: ";
    char c = cin.get();
    cout << "Your character was " << c << endl;

    return 0;
}

After I installed my game, I wound up copying my entire Warcraft II CD to my C:\DOSGAMES\WAR2 directory, then I added “mount d c:\dosgames\war2 -t cdrom” to the [autoexec] section. By copying the CD to the same path as the installed game, I don’t have to duplicate the space to hold the files from the CDROM.

As for playing multiplayer Warcraft II in DOSBOX, it could not be made any easier. There is NOTHING that the user has to configure in Microsoft Windows (or Linux…or OSX) to get IPX gaming working under DOSBOX. The DOSBOX team has built an IPX wrapper right into DOSBOX. Once the Warcraft II game is operational on two or more computers on your network you are ready to setup networking in DOSBOX.

Instructions:
1) Identify the IP addresses or names of each computer that will be participating in the gaming session. (Windows users: To display the computer’s IP address click START, click RUN, type in “cmd” and click the OK button. At the prompt, type in the command ipconfig and press enter. Write down or remember the number on the IP ADDRESS line. If you want to know the name of the computer, you can type in the command ”hostname” and press enter to see the name.) (Linux/OSX users: run ifconfig from a terminal (you may have to sudo the command or su to root)

2) Once you have identified all of the IP addresses (or names) of the computers on your network that will be playing the game, pick one to designate as your IPX SERVER.

3) *OPTIONAL STEP* Sometimes the Microsoft Windows firewall is turned on and it could interfere with proper communications between the client and the server. If you want to run a test to make sure that everyone can connect to your server, then go to each computer that will be connecting to your designated server and start a windows command prompt. Once the prompt is open, use the ping command along with the IP address of the server -OR- the server computer’s name to make sure that the server can respond to the clients. [Example: " ping 192.168.1.100 " -or- " ping HP-PAV6330 " ]

4) Start DOSBOX on your designated server. Run the DOSBOX command:

ipxnet startserver

That is IT!! That is ALL YOU NEED TO DO on the server! It is THAT SIMPLE!

–we’re almost done!–

5) Now start DOSBOX on each client computer that will be joining in the multiplayer fun. Once DOSBOX is running we will be using the DOSBOX command ‘IPXNET CONNECT’ but we’ll be adding something to it. We will either add the IP address of the server or the name. If we were to use the IP address or name from the examples in the optional step 3, our DOSBOX command might look something like this:

C:\> IPXNET CONNECT 192.168.1.100

-OR-

C:\> IPXNET CONNECT HP-PAV6330

At this point, DOSBOX will handle wrapping the IPX packets in TCP/IP.

6) Start WAR2 on the server, Select Multiplayer, select the IPX Network connection method and
click CONNECT then CREATE GAME.

7) Start War2 on each client, Select Multiplayer, select the IPX Network connection method and click CONNECT then JOIN GAME.

8) Begin your game and race your peons out to the unclaimed gold mines to put walls around them to protect them from any players..especially computer players. Oh..wait….that doesn’t belong in this set of instructions! Now who let that slip by quality control?!!?

NOTE 1: It *IS* possible to play WARCRAFT II with a friend across the internet. The variety of the additional steps needed are a bit beyond anyone’s ability to document in a single document but I can briefly outline the requirements below.

A) The gamer who will be the server ( the server user) will have to know their real-world public IP address. If you don’t know your public IP address, you can visit a site that displays your public IP address. A google search on finding your public IP will reveal many. http://www.whatismyip.com is one. [#]

B) If the server user is behind a router/firewall, then the server user will also need to..

*) know their private IP address. This is the IP address that was discovered in the ‘ipconfig’ command from step 1 above.

*) configure their router/firewall to forward the UDP port 213 –DOSBOX IPX WRAPPER traffic– from their external interface to UDP port 213 on the private IP Address of the computer that is the DOSBOX IPX server.

Note 2: The DOSBOX command ” IPXNET help ” will display a list of available networking commands and a small bit of documentation — like the fact that the DEFAULT port for the IPX wrapper in DOSBOX is UDP port 213

Note 3: These same networking steps should work for any IPX DOS game that runs in DOSBOX. These steps have been successfully tested with “One Must Fall”. [Google omf21cd.zip to download this free game.]

[#] Please avoid http://moanmyip.com if you are ..oh I don’t know… at work setting up for a Christmas LAN party! Of course using that link as a secondary browser-start-up-home-page can be fun.

Happy Retro-Gaming!

#include <sys/time.h>

unsigned GetTickCount()
{
        struct timeval tv;
        if(gettimeofday(&tv, NULL) != 0)
                return 0;

        return (tv.tv_sec * 1000) + (tv.tv_usec / 1000);
}

Waiting for root filesystem

I’ve just spent a few torturous hours trying to get it back up again. It took me a while to figure out what was happening but it seems that the updated package for UDEV changes the GRUB configuration so it tries to mount hdb1 instead of hda1 as the root file system. Of course hdb1 does not exist on this single-drive machine so it just sits there like a moron.

Turns out it is not frozen. If you wait about 3 minutes, it will eventually come up with the following prompt:

(initfs)

I found that I can kind of get the system running by typing the following commands. These are for a single-partition system on an EXT3 file system on an IDE hard drive. If your system is different, you will need to modify them a bit:

mkdir /mnt

mount /dev/hda1 -t ext3 /mnt

chroot /mnt

login

Then log in. The next thing to do is to correct the GRUB configuration:

nano -w /boot/grub/menu.lst

Change the root=/dev/sdb1 entry to root=/dev/sda1. Once again, this is for a single IDE drive, you may need to change it if you are booting from SATA or some other kind of device.

Now regenerate the initramfs image:

dpkg-reconfigure initramfs-tools

At last we can reboot. The system came up fine for me after this.

reboot

The Etch release of Debian does not have a driver for this card built-in and even though Adaptec claim to support Linux, their drivers simply do not work unless you are running some specific outdated versions of Red Hat or SUSE. That’s not what I call Linux support!

I’m not the only one discovering this, Brent Norris wrote a wonderful article titled “Adaptec 1420SA is JUNK!” on his blog which describes pretty much the exact situation I find myself in which Adaptec just doesn’t want to know about Linux.

When are these guys (by whom I mean most major hardware manufacturers) going to realize that Linux is here to stay and is getting real popular, especially in the server room.

Anyway, enough ranting. After a couple of hours Googling around, I see that there is an open source driver available for this card and it is built into Linux kernel version 2.6.22. Debian Etch uses 2.6.18 so all I need to do is upgrade the kernel.

The easiest way to install the upgraded kernel is to get a DEB package from Debian Backports. Go to this page:

http://packages.debian.org/etch-backports/admin/

and grab a kernel, there are usually a couple of different versions available there.

Install it and reboot. Works great so far.

PS. I notice that the driver for this card was released into the Linux kernel by Red Hat corporation. So it seems even they are fed up with Adaptec’s poor support for Linux!

I can see it won’t be long before DVD drives will be an optional extra on new PCs (especially laptops) and will eventually disappear like floppy drives (remember them ?).

So it’s time to look at installing from USB on a machine which has no disc drive at all. I’ve found a few guides out there on the internet but none of them were easy to follow. I had to read several of them and then I still had to guess at stuff that wasn’t mentioned.

So here is my guide which is a little more comprehensive.

NOTE 2: I’m assuming you are logged in as a regular user. if you are logged in as root, just drop “sudo” off the beginning of all these commands.

Step 1 – Download the installation image

While there are several “small” installs for putting on a credit-card CD and so on, USB sticks are now large enough that you can use a normal install CD image. I am going to use the Debian Net Install which weighs in at around 160MB. This should easily fit on a 256MB device which quite frankly, people throw away these days because it is so uncool to have such a small device dangling from your keyring.

Go to http://www.debian.org/CD/netinst/ and download the netinst image for your platfom (if you don’t know, it’s probably i386).

Step 2 – Partition and Format the USB device

Most USB keys come pre-formatted with a FAT16 or FAT32 file system. If this is the case with your stick, just erase all the files on it and proceed to Step 3.

But of course, I had previously formatted mine with EXT3 so I’ll need to reformat it with a DOS format.

First set the partition type to DOS

sudo sfdisk -c /dev/sdb 1 c

Next, format the partition.

sudo mkdosfs /dev/sdb1

Step 3 – Obtain a kernel and RAMdisk image

Next you need an hd-install kernel and initrd image. You can download these from Debian also. For the current version of the kernel, they should be available from here:

http://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/hd-media/

Grab the two files vmlinuz and initrd.gz then mount your USB device and copy them onto it:

sudo mount /dev/sdb1 /mnt

sudo cp vmlinuz /mnt/

sudo cp initrd.gz /mnt/

Then you will need to make a file on the USB device called syslinux.cfg – just create a plain text file. Cut and paste the following two lines into it:

default vmlinuz
append initrd=initrd.gz

Step 4 – Copy the installation image

Next copy the ISO file you downloaded onto the USB device. From the commandline you can do it like this:

sudo cp debian-40r3-i386-netinst.iso /mnt/

Step 5 – Make the device bootable

You will need to have a couple of additional packages installed to do this:

sudo apt-get install syslinux mtools

Type these commands to make the stick bootable:

sudo syslinux /dev/sdb1

sudo install-mbr -r -p 1 /dev/sdb

Now you can unmount the USB device and you are good to go!

sudo umount /mnt/usb

Step 1. Install Cygwin

Go to http://www.cygwin.com/ and download setup.exe. Run it.

During the setup, you will have the opportunity to select what packages to install. Choose the following:

• binutils
• gcc-core
• bzip2
• flex
• make

Step 2. Download the compiler source code

You want binutils and gcc-core from GNU. Go to the GNU download page, choose a mirror and download the following files. Place them in your Cygwin home directory.

• binutils-2.15.tar.bz2
• gcc-core-3.4.2.tar.bz2

Yes there are more up-to-date versions but at the time of writing, the latest gcc versions do not support the 68000 platform. Feel free to try different versions but I know the versions just mentioned will work.

Step 3. Compile and install binutils

Launch Cygwin and type the following commands. Typing this kind of stuff is automatic for me these days. Its a pretty standard GNU setup procedure.

mkdir /usr/local/m68k

tar jxvf binutils-2.15.tar.bz2

cd binutils-2.15/

./configure --prefix=/usr/local/m68k --target=m68k-coff

make install

Step 4. Compile and install gcc

Same again for the C compiler.

cd ~

export PATH=$PATH:/usr/local/m68k/bin

tar jxvf gcc-core-3.4.2.tar.bz2

cd gcc-core-3.4.2/

./configure --prefix=/usr/local/m68k --target=m68k-coff --enable-languages=c

make install

Step 5. Set up your path

The 68000 compiler will be located in /usr/local/m68k/bin. To make life easier, you might like to add the following to your ~/.bashrc file:

export PATH=$PATH:/usr/local/m68k/bin

Step 6. Enjoy

Here’s the command to compile some C code:

m68k-coff-gcc -o test.out test.c

And the command to create a binary image from the compiled code:

m68k-coff-objcopy -O binary test.out test.bin

The solution ? Set up a degraded array, copy the data and then add the original disk to the array.

Put simply, a degraded array is a RAID array with one or more drives missing. RAID5 can operate with any one drive down. This is very useful if a drive fails, you can replace the faulty drive without losing any data. So we are going to pretend the drive with the data on it is ‘faulty’ so it won’t be part of the RAID until later when we miraculously ‘fix’ it.

On my machine, the new drives are /dev/sde, /dev/sdf and /dev/sdg. The drive with the data is /dev/sdh1. First we partition the new drives. You’ll need to type these two commands for each new drive:

echo ",,L" | sfdisk /dev/sde

sfdisk --change-id /dev/sd1 1 fd

You don’t have to use sfdisk, as long as you set up the partitions somehow and set them to type 0xFD (Linux RAID).

Now to create the degraded array. This is the magic bit.

mdadm --create /dev/md3 --level=5 --raid-devices=4 --spare-devices=0 /dev/sde1 /dev/sdf1 /dev/sdg1 missing

The magic word missing stands in for the drive with the data on it.

Next format the RAID array, mount the data drive and copy the data

mkfs.xfs /dev/md3

mount /dev/md3 /home/adam

mount /dev/sdh1 /mnt

cp -prv /mnt/* /home/adam/

This will take a while so you might want to do it in a screen session.

Finally, after the data is copied, we can add the data drive to the array. This is the bit where we can lose everything if it goes wrong so check your data is all on the RAID before proceeding.

umount /dev/sdh1

sfdisk --change-id /dev/sdh 1 fd

mdadm --manage /dev/md3 --add /dev/sdh1

I’m really pleased at this neat trick. I’ve now got a shiny RAID array with a total storage of 3TB. It all worked so well, I just had to blog about it!

My solution is to mount the drives by their UUID rather than by their device node. It took me quite a bit of Googling to find an example of how to do this so I thought I’d write it here so I will know for next time.

Normally, I’d put an entry in /etc/fstab like this to mount a drive:

/dev/sdb1  /var/www  ext3  defaults  0  2

But now I change it like so:

UUID=bd412298-d540-4e4e-8f31-33ff45644bc4  /var/www  ext3  defaults  0  2

You’ll notice it is exactly the same except I have used the UUID instead of /dev/sdb1.

But wait! I hear you ask, how do you find out what your drive’s UUID is ?

Well, I have the answer for that too:

ls -l /dev/disk/by-uuid/

The problem is that the PVR150 cards sometimes register themselves as /dev/video0, 1 and 2 but other times, after a reboot they register themselves as /dev/video2, 3 and 4. I needed some way to make them stay on the same device nodes.

Enter this little UDEV rules file I wrote. It creates new device nodes called /dev/ivtvenc0, /dev/ivtvenc1 etc. up to however many cards you have. These will symlink to the correct device nodes every time. Here’s the script. Call it 010_ivtv.rules and put it in /etc/udev/rules.d/

# Rule to sort out those pesky IVTV cards which never
# seem to load in the correct order when DTV cards are
# also installed.
# by Adam Pierce 01-Feb-2008

ATTR{name}=="ivtv0 encoder MPEG",SYMLINK+="ivtvenc0"
ATTR{name}=="ivtv1 encoder MPEG",SYMLINK+="ivtvenc1"
ATTR{name}=="ivtv2 encoder MPEG",SYMLINK+="ivtvenc2"
ATTR{name}=="ivtv3 encoder MPEG",SYMLINK+="ivtvenc3"
ATTR{name}=="ivtv4 encoder MPEG",SYMLINK+="ivtvenc4"
ATTR{name}=="ivtv5 encoder MPEG",SYMLINK+="ivtvenc5"
ATTR{name}=="ivtv6 encoder MPEG",SYMLINK+="ivtvenc6"
ATTR{name}=="ivtv7 encoder MPEG",SYMLINK+="ivtvenc7"

Watch it in action. Here it is after one reboot:

# ls -l /dev/ivtv*
lrwxrwxrwx 1 root root 6 2008-02-01 13:54 /dev/ivtvenc0 -> video0
lrwxrwxrwx 1 root root 6 2008-02-01 13:54 /dev/ivtvenc1 -> video1
lrwxrwxrwx 1 root root 6 2008-02-01 13:54 /dev/ivtvenc2 -> video2

And again after the next reboot

# ls -l /dev/ivtv*
lrwxrwxrwx 1 root root 6 2008-02-01 13:54 /dev/ivtvenc0 -> video2
lrwxrwxrwx 1 root root 6 2008-02-01 13:54 /dev/ivtvenc1 -> video3
lrwxrwxrwx 1 root root 6 2008-02-01 13:54 /dev/ivtvenc2 -> video4

Now I can always rely on the ivtvenc device nodes to point at the right cards.

This solder paste stuff is pretty toxic. Perhaps I’m going overboard here but I thought some rubber gloves would be a good idea.


To apply the paste, I just squirted it on the board. It kinda went everywhere at first until I got the hang of it. Next time I’ll get a smaller tube and perhaps a smaller nozzle. I fixed it up as best I could using a toothpick and cotton tips. It took quite a lot longer and was much more messy than I anticipated.


Next comes the pick-and-place. I got most of my parts from Digi-key who send them out as “Cut tape” which is pretty convenient, you just peel the backing off the tape until you get the quantity of parts you need and the rest are left still attached to the tape so you don’t lose them in the carpet. I positioned the parts with tweezers since most of them are incredibly teeny.

My board includes both surface-mount and through-hole components. I just placed the SMT stuff at this stage because I need the back of the board to be flat for heat transfer.

Now for the fun bit. I put the loaded board onto the pan cold. Then I increased temperature to around 100°C. I left it at that heat for a minute to get everything nice and warm. Then I cranked up the heat to maximum (in my case, 175°) until the solder melted. It was magic to watch. Everything just blobbed into place. Even components which were not exactly positioned right pulled themselves into line.

After a slow cool-down over 5 minutes, I examined the board. Everything looks good to my eye except for some pretty major bridging between the pins of my ARM chip. I’ll leave dealing with these to part 3.

In the end though, I’m pretty pleased with the result. Not bad for my first try!

The idea is to use a frying pan or toaster oven to perform solder reflow for SMT circuit boards. I decided to use a skillet thinking that a toaster oven would melt components since it heats both top and bottom.

I managed to find the perfect thing. A pre-owned 9″ electric skillet from the Salvation Army shop for $3.

Believe it or not, this device is not a precision instrument. The temperature dial is simply numbered from 1 to 10. The first thing I need to do is get some idea of what actual temperature this thing gets to.


So I need to do a scientific experiment. Firstly I put some oil in the pan and stuck in a thermometer (the fork is to hold the probe in the oil). Then I turned up the heat slowly making a note of the temperature. Finally I graphed the result. Here are the results in degrees C. That cheap little temperature knob is surprisingly linear.

1. Element not energized
2. 30°
3. 46°
4. 65°
5. 90°
6. 105°
7. 125°
8. 140°
9. >150°
10. >150°

The last two entries I could not measure since the thermometer only went up to 150°C, but by extrapolation I get 155° and 175°. Yes I did this on paper, it is much quicker than using Excel!

I am now ready to use this thing for solder reflow.

DOS Emulation

First you need the very excellent DOSBOX which is a DOS emulator. You can download it from http://www.dosbox.com/.

Once DOSBOX is installed, we need somewhere to put our DOS games. I created a folder called C:\DOSGAMES for this purpose.


Now it is time to run DOSBOX. Once it is going, type the following two commands:

mount c C:\DOSGAMES\

mount d D:\ -t cdrom

NOTE: If your CD-ROM drive is not D:\, modify this accordingly.

Then you can insert your Warcraft II CD. The game can be installed like so:

D:

SETUP

Just select all the default options except for the soundcard and music device which you should set to Soundblaster 16.

Making an icon

At this point you can run the game by typing WAR2. But I don’t want to stop there. Let’s now make a pretty icon so you can launch the game with a mouse-click.

Open the folder C:\Program Files\DOSBox-0.72 and find the file dosbox.conf. Copy it to your C:\DOSGAMES\WAR2 folder.

Edit the copy of dosbox.conf and add the following line to the bottom under the [autoexec] section:

mount d D:\ -t cdrom

I’ve found it is also a good idea to reduce the speed of CPU emulation otherwise the map can scroll too fast. Modify the cycles entry in dosbox.conf like so:

cycles=20000

Now save the changes you made to dosbox.conf.

Copy the DOSBOX icon on your desktop. Rename the copy to “Warcraft II”. Now right-click on the icon and select Properties.

Enter the following text (all on one line) into the Target box:

 "C:\Program Files\DOSBox-0.72\dosbox.exe" "C:\DOSGAMES\WAR2\WAR2.EXE"
-conf "C:\DOSGAMES\WAR2\dosbox.conf" -exit -fullscreen

Then finally click on the Change Icon button.

Click Browse and navigate to the folder C:\DOSGAMES\WAR2. Double-click the file WAR2ICON.DLL.

Choose the WarCraft icon and then click OK. Click OK on the shortcut properties window also.

Now we are done. Click the WarCraft icon and enjoy!

I’ve only had it for a couple of days but in that time I have transferred more than 10GB through it and it has been 100% reliable.

This one was not too difficult to get going on Ubuntu since it is well supported by the MadWifi drivers which are built in to Ubuntu.


However there is a little catch if you want to use WEP. You need to add the iwpriv command to activate your WEP. Here’s my /etc/network/interfaces file with the tricky bit highlighted in bold:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# TP-Link Wi-fi card
auto ath0
iface ath0 inet dhcp
        wireless-mode Managed
        wireless-essid adamnet
        pre-up iwpriv ath0 authmode 2
        wireless-key 1234567890

NOTES: If you are copying this, make sure to change the essid and key to match those of your own network. And if you think this is my real WEP key, you are in for some disappointment.

I really wish I’d read this one back when I was getting started in VHDL. I wouldn’t have found it so hard. This document describes the basics of VHDL in a very clear and readable way. It’s well worth a look if you are wanting to learn VHDL.

void CMyWindow::OnMove()
{
    CRect r;
    GetClientRect(r);

// _piWindow is a pointer to my filtergraph's IVideoWindow interface.
    _piWindow->SetWindowPosition(r.left, r.top, r.Width(), r.Height());
}

It works fine if the video is playing but if the replay is paused, the active movie window will ignore the window move commands.

The solution was to trick DirectShow into thinking that you want to resize the window like so:

void CMyWindow::OnMove()
{
    CRect r;
    GetClientRect(r);

    _piWindow->SetWindowPosition(r.left, r.top, r.Width() + 4, r.Height());
    _piWindow->SetWindowPosition(r.left, r.top, r.Width(), r.Height());
}