[vb_ftp.txt] This extra text to vb_info.txt is important for some (esp. Linux and Unix) platforms and written so as to help tune the file transfer to work if there is anything that doesn't work when the normal instructions in vb_info.txt are followed more or less to the letter. If it turns out that this document, written at the same time, about as the vb_info (this written 13th of feb.,'12) has a validity also many years into the future, -- the same solutions applying there -- we will simply let this document be there, right beside the link to vb_info.txt at the norskesites.org/fic3 and moscowsites.org/fic3 download pages. *** Hi! When we made the vb_info.txt, we made some assumptions as to how to get the FTP file transfer to work. It turns out that for some platforms, the VirtualBox.org is implemented so that a slight but acceptable modification has to be done relative to what we said in the vb_info.txt on how to get the file transfer flowing smoothly in and out of the vb. If you have a VirtualBox program that, when you follow the instructions in vb_info to change the vb SETTINGS -> NETWORK and set it as said there, namely to HOST-ONLY ADAPTER, then it turns out that on some VirtualBox.org implementations (at present e.g. the Linux Fedora version) it comes up with 'Not selected' any such adapter in the next field. And so this one won't be an acceptable setting for the vb program. What we have got to do then is to do something along these lines, which does work although there may be some tweaks to how you do it on some platforms: First, set SETTINGS -> NETWORK to BRIGDED ADAPTER and watch what it comes up with -- e.g. 'eth0' which may be exactly the internet interface for your PC. Click on Advanced. Be prepared to experiment here if need be, but initially -- IN THIS CASE -- put 'deny' to Promiscuity, at first, anyway. Also, leave the other fields as they are, and just make sure it is clicked on 'Cable connected'. Second, make sure the net is PLUGGED IN, which will matter in some cases, as otherwise the Linux may automatically make this 'eth0' unavailable, even for connections within the computer to it. This may mean turning wireless on, or plugging the physical cable on, and manually also enabling it. You can then later on see if it also works with cable not plugged in. Let it first be plugged in, and let the network connection be real -- test it by going to internet with a browser. The good news is that when using this approach, you can probably, for most machines, let the Firewall be on. (To adjust or check Firewall settings e.g. in Fedora16, type in the word Firewall in the search button when you open up for applications, and have the root password ready.) When you get it to work you maybe want to get into the C:\FDOS\FTPPASS.TXT and set your own proper user id and password since we are going to have a little bit more opening to internet when using this particular way of doing FTP within the PC. At any rate, you should now give it a test. On some PC platforms, reboot the PC after any big change or big software installation to fully get refreshed all drivers. Start up the Vibe F3 and use the menu #3, which is the one you should always use for FTP. Answer 'N' on loading CD, and answer 'N' on loading F3, and then type, as normal for FTP, CD \ FTPSRV and press an extra lineshift. If it reported success when booting the Vibe, then it probably also here will report success. With luck and (in some cases, also) perserverance it will now report 'Good news' on startup, and tell you a number like 10.0.0.nn or 192.nnn.nnn.nn or something like that to be used as address. Make a note of it. The user name is 123456 and password also 123456 before you change it. There are now two possibilities: One, that using a graphical FTP program is possible, and it shows you a filelist. If it doesn't show you a filelist, do not despair in the slightest, as long as it reports /DRIVE_C/ as file directory. First of all, you can still export files INTO the Vibe even if it doesn't show a file-list. Second, you will probably also be able to get files out of it, with ease. Here is now you can do it in most platforms, if it reports contact with /DRIVE_C/ but doesn't give any filelist. On something like Centos Linux, which is very much like Fedora Linux only even more near the original RedHat8.0 standard (a standard which is the R CD-set called 'USB utility partition' in the files at yoga4d.org/download or /downloads, the GNU GPL Open Source platform which became Fedora when Red Hat made the 9.0 and onwards its commercial version of GNU/Linux) you can open a new program named Terminal, in it type the word su for superuser as you always do when doing anything administrative, type your own root password, then type cd /backup1 or something, if you have e.g. TEST1.TXT and wants to try to put it into the Vibe. Then type ftp open 10.0.0.4 or whatever number that you made a note of as the correct number. If all goes well you are then prompted for user name and password. Then type put and you will be prompted for two things, the name of the local file on your surrounding platform, and the name of the new file when it is put into the Vibe F3. The local name can be e.g. TEST1.TXT. The local name is then specified as something which always begins by /DRIVE_C/ and a natural thing to type is /DRIVE_C/BOEHM/BOEHMIAN/ We suppose this works, and you now test getting a file out of just this location. You type get and the local name in this case is e.g. TEST3.TXT while the name in the Vibe can be e.g. /DRIVE_C/BOEHM/BOEHMIAN/MTDOC.TXT which is a large standard manual file. After this, type quit and also, inside the Vibe, you click to activate that frame and press CTR-C (make sure you use left control button), to leave the ftpsrv. You then try to write e.g. TYPE TEST1.TXT and with luck, it is right. You also check if your TEST3.TXT in the surrounding platform is available as it should. ***