Thanks Liam, Not sure if you saw my more recent post... I now have a version of FreeDOS 1.2 with the NIC and MS Client installed and working. I went with v1.2 because after some googling I read that 1.2 is more stable than 1.3 for network sharing and things. Maybe that is not true anymore?
At my work I use a DOS application. It is "installed" onto a network share on a file server and by mapping this share as a network drive I and my colleagues are able to run that DOS application in Windows 7 32- bit which we are still using as our daily driver OSs on our work laptops. My IT dept wants to upgrade the OS of that file server and our laptops to Win 10. So I am trying to find a new way to host that DOS applciation and make it available to the two or three people who still use it, sometimes simultaneously. My idea is to have Win 10 on my laptop and use Virtualbox to run FreeDOS which would run this DOS application which would again need to be located on a network share... or such is my understanding... in order that more than one person can use it potentially at the same time as others using it or maybe when no one else is around and their computers are turned off. That's why I want to set up MS client and make it a Samba client to whatever PC the DOS application will reside on. If necessary it could be a small form factor PC running Win 7 32-bit that is isolated from the company network but exists only to host the DOS application and network with the few Win 10 laptops running FreeDOS in a VM that will connect to it to run that DOS application. I don't so much like your idea about using Win 98 or any other Microsoft OS that is no longer supported and we are not supposed to even be using anymore. Not so much for security reaons but for legal and licensing purposes. FreeDOS only seems to support SMBv1 with all it's gaping security holes but at least FreeDOS is free and my understanding is that I could use it even in a workplace without having to worry about licensing. I'm happy to be corrected if I'm wrong about that. I tried vDOS and DOSBOX but neither with work with my DOS applciation. It needs to be able to be run by more than one person at the same time, it needs to print to LPT ports and a potential showstopper... it needs a USB dongle to activate a licence to give it full funtionality. This is working with the USB key connected to a machine running Win 7 32-bit which then runs the DOS applciaion. But I'm not sure if this will work at all by replacing Win 7 with FreeDOS running in a VM and not bare metal. At the moment I still have not managed to get FreeDOS client to NET USE connect to a share on Win 10. I made a user account and pwd in Win 10 the same as the user in FreeDOS. I enabled SMBv1 and LANMAN in the Win 10 local security policy. It's still not connecting. I will try see if it connects to a share on a linux OS. Shame FreeDOS does not let you specify a different username in the net use command. If you have other suggestions about what I could try or entirely different approaches I should consider please let me know! Sean On Mon, 2022-02-28 at 11:46 +0100, Liam Proven wrote: > On Sun, 27 Feb 2022 at 19:54, Sean Warner <[email protected]> > wrote: > > > > I installed FreeDOS 1.2 today in Virtualbox on Win 10. > > Why the out-of-date version? 1.3 is out now. It's usually a good plan > to use the latest version. > > > I am trying to mount a Samba Share that is on another machine in my > > LAN as a network drive in FreeDOS using commands like net share and > > net use. > > That is going to be very complicated. Why do you want to do it from > DOS? > > For instance, could you install Win98 in your VM, use its built-in > networking to get the files you want, and then just boot the VM into > DOS mode? > > > > I am following several guides I googled including this one from > > wiki.samba.org: > > > > https://wiki.samba.org/index.php/Configuring_FreeDOS_to_Access_a_Samba_Share > > > > > > > > And also from this guide at virtualbox.org > > > > https://www.virtualbox.org/wiki/Sharing_files_with_DOS > > > > > > > > I’m not able to follow those instructions! I got the DSK3-1.EXE > > and DSK3-2.EXE files and used an FTP server in FreeDOS to > > transfer them into the FreeDOS OS but I don’t have any file called > > setup.exe ?? > > Have you unpacked the archives as the how-to guide says? > > Then changed into the relevant subdirectory to find the setup > program? > > > > > Do I need to install the NIC driver > > Yes. > > > and MS Client 3.0 > > Yes. > > > in order to get the net use command to work? > > Of course. Otherwise it's not there to use. > > > Because when I type net use in FreeDOS I get the error: Bad command > > or file name – “net”. I guess that program is not installed in my > > FreeDOS. Am I supposed to have a C:\NET directory? Because I don’t > > have one. I’m not why? I did a full install of FreeDOS. > > But you haven't installed the client yet. It's not there to work yet. > > > Any help much appreciated! > > It sounds to me like you are way out of your depth, technically > speaking. > > Start with the basics: why are you doing this? What do you hope to > achieve? >
_______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
