- Joined
- Nov 12, 2020
- Messages
- 67
- Reaction score
- 36
- Points
- 18
Welcome to part 2 of the "how to set up a retro with IIS" series! In this part, we'll make A LOT of progress towards making your new hotel playable 
What will we cover in part 2:
Download the default assets:
Time to setup the assets:
Good job! The next part will be on how to set up:
Java
Arcturus Emulator
Nitro v2 (latest as of August 2022)
To learn how to do all of the above, head to part 3 of this series, which will be the last and final part
Click here to go to part 3 of the "How to set up a retro (IIS) series
Did I miss anything?
Please let me know if I missed anything, as the guide contains a lot of information.
Credits: Object / Dennis
What will we cover in part 2:
Atom CMS setup
Atom HK setup
Volta (multi-node installations)
Nitro Converter setup
Atom HK setup
Volta (multi-node installations)
Nitro Converter setup
We'll need multiple versions of Node in-order to setup everything needed to play your new hotel, so to do that, we'll install a tool called "Volta" - Volta is a tool that lets us install & manage multiple versions of node hassle-free 
Head to and click on "" - Go through the installation process. Once volta has been installed re-open your CMD (command prompt) and enter:
Head to and click on "" - Go through the installation process. Once volta has been installed re-open your CMD (command prompt) and enter:
It's finally time to set up Atom CMS! this is the part where things start to get a little exciting, as we will get to see our website start functioning.
The first step of our road to set up Atom CMS will be to enable the PHP extensions required by Atom CMS to function properly, to do that head to C:\Program Files\PHP and scroll down until you find a file named "php" which is of file type "INI"
Open the file in your preferred editor (Mine will be Visual Studio Code)
Find the extensions list (You can find the list quickly by searching for "Dynamic Extensions") Once you've found the list, replace it with the extension list below.
The next step
* If you have the URL Rewrite extension installed already, skip to the "Clone Atom CMS" step below.
If you didn't install the URL Rewrite extension in part one, you'll have to install it now - . Simply click "Install this extension" and go through the setup process
Clone Atom CMS:
Now we will have to clone the Atom CMS repository and to do that you'll have to open your CMD (command prompt) application and enter the following:
press "enter" and then write
and press enter once again. Atom CMS will then be cloned into your C:/inetpub/wwwroot in a folder named "atomcms"
Dependencies installation:
Atom CMS relies on multiple different dependencies which we will have to install - To install those dependencies write
inside your CMD (command prompt) application which will bring you to the following path: "C:/inetpub/wwwroot/atomcms"
When you're inside the path mentioned above, enter the following commands
This will install all the required dependencies & compile the necessary assets for you.
Add the necessary database tables:
Atom CMS relies on a few custom database tables. Luckily it is super simple to add those, as Atom is making use of something called "migrations" which allows us to scaffold our database with all the necessary tables & columns that Atom CMS needs.
However, before Atom CMS can import the missing data, we'll have to connect it to our database, which we made in Part 1 of the series.
Connect Atom CMS to your database:
To make Atom CMS able to communicate with our database, we'll have to set the correct credentials, to do that copy the .env.example by using the following command in your CMD (command prompt):
Next up, open the .env file that is now located in the root of the Atom CMS folder, and fill in your database credentials as well as the correct database name - The variables you'll have to edit can be found below:
Once you have edited the variables above, all that is left to do is enter the following commands:
Once the commands above are done doing their thing, all the necessary tables & columns will be available within your database.
For Atom CMS to function we'll also have to generate an application key - luckily this is a simple process as well! All you have to do is to enter the following command in your CMD (command prompt)
Connect Atom CMS with IIS:
The time has come! We will now be connecting Atom CMS with IIS to make us able to browse our newly setup website
Step one:
Open up your Internet Information Services application and expand the section just below "Start Page"
Expand the "sites" section and right-click on the "Default website" and then "remove".
You will then have to add a new site to IIS and to do that, right-click yet again on the "Sites" and click "Add Website..."
In the "Site name:" field enter whatever name you find appropriate. In my case, I will just enter my domain name.
Next click the 3 dots next to the "Physical path:" field and browse into the "public" folder inside the "atomcms" folder. Once you have clicked on the "public" folder, click the "OK" button.
Next up we'll have to give full permission to the "atomcms" folder. To achieve this, browse yourself into the "C:\inetpub\wwwroot" folder and right-click on the "atomcms" folder select "Properties" then click the "Security" tab and click on "Edit..." and then "Add..." - A pop up should appear looking like the image below.
Enter "IIS_IUSRS" and then "OK". Click on "Add..." once more and add "IUSR" and then "OK".
Once both the "users" have been added, find both of them in the list and click them individually, once they have been selected toggle the "Full control" and then click "Apply" (Don't forget to do this on both the added users).
Check the images below, if you're unsure if you did it correctly
The first step of our road to set up Atom CMS will be to enable the PHP extensions required by Atom CMS to function properly, to do that head to C:\Program Files\PHP and scroll down until you find a file named "php" which is of file type "INI"
Open the file in your preferred editor (Mine will be Visual Studio Code)
Find the extensions list (You can find the list quickly by searching for "Dynamic Extensions") Once you've found the list, replace it with the extension list below.
The next step
* If you have the URL Rewrite extension installed already, skip to the "Clone Atom CMS" step below.
If you didn't install the URL Rewrite extension in part one, you'll have to install it now - . Simply click "Install this extension" and go through the setup process
Clone Atom CMS:
Now we will have to clone the Atom CMS repository and to do that you'll have to open your CMD (command prompt) application and enter the following:
press "enter" and then write
and press enter once again. Atom CMS will then be cloned into your C:/inetpub/wwwroot in a folder named "atomcms"
Dependencies installation:
Atom CMS relies on multiple different dependencies which we will have to install - To install those dependencies write
inside your CMD (command prompt) application which will bring you to the following path: "C:/inetpub/wwwroot/atomcms"
When you're inside the path mentioned above, enter the following commands
This will install all the required dependencies & compile the necessary assets for you.
Add the necessary database tables:
Atom CMS relies on a few custom database tables. Luckily it is super simple to add those, as Atom is making use of something called "migrations" which allows us to scaffold our database with all the necessary tables & columns that Atom CMS needs.
However, before Atom CMS can import the missing data, we'll have to connect it to our database, which we made in Part 1 of the series.
Connect Atom CMS to your database:
To make Atom CMS able to communicate with our database, we'll have to set the correct credentials, to do that copy the .env.example by using the following command in your CMD (command prompt):
Next up, open the .env file that is now located in the root of the Atom CMS folder, and fill in your database credentials as well as the correct database name - The variables you'll have to edit can be found below:
DB_DATABASE=your-database-name
DB_USERNAME=root
DB_PASSWORD=your-database-password
DB_USERNAME=root
DB_PASSWORD=your-database-password
Once you have edited the variables above, all that is left to do is enter the following commands:
Once the commands above are done doing their thing, all the necessary tables & columns will be available within your database.
For Atom CMS to function we'll also have to generate an application key - luckily this is a simple process as well! All you have to do is to enter the following command in your CMD (command prompt)
Connect Atom CMS with IIS:
The time has come! We will now be connecting Atom CMS with IIS to make us able to browse our newly setup website
Step one:
Open up your Internet Information Services application and expand the section just below "Start Page"
Expand the "sites" section and right-click on the "Default website" and then "remove".
You will then have to add a new site to IIS and to do that, right-click yet again on the "Sites" and click "Add Website..."
In the "Site name:" field enter whatever name you find appropriate. In my case, I will just enter my domain name.
Next click the 3 dots next to the "Physical path:" field and browse into the "public" folder inside the "atomcms" folder. Once you have clicked on the "public" folder, click the "OK" button.
Once you have done all of the above your "Add website" popup should look like this:
If that's the case simply click "OK".
If that's the case simply click "OK".
Next up we'll have to give full permission to the "atomcms" folder. To achieve this, browse yourself into the "C:\inetpub\wwwroot" folder and right-click on the "atomcms" folder select "Properties" then click the "Security" tab and click on "Edit..." and then "Add..." - A pop up should appear looking like the image below.
Enter "IIS_IUSRS" and then "OK". Click on "Add..." once more and add "IUSR" and then "OK".
Once both the "users" have been added, find both of them in the list and click them individually, once they have been selected toggle the "Full control" and then click "Apply" (Don't forget to do this on both the added users).
Check the images below, if you're unsure if you did it correctly
Download the default assets:
For us to be able to actually have fun and play the hotel, we will need to download some assets, which later on will be converted from ".swf" to ".nitro" files.
The assets we will be using will be the most recent files from Habbo itself.
So for us to ensure we get the absolute most recent assets, we'll start off by cloning an amazing tool made by Higoka called "Habbo downloader".
Habbo tool:
Before we can start using the tool, we'll need to clone it, to clone it - Open your CMD (command prompt) and write "cd C:\Users\Administrator\Desktop" and then press "enter":
Once you've done the above, enter the command below (It will take a while, so please be patient)
Once the cloning is finished, you'll then find yourself with a folder on your desktop named "habbo-downloader" which we'll have to "cd" into by entering the following command in your CMD (command prompt):
Once we're inside the folder we want to pin our node version to the Habbo downloader, and to do that enter the following commands:
Once we've pinned our node version you should run the command below:
The assets we will be using will be the most recent files from Habbo itself.
So for us to ensure we get the absolute most recent assets, we'll start off by cloning an amazing tool made by Higoka called "Habbo downloader".
Habbo tool:
Before we can start using the tool, we'll need to clone it, to clone it - Open your CMD (command prompt) and write "cd C:\Users\Administrator\Desktop" and then press "enter":
Once you've done the above, enter the command below (It will take a while, so please be patient)
Once the cloning is finished, you'll then find yourself with a folder on your desktop named "habbo-downloader" which we'll have to "cd" into by entering the following command in your CMD (command prompt):
Once we're inside the folder we want to pin our node version to the Habbo downloader, and to do that enter the following commands:
Once we've pinned our node version you should run the command below:
Time to setup the assets:
It's time for us to set up most of our assets which we'll need later on when we're gonna convert everything into ".nitro" files.
Start by opening your CMD (command prompt) and copy-paste the following
The command above will clone all the default assets we need into "C:/inetpub/wwwroot/atomcms/public/client/flash" - Please be patient, it might take a while.
Once everything is finished cloning, we will have to update a few assets, since we want the most up2date assets possible.
Start by heading into "C:/inetpub/wwwroot/atomcms/public/client/flash/gordon" and delete the "PRODUCTION-202006192205-424220153" folder.
Once the folder has been deleted, open the "habbo-downloader" folder on your desktop, head into the "resource" folder then into the "gordon" folder, and scroll all the way to the bottom. You'll see a lot of folders named something like "PRODUCTION-2022xxxxxxxxx" however the bottom one will be the most recent one, which will also be the one we're gonna copy.
So copy the very last folder within the list into the "C:/inetpub/wwwroot/atomcms/public/client/flash/gordon" folder.
Once it has been copied rename the copied folder to "PRODUCTION".
I've recorded a GIF showing the process of copying the folder, in case you're in doubt -
After you've copied & renamed the "PRODUCTION" folder you have to go 1 step out - which should land you inside of "C:/inetpub/wwwroot/atomcms/public/client/flash" and for the "habbo downloader" you also go 1 step out which should land you within the "resource" folder.
Once you've done so in both folders, you have to copy the "c_images", "dcr" and the "gamedata" folder into the "flash" folder.
Yet again I have recorded a GIF, in case you're a bit confused or in doubt: - If it asks you to replace any assets, simply allow to replace them all.
Import 2022 catalogue
Open git bash and enter the following commands:
Once the catalog SQL has been cloned, open your DBeaver and import it. Here's a GIF showing some of the process of importing the SQL:
That's it for this section, next up will be to set up the Nitro converter, so that we can convert all our assets into usable nitro assets.
Start by opening your CMD (command prompt) and copy-paste the following
The command above will clone all the default assets we need into "C:/inetpub/wwwroot/atomcms/public/client/flash" - Please be patient, it might take a while.
Once everything is finished cloning, we will have to update a few assets, since we want the most up2date assets possible.
Start by heading into "C:/inetpub/wwwroot/atomcms/public/client/flash/gordon" and delete the "PRODUCTION-202006192205-424220153" folder.
Once the folder has been deleted, open the "habbo-downloader" folder on your desktop, head into the "resource" folder then into the "gordon" folder, and scroll all the way to the bottom. You'll see a lot of folders named something like "PRODUCTION-2022xxxxxxxxx" however the bottom one will be the most recent one, which will also be the one we're gonna copy.
So copy the very last folder within the list into the "C:/inetpub/wwwroot/atomcms/public/client/flash/gordon" folder.
Once it has been copied rename the copied folder to "PRODUCTION".
I've recorded a GIF showing the process of copying the folder, in case you're in doubt -
After you've copied & renamed the "PRODUCTION" folder you have to go 1 step out - which should land you inside of "C:/inetpub/wwwroot/atomcms/public/client/flash" and for the "habbo downloader" you also go 1 step out which should land you within the "resource" folder.
Once you've done so in both folders, you have to copy the "c_images", "dcr" and the "gamedata" folder into the "flash" folder.
Yet again I have recorded a GIF, in case you're a bit confused or in doubt: - If it asks you to replace any assets, simply allow to replace them all.
Import 2022 catalogue
Open git bash and enter the following commands:
Once the catalog SQL has been cloned, open your DBeaver and import it. Here's a GIF showing some of the process of importing the SQL:
That's it for this section, next up will be to set up the Nitro converter, so that we can convert all our assets into usable nitro assets.
Alright, the time has come to convert all of our assets into usable nitro assets, and luckily for us, the Nitro team has made this process super easy, as they've provided us with a converter, that we'll be using.
The first step:
We will need to clone the converter, and as usual, we'll start by opening our CMD (command prompt) and navigating yourself to your desktop, usually, all you have to do is to write
and press enter.
Next, enter the following:
Once the converter has been cloned, open the "nitro-converter" folder on your desktop and head to the, and rename the "configuration.json.example" to "configuration.json", once you have renamed the configuration file, you'll have to set it up, so that it knows where to grab the files, that it should convert.
If you have been following along since part one of this series and do everything 1:1 then linking everything will be easy for you, as I have already prepared the entire configuration, which you can copy below.
Replace everything inside of your original configuration.json with the code above.
Once you have set up your configuration correctly, open your Command Prompt and navigate into the nitro-converter folder by entering the following:
Once you're inside the nitro-converter folder, in your command prompt, write:
Once the commands have been entered, it should look something like the images below
Now that the necessary dependencies have been installed, you can start converting your assets, and do that, write:
Then press enter and the converter will then do its magic and convert all of your assets into usable nitro assets - This will take a while, so be patient and wait until it has finished.
Once all your assets have been converted, your converter should look something like the image below:
You have now successfully converted all of your assets into nitro assets.
Move assets to Atom
Now that we have all of our assets converted into .nitro files, we'll need to move them into atom, so once we setup the nitro client, it will be able to fetch and display them!
So let's start by creating a new folder inside the "C:\inetpub\wwwroot\atomcms\public\client" called "nitro".
Next, open your "nitro-converter" folder and copy all the converted assets within the "assets" folder and paste them inside the "C:\inetpub\wwwroot\atomcms\public\client\nitro" folder.
The next part will be to set up the Arcturus Morningstar emulator. Which we will cover in the last and final part of this series!
The first step:
We will need to clone the converter, and as usual, we'll start by opening our CMD (command prompt) and navigating yourself to your desktop, usually, all you have to do is to write
and press enter.
Next, enter the following:
Once the converter has been cloned, open the "nitro-converter" folder on your desktop and head to the, and rename the "configuration.json.example" to "configuration.json", once you have renamed the configuration file, you'll have to set it up, so that it knows where to grab the files, that it should convert.
If you have been following along since part one of this series and do everything 1:1 then linking everything will be easy for you, as I have already prepared the entire configuration, which you can copy below.
Replace everything inside of your original configuration.json with the code above.
Once you have set up your configuration correctly, open your Command Prompt and navigate into the nitro-converter folder by entering the following:
Once you're inside the nitro-converter folder, in your command prompt, write:
Once the commands have been entered, it should look something like the images below
Now that the necessary dependencies have been installed, you can start converting your assets, and do that, write:
Then press enter and the converter will then do its magic and convert all of your assets into usable nitro assets - This will take a while, so be patient and wait until it has finished.
Once all your assets have been converted, your converter should look something like the image below:
You have now successfully converted all of your assets into nitro assets.
Move assets to Atom
Now that we have all of our assets converted into .nitro files, we'll need to move them into atom, so once we setup the nitro client, it will be able to fetch and display them!
So let's start by creating a new folder inside the "C:\inetpub\wwwroot\atomcms\public\client" called "nitro".
Next, open your "nitro-converter" folder and copy all the converted assets within the "assets" folder and paste them inside the "C:\inetpub\wwwroot\atomcms\public\client\nitro" folder.
The next part will be to set up the Arcturus Morningstar emulator. Which we will cover in the last and final part of this series!
Good job! The next part will be on how to set up:
Java
Arcturus Emulator
Nitro v2 (latest as of August 2022)
To learn how to do all of the above, head to part 3 of this series, which will be the last and final part
Click here to go to part 3 of the "How to set up a retro (IIS) series
Did I miss anything?
Please let me know if I missed anything, as the guide contains a lot of information.
Credits: Object / Dennis
Last edited:
