Ok msxvr here are my questions:
1. How will we be able to update MSXVR, is there an online update mechanism or do we need to remove the sd-card and write a new image?
2. I read the sd-card is ‘internal’ so can it even be removed without opening the case (which would break the warranty).
3. Will the network connection be available to the MSX? through UNAPI? Or is it only available through emulated ObsoNet like in the HispaMSX BBS video?
4. In tour videos I see that MSXVR in MSX mode extends the border to fill the 16:9 screen whilst maintaining aspect ratio in the main part. It is visible as a typical dark blue, light blue combo (aka color 15,4,7) is shown. Then there is a lot of light blue in the screen. Personally I would prefer it if those borders were black. Make it look more like a real MSX in a 4:3 screen would look like). Is that going to be an option?
5. Talking abou screens and resolution. What resolutions will VROS support (I have a 2560x1440 screen for example) and can will we be able to adjust how VROS is shown size wise. So I mean will it support scaling like MacOS or Windows? If it uses fixed sizes for menu fonts, buttons etc. it can become unreadable on high resolution screens.
6. How is scaling of the MSX display achieved? Is it comparable to ‘Simple’ scaler in openMSX? Are different schakers available (personally I prefer Simple though).
7. On the point of storage, will MSX part of MSXVR have Nextor kernel and van we assign one or multiple partitions to the MSX from the sd-card? Or is there maybe a second sd-card slot? Or do we go through an emulated SD cartridge as with ObsoNET?
Well that’s it for now. One last note. I hope in these days you still find time for yourself and your family and friends! This may all seem very important to us here on MRC but it is a hobby 
I for one will enjoy this product for sure. The curiosity we are observing here (my questions included) are just our minds being so anxious to get our hands on the real deal!
On which API is the emulator running?
Emulator is running in a C++ engine. This engine was started in 1998 by me. It is multiplatform. Raspberry Layer - Graphics: OpenGL, Sound: OpenAL/ALSA.
Why is there a 12v 10A psu?
RPI3B+ is very restrictive with amperage. We have 4 usb ports. We have cartridge slots that can support other protocols like I2C and USB too. We have the DB37 I/O interface. We can NOT be tight fisted with the power supply.
How do the vrdos and vrbasic books and service manuals look like? Are they finished?
At this moment this books/manual are not printed so I can’t take photos. All them are A5 books. They are at this moment is Spanish. Service manual will be the first to be translated to English. VR-BASIC has currently 262 pages (90%). VR-DOS has 118 pages (60%). VR-SCRIPT has only some pages and a huge index to be completed (1%), SERVICE MANUAL has 60 pages and I don’t think the completed version will have more than 100. This Service Manual shows the user how to keep in good condition the computer, warnings & guarantee, elements of the computer and an introduction of several parts of the software/features on this machine.
NOTE: Books (VR-BASIC, VR-DOS, VR-SCRIPT) are an extra ítem that we would want to offer next year, so, they are not our priority now because they won’t be included in the computer package. Is not the case of the SERVICE MANUAL, that it has high priority.
How does the packaging looks like? Is it finished?
Packaging desing yes. It is like the web picture. Real packaging no. We need to buy the cardboard box die (“troquel” in spanish). The box it has a style like this one:
But of course without animals and full coloured like the MSXVR web site picture ????
We are looking too how to protect this packaging in the shipping. It is important to use protect all the packaging to give a positive/happy experience to all the users.
Can we get images and videos of the internal hardware? I believe tomorrow this will happen Smile
This PCB is the last revision. We will need another one. Final PCB will be color Black. This PCB has arrived this morning and needs a little soldering work. When we will have all ready, I will update the image.
Is all the promised software in release candidate phase?
About software. We have done a lot of things but there are some things better finished/tested than others. We can consider that we have some apps in release candidate and other ones in beta.
To us the most important apps that should work in the initial STAGE are: VR-OS and system tools, VR-DOS, VR-BASIC, VR-SCRIPT.
So, computer must be operative, safe and give full MSX operatibility. To explain al the software/tools and his status, I will need to create a list and estimate a % to be RC. I will prepare it, give me some days, please.
What about boot time?
Currently is 14 seconds .. since you press POWER ON Button until you can write in the VR-DOS.
We can improve this time, but really, is not our priority. One time the computer is ON, you don’t need to worry about this anymore and sincereslly, this time is really nothing.
How will we be able to update MSXVR, is there an online update mechanism or do we need to remove the sd-card and write a new image?
The system update is just pressing a UI button or using a VR-DOS command. Of course, you can DOWNLOAD the last image file and burn it, but this is not necessary. If you corrupt your SD or similar, you can create another SD with the image file. If you don’t want or you don’t know how to do this things, we will offer SD’s with an image included.
I read the sd-card is ‘internal’ so can it even be removed without opening the case (which would break the warranty).
Yes. SD card connector is in the back of the computer. You can extract/put SDs without problems and you don't need to break the warranty.
Will the network connection be available to the MSX? through UNAPI? Or is it only available through emulated ObsoNet like in the HispaMSX BBS video?
At this moment only OBSONET was implemented. The RTL8019 emulation is not perfect but it works more or less correctly, so you can use INTERNESTOR LITE / UNAPI tools like you can see in the video to use Network connection in your MSX Virtualized machine.
In tour videos I see that MSXVR in MSX mode extends the border to fill the 16:9 screen whilst maintaining aspect ratio in the main part. It is visible as a typical dark blue, light blue combo (aka color 15,4,7) is shown. Then there is a lot of light blue in the screen. Personally I would prefer it if those borders were black. Make it look more like a real MSX in a 4:3 screen would look like). Is that going to be an option?
Yes. You can configure that. In fact, that color is the “border” screen, but we can force a fixed border color (I will add this to the TODO list). You can modify by default what video aspect that you want, at this moment: 1x, 2x, 3x, ORIGINAL, EXPANDED
Talking abou screens and resolution. What resolutions will VROS support (I have a 2560x1440 screen for example) and can will we be able to adjust how VROS is shown size wise. So I mean will it support scaling like MacOS or Windows? If it uses fixed sizes for menu fonts, buttons etc. it can become unreadable on high resolution screens.
You have a lot of choices available, until 1920x1080. But is not convenient due to the huge use of the VRAM, but! You can. We recommend (by default) the 800x600. Of course, if you choose 1920x1080, you will see all very little.
How is scaling of the MSX display achieved? Is it comparable to ‘Simple’ scaler in openMSX? Are different schakers available (personally I prefer Simple though).
You have: 1x, 2x, 3x, ORIGINAL and EXPANDED. ORIGINAL is trying to adapt maximal possible without lose the aspect ratio. EXPANDED use all your monitor resolution. Adding this, you have an scaline filter (shaders) configurable to have a better retro experiencie in HDMI monitors.
On the point of storage, will MSX part of MSXVR have Nextor kernel and van we assign one or multiple partitions to the MSX from the sd-card? Or is there maybe a second sd-card slot? Or do we go through an emulated SD cartridge as with ObsoNET?
You can share one of the MSXVR drives in a MSX Virtualized machine. This can be possible using a driver device called “VRTunnel”
VRTunnel capture MSXDOS/MSXBASIC/NEXTOR calls and creates a fake to serve the new VR Drives, so, you can have FAT32 in the MSXDOS or NEXTOR, for example.
You can share drive folders, if you share a root folder, you will have all the drive available.
You can map this drive folder in the MSXDOS as a drive from A: to H:
NOTE: "VRTunnel" is in BETA but it is working pretty well.
That only happens on keyboards without anti-ghosting. In mechanical keyboards I think it doesn't happen. But maybe the developer can confirm It 
Actually, the ghosting happens because of the keyboard matrix. Since on a membrane keyboard part of the matrix is usually on the membrane itself to save costs, they are more prone to ghosting. In a real typical MSX you can easily short the matrix's lines and rows and get four characters by pressing three keys (kind of the reverse of what happens with PC keyboards, when no keys are registered at all, or only the first two), for example. I hope the developer will shine more light into this question.
