Re: [Freedos-user] Networking FreeDOS 1.3 on QEMU

I've found that the ADM PCNet adaptor in QEMU (-device pcnet) with the matching DOS drivers work well under FreeDOS. I wasn't able to get any of the other QEMU emulated ethernet devices to work properly under DOS. I spent a lot of time fighting with the Intel adaptors - it seems the QEMU

Re: [Freedos-user] Shared folders in VirtualBox: Freedos-user Digest, Vol 2235, Issue 1

A simple way to move files into a Virtualbox FreeDOS instance under Windows is to just use a separate virtual hard disk. A VHD disk file can be created in Windows using standard Windows-provided disk utilities (Virtualbox supports the VHD disk format as do most other virtualizers like Hyper-V and

Re: [Freedos-user] how to get dosemu working under ubuntu installed in wsl

ut I have it all worked out. - Darrin On Mon, Mar 14, 2022 at 6:41 PM Liam Proven wrote: > On Mon, 14 Mar 2022 at 21:29, Darrin M. Gorski wrote: > > > > > Same _time_? Ek! That sounds like a recipe for file corruption. > > > No, not tried and don't want to.

Re: [Freedos-user] how to get dosemu working under ubuntu installed in wsl

> Other than that I don't really consider dosemu (or DOSBox) anything > other than a "Virtual Machine" with some DOS-specific knacks. Or rather, "a 'virtual machine' that only supports DOS". - Darrin On Mon, Mar 14, 2022 at 4:13 PM C. Masloch wrote: > On at 2022-03-14 18:47 +0100, Liam

Re: [Freedos-user] how to get dosemu working under ubuntu installed in wsl

> Same _time_? Ek! That sounds like a recipe for file corruption. > No, not tried and don't want to. But surely that isn't what you meant? Yes, that's exactly what I mean - concurrency. My DOS use case is a multi-node BBS which needs a (safe) shared file system. (solved with MSNET and

Re: [Freedos-user] how to get dosemu working under ubuntu installed in wsl

You can also do that with qemu: -drive format=raw,file=fat:rw:$HOME/shared The QEMU docs state that the FAT is created at startup - so any new files added on the linux side won't appear to DOS after booting However, new files created from DOS will update the in-memory FAT and thus appear to DOS

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

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

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

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 unneces

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

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

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

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

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.

Re: [Freedos-user] Why do you use DOS

That makes great sense - learning! Thanks for the reply, the detail, and the great links. - Darrin On Sat, May 15, 2021 at 12:33 PM Robert Riebisch wrote: > Hi Darrin, > > > How is EIDL (claims to mimic IDLE.COM ) different from > > FDAPM (which is basically POWER.EXE)? > >

Re: [Freedos-user] Why do you use DOS

> There also is my tiny EIDL: How is EIDL (claims to mimic IDLE.COM) different from FDAPM (which is basically POWER.EXE)? I'm curious to know the differences between all of the solutions really. But I'm mostly curious why (freedos related) FDAPM didn't work for you? (worked great for me!)

Re: [Freedos-user] Windows 95

I'd recommend QEMU for running FreeDOS on Raspberry Pi (RPI). Personally, I prefer it for x86 too. I run multiple qemu-based x86 FreeDOS nodes (sometimes 6 or more) on a single RPI-4 with plenty of CPU cycles to spare. Using APM aware software in FreeDOS (like FDAPM) really helps with CPU usage,

Re: [Freedos-user] (no subject) - ems support

It's always nice to have a link too: https://www.japheth.de/Jemm.html On Wed, Sep 30, 2020 at 8:12 AM Eric Auer wrote: > > does freedos support ems and if so, how would i go about enabling it? > > you simply load himemx and jemm386 (or jemmex, which combines both). > > they both come with

Re: [Freedos-user] command.com exit status

that is set to zero, a literal zero. https://github.com/FDOS/freecom/issues/22 - Darrin On Wed, Apr 29, 2020 at 2:52 AM Rugxulo wrote: > Hi, > > On Sun, Apr 26, 2020 at 2:42 PM Darrin M. Gorski > wrote: > > > > > Like what other command processors? > > > >

Re: [Freedos-user] command.com exit status

> Like what other command processors? All of them. MS-DOS, 4DOS (which is the one I've switched to for now, despite it being a bit slow). I'm running in QEMU on a pi4, so disk IO can be painful. 4DOS.COM is 5 times larger than COMMAND.COM. I ran these batch files under MS-DOS back in the

[Freedos-user] command.com exit status

Hi All, Wondering why FreeDOS COMMAND.COM doesn't exit with ERRORLEVEL like other command processors. main() in command.c ends with "return 0" where it should really be "return errorlevel". This way error codes are returned to the calling shell (or other program). For my purposes it is a