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
qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq
OK G: \\BBSMAIN\SHARED
The command completed successfully.
C:\>
- Darrin
On Thu, Mar 3, 2022 at 5:33 AM Sean Warner <[email protected]> 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, <[email protected]> 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 <[email protected]>
>> 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 108K 92K 16K
>> Reserved 277K 277K 0K
>> Extended (XMS) 129,920K 21,102K 108,818K
>> ---------------- -------- -------- --------
>> Total memory 130,944K 21,675K 109,269K
>>
>> Total under 1 MB 747K 296K 451K
>>
>> Total Expanded (EMS) 8,576K (8,781,824 bytes)
>> Free Expanded (EMS) 8,192K (8,388,608 bytes)
>>
>> Largest executable program size 435K (445,776 bytes)
>> Largest free upper memory block 13K ( 13,728 bytes)
>> FreeDOS is resident in the high memory area.
>> C:\>
>> C:\>type config.sys
>> !SWITCHES=/F
>> !DOS=HIGH,UMB
>> !DOSDATA=UMB
>> !FILES=40
>> !BUFFERS=20
>> !LASTDRIVE=Z
>>
>> MENUCOLOR=7,0
>> MENUDEFAULT=1,5
>> MENU 1 - Start a standard BBS node
>> MENU 2 - Start in setup/configuration mode
>> MENU 3 - Don't load anything
>>
>> 1?SET CONF=BBSNODE
>> 2?SET CONF=SETUP
>>
>> 12?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
>> 12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024
>> /P=C:\AUTOEXEC.BAT
>> 12?DEVICEHIGH=C:\NET\ifshlp.sys
>>
>> 3?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /D
>> 3?SET PATH=C:\FDOS\BIN
>>
>> C:\>type autoexec.bat
>> @ECHO OFF
>>
>> PATH C:\NET;C:\FDOS\BIN;C:\UTILS
>> PROMPT $P$G
>> SET TEMP=C:\TEMP
>>
>> LH FDAPM APMDOS
>>
>> IF "%CONF%"=="BBSNODE" GOTO SKIPCD
>>
>> DEVLOAD /H /Q C:\FDOS\BIN\UDVD2.SYS /D:FDCD0001
>> SHSUCDX /QQ /~ /D:FDCD0001
>>
>> :SKIPCD
>>
>> LH LBACACHE 20480
>> LH SHARE
>>
>> C:\NET\net initialize
>> C:\NET\netbind.com
>> C:\NET\umb.com
>> C:\NET\tcptsr.exe
>> C:\NET\tinyrfc.exe
>> C:\NET\nmtsr.exe
>> C:\NET\emsbfr.exe
>> C:\NET\net start
>>
>> IF NOT "%CONF%"=="BBSNODE" GOTO END
>>
>> :BBS
>> echo Starting BBS
>> CD \BBS
>> TAG
>> if errorlevel 255 goto END
>> goto BBS
>>
>> :END
>>
>> C:\>
>> C:\>fdapm /poweroff
>> Performing action: POWEROFF
>> Turning OFF system...
>> Calling int28 so MSCLIENT can flush...
>> Resetting DOS filesystem and BIOS disk handler... done.
>> Giving disk handlers some time..
>>
>>
>> On Tue, Mar 1, 2022 at 9:22 AM Sean Warner <[email protected]> wrote:
>>
>>>
>>> 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
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>> _______________________________________________
>> Freedos-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> _______________________________________________
> Freedos-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
