Search the Community

Hi! Since I could not find any actual (updated) post guiding on how to use the updated loaders for Xpenology, and since I am NOT using Proxmox (I rather not have the overhead and don't need the extra abilities for now), I would like to present to all noobs and Xpenology enthusiasts starting out on this really cool journey, my guide on How-to create a Synology-like NAS machine (First a short-hand version, and after, the full version): Get a Bare metal PC/NAS build. Download your desired Loader. RR/ARPL, and ARC are the common options. Burn the loader onto a fast USB flash drive. Setup your Bare metal PC Bios boot order to load your USB flash drive FIRST. Plug said flash drive into the PC, and boot Select model and version Select and add addons and configure them as necessary Build the loader Boot the loader Enter the DSM via the supplied web IP address And here is for the meat and potatoes of it: You'll need a bare metal setup. You've probably heard the term before, but basically it means a constructed PC, almost any PC, without an operating system installed (so a virgin , one HDD/M2 NVME/SATA NVME storage at the minimum, to install the DSM environment). As for recommendations for what to use? It depends on your requirements really. Synology/Xpenology Machines are quite versatile, especially when you build them on a (more) powerful basis. But the range is Huge. You can get away with an ancient platform such as i7-26xx based PC, or go all the way to 12th-13th-14th gen CPU (although it is less recommended due to compatibility issues and drivers support). The sweet spot, for me, is 7th-9th gen CPU platforms. If you wish to save power, go for a "T" CPU (desktop CPUs with T at the end of the model name, are using much less power. Usually around 35W vs 65W-140W of the more powerful Intel CPUs). Once you have an assembled PC, you can head over (on another PC unless you have a temporary windows installation on the bare metal machine) to download the Loader. The Loader is as it says - a way to load the DSM - which is the Synology Operating system. Nowadays, there are basically two automated loaders (automated as they save you from having to work harder on building your specific loader for your requirements): RR/ARPL, and ARC. Both work in a very similar way that will be explained soon. You go to the releases section on the right of the page, and download the latest version. For instance: arc-24.5.26.img.zip for ARC, or rr-24.5.5.img.zip for RR. Then you will unzip the image from the zip file. you'll get a file with the suffix img. Next, you will need to use a program such as Rufus, or Belena Etcher to "burn" the img file you got, into a USB flash drive. I find Belena Etcher is simpler for that, but Rufus would work just as well. The resulting flash drive will have 3 partitions that may not be read by your windows PC. That's totally normal and fine. It will still work and boot. Do make sure you have at least a 16GB/32GB fast flash drive, as I have heard of slower (USB 2.0) flash drives that will simply not boot properly. Also, remember that the loader runs directly from the flash drive. NOT from your PC hardware. There are some workarounds, but I see no issue in keeping it that way. I simply use a fast tiny drive such as Samsung fit. Turn on your new NAS PC and go into bios (usually it's Del or F1/F2/F12 to enter bios). Then go and find the Boot order and make sure that your USB flash drive is set to boot first. You can disable any other boot drive/network (You will boot from the flash drive in any case for an Xpenology machine). Save the changes in the bios, and shut down. Then, plug in your flash drive if you haven't already, and turn the PC on again. You should get this screen after it boots: If your PC does not have a video card (integrated or discreet), you can still access the output using your network. You will need to find out what IP the machine will use, so you still might need to have a video card just to find that first.. But there are network sniffers out there like wireshark that can also scan your local network and find what new IP connected to it. So, in this example, you can see on the top of the image, a line with some information. When you first boot, this line will be shorter, as no DSM model or version will be selected yet. But once you select a model and version, the information will reflect on that top line. The menu shows you many options. We start with "choose a model": This list is MASSIVE and daunting! So which model should you choose?? Well, that's the million dollar question. If you go to Synology's website you can see all the models and some information about each. They are to match a person's budget and requirements. Some are more for office use and some are even for (up-to) mid-sized companies. There are also NAS models that are meant for video surveillance. Those are usually with "SA" at the start of the model name. Whichever model you choose, you can see some extra text next to it. That indicates the original hardware base used in the actual Synology Device. So, "r1000" for instance indicates AMD based hardware. You can find out more information regarding that here. However, it doesn't really matter. Your hardware may differ A LOT from the original hardware in a Synology machine, but the Xpenology loader you use will bridge any (or at least most) such differences, and allow your machine to work. I did find that some models do work better with my hardware than others, but I can't give you specifics as your hardware may be quite different than mine. After you selected a machine model (move with keyboard arrows and then navigate with tab and click ok), we move to the version selection (on the first screen): Optimally, you will want to select the newest product version (naturally), but if you are using especially old hardware, you might want to opt for an older version. As you can see, with this newest loader version, there are only two options. If you want older ones, you might have to get a older loader to match. Once you select it and click ok, you'll get this screen: and click ok as well. Then you are back again to the main screen. Next go to addons: Here you can select some addons you may want to add before you build your very own loader image. You can see the list by choosing "show all addons" Interesting ones are: hdddb for better compatibility with non listed hard drives and other storage (no parameters needed), cpuinfo for correct showing of your hardware in the DSM control panel info screen (again, no parameters required unless your info is not found correctly or automatically, in which case you can enter it manually), i915le10th which is to allow support for intel integrated graphics solutions (up to and including 10th gen Intel CPUs) - but only on certain models, as not all Synology models support integrated CPUs (they are mostly used for video transcoding), nvmecache which is to allow usage of your M2 NVME to be used as a cache to accelerate read/write speeds (you will need to create a SSD Cache inside your machine for this to work and use SSD advisor), sensors which are to report temperatures of your pc parts (hard drives, CPU, case fan and so on) - from my experience it does work too well, but will give you necessary information regarding your storage temperatures which is VERY important), and last is storagepanel which allows you to change the visible model/size in your DSM. What do I mean? Say you picked a simple DS224+ model which is a modest 2-Bay synology machine, but you are actually running 5 hard drives and one M2 NVME. If you don't make changes under storagepanel, all you'll see is a two bay model in your DSM (you will still be able to use all 5 disks). In order for the DSM interface to reflect your hardware correctly, you will enter the proper choice in parameters (when it is asked when you add this addon). In this case you will put TOWER_5_Bay 1X1 which indicates a similar Synology model, but one with room for 5 disks. It will actually put a photo of such a device for you to see when you log into the DSM. So the first part (TOWER_5_Bay) is to indicate the type of the model (tower) and how many bays. The second part (1X1) indicates how many M2 NVME devices are there. So, if you have two M2 NVME devices, it would be 1X2 instead. However... be mindful that there is a list of possible items that you can put in (other than TOWER_5_Bay and so on), which is (as far as I know): TOWER_4_Bay 1X4 # RACK_0_Bay RACK_2_Bay RACK_4_Bay RACK_8_Bay RACK_10_Bay RACK_12_Bay RACK_10_Bay_2 RACK_16_Bay RACK_20_Bay RACK_24_Bay RACK_60_Bay TOWER_1_Bay TOWER_2_Bay TOWER_4_Bay TOWER_4_Bay_J TOWER_4_Bay_S TOWER_5_Bay TOWER_6_Bay TOWER_8_Bay TOWER_12_Bay This list is actually inside a storagepanel.sh file (a script file) from the loader installation itself. I don't recommend trying values that are not in this list as it may just cause issues. Another thing I noticed is, that if you select a RACK model (such as SA6400 for instance), you can only use a RACK value. It simply won't let you put in another (such as a TOWER value). At least it didn't let me. If you don't change the storagepanel value, you'll get a default picture. Which may be a 24 bay rack.. Okay. So once you have added each of the addons you want, you go back to the main menu, and click on "Build the loader". This will take a while (can be a few minutes at least), once it is done, it will again go back to the main menu, and you can click on "Boot the loader". That will give you a screen where the DSM is booted, and after a minute or two you'll get something like this: This is the Loader boot up screen. As it mentions in the yellow text that will appear after a bit, you will need to go into your DSM interface after a few more minutes via https://x.x.x.x:5000 (where x.x.x.x is your NAS IP address - same as the loader IP address, but on port 5000 rather than on port 7681 as the loader) I hope you find it useful and easier to install the new loaders with this guide. I wish I had one like this to avoid some of the pitfalls along the way. Cheers!

Hey, been lurking that forum for a while.....red almost all topics regarding "how to install".....but to no avail! I am unable to set up Xpenology on my HP. I was experimenting with almost all DS3615xs loaders (Juns versions)....1.03b, 1.02......tried 6.2.3, 6.2 to 6.1.7 <----- the most bullet proof version.....as said on this forum! DS3615xs......since I have i3 550 processor and it seems to be the closest to my setup (regarding Synology specs) My motherboard is MS 7613 v1.1 : https://support.hp.com/id-en/document/c02014355 My setup: 4Gb of RAM i3 550 Realtek RTL8111DL Lan card (NIC) I have no problems with how to make bootable loader.....got into GUI every time......find synology finds my "server"......but after I upload *.pat image and "server" reboots I get blinking cursor. I came the longest with DSM 5.2 loader.....server was operational...came into its interface....could set up its discs etc...till its first reboot Than blank screen again. I dont know anymore what to do (beside switching back on OMV). I did not experiment with any extra.izma etc..., dont even know if I need it? Is my HP cursed one? One of those PCs which refuse to cooperate no matter what you throw at them? Or am I "missing" something in a process? Many thanks!

***For experienced individuals comfortable with synology and linux command line, I take no responsibility for any issues encountered*** ***Read fully before considering*** Please read all necessary documentation for setting up Xpenology before reading this guide. Try the start-here guides below: https://xpenology.com/forum/forum/83-faq-start-here/ This guide docuements the process of using Linux to modify the synoboot.img for your environment and writing to a usb hard drive. Additonally, this guide shows the upgrade process from 6.1.7 to 6.2.2 with extra drivers (extra.lzma file), your use case my not have the same requirements, so please make you know the process for your environment regardless of the directions shown here. Collect required files ***this guide is using synology model 3617, adjust accordingly for the model you want to use*** Recommended to save your files to a unique folder on your system, in this example we will use folder "xpenology-3716-20200215" (model and timestamp) Download the 6.2 boot loader from this post: https://xpenology.com/forum/topic/12952-dsm-62-loader/ Downloaded extra drivers files from this post (this post also includes links to the synology pat file as well): ***Extra Drivers are only needed if your devices are not supported by the current boot loader files*** https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ Download the synology pat file (from the post above) Extact files for modifications Extract synoboot zip file unzip synoboot_3617.zip -d synoboot Extract extra drivers zip file unzip extra3517_v0.5_test.zip -d extra_lzma Extract Synology DSM pat file ***Requires 7zip*** Install 7zip for your linux distribution (example shown is Ubuntu) sudo apt install p7zip-full p7zip-rar Use 7zip to extract pat file 7z -odsm x DSM_DS3617xs_24922.pat Your folder should now have 3 new folders within as shown ls -1 Output: dsm <--- new folder DSM_DS3617xs_24922.pat extra3617_v0.5_test.zip extra_lzma <--- new folder synoboot <--- new folder synoboot_3617.zip Create mount folders to modify synoboot.img files make these folders to mount the partitions of the synoboot.img for editing mkdir usb mkdir usb/part1 mkdir usb/part2 mkdir usb/part3 Mount synoboot.img partitions First view the partition layout of the synoboot.img for mounting information fdisk -l synoboot/ds3617_6.2/synoboot.img Output: Disk synoboot/ds3617_6.2/synoboot.img: 50 MiB, 52428800 bytes, 102400 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: B3CAAA25-3CA1-48FA-A5B6-105ADDE4793F Device Start End Sectors Size Type synoboot/ds3617_6.2/synoboot.img1 2048 32767 30720 15M EFI System synoboot/ds3617_6.2/synoboot.img2 32768 94207 61440 30M Linux filesystem synoboot/ds3617_6.2/synoboot.img3 94208 102366 8159 4M BIOS boot Important mounting information Units byte size: here its 512 bytes Start byte for each partition: to mount these partitions you need to multiply the start byte by the unit byte size for the offset Mount partition 1 (we use bash arithmetic expansion to multiple the offset) sudo mount -o loop,offset=$((512*2048)) synoboot/ds3617_6.2/synoboot.img usb/part1 Mount partition 2 sudo mount -o loop,offset=$((512*32768)) synoboot/ds3617_6.2/synoboot.img usb/part2 Mount partition 3 ***This partition does not get modified and does not need to be mounted, but shown for those interested in looking at the contents*** sudo mount -o loop,offset=$((512*94208)) synoboot/ds3617_6.2/synoboot.img usb/part3 Collect required hardware information for modifying grub.cfg in partition 1 Get USB vid/pid information ***Run this command before plugging in your usb drive*** lsusb Output: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2c07 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Plugin your USB drive and run lsusb again to see the new device (comparing the two outputs makes this easier to know which drive is the USB) Output: Bus 002 Device 009: ID 0781:5583 SanDisk Corp. <--- new drive Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2c07 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Our USB VID is 0781 Our USB PID is 5583 Get Network Interface Card (NIC) MAC address Find MAC address of NIC on your synology device (can be found in bios, use a bootable usb linux distribution, or physical nic mac information on card label if available) Our MAC was in the bios of our motherboard, it is 90:2B:34:AC:9F:C4 If you have access to your device through cli you can use ifconfig to find the MAC address as well Get Synology Serial Number Generate a serial number for the model being used or use existing if your device is being upgraded (https://xpenogen.github.io/serial_generator/index.html) Our Serial Generated is 1130ODN024917 (Note these are not official synology serial numbers) We will use these values for modifying grub.cfg on partition 1 Modify grub.cfg on partition 1 ***VIM is the editor used to modify files, please ensure you are familiar with the editor you choose*** Edit grub.cfg sudo vi usb/part1/grub/grub.cfg Modify the following lines (Shift+i to go into insert mode in VIM) set vid=0x0781 <--- Our VID found earlier set pid=0x5583 <--- Our PID found earlier set sn=1330NZN022235 <--- Our Serial Number generated earlier set mac1=902B34AC9FC4 <--- Our NIC MAC address found earlier ***You may want to modify SataPortMap for your environment and timeout if you want a faster boot time when grub loads*** Save changes (Hit escape a few times) :wq (write and quit) Add extra driver files (optional) to partition 2 ***Only needed if you require extra drivers*** List current files in partition 2 to view permissions and ownership ls -la usb/part2/ Output: total 11068 drwxr-xr-x 2 root root 16384 Dec 31 1969 ./ drwxrwxr-x 3 user user 4096 Feb 16 09:46 ../ -rwxr-xr-x 1 root root 1860613 Aug 1 2018 extra.lzma* -rwxr-xr-x 1 root root 6441636 Aug 1 2018 rd.gz* -rwxr-xr-x 1 root root 3006864 Aug 1 2018 zImage* Copy extra.lzma file to partition 2 sudo cp extra_lzma/extra.lzma usb/part2/ sudo cp dsm/rd.gz usb/part2/ sudo cp dsm/zImage usb/part2/ List files in partition 2 to view permissions and ownership after copy ls -la usb/part2/ Output: total 13748 drwxr-xr-x 2 root root 16384 Dec 31 1969 ./ drwxrwxr-x 3 user user 4096 Feb 16 09:46 ../ -rwxr-xr-x 1 root root 4570532 Feb 16 09:55 extra.lzma* -rwxr-xr-x 1 root root 6465192 Feb 16 09:58 rd.gz* -rwxr-xr-x 1 root root 3019392 Feb 16 09:58 zImage* Each file should retain root ownership and permissions, the files copied should have a different size and date stamp Unmount partitions sudo umount usb/part1/ sudo umount usb/part2/ sudo umount usb/part3/ confirm each partition is unmounted ls -la usb/part1/ ls -la usb/part2/ ls -la usb/part3/ Output: total 8 drwxrwxr-x 2 user user 4096 Feb 16 09:46 ./ drwxrwxr-x 3 user user 4096 Feb 16 09:46 ../ Find USB device name Ensure USB drive is unplugged ls -1 /dev/sd* Output: /dev/sda /dev/sda1 This shows the existing storage devices, sda is the drive (my laptop root hdd), sda1 is the first partition Plug in your USB drive ls -1 /dev/sd* Output: /dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdb3 You may not see the same partitions, but you want to see the additional device (sdb) showing Format USB drive ***Please backup any data you want to retain from this drive, as it will be lost*** ***Commands shown here are potentially dangerous, make sure you know the correct drives to format and double check your syntax (or use an alternative tool within your comfort level)*** Unmount any partitions that may have auto mounted (example shown here attempts to unmount any drives listed for the USB drive device sdb) sudo umount /dev/sdb1 sudo umount /dev/sdb2 sudo umount /dev/sdb3 Wipe all filesystems off existing drive sudo wipefs --all /dev/sdb Output: /dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 /dev/sdb: 8 bytes were erased at offset 0xe51fffe00 (gpt): 45 46 49 20 50 41 52 54 /dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa /dev/sdb: calling ioctl to re-read partition table: Success Check USB drive layout sudo fdisk -l /dev/sdb Output: Disk /dev/sdb: 57.3 GiB, 61505273856 bytes, 120127488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Confirm clean output without any partitions remaining Write Synoboot Image to USB drive ***Commands shown here are potentially dangerous, make sure you know the correct drives to write to and double check your syntax*** sudo dd if=synoboot/ds3617_6.2/synoboot.img of=/dev/sdb bs=512 Output: 102400+0 records in 102400+0 records out 52428800 bytes (52 MB, 50 MiB) copied, 9.14248 s, 5.7 MB/s Check drive and partition information to ensure it was written correctly sudo fdisk -l /dev/sdb Output: GPT PMBR size mismatch (102399 != 120127487) will be corrected by w(rite). <--- this can be ignored, it alerts because fdisk does not support GPT partitions Disk /dev/sdb: 57.3 GiB, 61505273856 bytes, 120127488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: B3CAAA25-3CA1-48FA-A5B6-105ADDE4793F Device Start End Sectors Size Type /dev/sdb1 2048 32767 30720 15M EFI System /dev/sdb2 32768 94207 61440 30M Linux filesystem /dev/sdb3 94208 102366 8159 4M BIOS boot Unmount and plug into your Xpenology device sudo umount /dev/sdb1 sudo umount /dev/sdb2 sudo umount /dev/sdb3 Last minute changes after write You can still make changes to the paritions/files on the USB drive by mounting the partition on your system sudo mount /dev/sdb1 usb/part1 sudo mount /dev/sdb2 usb/part2 sudo mount /dev/sdb3 usb/part3 This mounts the usb drive directly to the folder specified, you can edit files as per previous steps in the guide

Hi all, I'm trying to setup a server. I have connected my usb and power on the computer. I can see the balck screen which shows that all is OK but when I run the assistan from other computer, I can't see the diskstation and if I go into muy router, I don't see the computer connected. I have a motherboard AsRock 775-Dual Vsta with a VIA PHY VT6103 ethernet. Could the problem be an incopatibility with this card?

So, here we go: another Noobie, another set of questions! First: I'm so grateful people are doing this XPEnology thing, this is just great. Great for user having leftover hardware or can not afford Synology Hardware. Also great for Synology promoting their Software, maybe gathering future DS users. Thanks. Thanks a lot! *deep and slow bow* Now to me: Quite normal PC user, Gamer, having build silent/watercooled PCs for over 15 years, nothing fancy, still fascinated by PC Hardware, although now getting a bit tired of the hobby. Always more Hardware than Software Guy. English is not my native tongue, so please excuse any glitches in my writing. My Hardware: I'm runnning a HP N54L since a few years, 4 disks as of now (2x2GB + 2x3GB slow eco HDDs, non NAS, both couples as Raid1 for redundancy), 8GB ECC RAM and the Intel Gigabit NIC (is that right? NIC? the networkcard?), upgraded with a fanless power supply and a slowed down Noiseblocker 140mm Fan. For a while running Windows Home Server 2011, than switched to FreeNAS. Ever since I feel FreeNAS is not really what I'd call accessible. FreeNAS gave me quite a lot trouble with access rights and is hard to master when you only access it once or twice a year for checkup or when something is wrong. Hence my intention to use DSM. I only need a stable NAS to backup all PC in the household via Acronis, store a few things and have kind of a shared or exchange folder. No streaming, no multimedia, no cloud or anything else. (Maybe a mail server in the future... if feasable) I just need NAS in it's purest form, no bells and whistles, easily handled and stable. So, this weekend I'm gonna give it a try and have some questions beforehand. Of course I'd like somebody to take my hand and guide me through everything, taylored to my specific case, but I'm not gonna get that. It's ridiculous, I know that. So I just would like to ask you guys if got everything right so far, ok? So could someone please confirm or answer to the following: There are obviously 2 ways to get DSM on any hardware: having a VM in which it runs (that's this EXSI thingy, right?), basically emulating suitable hardware, emulating a Synology DS? having a simple Bootloader running from USB stick, which just makes DSM start on non Synology Hardware, you called that "bare metal", right? This thing provides the drivers needed for the "Alien Hardware", correct? I'd like to go for the "bare metal" solution, as VM is overkill for me, so this Bootloader would start DSM, which is installed on my Drive array. Is there any way to have DSM not on the Drive array but on, say a little SSD or 2.5" HDD? Does that would even make any sense? Performance wise? Or for the integrity of the Data on the array? The N54L is obviously very commonly used with XPEnology but seemed to have trouble getting the latest DSM versions and with the WPA/WPA2 breach I'd like to make sure that it's possible to update to the latest version as Synology just fixed the issue (like 2 Days or so ago) --> I've seen people confirming latest update on N54L, but how? Which loader are they using? The N54L had no Wake on LAN, hence I bought the Intel NIC which added that but never got it working under FreeNAS. There is the compplexity of FreeNAS again... gave up, NAS was always on ever since. Is Wake on LAN possible with DSM and the onboard LAN? Do I still need the Intel NIC? Will my N54L finally work like supposed to concerning going to sleep and wake up if there is Network activity? What happens when the DSM gets somehow corrupted? Is all Data lost or can it be extracted after DSM reinstall? It's certainly not as handy as a Windows PC after crash, where the data would still be available if plugged in another system, or is it? Does the hardware of the N54L provide any benefit over the rather lowish Hardware of the Synology DSs available to by? Or is it a waste? Thinking of buying a proper DS in the future and selling the N54L, lowering space and energy usage Finally: I've heared of encryption in the commercial talk of synology. Is that done via the DSM software or rather a hardware feature of their processors used? Hence: is encryption available for XPEnology users? Oh and were to get the latest Bootloader & XPEnology version for the N54L? I can certainly find something but whats the best / most trusted source in your opinion? I guess these are my most pressing questions, no doubt to be followed up by some more if installation is not a breeze like in all the youtube tutorials. And it never is, is it? Thanks in advance for any answers, looking forward to make use of the community power here! Cheers, Myrixamophit