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

[Freedos-user] FreeDOS on Vinyl

[Jerome Shidel]

Hi all, 

I don’t know if you’ve seen this or not.

Booting FreeDOS from a vinyl record. It was mentioned on Hack a Day episode 95, 
starting just before the 13 minute mark 
https://hackaday.com/2020/11/27/hackaday-podcast-095-booting-freedos-from-a-vinyl-record-floating-on-mushrooms-and-tunneling-through-a-living-room/
 

 

There is also a quick article and video of the boot at 
https://hackaday.com/2020/11/23/booting-a-pc-from-vinyl-for-a-warmer-richer-os/ 

 

This reminds me so much of the days I used to load programs from cassette tape. 

:-)


___
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]

Liam,

> On Tue, 1 Mar 2022 at 20:02, Bret Johnson  wrote:
>>
>> Actually, no it's not.  It's fairly easy with System Commander.  And AFAIK, 
>> System Commander is the only multi-boot manager that works this way 
>> (manipulating the boot files instead of manipulating disks or partitions).  
>> Both approaches have advantages and disadvantages.

> That's not the point here.

> Can you roll back changes? Can you make a snapshop of one system and
> then revert to it? Can you duplicate a system and send it to someone?
> Can you keep backups of just one system? Can you store backups on a
> server or a removable drive?

> All those are trivially easy with VMs.

just about everything above is close to trivial. this is DOS, and
XCOPY (or ZIP) will do all of the above.

now YOU explain to the rest of the world how to keep all the different
systems synchronised. given that there will never be a direct
communication between different VMs. fixing a program requires synching
this for multiple VMs.

VMs are very useful, and Bret's approach might even be to a *single*
virtual machine.

but Bret's problem is to have ONE program (and possibly one batch file) to
be tested against multiple OS versions without too much fuss.

your approach doesn't help at this. just shut up.

Tom



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

Re: [Freedos-user] ECHO vs @ECHO

[Liam Proven]

On Tue, 1 Mar 2022 at 20:02, Bret Johnson  wrote:
>
> Actually, no it's not.  It's fairly easy with System Commander.  And AFAIK, 
> System Commander is the only multi-boot manager that works this way 
> (manipulating the boot files instead of manipulating disks or partitions).  
> Both approaches have advantages and disadvantages.

That's not the point here.

Can you roll back changes? Can you make a snapshop of one system and
then revert to it? Can you duplicate a system and send it to someone?
Can you keep backups of just one system? Can you store backups on a
server or a removable drive?

All those are trivially easy with VMs.

> As are QEMU

Can with hardware assist run native code, but that is harder. Works
with KVM on Linux to do it, but also harder.

>  BOCHS

Not the same thing. This is an emulator.

> PCem

Also an emulator, not a VM. Also no longer maintained.

DOSbox is also an emulator.

These are not the same sort of tool as the 2 I mentioned, which I
picked for good reasons. They are true hypervisors, they run real
unmodified OSes at full native speed, and they do not not require any
particular host OS.


>  All the VM's have advantages and disadvantages in various respects.

3 of the things you mentioned are not VMs. This makes me suspect that
perhaps you are not as familiar with this tech as you think you are,
and I urge you to at least evaluate it.

> In addition to the VMs mentioned above, I also have others including VMWare 
> and DOSBox and do tests with all of them.

DOSbox is not a VM.

>  VMWare and DOSBox are somewhat unique in that they can mount physical hard 
> drives instead of just virtual hard drives.

As can VirtualBox.

https://www.virtualbox.org/manual/ch09.html#rawdisk

> There are lots of different ways to "skin the cat" and there is not one 
> "correct" way.  There are tradeoffs and problems with every approach.  But, 
> for what I'm trying to accomplish, I think my setup is better (at least 
> easier to track and maintain) than what you're recommending.

I am not saying there isn't. I am saying that there are easier ways
than a tool you happen to know well and be familiar with. I am not
telling you you're wrong or anything, just suggesting something to
make life easier.

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

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