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

Re: [Freedos-user] ECHO vs @ECHO

[tom ehlert]

>> in addition, neither I nor you know if 'CTTY NUL' works on MSDOS 3.0

> The original requirement was MSDOS <3.30.
> I tested with MSDOS 3.21 and it worked.

> Test with MSDOS 3.0 was okay too.

correcting myself, CTTY NUL probably always worked, from MSDOS 1.0,
as MSDOS was supposed (I never tested) to be able to run on a serial
terminal.

so

   CTTY COM1

would redirect input and output to COM1. and you could move the cursor
on the screen (and other stuff) using ESCape sequences. ANSI.SYS was used
to simulate this (I think a VT100 terminal) on the CGA display, so
software could be written that would work 'everywhere'.

Tom





___
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

Re: [Freedos-user] ECHO vs @ECHO

[Robert Riebisch]

Hi tom,

>> Once you have debugged ALL your batch files you can place `CTTY
>> NUL' before the command(s) and `CTTY CON' after to avoid output to screen.
> 
> 
> excellent idea.
> 
> now you have exchanged the annoying
> 
>   echo off
> 
> for the much better
> 
>   CTTY NUL

Indeed.

> in addition, neither I nor you know if 'CTTY NUL' works on MSDOS 3.0

The original requirement was MSDOS <3.30.
I tested with MSDOS 3.21 and it worked.

Test with MSDOS 3.0 was okay too.

But as you already mentioned above, it won't help to prevent display of
the first line of a batch file.

Cheers,
Robert
-- 
  +++ BTTR Software +++
 Home page: https://www.bttr-software.de/
DOS ain't dead: https://www.bttr-software.de/forum/


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

Re: [Freedos-user] ECHO vs @ECHO

[tom ehlert]

Hallo Herr Bob Pryor,

am Sonntag, 27. Februar 2022 um 06:44 schrieben Sie:

> Once you have debugged ALL your batch files you can place `CTTY
> NUL' before the command(s) and `CTTY CON' after to avoid output to screen.


excellent idea.

now you have exchanged the annoying

  echo off

for the much better

  CTTY NUL


in addition, neither I nor you know if 'CTTY NUL' works on MSDOS 3.0

Tom



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

Re: [Freedos-user] Git for DOS?

[Tomas By]

On Sun, 27 Feb 2022 03:41:38 +0100, Brandon Taylor wrote:
> is there any way I can use Git on FreeDOS [?]


Yes, apparently:
https://github.com/openssl/openssl/blob/master/NOTES-DJGPP.md

/Tomas


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

Re: [Freedos-user] Git for DOS?

[Tomas By]

On Sun, 27 Feb 2022 09:36:46 +0100, Tomas By wrote:
> 
> On Sun, 27 Feb 2022 03:41:38 +0100, Brandon Taylor wrote:
> > is there any way I can use Git on FreeDOS [?]
> 
> Yes, apparently:
> https://github.com/openssl/openssl/blob/master/NOTES-DJGPP.md


Hmm, no I was too quick there.

Anyway, RCS works.

/Tomas


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

Re: [Freedos-user] Git for DOS?

[Regan Russell]

Hi Brandon,

CVS runs on DOS I think...
There is a CVS to SVN converter.
There is a SVN to git converter.
This might​​ work. But with this many moving parts it is unlikely.
There was also SCCS and RCS but I've touched neither in like maybe 20 or 30 
years.

The other and possibly easier option might be to have a network drive and do 
all the development on the DOS machine, then transfer the code on another 
machine and do source code control on the other machine (Linux, Mac, Windows, 
etc)

Hope this helps.


From: Brandon Taylor 
Sent: Sunday, 27 February 2022 1:41 PM
To: Freedos-user@lists.sourceforge.net 
Subject: [Freedos-user] Git for DOS?

This may sound odd, but is there any way I can use Git on FreeDOS, either 
natively (from COMMAND.COM) or from some third-party command interpreter (e.g. 
bash)?

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