|
Well done
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
It appears we need a detailed explanation! 
|
|
|
|
|
Is preoccupied an indicator for taking the first letter(s)?
|
|
|
|
|
I thought the "preoccupied with detail" gave "anal" (as it were) and was a bit confused that the "B" must then lead to book ...
|
|
|
|
|
To be honest I got the last four letters, and got "banal" from that. I didn't worry about the "B" because I wasn't going to give a "full explanation" for that one!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
Maybe it's that a book would be considered pretty boring if you were only allowed to use the letter "B" when writing it.
Can you tell I'm grasping? 
|
|
|
|
|
Can I get some ideas from the folks around here who have...
- Used all four of these...
As of this moment, I am unable to get Windows and FreeDOS to share files in this arrangement...
- Start with Windows
- Open and run Oracle VirtualBox
- From within VirtualBox, start and run FreeDOS
There is supposed to be some way to share files between the "Host" (i.e., Windows) and the "Guest" (in this case, FreeDOS).
Google search produces the expected SEO-Induced obfuscation
YouTube search produces vid clips of guys who talk so fast and click so fast that I can't follow a thing they're doing, and I suspect that they don't ever attempt to share files in the first place.
And, moderators, as always, if this topic belongs elsewhere on CodeProject, point me there and I'll take it all over there with me. (My initial search for this topic produced a couple of tangential hits on related topics, but nothing that answers this specific question)
|
|
|
|
|
I used VirtualBox a lot... It has an option to setup file sharing (folder that is) between host and guest... In the settings of the VM under Shared Folders
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Yes, I am aware that...
Kornfeld Eliyahu Peter wrote: "...It has an option to setup file sharing (folder that is) between host and guest... In the settings of the VM under Shared Folders
After something like nine or ten attempts to figure that out, I'm now searching for a video or website that explains what to click, and what to put in the fields, in what order, to make that happen.
I click
I put in the path
Supposedly, Virtual Box has assigned my path (i.e., the actual physical drive which windows sees)...
C:\A\Fake-Drive-G
...To (Virtual) Drive...
G:
Once in FreeDOS, I have no "G:" drive.
I'm trying to figure out what I did, or didn't do, to screw all this up.
Everything else is working quite well on all facets.
|
|
|
|
|
C-P-User-3 wrote: Supposedly, Virtual Box has assigned my path (i.e., the actual physical drive which windows sees)...
that's the error.
That path is only internal. Every virtualization will map the drive on its own. So you need to add the "Fake-Drive-G" folder in each virtual machine independently and drive letters might be different.
They might even change if you don't have the drives "always enabled" and connect other devices before activating the shared folder, because almost all map it as a "network" drive and if the letter is already being used gets another one. At least it has happened to me before in old VMWare virtualizations.
In VMWare you might address the shared folders as a net device too. I mean...
\\vm-ware-host\shared folders\fake-drive-g
\\vm-ware-host\shared folders\optional-second-share
Those should be more consistent that the drive letters
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
modified 21-Jul-21 3:46am.
|
|
|
|
|
Okay, so can you tell me ?...
- What button(s) to click
- Where to put those strings of bytes
- How to make that a permanent part of future startups
- The proper order in which to do that
|
|
|
|
|
With FreeDos... sorry but no idea, never used it.
I have used VirtualBox for a while some years ago, not sure how actual my knowledge would be with it.
I regularly use VMWare (VMPlayer for private use free) and it is pretty easy to use. I could guide you here, although I don't you would need a lot of help as it is quite intuitive.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I am failing with VirtualBox
Has anyone had any success trying this with Bochs under Windows ?
|
|
|
|
|
According to the VirtualBox manual:
Shared folders are supported with Windows 2000 or later, Linux, and Oracle Solaris guests
Additionally, you need to install VirtualBox Guest Additions to the guest OS. It looks like there's no chance for shared folders to work with FreeDOS.
|
|
|
|
|
markkuk wrote: It looks like there's no chance for shared folders to work with FreeDOS.
Shared Folders in the guest are implemented using the HGCM API of the VirtualBox Guest device, which looks to the guest OS like a PCI device, which VirtualBox emulates. The guest would have a device driver for this PCI device, which then exposes the various VirtualBox features to the guest OS.
That is very useful to have, as it not only provides shared folders, but shared clipboard, screen resize, host mouse integration, etc.
I've unofficially implemented a basic Shared Folders and Shared Clipboard VxD driver for Windows 9x, and in time I could implement it on DOS as well. Would anyone be willing to contribute to or fund such development?
Another option is to implement file sharing for FreeDOS using some network filesystem instead, such as SMB/CIFS, see: Configuring FreeDOS to Access a Samba Share - SambaWiki[^]
|
|
|
|
|
Excellent reply, and more detailed than I would have been able to supply.
Software Zen: delete this;
|
|
|
|
|
I am sharing files with windows 7 (guest) and windows 10 (Host). but it does require the virtualbox guest additions. I'm sure Freedos doesn't have guest additions.
And not really an answer to your question, but.....
Under Windows 10 you can mount certain virtual disk files as a disk. I think a VDK and maybe a VMDK files are mountable. I don't think VDI is.
Search for mounting virtual disk under windows 10. All this really allows as long as freedos uses a disk format that windows recognizes (fat, ntfs) you should be able to find the files and copy them off.
Again doesn't help for just transferring files on demand, but you might be able to recover files this way.
Jack of all trades, master of none, though often times better than master of one.
|
|
|
|
|
I do this with MANY vms. I actually mount my D: as the source code
and my VM contains my DEV Environments.
Here is the configuration screenshot:
ScreenShot
So, inside this vm, my hosts C:\TEMP is mapped to the Z: inside the vm.
I think this is exactly what you want.
I only have bridge network enabled, but I don't think it's required.
|
|
|
|
|
To follow up on an earlier reply… if FreeDOS supports \server\share, then just create a new share on the folder you want in the host OS and mount it as a network drive in FreeDOS
|
|
|
|
|
I always use the share capabilities of the guest OS, not the share capabilities of the virtual host.
In my case, I actually have a dell blade server, with 4 blades in all running Hyper-V 2019, so spinning up a VM is almost effortless, but it doesn't matter what your VM host is, Hyper-V, Bochs or anything else.
If I spin up a windows guest, one of the first things I do is make sure that the windows workgroup name matches the rest of my network, you can get to your network name by right clicking mycomputer, clicking on properties then "change settings" in the "Computer Name, domain and workgroup" settings
In my case, my "WORKGROUP" name is set to a specific name, and that name is set to match on every machine in the network, VM or otherwise, you don't need an active directory server or anything to do this.
When you click "Change Settings" a dialog will open, click the grey change button on that and you will see another dialog with computer name in and a choice of "domain" or "workgroup", if your NOT using active directory, then make sure you select "Workgroup" and pick a unique name then click OK.
REMEMBER the name you used.
You will be asked to reboot your PC etc.
Once you restart, do the same with the normal PC that your running your virtual host on, make sure you use the same name.
If your virtual machines are running Linux, then look in the folder "/etc/samba" after first making sure you have samba installed, and find the main samba.conf file, in the file look for the workgroup name option and set that name to be the same as the WORKGROUP name on windows.
Once you have all your VM's set up, then it's just a matter of sharing folders using the normal sharing tools in windows for example right click, properties and click on the sharing tab, under Linux set up shared folders in the samba.conf file in /etc/samba or if you have a linux desktop by using the desktop sharing tools.
Remember to use the correct privileges and restrict the user name, under windows for example the default is to give the "Everyone" user full read access by default to every share you create, I usually remove this and only add specific users and control who can read and who can write.
Can't tell you how to do this in free-dos unfortunately, but I suspect you'll need some kind of NetBios client.
On your regular PC once you set everything up, you should find that in explorer under the "Network" section of your file tree, your shared machines and folders should just show up as UNC paths.
|
|
|
|
|
Is your last drive (in FreeDOS config.sys) set to drive G or later?
|
|
|
|
|
Thanks guys, one and all.
Finally discovered the secret blend of eleven herbs and spices
(I swear, I think the magic did involve eleven different ones; and I have some questions about some of those herbs; hope the teenagers don't discover them)
Anyway, the documentation on FreeDOS was very close to accurate, but, VirtualBox and/or Microsoft and/or FreeDOS and/or neither of them and/or all of them and/or space aliens somehow made one tiny change to the user interface
When I adopted the mindset of questionable mental states (induced by some of those secret herbs) I started making pot-shot guesses as to which things changed between versions, and one of my crazy guesses turned out to be accurate.
And always remember, YOU are the idiot, and the experts are the smart ones.
Uh-Huh
Oh well, I need these guys to do this gig, so, I'm the idiot. yeah.
Whatever, whatever, it works now.
Thank you every one of you, for the loaned brain cells.
|
|
|
|
|
I use Microsoft Authenticator...
I had to install it on the new phone...
There is no way the get the QR a second time if you beyond it already...
Add the account in the old way (email/password)...
Receive a message on the phone in the Authenticator that I have to confirm the login via the Authenticator...
Only resetting my profile in MFA helped to resolve this catch 22...
I believe that inclusion of MFA in the Authenticator is a true gem...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
My very first job when I went freelance (as a home office PC expert, doing hardware as well as software) was to install a CD drive into a desktop machine. It needed drivers, which were helpfully supplied... on CD. Thanks, IBM.
Things only got better after that! 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
