Re: [Freedos-devel] Back at it with DOG

2024-05-31 Thread Wolf Bergenheim via Freedos-devel
On Fri, May 31, 2024 at 12:56 AM Eric Auer via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > Hi and welcome back, Wolf :-) > Thanks Eric, I remember you from ~20 years ago! :D > edit code on linux and then build and test in a QEMU box which is > > constantly running. :) > > Time

Re: [Freedos-devel] Back at it with DOG

2024-05-31 Thread Mercury Thirteen via Freedos-devel
Welcome back! :D My setup is a Linux desktop machine under which I edit code with Sublime Text and compile with the Linux versions of NASM and/or Watcom C, for whichever the current project calls. I test frequently while implementing a new feature or what-have-you, and for that I use DOSBox. M

Re: [Freedos-devel] Back at it with DOG

2024-05-30 Thread Eric Auer via Freedos-devel
Hi and welcome back, Wolf :-) I used to map a virtual drive to a folder on Linux - but like you found, I sometimes had problems with that (not all the time, just sometimes) so I stopped doing that. When I need to get access to my virtual drive, I use guestmount from the libguestfs package to "

Re: [Freedos-devel] Back at it with DOG

2024-05-30 Thread Wolf Bergenheim via Freedos-devel
On Thu, May 30, 2024 at 4:50 PM Steve Nickolas via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Thu, 30 May 2024, Wolf Bergenheim via Freedos-devel wrote: > > > I'm using Borland C++ 3.1 for now as that's the compiler I used 22 years > > ago... Looks like porting to Watcom will

Re: [Freedos-devel] Back at it with DOG

2024-05-30 Thread Wolf Bergenheim via Freedos-devel
On Thu, May 30, 2024 at 4:25 PM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Wed, May 29, 2024 at 9:53 PM Wolf Bergenheim via Freedos-devel > wrote: > > > > What do your dev environments look like? How do you make an efficient > > edit-build-test cycle? Has anyone

Re: [Freedos-devel] Back at it with DOG

2024-05-30 Thread Steve Nickolas via Freedos-devel
On Thu, 30 May 2024, Wolf Bergenheim via Freedos-devel wrote: I'm using Borland C++ 3.1 for now as that's the compiler I used 22 years ago... Looks like porting to Watcom will require a bit of work... It is something I want to do eventually, I think. Just need to read up on the inline assembler

Re: [Freedos-devel] Back at it with DOG

2024-05-30 Thread Jim Hall via Freedos-devel
On Wed, May 29, 2024 at 9:53 PM Wolf Bergenheim via Freedos-devel wrote: > [..] > Now a question: > What are your dev setups like? I'm on a linux host computer and I've > been using both DOSBox and QEMU to build and test in. I find though > that it's a bit of a chore, since DOSBox crashes randomly

Re: [Freedos-devel] Back at it with DOG

2024-05-30 Thread Wolf Bergenheim via Freedos-devel
On Thu, May 30, 2024 at 11:52 AM Bernd Böckmann via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > Hi Wolf, > > welcome to the mailing list. Great to hear you started working again on > DOG. Putting it on Github (or some other publicly accessible repo) sounds > like a good idea :) >

Re: [Freedos-devel] Back at it with DOG

2024-05-30 Thread Bernd Böckmann via Freedos-devel
Hi Wolf, welcome to the mailing list. Great to hear you started working again on DOG. Putting it on Github (or some other publicly accessible repo) sounds like a good idea :) Looking at https://gitlab.com/FreeDOS/util/dog, that seems to be version 0.83c. Is this the latest publicly available v

[Freedos-devel] Back at it with DOG

2024-05-29 Thread Wolf Bergenheim via Freedos-devel
Hi everyone, After ~22 years I got back into coding on DOG. I'm working my way towards a new release, 0.8.4b, in the ~soon timeframe. I'm also working on moving the source code to GitHub and fixing the website. It had apparently broken several years ago... So far I've been fixing the code and imp