Monty and Mpack,
I'm not sure what system the program (Micro Cookbook 5.0) was originally written for but I do remember that when I first tried to install it on my mom's old XP system -- now two generations back -- it wouldn't run until I copied two files (ODBCJT16.DLL and ODFOX16.DLL) into the Windows System library.
That little hack was the product of an Internet search and I and several of my mom's friends are eternally grateful to whomever put it out there.
I'm quite happy keeping the program in a VM. There's no need to hold the future hostage to that old piece of coding and I'd much prefer she have a relatively up-to-date computer. This recipe program is primarily a backup anyway. About 60% of her recipes were entered into another cookbook program about ten years ago (also now defunct; don't get me started) and she just needs this for the other 40%... Really just for reference and, perhaps, the feeling that she hasn't lost anything that was important to her in the past.
Thanks again for your suggestions and advice.
Trip
[Solved] Hiding VirtualBox
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Hiding VirtualBox
MSVCnn is a runtime support library required by applications written in Microsoft Visual C. The nn changes depending on the version of MSVC used. You can almost certainly find the DLL online, then copy it into the program's executable folder, or anywhere else on Windows standard search path - including Windows system folder if you really must, though that can cause problems when different programs expect different versions of that DLL.
Ditto for other missing DLLs.
Ditto for other missing DLLs.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Hiding VirtualBox
A bit of an aside, but can you tell me why a specialist cookbook program was needed?
I keep all my recipes as Excel spreadsheets. They can be easily scaled, and I'm pretty sure Microsoft will still be around in a couple of decades, and still able to read old Excel spreadsheets!
I keep all my recipes as Excel spreadsheets. They can be easily scaled, and I'm pretty sure Microsoft will still be around in a couple of decades, and still able to read old Excel spreadsheets!
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Hiding VirtualBox
RE the MSVCR120.dll error: Mpack mentioned a solution above, and Erdeslawe gave you a link on your post on the VboxVMservice discussion forum, about VC++ Redistrbutable needing to be installed.
You are correct that VboxVMservice will start the VM automatically, and that the tray icon will allow you to manually stop the guest.
See the Virtualbox manual, section 3.6.2, on the Remote Desktop server for your guest. You will need to have the Extension Pack that exactly matches the version number of your Virtualbox installed to get access to the Remote Desktop server. To access the guest settings of a guest that is started by the VboxVMservice, you will have to stop the guest, so you can start it with the main Virtualbox window if you needed to.
Typically the default port that your Virtualbox guest uses for Remote Desktop, port 3389, is the same as the physical Windows host may also use. Pick a different number than any other guests or other remote Desktop PCs you may have. Perhaps 3392 would work.
Now on the host PC go to the Start menu, Windows Accessories, Remote Desktop Connection. In the "Computer:" box enter:
127.0.0.1:3392
127.0.0.1 is the universal "loopback" address for all PCs. It means for the host to look to itself for the port number. The 3392 should be the number you set for the guest. Click Connect to show the guest window. "Show Options" allows you to, among other things, Save As the connection as a file, which you can then make a shortcut to on the desktop or some other convenient place. Opening the shortcut will show the guest window.
You are correct that VboxVMservice will start the VM automatically, and that the tray icon will allow you to manually stop the guest.
See the Virtualbox manual, section 3.6.2, on the Remote Desktop server for your guest. You will need to have the Extension Pack that exactly matches the version number of your Virtualbox installed to get access to the Remote Desktop server. To access the guest settings of a guest that is started by the VboxVMservice, you will have to stop the guest, so you can start it with the main Virtualbox window if you needed to.
Typically the default port that your Virtualbox guest uses for Remote Desktop, port 3389, is the same as the physical Windows host may also use. Pick a different number than any other guests or other remote Desktop PCs you may have. Perhaps 3392 would work.
Now on the host PC go to the Start menu, Windows Accessories, Remote Desktop Connection. In the "Computer:" box enter:
127.0.0.1:3392
127.0.0.1 is the universal "loopback" address for all PCs. It means for the host to look to itself for the port number. The 3392 should be the number you set for the guest. Click Connect to show the guest window. "Show Options" allows you to, among other things, Save As the connection as a file, which you can then make a shortcut to on the desktop or some other convenient place. Opening the shortcut will show the guest window.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Hiding VirtualBox
Just noticed the '16' in the DLL names for the cookbook program - meaning that it is indeed a 16bit (Win3.x) application.Trippp wrote: I do remember that when I first tried to install it on my mom's old XP system -- now two generations back -- it wouldn't run until I copied two files (ODBCJT16.DLL and ODFOX16.DLL) into the Windows System library.
A cookbook app will not have special hardware requirements, so I'm pretty sure this could be made to work directly on any Win32 host which has the NTVDM service (i.e. Win16/Win32 translation layer) enabled.
Re: Hiding VirtualBox
Gentlemen,
We are cooking with fire!! The VM runs, my mom is able to access it with remote desktop, and the cookbook program starts full screen.
I do have a number of small follow-up questions but at the moment I'm rushing to get on the plane to Zurich, where I live, and so will post them later.
In the meantime, I am so grateful for all of your help guiding me through this. Thank you on behalf of my mom and thank you from the bottom of my heart.
Trip
We are cooking with fire!! The VM runs, my mom is able to access it with remote desktop, and the cookbook program starts full screen.
I do have a number of small follow-up questions but at the moment I'm rushing to get on the plane to Zurich, where I live, and so will post them later.
In the meantime, I am so grateful for all of your help guiding me through this. Thank you on behalf of my mom and thank you from the bottom of my heart.
Trip
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Hiding VirtualBox
Glad you're up and running! Have fun.