Tips, Tricks and other hacks

How to get root access

Follow the steps below, known to work on Receptor 1 and 2 – uncertain on Qu4ttro, Trio or VIP *

1. Connect a monitor and keyboard to your Receptor
2. Start your Receptor and interrupt the Grub bootloader by pressing the ‘e’ key as it shows up, may need to hit F2 to get to see it.
3. When in edit mode, add the number ‘1’ after the kernel line, and press enter. The line should then read something like this

   kernel /vmlinuz ro root=/dev/hda2 vga=0x317 splash=silent 1

   Then press enter to drop to a command line

4. Press ‘b’ to boot the selected and modified line – don’t worry this is just a once off.
5. When the system is booted, you are now logged in as root, and you can change the by typing “passwd” and entering password twice. Note this down or as I have done, used a marker to write the password on the internal lid of the Receptor in case ever forget it!

How do I enable SSH?

As per default the system comes with root logins disabled. Since OS 1.6 on the Receptor sshd is disabled by default. To enable it run:

• chkconfig --add sshd

This is of course best done right after getting root access per above and only need to do once. Once you have enabled this you can use any SSH client (recommend PuTTY for Windows Clients) to remote into the Receptor and navigate the file system, with extreme care!!! You can also use a client such as WinSCP to navigate via a GUI.

SMB Access issues

 Modern operating systems, such as Windows 10, Windows 11, and recent versions of Linux, disable SMB1 by default to protect against vulnerabilities like WannaCry and other ransomware attacks. This sometimes stops the file share part of the Receptor to stop working.

Enable SMBv1 on Windows 10/11 via Control Panel

On a Windows 10/11 device, Press Win + R to open the Run dialog box. Type ‘control‘ and press the enter key to launch the Control Panel. In the Control Panel, select the Programs and Features menu. Now select ‘Turn Windows features on or off‘.

Scroll down the list of features until you find SMB 1.0/CIFS File Sharing Support. To enable SMB1, check the box next to SMB 1.0/CIFS Client. For enabling SMB1 on Windows servers, check the box next to SMB 1.0/CIFS Server. Click OK.

Known Passwords

VNC Passwords - typically Receptor or receptor
BIOS Password - if a password is set, it is often MUSE123
SSH Password - per above - you set this :)

Q: What motherboard is in my Receptor?

A:This is kind of hard to answer. I know for a fact that Muse have used serveral different brands of motherboards. In my Receptor, I have a slightly modified version of Asus A7V8MX-SE from around 2003. The difference between the “original” A7V8MX-SE and the one in my Receptor is that Muse (i guess it’them, because the soldering looked hand made) have removed (soldered away) the LPT port and Audio connectors for the integrated soundcard. The COM port is also removed. But not completely. Just soldered loose and it currently runs the LCD of the Receptor (I think, didn’t pay that much attention to it). If anyone needs the manual, look here.

Another motherboard that I think they have used is a version of FIC AM37. Both of these boards, the Asus one and the FIC one is kind of hard to get information about. This is just an educated guess thou (by snooping around the filesystem and it’s rc scripts).

Q: What is the BIOS password? / How do I reset it?

I’m not sure that the password is the same for every revision of the Receptor. But I at least know the password for my Receptor, and another one. If you want to know, you’ll have to ask Muse about it (or beg me ;).

When I get some spare time I’ll write down every setting in my BIOS to have in case of a battery faliure or something. I’m sure there’s nothing special about the settings, but it can be useful information to have in hand in case of an emergency.

For now, I can quote the section about this from my motherboard (ASUS A7V8X-SE) manual:

If you forget your password, you can clear it by erasing the CMOS Real Time Clock (RTC) RAM. The RAM data containing the password information is popwered by the onboard button cell battery. If you need to erase the CMOS RAM, unplug all the power cables and remove the button cell battery. Reinstall the battery after about 2 seconds, then power up the system. Refer to section “1.11 Switch and Jumpers – Clear RTC RAM” on how to erase CMOS RTC RAM.

Of course, the procedure is different if you don’t have an ASUS board. I know FIC boards have a jumper that is named CLR PASWD or similar somwhere on the motherboard. Just short circuit that one and boot up and you should get in.

Q: How do I enable regedit? *** TBC

A:First off you need root access and be able to edit a file under Linux. After you’ve mastered that, add the following line into the file /etc/sysconfig/receptor.

  export MUSE_PROVIDE_REGEDIT=1

Then restart the Receptor GUI either by running “restart-receptor” at the command prompt, pressing ALT-F4 in the Receptor Remote application or simply tripple-click the power button..

After this you should have a menu item that says “Run Regedit – ADVANCED” option under the Plugin Tools button on the Setup page.

Q: How do I install a plugin that the Receptor REJECTS?

I got this idea when reading about a failed installation attempt of EVE 2 on the Receptor forums. This is just an idea but it may actually work.

As far as I know, and have read, the Receptor keep a list with uniqe VST Id:s. So, whenever you try to install an unsupported plugin that shares the same ID as a supported one, you’ll run into problems. The receptor will simply reject the install. You’d see something like this in your system log:

    May 20 15:32:16 receptor rm-host: HostPluginList.cpp::AddDescription[1147]: REJECTED: NONAMEPLUGIN

This is actually pretty easy to circumvent. The solution is to make up an uniqe ID and tell the Receptor to use this ID instead of the original one. Here’s how to do that.

Create a NONAMEPLUGIN-custom-info.xml similar to this one. (The reason I linked to this file instead of including it in the HTML is because I’m one of the “lazy” programmers I mention below =D).

The most important parameter is uniqueID. Change this to whatever (I figure the higher number the better but you’ll have to try yourself).

The other paramters I have there is vst-plugin-name, this one can be useful to change also if you have a lazy programmer that haven’t changed the name of the VST even if it’s a new version. If you change this, you won’t end up with a duplicate listing in the Plugin list on the Receptor.

vst-plugin-vendor can also be good to change. As far as I know, this is what the Receptor goes by when you create patches. So, if you have NONAMEPLUGIN Vendor there, the patches will end up in /c/Banks and Patches/NONAMEPLUGIN Vendor/NONAMEPLUGIN/. Nice and tidy. (I’ve seen some plugin vendors that have names like “ooo.i.make.plugins.and.have.a.homepage.com” sort of name in the vendor tag, which in the long run just is irritating.

Anywhoo. After you’ve created the custom xml file, refresh the plugin cache by holding down the Multi button and tripple-click the power button. Then remove any .NONAMEPLUGIN-sign.xml, .NONAMEPLUGIN-muse-lock.xml and NONAMEPLUGIN-info-cache.xml that were created when you failed to install the first time. After that, just hit the install button and hope it’ll work.

** Parts of this borrowed from here – https://web.archive.org/web/20130408060400/http://ogg.kicks-ass.net/receptor/ – so respect to Olle Gustafsson and Kermit Jagger