• Guest would you be interested in CUPRA or SEAT valve caps? let us know in the poll

  • Welcome to our new sponsor Lecatona, a brand dedicated to enhancing performance for VAG group sports cars, including SEAT, Audi, Volkswagen and Škoda. Specializing in High Pressure Fuel Pump (HPFP) upgrades.
Tell

Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1

rctempire

Active Member
Jun 20, 2022
7
3
The old release should work straight away.

Failing that the new release with the old release overall.nds from year dot.

Failing that try the new release with the overall.nds that came with it. If that one works it means your unit had the life time navigation FeCs on it. The production issue which the Spanish board said about.

Do a long hold reboot on the infotainnnent unit each time so it sees the card afresh.
Update time.

So tried the day one from Skoda, straight replace, Navi booted up fine, Date in software shows 6P0919866 0430 ECE 2015-16.

Tried the DiscoverMedia2 EU1 1910 V16 you posted from June, straight overwrite and into car slot 1. Took a while and booted in, Date on software shows V03959817TG 1910 ECE1 2023. No messing with the NDS file from previous versions.

Success. Thank you.


So now the Nav instead of 6P0 is showing V03. Is this a issue going forward?

Should the shield: shield 2016-44 build 309 be updated at somepoint? If so how?
 

Tell

Full Member
Staff member
Moderator
Update time.

So tried the day one from Skoda, straight replace, Navi booted up fine, Date in software shows 6P0919866 0430 ECE 2015-16.

Tried the DiscoverMedia2 EU1 1910 V16 you posted from June, straight overwrite and into car slot 1. Took a while and booted in, Date on software shows V03959817TG 1910 ECE1 2023. No messing with the NDS file from previous versions.

Success. Thank you.


So now the Nav instead of 6P0 is showing V03. Is this a issue going forward?

Should the shield: shield 2016-44 build 309 be updated at somepoint? If so how?
Ok remember what you did for next time.

The V03 is picked out by the mib2 firmware. It doesn't mean anything. Probably the people who manufactured the release were lazy or not. Within the update file there will be a line in that which allocates Seats to V03. Just shows that on the screen. The original all Europe release always came up as 6Pxxx. Thats the Seat part number of that release. The release includes all part numbers of VAG brands. It just throws up the part number for that release for brand... all one release for all brands.

The Shield business names come from it running Nvidia Tegra chip where they like to use the word "Shield". What I told the last person that asked that. It runs QNX... 😂. I reckon that's where that comes from. Probably the boot loader. Any advance on that welcome.

It would only be the firmware that you could consider updating but I wouldn't if it's working fine.
 
  • Like
Reactions: rctempire

rctempire

Active Member
Jun 20, 2022
7
3
Ok remember what you did for next time.

The V03 is picked out by the mib2 firmware. It doesn't mean anything. Probably the people who manufactured the release were lazy or not. Within the update file there will be a line in that which allocates Seats to V03. Just shows that on the screen. The original all Europe release always came up as 6Pxxx. Thats the Seat part number of that release. The release includes all part numbers of VAG brands. It just throws up the part number for that release for brand... all one release for all brands.

The Shield business names come from it running Nvidia Tegra chip where they like to use the word "Shield". What I told the last person that asked that. It runs QNX... 😂. I reckon that's where that comes from. Probably the boot loader. Any advance on that welcome.

It would only be the firmware that you could consider updating but I wouldn't if it's working fine.
Makes sense, Nvidia always likes to hold onto a name for ever, geforce anyone.

Thats fine, will be using the navi system today on an extended drive so will see how it performs.

Thanks again. Looks like the spanish board was right, had the weird SD card with map updates. Back today dot and latest maps applied all working nicely.
 
  • Like
Reactions: Tell
Jul 24, 2022
4
1
Hi All
I've a seat leon 2018 FR 5F, navi 6P0, my navi database version as per the screenshot, then I've downloaded the recent maps updates from: https://www.seat.de/kontakt/downloads/map -updates /leon.html
I've followed the steps and updated the original SD Card and it works fine but unfortunately, now I don't see any thing in the Version Information page. any ideas?
Thanks!
 

Attachments

  • Navi Version.jpg
    Navi Version.jpg
    508.4 KB · Views: 292

Tell

Full Member
Staff member
Moderator
Hi All
I've a seat leon 2018 FR 5F, navi 6P0, my navi database version as per the screenshot, then I've downloaded the recent maps updates from: https://www.seat.de/kontakt/downloads/map -updates /leon.html
I've followed the steps and updated the original SD Card and it works fine but unfortunately, now I don't see any thing in the Version Information page. any ideas?
Thanks!
Two things. I'm wondering whether you have an older release. Seat and Skoda drag their feet and don't put up the most recent releases. In the know we take them off the servers direct not off the wrapped up web pages. 1910 with the year 2023 mentioned is the June 2022 release, released a month early for the mib2 standard. See here a few pages back on the link:


It's a common mistake using the brands own webpage which isn't up to date. The key really is the serial release which should be 1910.

On missing rows of the display these are populated from the files within the release. If when they are produce the files they miss off the title you won't see anything. That one has been reported in other releases in some of the zoned versions. This is just where QA has gone missing during production on the zoned maps. The real test is whether you are seeing the serial release in this case 1910 which is the summer release of these map files.

The titles are user editable in the release but don't bother. In the old days of the work around people would edit the release text to make it look like the old release that is just daft. Moving the overall.nds between your current release and the new one is the only thing that needs to be done (accepting one six month release talked about on the thread) the rest falls into place taking whatever the files are populated with but taken from the servers with the most up to date release. The servers / web pages / brand may not be aligned which is why we take them from the published in the know links. This period are the ones above.

All mib2 standard map release for the Vag brands are interchangeable so we use which ever is published first but direct from their servers not web page wrapped. Same holds true for mib2 high the Seat Plus but the workaround there is to get your FeCs changed.

yep Seat bless them are still posting up old map links use the ones I pointed too unless you like old maps:

 
Last edited:

Tell

Full Member
Staff member
Moderator
Yours is a mib1. The tell tail sign is the part number is 5F.... , 6P it's a mib2. Software version has STD in it which means it is a mib1 standard. It's a dealer task to update the maps on a mib1. The last updates by Vag were 2020 for mib1. Users never worked out a DIY task for them. When mib2 came out some people ripped out the mib1 and changed to mib2. Some stayed with standard mib2 others upgraded to mib2 high. Threads about on that. All things equal mib2 updates should go on to 2025 following the mib cycle of 5 year hardware refresh plus 5 years map updates.
 

H Rafiq

Active Member
Jan 5, 2022
1,101
444
Yours is a mib1. The tell tail sign is the part number is 5F.... , 6P it's a mib2. Software version has STD in it which means it is a mib1 standard. It's a dealer task to update the maps on a mib1. The last updates by Vag were 2020 for mib1. Users never worked out a DIY task for them. When mib2 came out some people ripped out the mib1 and changed to mib2. Some stayed with standard mib2 others upgraded to mib2 high. Threads about on that. All things equal mib2 updates should go on to 2025 following the mib cycle of 5 year hardware refresh plus 5 years map updates.
Thanks 🙏🏼 I’ll ask the dealer for an update when it goes for a service in a month or so. I don’t think it’s worth the money upgrading this to MIB2 or later to be honest. It doesn’t have CarPlay, or USBs or aux under the heater controls. But it does have sat nav, Bluetooth, DAB and park pilot, so can’t complain. Six of one and half a dozen of the other 🤷🏻‍♂️
 

Tell

Full Member
Staff member
Moderator
Thanks 🙏🏼 I’ll ask the dealer for an update when it goes for a service in a month or so. I don’t think it’s worth the money upgrading this to MIB2 or later to be honest. It doesn’t have CarPlay, or USBs or aux under the heater controls. But it does have sat nav, Bluetooth, DAB and park pilot, so can’t complain. Six of one and half a dozen of the other 🤷🏻‍♂️
Probably a task they don't often get asked about. They would probably have to go back to Seat technical support to get the update pack / file / online procedure. VW and Skodas in the UK were sold with unlimited Mapcare which meant you could do it yourself, it was a free perk for those brands. It never got to Seat. DIY procedures were found for mib2 to update if you didn't have it so you could enjoy the same common map update feature. The community did sort out how to replace a lost mib1 card within release period but not how to update it to a different year. That's in the resource section. In the corner of the net somewhere you might find someone who has done it for mib1 and that would be around changing the firmware but inherent risks in that one, if there isn't a body of knowledge on that one.
 
  • Like
Reactions: Walone and H Rafiq
Sep 2, 2022
1
1
Hi All,

thanks to this forum and the detailed explanation I was able to find out what is the problem with my navi update, the installed FEC code is 07300026 (I bought my car with 3 years Mapce in 2017...), I have Mib2 High with built-in HDD.
Is there any possibility to perform the update without involving the Seat dealer? The local service sad that they can do that but the cost is cca. 200EUR each time when I'd like to update the map (in 2017 the Mapcare for 3 years was less then half price).
Thanks!
 

Attachments

  • 20220902_073523_resized.jpg
    20220902_073523_resized.jpg
    83.4 KB · Views: 194
  • 20220902_073604_resized.jpg
    20220902_073604_resized.jpg
    77.7 KB · Views: 188
  • Like
Reactions: JoseKaLeL

Tell

Full Member
Staff member
Moderator
Hi All,

thanks to this forum and the detailed explanation I was able to find out what is the problem with my navi update, the installed FEC code is 07300026 (I bought my car with 3 years Mapce in 2017...), I have Mib2 High with built-in HDD.
Is there any possibility to perform the update without involving the Seat dealer? The local service sad that they can do that but the cost is cca. 200EUR each time when I'd like to update the map (in 2017 the Mapcare for 3 years was less then half price).
Thanks!
A group of hobbyists have generated two techniques for the mib2 high. Either work. One is to update the firmware to the final release with the code 1447 AIO. The AIO means all in one, gives the mapcare FeC boost you need to life time FeCs. The software is resilient so can be used on older Mib2 highs, doesn't seem to be depended on which "train" you were on so some very early mib2 highs have been done this way as well as the latest. The other method uses the mib2 high toolkit, that one can be used with specific mib2 firmware releases. It replaces a piece of code with another piece of code which allows the FeCs to be updated from within the green menu. The toolkit resides in the green menu. It gives retrofitter techniques in the car rather than on a work bench with a laptop and the usb / ethernet dongle. The original method. That one (Toolkit) I used when Seat for one release only of the maps decided not to release them for Seat. Retrofitters and hobbyists knew that they could use Skoda or VW FeCs on these units. The toolkit recognises which firmware you are on and offers up the appropriate module or if it doesnt have one you are invited to send you back up for the group to write the module, that's what I did since 1338 was not supported then. Use a text editor to add the FeC code.

The choice of which to use is up to you. The 1447 AIO method wasn't out when I did mine. 1447 was cumbersome then since some files had been left out so you had to top up with the previous release using the mib2 backend menu. Also you got a black screen and had to change the skin prior to starting and also had to use Mib Tool in anycase for the FeC work. So I stayed put on my firmware release. All of these issues were sorted out in 1447 AIO where they added in the missing files, sorted the screen issue out and built the FeC edit into it. You just sit back and let it run. With the car engine on, suppose to be on battery charger. Main thing is you can't interrupt firmware updates. Reboots several times and job should be done.

The links are on the firmware thread:

How it was before 1447 AIO with just the two options 1447 / Mib Tool:


Link to 1447 AIO:


All of the discussion is on the firmware thread on this. Certainly 1447 AIO has had a lot of reported success from the spring this year. You do need to let it run to the end. One poster answered the question wrong about do you want to use the toolkit. Popped the question up as it progressed. You reply yes and the FeCs get updated. Incorrect answer you get the firmware update but the FeC work isn't done with the updates.

@mykro got it working on a very early mib2 high in early spring followed by success with a number of other people:


The only stumbling block seems to be where people have fiddled with the screen palette colours then have to fiddle again to get it how they want it. Never fiddled with mine and I've got the ambient lights on my car (happy with circa 16 hues). That's covered on the firmware thread tinkering with the display after using 1447 AIO. Might need it on very old mib2 highs without ambient lighting where 1447 assumes ambient lighting or where you have changed the display colour pallete using Obdeleven / VCDS.

Mib Wiki is the self appointed administrator to the mib international hobbyist group... other members of the "collective" as I call them post on the mib2 firmware thread.
 
Last edited:

Tell

Full Member
Staff member
Moderator
Standard Navigation Map Release November 2022 - aka release code 2010

On these ones you do have to use the workaround and DON'T delete what is on the SD card without copying it since you need a file from it to make it work and DON'T format the card, just delete the contents
. Watch out if you use a Mac for this, suppose to use Keka and CleanMyDrive on the SD card if a Mac.. Use the zoned releases if you have a 16gb card or the language trick covered in the resource to fit ECE AS on the card or get a 32Gb card. All map files are interchangeable across the VAG brand for Mib2 FeCs allowing - they are identical premade to across VAG.

Resource link on how to do it:


# ECE AS(A1) 2023 15.2 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-AS_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-AS_2010_V17.7z

# ECE 1 2023 6.7 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU1_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU1_2010_V17.7z

# ECE 2 2023 6.3 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU2_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU2_2010_V17.7z

# ECE 3 2023 5.3 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU3_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU3_2010_V17.7z

# ECE 4 2023 8.5 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL1_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL1_2010_V17.7z

# ECE 5 2023 8.6 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL2_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL2_2010_V17.7z

# ECE 6 2023 8.0 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL3_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL3_2010_V17.7z

# ECE 7 2023 6.8 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_EU-DL4_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_EU-DL4_2010_V17.7z

# ROW 1 2023 7.0 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM1_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM1_2010_V17.7z

# ROW 2 2023 4.4 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM2_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM2_2010_V17.7z

# ROW 3 2023 5.3 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM3_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM4_2010_V17.7z

# MRM DL1 2023 5.7 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM-DL1_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM-DL1_2010_V17.7z

# MRM DL2 2023 1.4 Gb
VW portal: https://vw-maps-cdn.lighthouselabs.eu/vw-maps/DiscoverMedia2_MRM-DL2_2010_V17.7z
VW portal: https://navigation-maps.volkswagen.com/vw-maps/DiscoverMedia2_MRM-DL2_2010_V17.7z

Key

# ECE AS(A1)
Albania, Andorra, Austria, Belarus, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Czech Republic, Cyprus, Denmark, Estonia, Finland, France, Faroe Islands, Germany, Gibraltar, Greece, Hungary, Iceland, Ireland, Ireland, Italy, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malta, Moldova, Monaco, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, San Marino, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Ukraine, United Kingdom, Vatican City State
YuSgmVpHyD2FPsHNH29abdM6Olw-960.jpg






# ECE 1
Andorra, Belgium, Faroe Islands, France, Gibraltar, Iceland, Ireland, Ireland, Luxembourg, Monaco, Netherlands, Portugal, Spain, United Kingdom
pv5F6zXqno6eVs-pwKpA7YLI4B4-960.jpg






# ECE 2
Albania, Belarus, Bosnia and Herzegovina, Bulgaria, Cyprus, Denmark, Estonia, Finland, Greece, Kazakhstan, Kosovo, Latvia, Lithuania, Macedonia, Moldova, Montenegro, Norway, Romania, Russian Federation, Serbia, Sweden, Ukraine
L3UymUfst5cznTN7jAhpxX1lKCQ-960.jpg






# ECE 3
Austria, Croatia, Czech Republic, Germany, Hungary, Italy, Liechtenstein, Malta, Poland, San Marino, Slovakia, Slovenia, Switzerland, Vatican City State
ALKkbqgMnKv9EdJj_RAIq1G44Ok-960.jpg






# ECE 4
Andorra, Austria, Belgium, Croatia, Czech Republic, France, Germany, Hungary, Italy, Liechtenstein, Luxembourg, Malta, Monaco, Netherlands, Poland, San Marino, Slovakia, Slovenia, Switzerland, Vatican City State
ahUOEqem0o83NpiHWGSh1mHHBME-960.jpg






# ECE 5
Andorra, Austria, Belgium, Croatia, Czech Republic, Faroe Islands (land-use only), France, Germany, Hungary, Iceland, Ireland, Italy, Liechtenstein, Luxembourg, Malta, Monaco, Netherlands, Poland, San Marino, Slovakia, Slovenia, Switzerland, United Kingdom (incl. Isle of Man), Vatican City State
gV8WvR4Gu5TikwkohJeJeEenq0s-960.jpg






# ECE 6
Andorra, Belgium, Denmark, Faroe Islands (land-use only), Finland, France, Germany, Iceland, Ireland, Luxembourg, Monaco, Netherlands, Norway, Sweden, United Kingdom (incl. Isle of Man)
wsWKLsV0LVlOrwitpIaibQEyyG4-960.jpg






# ECE 7
Albania, Austria, Belarus, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, Estonia, Greece, Hungary, Italy, Kosovo, Latvia, Lithuania, Liechtenstein, Macedonia, F.Y.R.O., Malta, Moldova, Montenegro, Poland, Romania, San Marino, Serbia, Slovakia, Slovenia, Switzerland, Turkey, Ukraine, Vatican City State
v04GbGS7sHDighOrC1V_HOHm-4I-960.jpg






# ROW 1
Israel, Argentina, Brazil, Fr. Guyana *, Guadeloupe *, Martinique *, Mexico, Turkey *
_qdGOCVcaVkDWzRB9n8E9SDQ9jU-960.jpg








# ROW 2
India *, Chile *
A64OdkuuZAVU1MC1sQb828sgdMU-960.jpg








# ROW 3
Australia, New Zealand, Botswana *, Lesotho *, Mozambique *, Namibia *, South Africa, Swaziland *; Reunion *, Brunei, Indonesia *, Malaysia *, Philippines *, Singapore, Thailand, Egypt *, Algeria *, Bahrain *, Jordan *, Qatar *, Kuwait, Morocco, Oman *, Saudi Arbien *, Tunisia, United Arab Emirates *
td_mPMDjnivv5SWwtTltI2Z2YVk-960.jpg
# MRM DL1
Argentina, Brazil, Mexico, French Guiana, Guadeloupe, Martinique

# MRM DL2
Israel, Turkey

Normal success screen, ECE1 in this case:
20221108_123501.jpg


Credit file location to Briskoda MartiniB who uses advanced sniffing techniques to find them. Beats everybody else now.
 
Last edited:

Giuseppe Busso

Ioannis
Jan 29, 2021
91
53
Greece
# ECE 2
Albania, Belarus, Bosnia and Herzegovina, Bulgaria, Cyprus, Denmark, Estonia, Finland, Greece, Kazakhstan, Kosovo, Latvia, Lithuania, Macedonia, Moldova, Montenegro, Norway, Romania, Russian Federation, Serbia, Sweden, Ukraine
L3UymUfst5cznTN7jAhpxX1lKCQ-960.jpg


Sorry for the intrusion but there is not country called Macedonia. There is one called Republic of North Macedonia and it is northern of the Hellenic Macedonian territory.
 

Tell

Full Member
Staff member
Moderator
Sorry for the intrusion but there is not country called Macedonia. There is one called Republic of North Macedonia and it is northern of the Hellenic Macedonian territory.
It's what VW call it. The maps provide a guide to the area then they put the text around it. They have issues with disputed borders or where they have moved etc. The map files are produced under contract by another company as I understand it from the source material, in this case TomTom to fit into the car's API system of navigation screens. So those geographers may be using old zones or it gets lost in translation. The main thing is the illustrated area rather than the name.
 

jonial

Jonial
Nov 1, 2003
188
19
Garstang
www.g4ial.com
It's what VW call it. The maps provide a guide to the area then they put the text around it. They have issues with disputed borders or where they have moved etc. The map files are produced under contract by another company as I understand it from the source material, in this case TomTom to fit into the car's API system of navigation screens. So those geographers may be using old zones or it gets lost in translation. The main thing is the illustrated area rather than the name.
Thanks for the heads up Tell. Downloaded and updated very successfully
 
  • Like
Reactions: Tell

t_v

Active Member
Feb 19, 2021
98
78
Downloaded and updated without issue, using 32GB Skoda so can't comment on the 16GB cards any more (sold my v7 SEAT 16GB some time ago but it was still working with the languages workaround with the May update).
 
  • Like
Reactions: Tell

Tell

Full Member
Staff member
Moderator
Downloaded and updated without issue, using 32GB Skoda so can't comment on the 16GB cards any more (sold my v7 SEAT 16GB some time ago but it was still working with the languages workaround with the May update).
I reckon the issue with the 16gb card is when people reformat them rather than delete what's on them. Windows 11 defaults to a big sector size rather than the 4096 bytes that you need. Think that might swipe the CID but if they don't do that they move away from fat32 which won't work either. They end up with a card corrupted, been reported a few times. Most sensible is to delete after taking a copy of the overall.nds file and chill out whilst it slowly does it. Format is quicker but prone to issues. You need the 32gb card as you have for all of Europe without zoning now using the original overall.nds file of the 16gb card going forward.

All fine at this end with ece1. Slight delay and moaning about not reading the card on first boot up. Did a reboot which I tell people to do. Exciter's method forces the unit to compute new FeCs when you update with this method (moving the original overall.nds). So first time round it's a little longer as it computes new navigation FeCs in the unit. Suppose to be what happens and the vcds reported error you can't get rid of via a normal clear errors (but nobody is worried about) is due to multiple navigation FeCs in the unit. The standard mib2 toolbox is suppose to be able to get rid of them but you'd be loading that in the green menu for the pleasure. I've never been that worried about that much to fix it. Mr Fixit video on that. One of those standard tool boxes will write new navigation FeCs so you wouldn't have to do the extra file copy. Not worth the hassle.
 
SEATCUPRA.NET Forum merchandise