Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Liam Proven]

On Fri, 4 Mar 2022 at 19:26, Sean Warner  wrote:
>
> Gmail on my Android phone forces me to be type an answer above a previous 
> reply. Don't know how change the email to plain text..

Ah, yes. It doesn't work on the mobile client, so I try to avoid ever
answering anyone from the mobile client.

K9Mail does work for this.

> Anyway, thank you so much for all your helpful information! We are currently 
> running this "dos" program in win 7 32 bit and were using it in Win XP before 
> that. Yes I'm quite sure it's a dos program.. the only colours are black, 
> blue, white and yellow. It has no windows and it's all command line in 
> appearance, no mouse works just all arrow keys to navigate around.

That isn't evidence. Win32 Console Apps are a real thing:
https://en.wikipedia.org/wiki/Windows_Console

Here's how to build one:
https://stackoverflow.com/questions/61030578/win32-console-application

The best way to check if it's a console app is to try to run it under
DOS. Forget the dongle etc., just see if it launches.

Because, as others have said, if it needs a USB device then it very
probably is *not* a DOS app, because DOS doesn't really support USB.
(There are a handful of specialised drivers and things but it's
extremely limited.)

> I think I read that MS are ending support for XP mode but maybe that's worth 
> a try if it'll make things easier with networking and usb support which we 
> need. I'll see if I can keep this ancient program running for another year or 
> two!

I suspect it's already out of support. XP itself is, VirtualPC is, and
Win7 is on special paid-for emergency patches only.

But then again, FreeDOS is out of support, because it was never *in*
support. :-D

-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Ralf Quint]

On 3/3/2022 9:43 PM, Travis Siegel wrote:
I'm no expert, but I'm pretty sure linux does have locking in various 
increments.  File locking being the easiest, then access to portions 
of said file.  You may need to use various interfaces to accomplish 
the tasks, but there are several programs I use regularly on linux 
that couldn't function properly without some form of locking/sharing.  
You may need to do some research into how linux handles such things, 
but I'm positive such apis/includes exist. It's kind of required 
considering the multitasking nature of the os.


I'd be extremely surprised if MacOS didn't have something similar, 
considering it's based on Free BSD, and like linux, BSD almost has to 
have such facilities, just because of it's very nature. Perhaps you're 
not looking in the right places for documented information on such 
things, or perhaps I misunderstood the issue, and if so, I apologize 
for the confusion, but I can't imagine any way linux and MacOS don't 
have locking/sharing as part of the os in some way. 
As I mentioned, I am dealing with this for a larger (commercial) 
programming project. Again, neither Linux nor macOS properly support 
record locking (yes, there is a very rudimentary file locking in both of 
them, but that is no solution when requiring record locking in 
applications that share a common database but do not require a dedicated 
file server).
This was added to DOS (and mostly, but not completely supported by 
Windows) back in DOS 3.0, when first networking was introduced, in a 
rather simple to use and effective way.


Yes, it is surprising that this doesn't exist in Linux (macOS gives a 
rodents posterior regarding server use to begin with), but there has 
been the trend to work in a client-server setup, where such a server, as 
a single task/entity/application is in control who can read and/or write 
what contents and what time.


If you have a viable API, that works across at least a wide range of 
distros, if not all of them, then please share your wisdom. I would be 
glad to make use of that and reduce the amount of conditional program 
depending on the OS compiled for necessary...


Ralf

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[tom ehlert]

>> > Concurrent access to files is something already handled by SHARE

>> SHARE is all about access to *local* files, on the FreeDOS machine, and
>> has absolutely nothing to do with sharing remote files.



> MSCLIENT uses SHARE as well, it complains if you don't have it loaded.

if you use it as a SERVER.

Tom





___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Darrin M. Gorski]

> > Concurrent access to files is something already handled by SHARE

> SHARE is all about access to *local* files, on the FreeDOS machine, and
> has absolutely nothing to do with sharing remote files.

MSCLIENT uses SHARE as well, it complains if you don't have it loaded.

My concern was more with the underlying disk/filesystem layer in dosemu.

According to the latest dosemu2 release notes (end of January this year),
this may have recently received some attention.

https://github.com/dosemu2/dosemu2/releases

"Implemented region locking and share support in MFS. One of the most
requested/missed feature of dosemu1 times."

- Darrin


On Fri, Mar 4, 2022 at 6:54 AM tom ehlert  wrote:

>
>
> >> I was referring to the recommendation of using a "folder" as a drive
> under
> >> DOSEMU.  I don't believe that solution supports multiple node access to
> the
> >> same folder.
> >>
> >> SMB (i.e. MSCLIENT and Samba) were designed for this use case.
>
> > What makes you think so?
>
> Just because it's true? in MSDOS at least.
> However I have no idea if that is even implemented in FreeDOS, or
> DOSEMU.
>
> > Concurrent access to files is something already handled by SHARE
> SHARE is all about access to *local* files, on the FreeDOS machine, and
> has absolutely nothing to do with sharing remote files.
>
>
> Tom
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Hi Liam,

Gmail on my Android phone forces me to be type an answer above a previous
reply. Don't know how change the email to plain text..

Anyway, thank you so much for all your helpful information! We are
currently running this "dos" program in win 7 32 bit and were using it in
Win XP before that. Yes I'm quite sure it's a dos program.. the only
colours are black, blue, white and yellow. It has no windows and it's all
command line in appearance, no mouse works just all arrow keys to navigate
around.

I think I read that MS are ending support for XP mode but maybe that's
worth a try if it'll make things easier with networking and usb support
which we need. I'll see if I can keep this ancient program running for
another year or two!

Cheers,

Sean

On Fri 4 Mar 2022, 15:16 Liam Proven,  wrote:

> On Tue, 1 Mar 2022 at 15:22, Sean Warner  wrote:
>
> [By the way, it's convention and good netiquette to bottom-post on
> mailing lists. Gmail does it just fine; I'm doing it right now. Click
> the vertical 3 dots by the trashcan, pick "plain text" and then hit
> Ctrl-A to select all. Then you can edit and reply below the quoted
> text.]
>
> > If the dongle won't be recognized by an OS running in a VM then I guess
> I really do have a showstopper situation with freedos or win 7 or win 10 32
> bit.
>
> Definitely worth testing first!
>
> Also, DOS (any version) has next to no USB support, so I am surprised
> a DOS app would use a USB dongle. It couldn't be a text-mode Windows
> app, could it?
>
> > Is this for sure do you think? Well if I ever get the program to run
> I'll see.
>
> Well, no, I am not. I don't even know what the program is. But it's
> worth checking before you go to a lot of work.
>
> Did you know  that Microsoft makes a free WinXP virtual machine
> available for download for running DOS and 16-bit apps on 64-bit
> Windows 7? It's called XP Mode:
>
>
> https://answers.microsoft.com/en-us/windows/forum/all/windows-xp-mode/17961f45-bd96-4c10-9e24-5181d8c33db5
>
> It runs inside MS VirtualPC.
>
> There's an easy tweak to run that on Windows 8:
> http://www.win3x.org/win3board/viewtopic.php?t=19227=en
>
> I've done that and tried it. It worked fine.
>
> Linked from there is a discussion on how to run it on Win10:
> http://www.win3x.org/win3board/viewtopic.php?p=147758#p147758
>
> I haven't tried that.
>
> I wrote an article on how to run the XP Mode VM on VirtualBox or VMware:
> https://www.theregister.com/2014/04/10/how_to_run_xp_on_new_windows/
>
> I believe you can also run it inside the free Hyper-V hypervisor
> included in Win10. I have not tried that; I barely use Windows any
> more.
>
> https://www.tenforums.com/tutorials/135551-hyper-v-add-windows-xp-mode-virtual-machine-windows-10-a.html
>
> If you can get that working, it is authorised, legal MS code, produced
> and distributed by MS itself, and it would be a lot easier than
> networking FreeDOS in a VM, IMHO.
>
> I know that you can attach a USB device directly to a VirtualBox VM
> and a VMWare VM, so that the dongle would be visible to the copy of
> Windows inside the VM and therefore ought to active your app. I
> presume this is also possible with Hyper-V but I have not tried it.
>
> --
> Liam Proven ~ Profile: https://about.me/liamproven
> Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
> Twitter/LinkedIn: lproven ~ Skype: liamproven
> UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420)
> 702-829-053
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Liam Proven]

On Tue, 1 Mar 2022 at 15:22, Sean Warner  wrote:

[By the way, it's convention and good netiquette to bottom-post on
mailing lists. Gmail does it just fine; I'm doing it right now. Click
the vertical 3 dots by the trashcan, pick "plain text" and then hit
Ctrl-A to select all. Then you can edit and reply below the quoted
text.]

> If the dongle won't be recognized by an OS running in a VM then I guess I 
> really do have a showstopper situation with freedos or win 7 or win 10 32 bit.

Definitely worth testing first!

Also, DOS (any version) has next to no USB support, so I am surprised
a DOS app would use a USB dongle. It couldn't be a text-mode Windows
app, could it?

> Is this for sure do you think? Well if I ever get the program to run I'll see.

Well, no, I am not. I don't even know what the program is. But it's
worth checking before you go to a lot of work.

Did you know  that Microsoft makes a free WinXP virtual machine
available for download for running DOS and 16-bit apps on 64-bit
Windows 7? It's called XP Mode:

https://answers.microsoft.com/en-us/windows/forum/all/windows-xp-mode/17961f45-bd96-4c10-9e24-5181d8c33db5

It runs inside MS VirtualPC.

There's an easy tweak to run that on Windows 8:
http://www.win3x.org/win3board/viewtopic.php?t=19227=en

I've done that and tried it. It worked fine.

Linked from there is a discussion on how to run it on Win10:
http://www.win3x.org/win3board/viewtopic.php?p=147758#p147758

I haven't tried that.

I wrote an article on how to run the XP Mode VM on VirtualBox or VMware:
https://www.theregister.com/2014/04/10/how_to_run_xp_on_new_windows/

I believe you can also run it inside the free Hyper-V hypervisor
included in Win10. I have not tried that; I barely use Windows any
more.
https://www.tenforums.com/tutorials/135551-hyper-v-add-windows-xp-mode-virtual-machine-windows-10-a.html

If you can get that working, it is authorised, legal MS code, produced
and distributed by MS itself, and it would be a lot easier than
networking FreeDOS in a VM, IMHO.

I know that you can attach a USB device directly to a VirtualBox VM
and a VMWare VM, so that the dongle would be visible to the copy of
Windows inside the VM and therefore ought to active your app. I
presume this is also possible with Hyper-V but I have not tried it.

-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[tom ehlert]

>> I was referring to the recommendation of using a "folder" as a drive under
>> DOSEMU.  I don't believe that solution supports multiple node access to the
>> same folder.
>> 
>> SMB (i.e. MSCLIENT and Samba) were designed for this use case.

> What makes you think so?

Just because it's true? in MSDOS at least.
However I have no idea if that is even implemented in FreeDOS, or
DOSEMU.

> Concurrent access to files is something already handled by SHARE
SHARE is all about access to *local* files, on the FreeDOS machine, and
has absolutely nothing to do with sharing remote files.


Tom



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Travis Siegel]

I'm no expert, but I'm pretty sure linux does have locking in various 
increments.  File locking being the easiest, then access to portions of 
said file.  You may need to use various interfaces to accomplish the 
tasks, but there are several programs I use regularly on linux that 
couldn't function properly without some form of locking/sharing.  You 
may need to do some research into how linux handles such things, but I'm 
positive such apis/includes exist. It's kind of required considering the 
multitasking nature of the os.


I'd be extremely surprised if MacOS didn't have something similar, 
considering it's based on Free BSD, and like linux, BSD almost has to 
have such facilities, just because of it's very nature.  Perhaps you're 
not looking in the right places for documented information on such 
things, or perhaps I misunderstood the issue, and if so, I apologize for 
the confusion, but I can't imagine any way linux and MacOS don't have 
locking/sharing as part of the os in some way.



On 3/3/2022 11:38 PM, Ralf Quint wrote:

On 3/3/2022 3:36 PM, Eric Auer wrote:


I don't believe that solution supports multiple node access to the 
same folder.

SMB (i.e. MSCLIENT and Samba) were designed for this use case.


What makes you think so? Concurrent access to files is something
already handled by SHARE even in non-networked DOS contexts, so
it would not be surprising at all if DOSEMU2 supports this :-)

https://en.wikipedia.org/wiki/SHARE.EXE


Actually the question is more exciting than I thought:

https://stackoverflow.com/questions/1446891/record-locking-problem-between-linux-and-windows/65039196#65039196 



Thanks to Stas for the pointer to this Stackoverflow thread :-) 


Well, the short and gritty is that there is no OS beside DOS and (to 
some degree) Windows have proper record locking, on both Linux and 
macOS, it is pretty much non-existent, in any universally usable 
approach. I am currently dealing with a programming project of mine 
where I have to pretty much change all my record locking code even for 
Windows and completely omit it in the Linux and macOS versions.


Ralf






___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Ralf Quint]

On 3/3/2022 3:36 PM, Eric Auer wrote:


I don't believe that solution supports multiple node access to the 
same folder.

SMB (i.e. MSCLIENT and Samba) were designed for this use case.


What makes you think so? Concurrent access to files is something
already handled by SHARE even in non-networked DOS contexts, so
it would not be surprising at all if DOSEMU2 supports this :-)

https://en.wikipedia.org/wiki/SHARE.EXE


Actually the question is more exciting than I thought:

https://stackoverflow.com/questions/1446891/record-locking-problem-between-linux-and-windows/65039196#65039196 



Thanks to Stas for the pointer to this Stackoverflow thread :-) 


Well, the short and gritty is that there is no OS beside DOS and (to 
some degree) Windows have proper record locking, on both Linux and 
macOS, it is pretty much non-existent, in any universally usable 
approach. I am currently dealing with a programming project of mine 
where I have to pretty much change all my record locking code even for 
Windows and completely omit it in the Linux and macOS versions.


Ralf



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Eric Auer]

I don't believe that solution supports multiple node access 
to the same folder.

SMB (i.e. MSCLIENT and Samba) were designed for this use case.


What makes you think so? Concurrent access to files is something
already handled by SHARE even in non-networked DOS contexts, so
it would not be surprising at all if DOSEMU2 supports this :-)

https://en.wikipedia.org/wiki/SHARE.EXE


Actually the question is more exciting than I thought:

https://stackoverflow.com/questions/1446891/record-locking-problem-between-linux-and-windows/65039196#65039196

Thanks to Stas for the pointer to this Stackoverflow thread :-)

Regards, Eric




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Eric Auer]

I was referring to the recommendation of using a "folder" as a drive under
DOSEMU.  I don't believe that solution supports multiple node access to the
same folder.

SMB (i.e. MSCLIENT and Samba) were designed for this use case.


What makes you think so? Concurrent access to files is something
already handled by SHARE even in non-networked DOS contexts, so
it would not be surprising at all if DOSEMU2 supports this :-)

https://en.wikipedia.org/wiki/SHARE.EXE

Regards, Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Darrin M. Gorski]

I was referring to the recommendation of using a "folder" as a drive under
DOSEMU.  I don't believe that solution supports multiple node access to the
same folder.

SMB (i.e. MSCLIENT and Samba) were designed for this use case.

- Darrin



On Thu, Mar 3, 2022 at 9:13 AM Sean Warner  wrote:

> Hi Darrin,
>
> "As far as I know/recall, you can not have multiple DOS instances with
> read-write on the same shared linux folder."
>
> I am hoping to use your type of set up and have several... maybe 3
> freedos, or possibly 3 x Win 7 or Win XP clients (running in a VM) connect
> to the same samba share at the same time on the Linux os.
>
> The dos application won't let the clients update the same data
> simultaneously but they should be able to read and write to that share
> simultaneously.
>
> Are you saying this won't be possible if I use a Linux os to host the
> samba share? Can you explain a bit more that "period correct" solution you
> mentioned?
>
> Thank you,
>
> Sean
>
>
>
>
> On Thu 3 Mar 2022, 13:27 Darrin M. Gorski,  wrote:
>
>>
>> > That sounds unnecessarily complex
>>
>> Or interesting, I guess it depends on your perspective.
>>
>> > You could run the DOS apps in a number of DOSEMU2 windows which can use
>> Linux directories as drives.
>>
>> I did run this under DOSEMU on x86 Linux in the past, but I much prefer
>> QEMU over DOSEMU - for a number of reasons.  QEMU can run any guest OS,
>> DOSEMU only runs DOS.  QEMU can run on many host architectures and OSes,
>> DOSEMU can only run on x86 Linux.
>>
>> But the original question was about DOS and Samba, I just happen to use
>> QEMU to run DOS, so I thought I'd mention it.
>>
>> > which can use Linux directories as drives.
>>
>> As far as I know/recall, you can not have multiple DOS instances with
>> read-write on the same shared linux folder.  This is a problem for a
>> multi-node BBS where all nodes need to be able to write to the filesystem.
>> Using MSCLIENT with SHARE is a period-correct solution (many BBS systems
>> have direct built-in support for this).
>>
>> - Darrin
>>
>>
>> On Wed, Mar 2, 2022 at 4:53 PM Eric Auer  wrote:
>>
>>>
>>> Hi!
>>>
>>> >> I have a pi running raspbian (debian 10) and samba 4.9 which serves
>>> files
>>> >> to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.
>>>
>>> That sounds unnecessarily complex: You could run the DOS apps in a
>>> number of DOSEMU2 windows which can use Linux directories as drives.
>>> This would not require any Samba or any MSCLINT to be running :-)
>>>
>>> Not sure when DOSEMU2 will support Raspberry Pi, but for those who
>>> have PC compatible computers, it would be an easy method to run a
>>> number of DOS apps simultaneously.
>>>
>>> However, your answer is great for the general question how DOS can
>>> connect to Windows drives today! I think Linux and Samba make it a
>>> lot easier to disable security (only sane for restricted networks)
>>> sufficently to make DOS clients happy, compared to using Windows.
>>>
>>> Regards, Eric
>>>
>>>
>>>
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Hi Darrin,

"As far as I know/recall, you can not have multiple DOS instances with
read-write on the same shared linux folder."

I am hoping to use your type of set up and have several... maybe 3 freedos,
or possibly 3 x Win 7 or Win XP clients (running in a VM) connect to the
same samba share at the same time on the Linux os.

The dos application won't let the clients update the same data
simultaneously but they should be able to read and write to that share
simultaneously.

Are you saying this won't be possible if I use a Linux os to host the samba
share? Can you explain a bit more that "period correct" solution you
mentioned?

Thank you,

Sean




On Thu 3 Mar 2022, 13:27 Darrin M. Gorski,  wrote:

>
> > That sounds unnecessarily complex
>
> Or interesting, I guess it depends on your perspective.
>
> > You could run the DOS apps in a number of DOSEMU2 windows which can use
> Linux directories as drives.
>
> I did run this under DOSEMU on x86 Linux in the past, but I much prefer
> QEMU over DOSEMU - for a number of reasons.  QEMU can run any guest OS,
> DOSEMU only runs DOS.  QEMU can run on many host architectures and OSes,
> DOSEMU can only run on x86 Linux.
>
> But the original question was about DOS and Samba, I just happen to use
> QEMU to run DOS, so I thought I'd mention it.
>
> > which can use Linux directories as drives.
>
> As far as I know/recall, you can not have multiple DOS instances with
> read-write on the same shared linux folder.  This is a problem for a
> multi-node BBS where all nodes need to be able to write to the filesystem.
> Using MSCLIENT with SHARE is a period-correct solution (many BBS systems
> have direct built-in support for this).
>
> - Darrin
>
>
> On Wed, Mar 2, 2022 at 4:53 PM Eric Auer  wrote:
>
>>
>> Hi!
>>
>> >> I have a pi running raspbian (debian 10) and samba 4.9 which serves
>> files
>> >> to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.
>>
>> That sounds unnecessarily complex: You could run the DOS apps in a
>> number of DOSEMU2 windows which can use Linux directories as drives.
>> This would not require any Samba or any MSCLINT to be running :-)
>>
>> Not sure when DOSEMU2 will support Raspberry Pi, but for those who
>> have PC compatible computers, it would be an easy method to run a
>> number of DOS apps simultaneously.
>>
>> However, your answer is great for the general question how DOS can
>> connect to Windows drives today! I think Linux and Samba make it a
>> lot easier to disable security (only sane for restricted networks)
>> sufficently to make DOS clients happy, compared to using Windows.
>>
>> Regards, Eric
>>
>>
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Darrin M. Gorski]

> That sounds unnecessarily complex

Or interesting, I guess it depends on your perspective.

> You could run the DOS apps in a number of DOSEMU2 windows which can use
Linux directories as drives.

I did run this under DOSEMU on x86 Linux in the past, but I much prefer
QEMU over DOSEMU - for a number of reasons.  QEMU can run any guest OS,
DOSEMU only runs DOS.  QEMU can run on many host architectures and OSes,
DOSEMU can only run on x86 Linux.

But the original question was about DOS and Samba, I just happen to use
QEMU to run DOS, so I thought I'd mention it.

> which can use Linux directories as drives.

As far as I know/recall, you can not have multiple DOS instances with
read-write on the same shared linux folder.  This is a problem for a
multi-node BBS where all nodes need to be able to write to the filesystem.
Using MSCLIENT with SHARE is a period-correct solution (many BBS systems
have direct built-in support for this).

- Darrin


On Wed, Mar 2, 2022 at 4:53 PM Eric Auer  wrote:

>
> Hi!
>
> >> I have a pi running raspbian (debian 10) and samba 4.9 which serves
> files
> >> to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.
>
> That sounds unnecessarily complex: You could run the DOS apps in a
> number of DOSEMU2 windows which can use Linux directories as drives.
> This would not require any Samba or any MSCLINT to be running :-)
>
> Not sure when DOSEMU2 will support Raspberry Pi, but for those who
> have PC compatible computers, it would be an easy method to run a
> number of DOS apps simultaneously.
>
> However, your answer is great for the general question how DOS can
> connect to Windows drives today! I think Linux and Samba make it a
> lot easier to disable security (only sane for restricted networks)
> sufficently to make DOS clients happy, compared to using Windows.
>
> Regards, Eric
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Darrin M. Gorski]

Yes.  Because the samba share is configured for "guest ok = yes", it
doesn't matter what username you use.  MSCLIEINT wants a username and it
will save it and the password locally (unless you tell it not to) for the
next call to NET USE.

In this case, I used "net use /persistent:yes g: \\server\share".  This
causes MSCLIENT to remember this connection and re-establish it each time
the machine boots (when you call NET START.)

You can see this in the bootup messages:

MS-DOS LAN Manager v2.1 Netbind
Microsoft DOS TCP/IP 1.0a
G: connected to \\BBSMAIN\SHARED..
The command completed successfully.

Here is the output from NET USE, I meant to include this in the post.

C:\>net use

Status  Local name  Remote name
qqq
OK  G:  \\BBSMAIN\SHARED
The command completed successfully.
C:\>

- Darrin


On Thu, Mar 3, 2022 at 5:33 AM Sean Warner  wrote:

> Hi Darrin,
>
> Just checking with your approach detailed below.. to connect to a samba
> share on the Pi from freedos client you use something like this...
>
> net use X: \\SERVER\SHARENAME
>
> And you need either to be running freedos with a username the same as what
> exists in the samba server on the Pi? Or else to create a samba server user
> with same name as the freedos username?
>
> Cheers,
>
> Sean
>
> On Wed 2 Mar 2022, 06:46 Darrin M. Gorski,  wrote:
>
>>
>> I have a pi running raspbian (debian 10) and samba 4.9 which serves files
>> to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.
>>
>> It's pretty cool to see DOS boxes running on an ARM.
>>
>> Anyway, what follows isn't pretty but here are ALL of the pertinent
>> details I can think to share.  Note that it has been a year or two since I
>> set this up so I don't remember all of the little gotchas that I had to
>> deal with at the time.  There is always something.  I hope that there is
>> something in here that helps!
>>
>> Please note this is for a host-only network so security in this config is
>> wide open - you will need to decide if using "guest ok = yes" and "read
>> only = no" is safe - it would effectively allow anyone to connect and
>> delete all of your files.
>>
>>
>> pi@basement:~ $ cat /etc/os-release
>> PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
>> NAME="Raspbian GNU/Linux"
>> VERSION_ID="10"
>> VERSION="10 (buster)"
>> VERSION_CODENAME=buster
>> ID=raspbian
>> ID_LIKE=debian
>> HOME_URL="http://www.raspbian.org/;
>> SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
>> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;
>>
>> pi@basement:~ $ smbd --version
>> Version 4.9.5-Debian
>>
>> pi@basement:~ $ grep -v '^$' /etc/samba/smb.conf | egrep -v '^[#;]'
>> [global]
>>workgroup = BBSNET
>>netbios name = BBSMAIN
>>username map = /etc/samba/usermap.txt
>>log file = /var/log/samba/log.%m
>>max log size = 1000
>>logging = file
>>panic action = /usr/share/samba/panic-action %d
>>server role = standalone server
>>passwd program = /usr/bin/passwd %u
>>passwd chat = *Enter\snew\s*\spassword:* %n\n
>> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>>pam password change = yes
>>map to guest = bad user
>> [SHARED]
>>comment = BBS Common files
>>path = /bbs/shared
>>read only = no
>>guest ok = yes
>>browseable = yes
>>force create mode = 0660
>>force directory mode = 2770
>>force user = pi
>>
>> pi@basement:~ $ ls /etc/samba/
>> gdbcommands  smb.conf  tls
>>
>> pi@basement:~ $ ls /etc/samba/tls
>> pi@basement:~ $
>>
>>
>>
>> Here is one of the DOS nodes starting under freedos 1.3-rc2
>>
>> Inside the session I also show the contents of autoexec and config, as
>> well as the output of mem with all of the drivers loaded.
>>
>>
>> pi@basement:/data/nodes/file $ sudo ./start.sh
>> starting qemu
>>
>>
>>  1 - Start a standard BBS node
>>  2 - Start in setup/configuration mode
>>  3 - Don't load anything
>>
>>
>>Select from Menu [123], or press [ENTER] (Selection=2)
>>
>>Singlestepping (F8) is: OFF
>>
>>
>>
>> JemmEx v5.78 [07/15/12]
>> JemmEx loaded
>>
>> Kernel: allocated 45 Diskbuffers = 23940 Bytes in HMA
>>
>> FreeCom version 0.84-pre7 - WATCOMC - XMS_Swap [May 28 2020 19:21:14]
>> Performing action: APMDOS
>> If APMDOS slows down any app, use ADV:REG instead.
>> Going resident.
>>
>> UDVD2, 3-05-2015.   CD/DVD name is FDCD0001.
>> BAD Controller at I-O address C020h, Chip I.D. 80867010h.
>> CD0:  IDE0 Secondary-master, QEMU DVD-ROM, PIO.
>> LBAcache disk read cache for XMS + 386, E. Auer 
>> 2001-2006
>> License: GPL 2.  Up to 8 harddisks, 2 floppy, LBA / CHS. Version:
>> 07apr2008.
>> Detecting harddisks:
>>   disk 0x80 heads=0016 sectors=0063 [done]
>>  [No floppy cache: no change lines]
>> XMS allocated: 20.00  MB, driver size with tables and stack: 25859 bytes.
>> SHARE installed.
>>
>>  AMD PCNet Family Ethernet Adapter
>>  NDIS v2.0.1 MAC Driver,  

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Hi Darrin,

Just checking with your approach detailed below.. to connect to a samba
share on the Pi from freedos client you use something like this...

net use X: \\SERVER\SHARENAME

And you need either to be running freedos with a username the same as what
exists in the samba server on the Pi? Or else to create a samba server user
with same name as the freedos username?

Cheers,

Sean

On Wed 2 Mar 2022, 06:46 Darrin M. Gorski,  wrote:

>
> I have a pi running raspbian (debian 10) and samba 4.9 which serves files
> to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.
>
> It's pretty cool to see DOS boxes running on an ARM.
>
> Anyway, what follows isn't pretty but here are ALL of the pertinent
> details I can think to share.  Note that it has been a year or two since I
> set this up so I don't remember all of the little gotchas that I had to
> deal with at the time.  There is always something.  I hope that there is
> something in here that helps!
>
> Please note this is for a host-only network so security in this config is
> wide open - you will need to decide if using "guest ok = yes" and "read
> only = no" is safe - it would effectively allow anyone to connect and
> delete all of your files.
>
>
> pi@basement:~ $ cat /etc/os-release
> PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="10"
> VERSION="10 (buster)"
> VERSION_CODENAME=buster
> ID=raspbian
> ID_LIKE=debian
> HOME_URL="http://www.raspbian.org/;
> SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;
>
> pi@basement:~ $ smbd --version
> Version 4.9.5-Debian
>
> pi@basement:~ $ grep -v '^$' /etc/samba/smb.conf | egrep -v '^[#;]'
> [global]
>workgroup = BBSNET
>netbios name = BBSMAIN
>username map = /etc/samba/usermap.txt
>log file = /var/log/samba/log.%m
>max log size = 1000
>logging = file
>panic action = /usr/share/samba/panic-action %d
>server role = standalone server
>passwd program = /usr/bin/passwd %u
>passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>pam password change = yes
>map to guest = bad user
> [SHARED]
>comment = BBS Common files
>path = /bbs/shared
>read only = no
>guest ok = yes
>browseable = yes
>force create mode = 0660
>force directory mode = 2770
>force user = pi
>
> pi@basement:~ $ ls /etc/samba/
> gdbcommands  smb.conf  tls
>
> pi@basement:~ $ ls /etc/samba/tls
> pi@basement:~ $
>
>
>
> Here is one of the DOS nodes starting under freedos 1.3-rc2
>
> Inside the session I also show the contents of autoexec and config, as
> well as the output of mem with all of the drivers loaded.
>
>
> pi@basement:/data/nodes/file $ sudo ./start.sh
> starting qemu
>
>
>  1 - Start a standard BBS node
>  2 - Start in setup/configuration mode
>  3 - Don't load anything
>
>
>Select from Menu [123], or press [ENTER] (Selection=2)
>
>Singlestepping (F8) is: OFF
>
>
>
> JemmEx v5.78 [07/15/12]
> JemmEx loaded
>
> Kernel: allocated 45 Diskbuffers = 23940 Bytes in HMA
>
> FreeCom version 0.84-pre7 - WATCOMC - XMS_Swap [May 28 2020 19:21:14]
> Performing action: APMDOS
> If APMDOS slows down any app, use ADV:REG instead.
> Going resident.
>
> UDVD2, 3-05-2015.   CD/DVD name is FDCD0001.
> BAD Controller at I-O address C020h, Chip I.D. 80867010h.
> CD0:  IDE0 Secondary-master, QEMU DVD-ROM, PIO.
> LBAcache disk read cache for XMS + 386, E. Auer 
> 2001-2006
> License: GPL 2.  Up to 8 harddisks, 2 floppy, LBA / CHS. Version:
> 07apr2008.
> Detecting harddisks:
>   disk 0x80 heads=0016 sectors=0063 [done]
>  [No floppy cache: no change lines]
> XMS allocated: 20.00  MB, driver size with tables and stack: 25859 bytes.
> SHARE installed.
>
>  AMD PCNet Family Ethernet Adapter
>  NDIS v2.0.1 MAC Driver,  Version  3.12
>  DriverName  PCNTND$
> Station Address ... 00.43.DE.ED.01.50
>  Driver configuration.
> IOAddress . 0xC000
> Interrupt . 11
> DMA ... 0
> Rx Buffers .4
> Tx Buffers .4
> Microsoft DOS TCP/IP Protocol Driver 1.0a
> Copyright (c) Microsoft Corporation, 1991.  All rights reserved.
> Copyright (c) Hewlett-Packard Corporation, 1985-1991.  All rights reserved.
> Copyright (c) 3Com Corporation, 1985-1991.  All rights reserved.
> Microsoft DOS TCP/IP NEMM Driver 1.0
> The command completed successfully.
> MS-DOS LAN Manager v2.1 Netbind
> Microsoft DOS TCP/IP 1.0a
> G: connected to \\BBSMAIN\SHARED..
> The command completed successfully.
> C:\>
> C:\>dir /w g:
>  Volume in drive G is SHARED
>
>  Directory of G:\
>
> [.][..]   [SRC]  [TPPATCH]  [PERL]
> [OLD]  [BBS1] [SERIAL]   WG1049.EXE [MSGS]
> [TXTFILES] [DICT] [STATUS]   [ONLINERS] [TEMP]
> [TP6]  [FILES][UTILS]O7SC3C~9.EXE   [NODE]
> [TAG]  

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Eric Auer]

Hi!


I have a pi running raspbian (debian 10) and samba 4.9 which serves files
to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.


That sounds unnecessarily complex: You could run the DOS apps in a
number of DOSEMU2 windows which can use Linux directories as drives.
This would not require any Samba or any MSCLINT to be running :-)

Not sure when DOSEMU2 will support Raspberry Pi, but for those who
have PC compatible computers, it would be an easy method to run a
number of DOS apps simultaneously.

However, your answer is great for the general question how DOS can
connect to Windows drives today! I think Linux and Samba make it a
lot easier to disable security (only sane for restricted networks)
sufficently to make DOS clients happy, compared to using Windows.

Regards, Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Darrin,

This looks really promising. I'll give it a try and let you know how I got
on, probably with follow up questions!

Thanks a lot,
Sean

On Wed 2 Mar 2022, 06:46 Darrin M. Gorski,  wrote:

>
> I have a pi running raspbian (debian 10) and samba 4.9 which serves files
> to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.
>
> It's pretty cool to see DOS boxes running on an ARM.
>
> Anyway, what follows isn't pretty but here are ALL of the pertinent
> details I can think to share.  Note that it has been a year or two since I
> set this up so I don't remember all of the little gotchas that I had to
> deal with at the time.  There is always something.  I hope that there is
> something in here that helps!
>
> Please note this is for a host-only network so security in this config is
> wide open - you will need to decide if using "guest ok = yes" and "read
> only = no" is safe - it would effectively allow anyone to connect and
> delete all of your files.
>
>
> pi@basement:~ $ cat /etc/os-release
> PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="10"
> VERSION="10 (buster)"
> VERSION_CODENAME=buster
> ID=raspbian
> ID_LIKE=debian
> HOME_URL="http://www.raspbian.org/;
> SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;
>
> pi@basement:~ $ smbd --version
> Version 4.9.5-Debian
>
> pi@basement:~ $ grep -v '^$' /etc/samba/smb.conf | egrep -v '^[#;]'
> [global]
>workgroup = BBSNET
>netbios name = BBSMAIN
>username map = /etc/samba/usermap.txt
>log file = /var/log/samba/log.%m
>max log size = 1000
>logging = file
>panic action = /usr/share/samba/panic-action %d
>server role = standalone server
>passwd program = /usr/bin/passwd %u
>passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>pam password change = yes
>map to guest = bad user
> [SHARED]
>comment = BBS Common files
>path = /bbs/shared
>read only = no
>guest ok = yes
>browseable = yes
>force create mode = 0660
>force directory mode = 2770
>force user = pi
>
> pi@basement:~ $ ls /etc/samba/
> gdbcommands  smb.conf  tls
>
> pi@basement:~ $ ls /etc/samba/tls
> pi@basement:~ $
>
>
>
> Here is one of the DOS nodes starting under freedos 1.3-rc2
>
> Inside the session I also show the contents of autoexec and config, as
> well as the output of mem with all of the drivers loaded.
>
>
> pi@basement:/data/nodes/file $ sudo ./start.sh
> starting qemu
>
>
>  1 - Start a standard BBS node
>  2 - Start in setup/configuration mode
>  3 - Don't load anything
>
>
>Select from Menu [123], or press [ENTER] (Selection=2)
>
>Singlestepping (F8) is: OFF
>
>
>
> JemmEx v5.78 [07/15/12]
> JemmEx loaded
>
> Kernel: allocated 45 Diskbuffers = 23940 Bytes in HMA
>
> FreeCom version 0.84-pre7 - WATCOMC - XMS_Swap [May 28 2020 19:21:14]
> Performing action: APMDOS
> If APMDOS slows down any app, use ADV:REG instead.
> Going resident.
>
> UDVD2, 3-05-2015.   CD/DVD name is FDCD0001.
> BAD Controller at I-O address C020h, Chip I.D. 80867010h.
> CD0:  IDE0 Secondary-master, QEMU DVD-ROM, PIO.
> LBAcache disk read cache for XMS + 386, E. Auer 
> 2001-2006
> License: GPL 2.  Up to 8 harddisks, 2 floppy, LBA / CHS. Version:
> 07apr2008.
> Detecting harddisks:
>   disk 0x80 heads=0016 sectors=0063 [done]
>  [No floppy cache: no change lines]
> XMS allocated: 20.00  MB, driver size with tables and stack: 25859 bytes.
> SHARE installed.
>
>  AMD PCNet Family Ethernet Adapter
>  NDIS v2.0.1 MAC Driver,  Version  3.12
>  DriverName  PCNTND$
> Station Address ... 00.43.DE.ED.01.50
>  Driver configuration.
> IOAddress . 0xC000
> Interrupt . 11
> DMA ... 0
> Rx Buffers .4
> Tx Buffers .4
> Microsoft DOS TCP/IP Protocol Driver 1.0a
> Copyright (c) Microsoft Corporation, 1991.  All rights reserved.
> Copyright (c) Hewlett-Packard Corporation, 1985-1991.  All rights reserved.
> Copyright (c) 3Com Corporation, 1985-1991.  All rights reserved.
> Microsoft DOS TCP/IP NEMM Driver 1.0
> The command completed successfully.
> MS-DOS LAN Manager v2.1 Netbind
> Microsoft DOS TCP/IP 1.0a
> G: connected to \\BBSMAIN\SHARED..
> The command completed successfully.
> C:\>
> C:\>dir /w g:
>  Volume in drive G is SHARED
>
>  Directory of G:\
>
> [.][..]   [SRC]  [TPPATCH]  [PERL]
> [OLD]  [BBS1] [SERIAL]   WG1049.EXE [MSGS]
> [TXTFILES] [DICT] [STATUS]   [ONLINERS] [TEMP]
> [TP6]  [FILES][UTILS]O7SC3C~9.EXE   [NODE]
> [TAG]  [MULTI][FREECOM]  [DOC]
>  2 file(s) 84,249,523 bytes
> 22 dir(s)   2,147,450,880 bytes free
> C:\>
> C:\>ver
>
> FreeCom version 0.84-pre7 - WATCOMC - XMS_Swap [May 28 2020 19:21:14]
> C:\>
> C:\>type \fdos\version.fdi

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Darrin M. Gorski]

I have a pi running raspbian (debian 10) and samba 4.9 which serves files
to a set of DOS QEMU VMs using the MSCLIENT 3.0 for DOS network stack.

It's pretty cool to see DOS boxes running on an ARM.

Anyway, what follows isn't pretty but here are ALL of the pertinent details
I can think to share.  Note that it has been a year or two since I set this
up so I don't remember all of the little gotchas that I had to deal with at
the time.  There is always something.  I hope that there is something in
here that helps!

Please note this is for a host-only network so security in this config is
wide open - you will need to decide if using "guest ok = yes" and "read
only = no" is safe - it would effectively allow anyone to connect and
delete all of your files.


pi@basement:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/;
SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;

pi@basement:~ $ smbd --version
Version 4.9.5-Debian

pi@basement:~ $ grep -v '^$' /etc/samba/smb.conf | egrep -v '^[#;]'
[global]
   workgroup = BBSNET
   netbios name = BBSMAIN
   username map = /etc/samba/usermap.txt
   log file = /var/log/samba/log.%m
   max log size = 1000
   logging = file
   panic action = /usr/share/samba/panic-action %d
   server role = standalone server
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
   pam password change = yes
   map to guest = bad user
[SHARED]
   comment = BBS Common files
   path = /bbs/shared
   read only = no
   guest ok = yes
   browseable = yes
   force create mode = 0660
   force directory mode = 2770
   force user = pi

pi@basement:~ $ ls /etc/samba/
gdbcommands  smb.conf  tls

pi@basement:~ $ ls /etc/samba/tls
pi@basement:~ $



Here is one of the DOS nodes starting under freedos 1.3-rc2

Inside the session I also show the contents of autoexec and config, as well
as the output of mem with all of the drivers loaded.


pi@basement:/data/nodes/file $ sudo ./start.sh
starting qemu


 1 - Start a standard BBS node
 2 - Start in setup/configuration mode
 3 - Don't load anything


   Select from Menu [123], or press [ENTER] (Selection=2)

   Singlestepping (F8) is: OFF



JemmEx v5.78 [07/15/12]
JemmEx loaded

Kernel: allocated 45 Diskbuffers = 23940 Bytes in HMA

FreeCom version 0.84-pre7 - WATCOMC - XMS_Swap [May 28 2020 19:21:14]
Performing action: APMDOS
If APMDOS slows down any app, use ADV:REG instead.
Going resident.

UDVD2, 3-05-2015.   CD/DVD name is FDCD0001.
BAD Controller at I-O address C020h, Chip I.D. 80867010h.
CD0:  IDE0 Secondary-master, QEMU DVD-ROM, PIO.
LBAcache disk read cache for XMS + 386, E. Auer 
2001-2006
License: GPL 2.  Up to 8 harddisks, 2 floppy, LBA / CHS. Version: 07apr2008.
Detecting harddisks:
  disk 0x80 heads=0016 sectors=0063 [done]
 [No floppy cache: no change lines]
XMS allocated: 20.00  MB, driver size with tables and stack: 25859 bytes.
SHARE installed.

 AMD PCNet Family Ethernet Adapter
 NDIS v2.0.1 MAC Driver,  Version  3.12
 DriverName  PCNTND$
Station Address ... 00.43.DE.ED.01.50
 Driver configuration.
IOAddress . 0xC000
Interrupt . 11
DMA ... 0
Rx Buffers .4
Tx Buffers .4
Microsoft DOS TCP/IP Protocol Driver 1.0a
Copyright (c) Microsoft Corporation, 1991.  All rights reserved.
Copyright (c) Hewlett-Packard Corporation, 1985-1991.  All rights reserved.
Copyright (c) 3Com Corporation, 1985-1991.  All rights reserved.
Microsoft DOS TCP/IP NEMM Driver 1.0
The command completed successfully.
MS-DOS LAN Manager v2.1 Netbind
Microsoft DOS TCP/IP 1.0a
G: connected to \\BBSMAIN\SHARED..
The command completed successfully.
C:\>
C:\>dir /w g:
 Volume in drive G is SHARED

 Directory of G:\

[.][..]   [SRC]  [TPPATCH]  [PERL]
[OLD]  [BBS1] [SERIAL]   WG1049.EXE [MSGS]
[TXTFILES] [DICT] [STATUS]   [ONLINERS] [TEMP]
[TP6]  [FILES][UTILS]O7SC3C~9.EXE   [NODE]
[TAG]  [MULTI][FREECOM]  [DOC]
 2 file(s) 84,249,523 bytes
22 dir(s)   2,147,450,880 bytes free
C:\>
C:\>ver

FreeCom version 0.84-pre7 - WATCOMC - XMS_Swap [May 28 2020 19:21:14]
C:\>
C:\>type \fdos\version.fdi
PLATFORM=FreeDOS
VERSION=1.3-RC2
RELEASE=2019-12-02
C:\>
C:\>mem

Memory Type Total  Used   Free
        
Conventional  639K   204K   435K
Upper 108K92K16K
Reserved  277K   277K 0K
Extended (XMS)129,920K21,102K   108,818K
        
Total memory  130,944K21,675K   109,269K

Total 

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Thanks Liam,

If this app is copy-protected and needs a dongle, then I suspect it
won't run in a VM, because the dongle won't be connected to the VM.

How about just running Windows 7 32-bit in a VM, and trying that way?
You already have it, presumably licensed

If the dongle won't be recognized by an OS running in a VM then I guess I
really do have a showstopper situation with freedos or win 7 or win 10 32
bit.

Is this for sure do you think? Well if I ever get the program to run I'll
see.

Cheers,

Sean
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Liam Proven]

On Tue, 1 Mar 2022 at 02:41, Sean Warner  wrote:
>
> Thanks Liam,
>
> Not sure if you saw my more recent post...

You changed the subject/title line. In Gmail, that broke the thread
and made your 2nd message into a new thread.

> 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?

Well, 1.3 is final, released code now. But then, it's very new.

> 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.

OK. I see your point, and it is a valid point. However, the thing is this:

> it needs a USB dongle to activate a licence to give it full funtionality.

If this app is copy-protected and needs a dongle, then I suspect it
won't run in a VM, because the dongle won't be connected to the VM.

How about just running Windows 7 32-bit in a VM, and trying that way?
You already have it, presumably licensed.

> Shame FreeDOS does not let you specify a different username in the net use 
> command.

NET USE is not part of FreeDOS. It's part of the MS LAN Client for DOS.

The client does let you log in and out, and the username can be
changed... but I haven't used it since the 1980s or maybe early 1990s.

-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Thanks Jerome.

I'll take a look at EtherDFS..

Regarding Win 10 being snobbish. Smbv1 is now disabled by default in Win
10. You can enable it and you might need to change the local security
policy in each win 10 client also to allow lanman auth.. not sure if you
can do that in Win10 home Ed.

At least I gathered this from my googling though I am yet to succeed in
connecting from freedos to a share on Win10 using the NET USE command I
think those steps are needed. And the username in freedos needs to also
exist on the samba server it seems.

Cheers,

Sean

On Tue 1 Mar 2022, 12:13 Jerome Shidel,  wrote:

> Hi,
>
> I’m no expert on Samba shares. But from personal experience, your probably
> not going to have much luck.
>
> I have a Linux server on my home network. When I let it use a minimum of
> SMB2, all but one ancient Mac will chat with it. No problem.
> But to get that one Mac working, requires lowering the minimum to NT4.
> When I do that, all of the Macs (new and old) are happy. The Linux machines
> are happy. But, the Windows 10 machines get snobbish and no longer talk to
> it. So, I pretty much need to use a minimum of SMB2. Then relay the old Mac
> through a newer one.
>
> I mention that only to say that I doubt you’ll get it working in DOS with
> SMB2 and using a lower minimum will just cause problems.
>
> But, there is possibly an alternative. If you are not limited to only
> using Samba and have a Linux server, consider using EtherDFS. It’s lite
> weight and works pretty good.
>
> There are a couple minor hoops to jump through. But once setup, you don’t
> even notice.
>
> Basically, my Linux server has a FAT disk image that gets mounted to a
> directory. EtherDFS shares that dir for my DOS machines. Also, that dir is
> shared via Samba to everything else.
>
> The only issue I’ve noticed is with long file names. If I store something
> in that DIR that uses a non-DOS 8.3 filename, the file appears over
> EtherDFS but is not accessible from DOS.
>
> Otherwise, I’ve seen no issues.
>
> Jerome
>
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Jerome Shidel]

Hi,

I’m no expert on Samba shares. But from personal experience, your probably not 
going to have much luck. 

I have a Linux server on my home network. When I let it use a minimum of SMB2, 
all but one ancient Mac will chat with it. No problem. 
But to get that one Mac working, requires lowering the minimum to NT4. When I 
do that, all of the Macs (new and old) are happy. The Linux machines are happy. 
But, the Windows 10 machines get snobbish and no longer talk to it. So, I 
pretty much need to use a minimum of SMB2. Then relay the old Mac through a 
newer one.

I mention that only to say that I doubt you’ll get it working in DOS with SMB2 
and using a lower minimum will just cause problems.

But, there is possibly an alternative. If you are not limited to only using 
Samba and have a Linux server, consider using EtherDFS. It’s lite weight and 
works pretty good.

There are a couple minor hoops to jump through. But once setup, you don’t even 
notice.

Basically, my Linux server has a FAT disk image that gets mounted to a 
directory. EtherDFS shares that dir for my DOS machines. Also, that dir is 
shared via Samba to everything else.

The only issue I’ve noticed is with long file names. If I store something in 
that DIR that uses a non-DOS 8.3 filename, the file appears over EtherDFS but 
is not accessible from DOS. 

Otherwise, I’ve seen no issues.

Jerome 




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Hi Dennis,

Thanks for the detailed response.

There is a bit of pressure from my IT dept to upgrade both the file server
that the network share resides on and the win 7 laptops that we use to run
the dos app in.

When they recently upgraded another file server the dos app had to be moved
to another server  because it stopped working after the first server was
upgraded. My concern is this will happen again. I don't know the exact
details.. maybe the samba version the new server supports? Or maybe the os
of the file server does not support dos? Again my knowledge is limited
here. I can ask IT dept.

The dos app contains a customer database so changes made by one user need
to be seen by others and more than one person may be adding and updating
customer info at the same time. This is why I think the dos app would need
to be on a network share.

I tried dosbox and vdos but they won't work. The dos app needs to print to
net use mapped lpt ports and also there is a USB dongle that the dos app
needs to communicate with to allow full functionality. Although in practice
most functions work anyway even without that. I only tried the official
versions of vdos and dosbox tho so maybe there are other versions that
could work.

Any more advice greatly appreciated!

Sean


On Tue 1 Mar 2022, 05:41 dmccunney,  wrote:

> On Mon, Feb 28, 2022 at 8:41 PM Sean Warner  wrote:
> >
> > 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.
>
> I think you are making this far more complicated than it needs to be.
>
> Right now, you can access the DOS application and run it from a drive
> which is mapped as a network share.  If the company upgrades the
> server OS on the machine mapped as a share, why would that change the
> mapping, or the ability to access the network share and the DOS
> application that lives on it?
>
> When you run it now, you are loading it from the network and running
> it locally.  How many must use it simultaneously is irrelevant.  You
> are each running a local copy of the application, that happens to be
> run from a network server instead of being loaded from a local drive.
>
> You are using 32 bit Win7 because it still supports NTVDM, which
> provides enough of the DOS environment to load and run a 18 bit DOS
> application.  Microsoft removed the ability to run 16 bit applications
> in 64 bit Windows, so if you need to do that you need a VM of some
> sort to run them in.
>
> One possibility is a 32 bit build of Win10.  Those do exist, and will
> still run 16 bit apps using NTVDM, but it isn't the direction I would
> go,.  What happens if you need to run a 54 bit Windows application?
>
> These days, the preferred method of running 16 bit DOS applications on
> bit Windows is to use a VM, but it doesn't require VirtuaBox or the
> like.  What most folks here do is run DOSBox or vDOS Plus.  DOSBox is
> a VM designed to allow gamers to run DOS games on things that aren't
> DOS PCs.  It provides enough of a DOS environment to run the games.
> and provides emulation for various graphics and sound functions that
> aren't available on things like PCs that don't have a Creative Labs
> Sound Blaster ISA card to provide the audio for games written to use
> it, or a specidfic supported video card for EGA/VGA modes..  DOSBox is
> cross platform.  I used an ARM port to run several DOS apps on an
> Android tablet using an ARM Cortex 7 CPU.  (I had to find one that
> passed Ctrl-key combos to the running app, as a WordStar style editor
> was one of the things I wanted to use.)
>
> If your application is pure character mode, you can use a fork of
> DOSBox called vDOS Plus.  vDOS Plus only runs on x86 architecture, but
> that's not an issue for you.  It's specifically intended to run
> character mode applications like editors and spreadsheets, and drops
> the specialized video and 

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[dmccunney]

On Mon, Feb 28, 2022 at 8:41 PM Sean Warner  wrote:
>
> 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.

I think you are making this far more complicated than it needs to be.

Right now, you can access the DOS application and run it from a drive
which is mapped as a network share.  If the company upgrades the
server OS on the machine mapped as a share, why would that change the
mapping, or the ability to access the network share and the DOS
application that lives on it?

When you run it now, you are loading it from the network and running
it locally.  How many must use it simultaneously is irrelevant.  You
are each running a local copy of the application, that happens to be
run from a network server instead of being loaded from a local drive.

You are using 32 bit Win7 because it still supports NTVDM, which
provides enough of the DOS environment to load and run a 18 bit DOS
application.  Microsoft removed the ability to run 16 bit applications
in 64 bit Windows, so if you need to do that you need a VM of some
sort to run them in.

One possibility is a 32 bit build of Win10.  Those do exist, and will
still run 16 bit apps using NTVDM, but it isn't the direction I would
go,.  What happens if you need to run a 54 bit Windows application?

These days, the preferred method of running 16 bit DOS applications on
bit Windows is to use a VM, but it doesn't require VirtuaBox or the
like.  What most folks here do is run DOSBox or vDOS Plus.  DOSBox is
a VM designed to allow gamers to run DOS games on things that aren't
DOS PCs.  It provides enough of a DOS environment to run the games.
and provides emulation for various graphics and sound functions that
aren't available on things like PCs that don't have a Creative Labs
Sound Blaster ISA card to provide the audio for games written to use
it, or a specidfic supported video card for EGA/VGA modes..  DOSBox is
cross platform.  I used an ARM port to run several DOS apps on an
Android tablet using an ARM Cortex 7 CPU.  (I had to find one that
passed Ctrl-key combos to the running app, as a WordStar style editor
was one of the things I wanted to use.)

If your application is pure character mode, you can use a fork of
DOSBox called vDOS Plus.  vDOS Plus only runs on x86 architecture, but
that's not an issue for you.  It's specifically intended to run
character mode applications like editors and spreadsheets, and drops
the specialized video and sound support..  I use it here to run the
old VDE editor, a WordStar clone that originated under CP/M and was
ported to DOS, as well as some character mode games ported from Unix
like Larn and VMS Empire.

I run them from a shortcut.  The shortcut runs vDOS Plus, but starts
it in the directory where the DOS program is stored.  Local config
files in the directory do the setup to run the program.  Exit the
program and I'm back in Windows.

And for that matter, I don't see the need to host the DOS application
your folks use on a network server.  Does it ever *change*? Is there a
reason you and your coworkers can't each have a local copy you run
from your own PC, without needing to access a network share?  You
likely want a master copy on a network share as a backup, but I see no
need to load and run if across the network.

Tere may be specific things about the DOS app that will be problematic
herfe, but right now it sounds like you are way overthinking the
problem.
__
Dennis


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

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 
> 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.
> 

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Liam Proven]

On Sun, 27 Feb 2022 at 19:54, Sean Warner  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?

-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Thanks Ralf,

 

I’ve spent many hours today working on this.

 

I found this site with links to VHD files that can be opened in Virtualbox. Out 
of desperation I downloaded FreeDOS1.2net.vhd.zip

https://www.lazybrowndog.net/freedos/virtualbox/?page_id=437#comment-6783

 

Well I haven’t discovered what this image is doing that my own image isn’t but 
somehow the NET VIEW command does now work… well except it doesn’t really… it 
shows a list of servers in the workgroup that is called: WORKGROUP. I am 
sharing out a directory in my Win 10 Pro host with access permissions to 
EVERYONE but when I try to connect to that from freedos like this:

 

# net use g: \\servername\sharename  

 

I get this error message:

 

Error 53: The Computer name specified in the network path cannot be located.

 

Despite the fact that “servername” appears when I run # net view ???

 

Earlier I made changes to Win 10 local policy settings as well as enabling 
SMBv1 and now other Samba shares I have in Win File Explorer Network section 
are not opening… maybe the config files of those samba servers need to be 
configured to allow SMBv1 now or something.

 

If you get it working can you please let us know?? Thank you.

 

Sean

 

From: Ralf Quint [mailto:freedos...@gmail.com] 
Sent: 28 February 2022 00:48
To: freedos-user@lists.sourceforge.net
Subject: Re: [Freedos-user] Looking for easy to follow instructions on how to 
connect to Samba share

 

On 2/27/2022 3:25 PM, Sean Warner wrote:

 

I have enabled SMBv1 in Win 10 and enabled file and printer sharing.

Also in Win 10 Function Discovery Provider Host and Resource Publication are 
both enabled and running.

That simply might not work. I have similar problems were for a while still, I 
have to support a Windows 2003 server in an environment where all user 
workstations are on Windows 10 Pro. It is kind of random if those clients are 
able to access a SMB 1. share on that Windows 2003 server or not. I have spend 
literally days trying to come up with working solution, NOTHING that I have 
found in regards to enable SMB 1.x on Windows 10 or newer (Windows 11, Server 
2016/2019,...) is working reliably...

Ralf

 

 


 

 Image removed by sender.

Virus-free.  

 www.avast.com 

 

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Ralf Quint]

On 2/27/2022 3:25 PM, Sean Warner wrote:


I have enabled SMBv1 in Win 10 and enabled file and printer sharing.

Also in Win 10 Function Discovery Provider Host and Resource 
Publication are both enabled and running.


That simply might not work. I have similar problems were for a while 
still, I have to support a Windows 2003 server in an environment where 
all user workstations are on Windows 10 Pro. It is kind of random if 
those clients are able to access a SMB 1. share on that Windows 2003 
server or not. I have spend literally days trying to come up with 
working solution, NOTHING that I have found in regards to enable SMB 1.x 
on Windows 10 or newer (Windows 11, Server 2016/2019,...) is working 
reliably...


Ralf



--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

OK,

 

Following on from my earlier post.

 

To recap:

I am using FreeDOS v1.2 in Virtualbox on Win 10 Pro.

 

I have installed the NIC driver and MS Client 3.0 and now have a C:\NET
directory and can use the NET command to do: NET USE and NET VIEW.

 

However when I try the net view command in freedos each time I get:

Error 6118 - The list of servers for this workgroup is not currently
available.

 

I have enabled SMBv1 in Win 10 and enabled file and printer sharing.

Also in Win 10 Function Discovery Provider Host and Resource Publication are
both enabled and running.

 

Networking is working in FreeDOS and I can ping FreeDOS from the Windows 10
host and vica versa. Although Name resolution is not working from FreeDos to
Win 10.

 

And advice really appreciated!

 

Sean

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Looking for easy to follow instructions on how to connect to Samba share

[Sean Warner]

Hello,

 

I installed FreeDOS 1.2 today in Virtualbox on Win 10.

 

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.

 

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 ??

 

Do I need to install the NIC driver and MS Client 3.0 in order to get the
net use command to work? 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.

 

Any help much appreciated!

 

Sean

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user