Re: [Freedos-user] Looking for easy to follow instructions on how to connect to Samba share
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
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
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
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
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
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
> 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
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,
[Freedos-user] Too difficult
I'm wondering if BlockDrop still gets to difficult too fast. Getting past level 10 is really hard. And level 11, will probably eat all remaining lives. At level 11, there are still a bunch of other color and special blocks that haven't even appeared yet. Have you tried it? What do you think? Should I slow the difficulty increase even further? After all, if you like to torment yourself, you can skip a level before it starts by pressing the TAB key. You don’t get any points for that level, but thats up to you. Also, within limits restricted by your level, you can usually speed up and slow back down using +/- keys. Has no effect on score and it won’t slow below a minimum for a level. Mostly, that is to keep the lower levels from being too boring for experienced players. Opinions? ___ 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
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] FreeDOS on Vinyl
It seems that vinyl booted FreeDOS feels richer, warmer, more open, because of the grooves on the record allow for a more resonant quality. El mié, 2 mar 2022 a las 22:11, Jerome Shidel () escribió: > 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 > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
