Re: [Freedos-user] Report back: QEMU - Max size of Linux access folder

[Louis Santillan via Freedos-user]

You might try updating the 2nd drive's argument to `-drive
file=fat:rw:dosfiles/,format=raw,cache=writeback`.  [0]

[0]
https://manpages.debian.org/unstable/qemu-system-x86/qemu-system-i386.1.en.html

On Wed, Mar 13, 2024 at 10:29 AM h...@iafrica.com  wrote:

> I removed CDROM and Sound support. I moved all program directories from
> the D: drive (FAT16 access drive) to the C: drive and this appears to have
> improved the speed to about 7x slower. I then checked to see if KVM was
> running and it was.
> The command line I was using to invoke the emulator was:-
> $ qemu-system-i386 -m 32 -rtc base=localtime -drive
> file=dos.img,index=0,media=disk,format=raw -drive
> file=fat:rw:dosfiles/,format=raw -boot order=c -display sdl
> I then added "-enable-kvm"
> eg.
> $ qemu-system-i386 -m 32 -rtc base=localtime -drive
> file=dos.img,index=0,media=disk,format=raw -drive
> file=fat:rw:dosfiles/,format=raw -boot order=c -display sdl -enable-kvm
> This has moved speed to parity to 2x slower which is excellent.
>
> I have switched to the 4DOS shell with no speed penalty. In 4DOS I have
> always used Function key F11 to toggle between two directories. This does
> not work as QEMU appears to use F11 to toggle between current window size
> and full screen. I have searched on the Internet but not found any
> reference to the use off F11 in QEMU. Anyone have any ideas how to reassign
> the key? I suspect it is hard coded?
>
> Using drive D:, the access drive, appears to be problematic. Best not to
> use it other than transfer files.
>
>
> On 2024/03/13 18:53, Louis Santillan wrote:
>
> What was the qemu command you used?  It sounds like you paying a double
> penalty somewhere for how you’re get the disk image into qemu.  Loopback
> devices pay some penalty.  10x seems like some option is missing to improve
> performance.
>
> On Wed, Mar 13, 2024 at 2:57 AM hms--- via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
>
>> Hi All
>> Some feedback. Creating a 2G image allowed me to assemble source code
>> correctly. The only penalty being speed. About 6 to 11 times slower than
>> running DOS under XP.
>> I mounted the image and copied source files from backup directory to
>> mounted C: drive.
>> Lubuntu Linux error on boot up resolved. QEMU-KVM had crashed on two
>> occasions and logs created in the /dev/crash directory. Deleting the log
>> files in /dev/crash removed the error message on start up.
>>
>> I used "mount" instead of "guestmount". Steps below.
>>
>> Display start sector and sector size:
>> $ fdisk -l dos.img
>> Eg. 63 and 512 bytes. Offset = 63 * 512 = 32256
>>
>> Create directory:
>> $ mkdir /tmp/dos
>>
>> Mount image in directory:
>> $ sudo mount -o loop,offset=32256 dos.img /tmp/dos
>>
>> Copy directories:
>> Eg.
>> $ cp -r /temp/source-dir  /tmp/dos
>>
>> Unmount image:
>> umount /tmp/dos
>>
>> John
>>
>>
>> ___
>> 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] Report back: QEMU - Max size of Linux access folder

[Louis Santillan via Freedos-user]

What was the qemu command you used?  It sounds like you paying a double
penalty somewhere for how you’re get the disk image into qemu.  Loopback
devices pay some penalty.  10x seems like some option is missing to improve
performance.

On Wed, Mar 13, 2024 at 2:57 AM hms--- via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hi All
> Some feedback. Creating a 2G image allowed me to assemble source code
> correctly. The only penalty being speed. About 6 to 11 times slower than
> running DOS under XP.
> I mounted the image and copied source files from backup directory to
> mounted C: drive.
> Lubuntu Linux error on boot up resolved. QEMU-KVM had crashed on two
> occasions and logs created in the /dev/crash directory. Deleting the log
> files in /dev/crash removed the error message on start up.
>
> I used "mount" instead of "guestmount". Steps below.
>
> Display start sector and sector size:
> $ fdisk -l dos.img
> Eg. 63 and 512 bytes. Offset = 63 * 512 = 32256
>
> Create directory:
> $ mkdir /tmp/dos
>
> Mount image in directory:
> $ sudo mount -o loop,offset=32256 dos.img /tmp/dos
>
> Copy directories:
> Eg.
> $ cp -r /temp/source-dir  /tmp/dos
>
> Unmount image:
> umount /tmp/dos
>
> John
>
>
> ___
> 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] Adapter PCMCIA to CF

[Louis Santillan via Freedos-user]

I tested a generic/brandless/labelless/white label 5 pack of CF PCMCIA
adapters on an old Epson 286 laptop & Librex 386 laptop.  They worked as
generic IDE drives and I was able to format an old 8MB CF card as FAT16
with DOS.

They looked like the ones here -
https://www.ebay.com/sch/i.html?_nkw=PCMCIA+Compact+Flash+CF+Card+Reader+Adapter+for+Laptop

They could be slightly cheap on aliexpress if you have patience for
delivery -
https://www.aliexpress.us/w/wholesale-PCMCIA-Compact-Flash-CF-Card-Reader-Adapter-.html

On Thu, Mar 7, 2024 at 3:47 AM Ian Park via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> The CF to PCMCIA adapter is purely mechanical - you don't need any driver
> software. I used to use one in my Psion Series 7.
>
> HTH
>
> Ian
>
> Ian Park
> Email: i.d.c.p...@chalmers-park.name
> Mobile: +44 (0) 7785 300290
> Sent from my Galaxy
>
>
>  Original message 
> From: Manuel Sobral via Freedos-user 
> Date: 07/03/2024 11:07 (GMT+00:00)
> To: freedos-user@lists.sourceforge.net
> Cc: Manuel Sobral 
> Subject: [Freedos-user] Adapter PCMCIA to CF
>
> Hello everyone,
>
> First time using a mailing list, if I am doing something wrong please let
> me know.
>
> I recently purchased an IBM Thinkpad 370C and am running FreeDOS 1.3.
>
> My question is, is it possible to use a PCMCIA to Compact Flash adapter?
> Do I have to install the drivers or is it already included with FreeDOS? Do
> I have to buy an old PCMCIA adapter? Does it work with any Compact Flash?
>
> If it only works with certain adapters or Compact Flash, could someone
> provide me with already tested adapters and CF models?
>
> Thank you
> Manuel
> ___
> 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] Ramdisk

[Louis Santillan via Freedos-user]

Best to share your CONFIG.SYS/FDCONFIG.SYS and AUTOEXEC.BAT/FDAUTO.BAT file
contents.

On Sun, Mar 3, 2024 at 3:14 PM Norby Droid via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> I am usin a msi computer to run FreeDos 1.3 and setup a ramdrive.
>
> Reading through the docs I setup fdconfig with srdxms.sys h: srdummy,sys
> h: and then in fdauto I run srdisk h: 51200.
>
> If I try usin the srdems.sys after chioosin option 3 for ems the computer
> just stalls and I have to reboot the system.
>
> The prooblem I am havin is it shows that I have H: as a ramdisk, but when
> I try to go to H: it tells me that H: is an invalid drive.  I forst tried
> with R: but that also gives invalid fdrive when I tryo to go to it.
>
> Maybe it is my setup?  Currently I have an 80gb drive (probably overkill
> for DOS).  It has 4 partitions 3@20GB and the last one woth remainin
> space.
>
> There is 6GB ram instaled in the system.  Can I setup 2 or 4 gb to a drive?
>
> Thank you.
> ___
> 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] GNU Cobol on the FreeDOS ....

[Louis Santillan via Freedos-user]

If you’re ok with a Linux cross compiler, you can add “cobol” here (
https://github.com/andrewwutw/build-djgpp/blob/master/script/common-settings#L6)
and then build on a Linux box.  Have you tried that?

In Fedora I did,
# sudo dnf install g++ gcc unzip bison flex make texinfo patch zlib-devel
curl wget perl-File-Compare automake
# DJGPP_PREFIX=`pwd` time -p bash build-djgpp.sh 12.1.0
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Using HDMI monitor and USB keyboard/mouse on FreeDOS

[Louis Santillan via Freedos-user]

You inspired me to build one myself.  I’m awaiting a few parts now.

On Tue, Jan 30, 2024 at 12:15 PM Bill Gee via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> An update for the group -
>
> Today I built an adapter that translates USB keyboard and mouse to PS/2
> signals.
>
> https://docs.pikvm.org/pico_hid_bridge/
>
> It works great!  I can get into BIOS setup with it.  CTL-ALT-DEL works.
> I cannot see any problems with response time.  Wolfenstein runs just fine.
>
> I had to buy one PS2 cable and the logic level converter.  I already had
> a Pico, one PS/2 cable and the micro-USB to USB-A adapter.
>
> Next to try is a different display adapter.
>
> ===
> Bill Gee
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] shutdown and USB Stick ?

[Louis Santillan via Freedos-user]

FAT is always a finicky filesystem, especially if you're utilizing a
caching or BIOS emulation for USB HDDs.  Are you using a caching program
like lbacache, cdrcache, smartdrv, etc?

On Mon, Jan 29, 2024 at 7:11 AM Thomas Cornelius Desi via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> I boot FD from a USB Stick.
> Can using »shutdown« command prevent that a bootable USB Stick with FD
> becomes unusable? (Happened last week.)
>
> add: is the shutdown command also working in the previous FD version?
> (Which I am normally using. I never used the »shutdown«  command before.
> Just switch off the computer )
>
>
> T.
>
> ___
> 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] One use case for FreeDos

[Louis Santillan via Freedos-user]

You may also be interested in the Blocek editor -
http://www.laaca.borec.cz/blocek/#blocek

On Mon, Jan 29, 2024 at 7:55 AM Thomas Cornelius Desi via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Apropos authoring on DOS Software: As I was looking for someting nifty
> that would enhance my writing workflow on the computer, I decided for
> VDE by Eric Meyer writer. ( have a look here:
> https://archive.org/details/vde-197 )
>  It actually does sort-of-UTF8 encoding which in my case (German Umlaute
> äöü ß) is important.
> And yes: why has it become so cumbersome to switch of
> internet-connections?!
>
> and let’s mention »Captain Blackbeard« editor. Also great!
>
>
> > On 29.01.2024, at 16:44, Jim Hall via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
> >
> > Mart Zirnask wrote:
> >>> As for writers with DOS, I recalled and managed to dig up a video with
> >>> Philip Roth using a standing desk and a Blue DOS Screen - is this also
> >>> Wordstar? https://www.youtube.com/watch?v=eBlVEcMSOGw=201
> >>>
> >>> The video is dated 2004, though - back then, I imagine it was not that
> >>> uncommon yet to use a DOS wordprcessor.
> >
> > Louis Santillan wrote:
> >>
> >> That looks like Wordperfect for DOS.
> >
> > Agreed, that's definitely WordPerfect for DOS at 3:30 in the video.
> > And a few seconds earlier at 3:25, you can see the WordPerfect
> > template over the Model M function keys.
> >
> >
> > ___
> > 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] One use case for FreeDos

[Louis Santillan via Freedos-user]

That looks like Wordperfect for DOS.

On Sat, Jan 27, 2024 at 9:29 PM Mart Zirnask via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
[SNIP]

> As for writers with DOS, I recalled and managed to dig up a video with
> Philip Roth using a standing desk and a Blue DOS Screen - is this also
> Wordstar? https://www.youtube.com/watch?v=eBlVEcMSOGw=201
>
> The video is dated 2004, though - back then, I imagine it was not that
> uncommon yet to use a DOS wordprcessor.
>
> Greetings from Estonia,
> Mart
>
> 1: http://tinycorelinux.net/
> 2: http://tedfelix.com/qbasic/ (Haven't made my translation public yet
> - nor informed the author -, but eventually might do this as well.)
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Using HDMI monitor and USB keyboard/mouse on FreeDOS

[Louis Santillan via Freedos-user]

The quality of the VGA to HDMI adapter isn't great but it works.  In
particular, on an HB8088 with an NEC v20 CPU & Chips 451 VGA there's large
banding and the signal seems to ripple on dark black.  On a Dell Optiplex
9020 with a Core i7-4790 the banding and ripple are reduced (probably a
better signal coming out of the Intel HD's VGA port).  Even better, the
Optiplex has USB for Legacy Support, Legacy BIOS boot option, will boot DOS
off a FAT32 USB drive, has a really clean video signal if you use a
DisplayPort to HDMI adapter (last video).  Didn't have a chance to do
something like run PhilsComputerLab DOSBench suite but that could be next.
The DP to HDMI adapter happens to be a variant of this (
https://www.amazon.com/DisplayPort-Gold-Plated-Avacon-Display-Adapter/dp/B01FX3K7T2/).
A USB keyboard, mouse, DP-to-HDMI, USB drive, and 4GB or less RAM (9020 can
use 1GB & 2GB DDR3 DIMMs), you have a legacy free DOS machine (retro
rocket) for very little money.  You could even add a USB Floppy to the mix.

Videos on Google Drive (
https://drive.google.com/drive/folders/1JKjjNO2t7bu8rJYmbxRFRRhD3BEyUr7x?usp=sharing).
Apologies in advance for the poor narration, background noise, and lack of
video editing.  I rushed this out before leaving the house for the weekend.
I had planned to edit out the audio but ran out of time.  Video is still
"processing" by Google at the time of this writing.

On Fri, Jan 26, 2024 at 11:25 AM Felix Miata via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Bill Gee composed on 2024-01-26 12:59 (UTC-0600):
>
> > Go back to the original set of questions that started this ...  My
> > FreeDOS machine is plugged into a KVM switch which supports only VGA and
> > PS2.  In the near future - 6 months or so - that KVM must be upgraded to
> > support HDMI displays and USB keyboard/mouse.  In order to continue
> > using the FreeDOS machine, it also must support HDMI display and USB
> > keyboard/mouse.
>
> New day after long sleep. I forgot. :)
>
> > I could put it on a dedicated display, but there is no place in the
> > house to set it up that way.  The FreeDOS system has to live on my
> > computer rack.
>
> > I was leery when I bought the adapter, but I figured for $10 it was hard
> > to go far wrong.  It was worth a try.
>
> It still is worth trying, but with more skill applied, and almost
> certainly more
> money spent. :p Surely you're not the only one with similar configuration.
>
> I am able to avoid KVM issues with big physical desktop, 6 displays, 3
> full-time
> keyboards, 2 trackballs, one mouse, and a *lot* of cable switching, for
> 40+ PCs,
> normally with at most 3 up at once, occasionally a 4th, along with cable
> switching
> multiple times most days.
> --
> Evolution as taught in public schools is, like religion,
> based on faith, not based on science.
>
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata
>
>
> ___
> 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] Using HDMI monitor and USB keyboard/mouse on FreeDOS

[Louis Santillan via Freedos-user]

I used this adapter in the past (
https://www.amazon.com/gp/product/B07F1K3QQX/).  Tons of similar adapters
on eBay, Amazon, AliExpress.  Pretty sure it worked with an old Dell
monitor over HDMI.  I can try retesting it this weekend.


On Thu, Jan 25, 2024 at 7:54 PM Felix Miata via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Bill Gee via Freedos-user composed on 2024-01-25 12:20 (UTC-0600):
>
> > Lots of good graphics modes on that card you are using.  Problem is,
> > that all came from Linux.  What happens if you boot the system in
> > FreeDOS?  Will it show the POST?
>
> Turns out that PC had primary #2 allocated for FreeDOS, but it never got
> installed. It does have WinXP and MDOS 7.1, which boots just like PC DOS
> 2000 and older MDOS versions, same default 80x25 mode as for BIOS setup. I
> have very few "active" PCs with populated AGP slots. Most AGPs I have are
> in storage.
>
> The following, which like the prior, has WinXP and MDOS 7.1 but no
> FreeDOS, and boots BIOS and DOS in 80x25 text, has PCIe instead of AGP:
> # pinxi -CMSz --vs
> pinxi 3.3.31-70 (2024-01-23)
> System:
>   Kernel: 6.5.9-3-default arch: i686 bits: 32
>   Desktop: KDE Plasma v: 5.27.9 Distro: openSUSE Tumbleweed 20231126
> Machine:
>   Type: Desktop System: Dell product: OptiPlex GX280 v: N/A serial:
> 
>   Mobo: Dell model: N/A serial:  BIOS: Dell v: A07 date: 11/29/2005
> CPU:
>   Info: single core model: Intel Pentium 4 bits: 32 type: MT cache:
> L2: 1024 KiB
>   Speed (MHz): avg: 2793 min/max: N/A cores: 1: 2793 2: 2793
> # pinxi -Gaz
> Graphics:
>   Device-1: AMD RV516 [Radeon X1300/X1550 Series] vendor: Dell driver:
> radeon
> v: kernel alternate: amdgpu arch: Rage-7 code: R200 process: TSMC 150nm
> built: 2001-06 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
> active: DVI-I-1,VGA-1 empty: SVIDEO-1 bus-ID: 01:00.0 chip-ID:
> 1002:7183
> class-ID: 0300
>   Display: x11 server: X.Org v: 21.1.9 compositor: kwin_x11 driver: X:
> loaded: modesetting dri: swrast gpu: radeon display-ID: :0 screens: 1
>   Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 761x253mm (29.96x9.96")
> s-diag: 802mm (31.57")
>   Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: 
> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
> size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
> max: 1920x1200 min: 640x480
>   Monitor-2: VGA-1 pos: right model: Dell P2213 serial:  built:
> 2012
> res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
> diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
>   API: EGL v: 1.5 hw: drv: amd r300 platforms: gbm: egl: 1.4 drv: r300 x11:
> drv: swrast inactive: wayland
>   API: OpenGL v: 4.5 compat-v: 2.1 vendor: mesa v: 23.2.1 glx-v: 1.4
> direct-render: yes renderer: llvmpipe (LLVM 17.0.5 128 bits)
> device-ID: : memory: 1.42 GiB unified: yes
> # xrandr
> Screen 0: minimum 320 x 200, current 3600 x 1200, maximum 8192 x 8192
> DVI-I-1 connected primary 1920x1200+0+0 (normal left inverted right x axis
> y axis) 519mm x 324mm
>1920x1200 59.95*+
>1920x1080 59.9659.93
>1600x1200 60.00
>1680x1050 59.9559.88
>1400x1050 59.9859.95
>1600x900  59.9559.82
>1280x1024 60.02
>1440x900  59.90
>1400x900  59.9659.88
>1280x960  60.00
>1440x810  59.97
>1368x768  59.8859.85
>1280x800  59.9959.9759.8159.91
>1280x720  60.0059.9959.8660.0059.9459.74
>1024x768  60.0460.00
>960x720   60.00
>928x696   60.05
>896x672   60.01
>1024x576  59.9559.9659.9059.82
>960x600   59.9360.00
>960x540   59.9659.9959.6359.82
>800x600   60.0060.3256.25
>840x525   60.0159.88
>864x486   59.9259.57
>700x525   59.98
>800x450   59.9559.82
>720x480   60.0059.94
>640x512   60.02
>700x450   59.9659.88
>640x480   60.0060.0059.94
>720x405   59.5158.99
>684x384   59.8859.85
>640x400   59.8859.98
>640x360   59.8659.8359.8459.32
>512x384   60.00
>512x288   60.0059.92
>480x270   59.6359.82
>400x300   60.3256.34
>432x243   59.9259.57
>320x240   60.05
>360x202   59.5159.13
>320x180   59.8459.32
> SVIDEO-1 disconnected (normal left inverted right x axis y axis)
> VGA-1 connected 1680x1050+1920+0 (normal left inverted right x axis y
> axis) 473mm x 296mm
>1680x1050 59.95*+  59.88
>1400x1050 74.7659.98
>1600x900  59.9559.82
>1280x1024 75.0260.02
>1440x900  59.98
>1400x900  59.9659.88
>1280x960  60.00
>1440x810  59.97
>1368x768  59.88

[Freedos-user] Interesting Project: dosfetch like neofetch

[Louis Santillan via Freedos-user]

https://github.com/leahneukirchen/dosfetch

One of the hallmarks of modern Linux CLI environments differentiating the
various distro vendors is a linux tool called neofetch.  A tool
which probes the local environment will let you know some of the key
features or metrics of the local environment (CPU, RAM, DISK, NET usage, OS
flavor, CPU vendor, Hypervisor vendor) and pretty print that info (great
for CLI OS screen captures to make them nicer looking/more appealing).
Somewhat akin to a combination of `uname`, `top`, and others.

Jerome's V8 Power Tools (https://github.com/LoopZ/V8Power) also has some of
these features (I think) as well.

dosfetch seems to aspire to do the same for DOS as neofetch.
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] What DOS programs represent the 1980s and early 90s?

[Louis Santillan via Freedos-user]

On Mon, Jan 1, 2024 at 4:04 PM Jim Hall via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
[SNIP]

> (*) Did anyone else subscribe to a shareware catalog? I know you could
> dial into a BBS to find shareware apps, but I found a catalog that
> tested tons of shareware apps and games and listed the ones they
> thought were the best. You sent in an order with a


I subscribed to TigerDirect in the early to late 90s.  They initially
(during my subscription) offered 3.5” floppies, CDs with dozens to hundreds
of shareware apps, games, and utilities.  I still have a couple CDs on a
spindle somewhere in my office.  Eventually they pivoted to consumer PC
hardware and then finally focused on business hardware including off lease
hardware before getting bought out.

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

Re: [Freedos-user] Dunfield releases 40+ years of Source Code

[Louis Santillan via Freedos-user]

The manual is usually in the source zip or binary zip.  If not, reach out
to Dave and ask.

On Tue, Nov 7, 2023 at 3:15 AM hms--- via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> This is indeed a treasure trove of material.
> Does anyone know where to find the user manuals and binary files?
> John
>
> On 2023/11/06 05:32, Louis Santillan via Freedos-user wrote:
> > Dave Dunfield has released what he calls "40+ years of source code".
> >
> > https://www.vogons.org/viewtopic.php?f=7=97034
> > <https://www.vogons.org/viewtopic.php?f=7=97034>
> >
> > https://dunfield.themindfactory.com/dnldsrc.htm
> >
> > What I find most interesting is the source to his C compiler,
> > Micro-C.  Lots of other tools other bits that are new to me.
> >
> > The terms seem liberal but not quite OSS.
> > https://dunfield.themindfactory.com/dnld/sc/COPY.TXT
> >
> > Maybe in the line of BSD or MIT/X like licenses.
> >
> > If you would like to see the binary versions of some of these
> > projects, you can find them here.
> > https://dunfield.themindfactory.com/dnld.htm
> >
> >
> > ___
> > 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] Dunfield releases 40+ years of Source Code

[Louis Santillan via Freedos-user]

Dave Dunfield has released what he calls "40+ years of source code".

https://www.vogons.org/viewtopic.php?f=7=97034

https://dunfield.themindfactory.com/dnldsrc.htm

What I find most interesting is the source to his C compiler, Micro-C.
Lots of other tools other bits that are new to me.

The terms seem liberal but not quite OSS.
https://dunfield.themindfactory.com/dnld/sc/COPY.TXT

Maybe in the line of BSD or MIT/X like licenses.

If you would like to see the binary versions of some of these projects, you
can find them here.
https://dunfield.themindfactory.com/dnld.htm
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Networking on UTM

[Louis Santillan via Freedos-user]

Docs (
https://docs.getutm.app/settings-qemu/devices/network/network/#hardware)
say that the emulated network device is a  “virtio-net-pci” device.  Docs
also mention that the OS will require a driver for it.  virtio is a common
interface for modern Linux, Windows, and I think Mac OS VMs.  For DOS,
you’ll need to find a packet driver for it.  I’m not aware of any.

On Fri, Oct 27, 2023 at 6:33 AM Knedlik via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hello there!
>
> I’ve been venturing a bit into DOS world once again just for run, and it
> seems that my UTM virtual machine doesn’t automatically set up networking.
> I installed the networking packages from FDIMPLES, but when I boot the
> machine, I get „QEMU network detected“ and right after that „Physical
> hardware networking is not supported at this time“…
>
> Does anyone have an idea on how to solve this? I’m fine using FreeDOS
> without networking, but having to download stuff onto my Mac and then stick
> it into the VM can be a painful process…
>
> Thanks in advance,
> -Knedlik
>
> ___
> 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] quick help finding the dos driver for intel etherexpress pro 100+

[Louis Santillan via Freedos-user]

IIRC, there are some extra (Windows & OS/2) drivers and docs you can remove
from the package to make it fit on a floppy.  Try removing those folders
first.

On Tue, Oct 24, 2023 at 7:03 PM Karen Lewellen via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hi folks,
> when I locate the img file, its a 1.57, which I believe would fit on the
> later  floppies, but apparently not on my  1.44 ones.
> So hoping to find a copy, even if in .zip that will fit?
> Apparently Intel has an entire package of drivers that include ones for
> DOS.  However, I believe the ISO image needs a cd burn, likely not an
> option here, but will take the package if it can be found.
> Doing the work with sighted help on 26 October Toronto time.
> ideas?
> Thanks,
> Karen
>
>
>
>
> ___
> 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] How do I update certificates in FreeDOS?

[Louis Santillan via Freedos-user]

And yet here we are talking about UNIX utilities ported to a 32-bit
compiler running on a 16 bit patch to an 8 bit operating system originally
coded for a 4 bit microprocessor, originally written by a 2 bit company,
that can't stand 1 bit of competition.

I daily drive Fedora Linux myself.  But curling DOS software zip files on
it is not as useful as doing that directly on 386 Dell I have sitting 3
feet away when I want to run a bit of new software on it.

On Sat, Aug 5, 2023 at 12:56 PM Ralf Quint via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> On 8/5/2023 12:51 PM, Louis Santillan via Freedos-user wrote:
> >
> >
> > Don’t do anything that requires security (banking, personal info,
> > connecting to work) if you decide to use a 3rd party proxy.  All of
> > these proxies can potentially see your credentials and sensitive
> > information.  It would be best to stand up your own proxy if your
> > technically capable of doing so.
>
> Seriously? Why not use a Linux host, with proper encryption protocol
> support in the first place? What you suggest looks to me just like
> another "von hinten durch die Brust ins Auge" issue..
>
>
> Ralf
>
>
>
>
> ___
> 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] How do I update certificates in FreeDOS?

[Louis Santillan via Freedos-user]

https://linux.die.net/man/1/curl

-k/--insecure(SSL) This option explicitly allows curl to perform "insecure"
SSL connections and transfers. All SSL connections are attempted to be made
secure by using the CA certificate bundle installed by default. This makes
all connections considered "insecure" fail unless *-k/--insecure* is used.


In short, curl will still make encrypted SSL/TLS connections at supported
protocol versions (some servers and companies will still fall back to
earlier standards).  The encrypted/decrypted communication is considered
insecure because the trust portion of the protocol is bypassed.

And yes Ralf, if the servers or companies have strict security standards
requiring newer protocol versions, then curl will fail or will eventually
fail to communicate with them.

This is why the proxy support is a better solution today.  The system
hosting the proxy can be newer and support the newest security standards
for older systems.


On Sat, Aug 5, 2023 at 12:50 PM Ralf Quint  wrote:

> On 8/5/2023 12:37 PM, Louis Santillan wrote:
> > zerofive, you did not provide us actual error messages.  We can only
> > speculate.
> >
> > At least with curl on Linux, you can bypass cert checks with “-k”.  If
> > you still believe it’s certs and you have a known good certificate and
> > private key, you pass them as “--cert” and “--key”, respectively.
> >  wget has similar arguments as well.
> The general problem here is, as I already mentioned, more likely the
> lack of support of current encryption protocols rather than the use of
> any certificate by those protocols.
>
> And any bypass you mentioned is likely just a way to fall back to
> unencrypted http, which more and more sites these days simply do not
> support anymore.
>
>
> Ralf
>
>
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] How do I update certificates in FreeDOS?

[Louis Santillan via Freedos-user]

You might also try standing up an http to https proxy.  There are some
proxies setup specifically for retro computers like

https://protoweb.org/get-started/
https://github.com/DrKylstein/retro-proxy
https://youtu.be/-Qs3LVPmLgk
https://protoweb.org/wiki/servers/
http://www.steptail.com/retroweb:servers


curl let’s you specify a proxy server with “-x” and a “username:password”
(some proxies require this) with “-U”.  Examine curl’s arguments with “-h”.


Don’t do anything that requires security (banking, personal info,
connecting to work) if you decide to use a 3rd party proxy.  All of these
proxies can potentially see your credentials and sensitive information.  It
would be best to stand up your own proxy if your technically capable of
doing so.


On Sat, Aug 5, 2023 at 12:35 PM zerofive--- via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Then what do I do if I want to make a cURL request or WGet to a secure
> HTTPS page?
> Do I just use HTTP?
> But then it will forcefully redirect to HTTPS connection...
> What do I do?
> *Sent:* Sunday, August 06, 2023 at 1:24 AM
> *From:* "Ralf Quint via Freedos-user" 
> *To:* freedos-user@lists.sourceforge.net
> *Cc:* "Ralf Quint" 
> *Subject:* Re: [Freedos-user] How do I update certificates in FreeDOS?
> On 8/5/2023 5:35 AM, zerofive--- via Freedos-user wrote:
>
> Hello everyone! I am new to FreeDOS.
> When I try to use cURL or WGet, they sometimes error and refuse to use
> secure HTTPS connection.
> I figured it was from outdated certificates. Is there any way I can update
> them, manually or automatically?
> Thanks!
>
> FreeDOS knows jacksh@t about any certificate.
>
> And rather than a certificate issue, it is much rather an issue about the
> encryption protocols and associated key length in general that prevent you
> from using https connections in recent years. This is totally an issue of
> the applications you are using, making sure that they would be able to at
> least support TLS 1.2, or newer...
>
>
>
> Ralf
>
>
> ___ 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] How do I update certificates in FreeDOS?

[Louis Santillan via Freedos-user]

zerofive, you did not provide us actual error messages.  We can only
speculate.

At least with curl on Linux, you can bypass cert checks with “-k”.  If you
still believe it’s certs and you have a known good certificate and private
key, you pass them as “--cert” and “--key”, respectively.  wget has similar
arguments as well.

On Sat, Aug 5, 2023 at 12:25 PM Ralf Quint via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> On 8/5/2023 5:35 AM, zerofive--- via Freedos-user wrote:
>
> Hello everyone! I am new to FreeDOS.
> When I try to use cURL or WGet, they sometimes error and refuse to use
> secure HTTPS connection.
> I figured it was from outdated certificates. Is there any way I can update
> them, manually or automatically?
> Thanks!
>
> FreeDOS knows jacksh@t about any certificate.
>
> And rather than a certificate issue, it is much rather an issue about the
> encryption protocols and associated key length in general that prevent you
> from using https connections in recent years. This is totally an issue of
> the applications you are using, making sure that they would be able to at
> least support TLS 1.2, or newer...
>
>
> Ralf
>
>
> ___
> 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] USB serial & DOSBox

[Louis Santillan via Freedos-user]

Very cool!

On Tue, Jul 25, 2023 at 4:05 AM Bryan Kilgallin 
wrote:

> Yay, Louis:
>
> > It should be at `/dev/ttyUSB0` and you should refer to realport
> > `ttyUSB0` or something like that (`serial1=directserial
> > realport:ttyUSB0`).
>
> Yes, I found that character device.
>
> lsusb lists the following.
>
> {Bus 001 Device 005: ID 050d:0109 Belkin Components F5U109/F5U409 PDA
> Adapter}
>
> In DOSBox, at the C: prompt, I entered:
>   "serial1=directserial realport:ttyUSB0".
>
> Then I launched the POLAR software. and told the heart-monitor to
> transmit. The POLAR software immediately received the data!
> --
> members.iinet.net.au/~kilgallin/
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] USB serial & DOSBox

[Louis Santillan via Freedos-user]

It should be at `/dev/ttyUSB0` and you should refer to realport `ttyUSB0`
or something like that (`serial1=directserial realport:ttyUSB0`).  This
article (
https://www.cyberciti.biz/faq/find-out-linux-serial-ports-with-setserial/)
gives a good example of how to manage serial ports (including USB
connected) in Ubuntu.

This article (https://www.scivision.dev/dosbox-linux-serial-port/) gives
additional tips on how to set up serial ports for DOSBox on Linux.

On Mon, Jul 24, 2023 at 6:32 PM Bryan Kilgallin via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> My heart monitor is an old Polar Sport Tester 4000.
> https://www.manualslib.com/manual/1393035/Polar-Electro-Sport-Testert.html
>
> Its interface box has an RS2323 socket.
>
> I had been downloading data to an old PC with a serial port. That PC
> runs FreeDOS. VER/R reports "DOS version 7.10".
>
> My Ubuntu PC does not have a serial port.
>
> But I have a Belkin F5U409 USB-serial adaptor. My Linux kernel is
> 5.19.0-50-generic.
>
> {The device is supported by kernel versions 2.6.0 and newer according to
> the LKDDb:
>
> Ver Source  Config  By ID   By Class
> 2.6.0 - 6.3 drivers/usb/serial/mct_u232.c   CONFIG_USB
> CONFIG_USB_SERIAL
> CONFIG_USB_SERIAL_MCT_U232  050d:0109   *}
>
> https://linux-hardware.org/?id=usb:050d-0109
>
> That adaptor's LNK LED is on (green).
>
> The Ubuntu PC has DOSBox v0.74-3. It runs the POLAR software OK. That
> can set serial port to COM1 or COM2.
>
> DOSBox Wiki says this.
>
> {Configuration:SerialPort
> Jump to navigation
> Jump to search
>
> serialX = device [parameter:value]
>
>  device can be: dummy | modem | nullmodem | directserial
>  parameter is: irq
>  value is:
>
>  for directserial: realport (required), rxdelay (optional).
>  for modem: listenport (optional).
>  for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
> transparent, port, inhsocket (all optional).
>
>  Defaults:
>  serial1=dummy
>  serial2=dummy
>  serial3=disabled
>  serial4=disabled
>
>  An example of how to configure an actual serial port for I/O use:
>
> serial1=directserial realport:com1}
>
> So in DOSBox, I enter that last line.
>
> Then I launch the POLAR software.
> And I check its default serial port:
> "THE SELECTED SERIAL PORT FOR HR INPUT IS: COM1".
>
> Then I instruct the heart monitor to transmit data. And the adapter's RX
> LED illuminates red. But the POLAR software fails to detect data!
>
> Please advise.
> --
> members.iinet.net.au/~kilgallin/
>
>
> ___
> 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] Basic freedos question before I try this?

[Louis Santillan via Freedos-user]

AFAICT, the FDNET package contains packet drivers for (16-bit?) NE2000 and
PCnet ethernet cards.   The crynwr package has several dozen other packet
drivers.  If we knew the exact Thinkpad model, we could advise you better.

http://crynwr.com/drivers/00index.html

WRT saving items to floppy, are you considering a hard drive install or
booting from floppy only?

On Tue, Jul 18, 2023 at 12:46 PM Karen Lewellen via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> meaning that packet drivers are included in packages, or that I will need
> to hunt them?
> also, is there  a   install copy that lets me save items to floppies?
>
>
>
> On Tue, 18 Jul 2023, Rugxulo via Freedos-user wrote:
>
> > Hi,
> >
> > On Tue, Jul 18, 2023 at 3:56 PM Karen Lewellen via Freedos-user
> >  wrote:
> >>
> >> My goal is supporting the built in  Ethernet infrastructure on the
> >> thinkpad.
> >>   My understanding, perhaps incorrect, is that freedos has networking
> >> infrastructure  in the system itself?
> >
> > No, FreeDOS isn't special, it just uses pre-existing packet drivers
> > (usually for old hardware).
> >
> >
> > ___
> > 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] Basic freedos question before I try this?

[Louis Santillan via Freedos-user]

Correct and it would help to know which machine you are choosing.

On Tue, Jul 18, 2023 at 11:02 AM Rugxulo via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hi,
>
> On Tue, Jul 18, 2023 at 3:56 PM Karen Lewellen via Freedos-user
>  wrote:
> >
> > My goal is supporting the built in  Ethernet infrastructure on the
> > thinkpad.
> >   My understanding, perhaps incorrect, is that freedos has networking
> > infrastructure  in the system itself?
>
> No, FreeDOS isn't special, it just uses pre-existing packet drivers
> (usually for old hardware).
>
>
> ___
> 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] Basic freedos question before I try this?

[Louis Santillan via Freedos-user]

Depends on the vintage of Thinkpad, but I wouldn't just assume a Thinkpad
has a DOS compatible Ethernet card.  I would verify.

On Tue, Jul 18, 2023 at 10:08 AM Karen Lewellen via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hi folks,
> Due to some layered power issues in my new apartment, I am considering
> installing Freedos onto a laptop as a backup for my desktop computer.
> My main reason for considering this is the likelihood, given its an IBM
> Thinkpad, that Freedos networking should work for the onboard Ethernet
> setup.  Meaning I will not need to find a different Ethernet card for this.
> Am I correct?
> Thanks,
> Karen
>
>
>
>
> ___
> 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] A new mTCP (2023-03-31) is available

[Louis Santillan]

YES!!! Thanks a ton!

On Mon, Apr 10, 2023 at 1:50 PM Andy D  wrote:
>
> Great stuff Mike, great stuff!
> 
> From: Michael Brutman 
> Sent: Monday, April 10, 2023 12:01 PM
> To: Discussion and general questions about FreeDOS. 
> 
> Subject: Re: [Freedos-user] A new mTCP (2023-03-31) is available
>
> Just a small correction - please change the URLs to start with 
> http://www.brutman.com/ as per the original announcement.  You've got 
> http://brutmanlabs.org/, which is a PCjr running at 4.77Mhz.  It's doing fine 
> under load, but eventually it will run out of log space and be moved back to 
> something more fun. :)  Perhaps an online version of Eliza to compete with 
> ChatGPT.
>
> (The PCjr has been running and serving traffic for 10+ days now.  I was 
> redirecting from the usual home page to get some traffic for better testing.  
> I'm going to see if I can get 1000 continuous hours on it, which for 39 year 
> old hardware is no small feat.)
>
>
> -Mike
>
> On Fri, Apr 7, 2023 at 3:12 PM Jim Hall  wrote:
>
> Sounds good! I've mirrored this, but marked it as invisible (sort of
> "pre-mirrored" it, if you will). I can mark it as "visible" at some
> later time.
>
> News item posted on the website. I'll also share it on Mastodon.
>
>
> Jim
>
> On Sat, Apr 1, 2023 at 11:38 AM Michael Brutman  wrote:
> >
> > http://www.brutman.com/mTCP/mTCP.html
> >
> > From the release notes:
> >
> > Unicode support for Telnet and IRCjr
> > RLE graphics support in Telnet (fun as a demonstration, but not very 
> > practical)
> > The web server gets a built-in SNTP client for keeping the server time 
> > correct across many days/weeks of runtime.
> > A keyboard handling workaround for VirtualBox users.  (OpenWatcom had a 
> > run-time bug that interacts poorly with the incomplete BIOS keyboard 
> > handling in VirtualBox.)
> > Many small bug fixes and improvements, including in the base TCP/IP library.
> >
> >
> > Jim & Jerome - As before, please give me a few weeks before mirroring it so 
> > that I can get a rough idea of how many people are downloading it.  I need 
> > some reason to justify all of this work. ;-0
> >
> > On a side note, unless something huge happens this is going to be the last 
> > update for a while.  I suspect this code will last a few years.
> >
> >
> > -Mike
> >
> >
> > ___
> > 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] Question about xFDisk and a multiboot setup

[Louis Santillan]

Might I suggest you try Microwindows/Nano-X on DOS and Linux?

http://www.microwindows.org/


On Mon, Mar 13, 2023 at 11:41 AM usul  wrote:

> I probably am that guy.  I couldn't post in groups on FB for a couple of
> days.   and I am itching to do something. LOL.
>
> Thanks for the links...
> As soon as I find a linux distro that I like that works on the laptop I
> will start looking at them in more detail.
>
> I think it would be fun to write something that looks like Windows 3.11
> maybe even be able to run apps written for it. DESQview/X  could run both
> if I could get something going that
>
> I have always thought that if xserver and a wm/desktop could be ported
> from linux to freedos that were small enough,
> then perhaps others would port apps as well. beyond the standard
> minefield, wordpad etc clones the other "desktops" like seal, opengem. etc.
> with those they never seemed to catch on, and most of them barely
> function when I run them.
>
> xvesa, wxwidgets, nano-x / microxwindows etc
> I don't really know how all of the linux windowing system works yet.  And
> really the last time I messed with linux, it was zipslack on jaz drives was
> the thing.
> I even have a copy of dragonlinux (the linux that installed on a dos
> partition not a different partition)
>
> I still have a bunch of books in the closet for programming windows 3.11
> and dos.
> Never did much win 95 came out shortly (like a couple of years) after I
> got started.
>
> I'll find something simpler freedos related to cut my dos programmer teeth
> on.
> Probably... :)
>
> Adam
>
>
>
>
>
>
>
>
>
>
> On Mon, Mar 13, 2023 at 6:24 AM Liam Proven  wrote:
>
>> On Thu, 9 Mar 2023 at 15:18, usul  wrote:
>> >
>> > Why? cause I always get asked...
>>
>> Ah, you are the same person who asked on the Facebook FreeDOS group?
>>
>> > Because I want to code some stuff for windows 3.11 last time I did I
>> was working in VB 3 lol,
>> > run XAppeal and DESQview/X 2.1 and cause if they can do it see If I can
>> port a minimal xserver to FreeDos for fun. And I really don't want to do
>> any of that in a VM.
>>
>> DESQview/X _is_ a minimal X server.
>>
>> There were other X servers for DOS, e.g.
>>
>>
>> https://sourceforge.net/p/freedos/mailman/freedos-user/thread/4f0b8ad3.7050...@gmail.com/
>>
>> http://www.linuxmisc.com/4-linux/54d11736a319f7ae.htm
>>
>>
>> https://techmonitor.ai/technology/ms_dos_x_server_releases_from_hummingbird
>>
>> The DEC PATHWORKS client for DOS also included an X server.
>>
>>
>> http://bitsavers.informatik.uni-stuttgart.de/pdf/dec/decnet/pathworks_DOS/AA-PAF5C-TK_Pathworks_for_DOS_Overview_V4.1_Aug91.pdf
>>
>>  You might be able to find a download of that out there somewhere. I
>> think it was free if you owned the PATHWORKS server.
>>
>> --
>> Liam Proven ~ Profile: https://about.me/liamproven
>> Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
>> Twitter/LinkedIn: lproven ~ Skype: liamproven
>> IoM: (+44) 7624 277612: 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
>>
> ___
> 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] Can you recommend a good single-board-computer for legacy OSs?

[Louis Santillan]

Have a look at parkytowers and consider a thin client of pre-Windows 7
or Windows XP vintage.  They're usually cheap and plentiful on ebay
and the like.

https://www.parkytowers.me.uk/thin/hware/hardware.shtml

On Wed, Mar 8, 2023 at 3:19 AM Frantisek Rysanek
 wrote:
>
> ...oops, I have a small typo correction:
>
> > Note that Vortex86, especially in the DX2 generation, is pretty close
> > to machines of the 486 / Pentium era.
> >
> actually I meant the Vortex86DX, not the DX2.
> (The DX2 is actually moving away slightly from the old-skool bare
> metal.)
>
> Frank
>
> > It's got a proper, full-blown
> > ISA bus straight from the SoC, and also 32bit / 33MHz PCI.
> > The DX-based boards by ICOP come with an XGI Z9s graphics chip that
> > has something like 32 MB of dedicated Video DRAM and is accompanied
> > by a pretty good VESA BIOS, where good = decent compatibility with
> > DOS-era software. It can run Windows up to XP, although for XP the
> > onboard 512 MB of RAM is already hardly sufficient. Graphics drivers
> > are available for the Windows 9x and NT.
> ...
>
>
> ___
> 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] UDVD2 drivers not starting on UTM MacOS - help needed

[Louis Santillan]

Are you using something like this guide?

https://teachernerd.com/2022/07/16/how-to-run-ms-dos-on-a-mac-with-intel-or-m-series-processor/

Maybe try booting FreeDOS in DOSBOX-X instead?

https://nomadic-dmitry.medium.com/apple-silicon-m1-how-to-run-dos-games-and-apps-b5858e51e339


On Wed, Jan 4, 2023 at 7:47 AM Knedlik  wrote:

> Hello!
> I wanted to take a look again at FreeDOS, but when I install it using UTM
> on my MacBook Pro (Entry level M1), I’m not able to use the package manager
> due to UDVD2 and thus the entire CD-ROM system not working. If you have any
> ideas, help will be greatly appreciated.
> Thanks in advance,
> -Knedlik
>
> ___
> 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] FreeDOS in proxmox

[Louis Santillan]

Right.  I thought about it later and wondered what the other DOS
stacks did.  What does MS-NET or Trumpet do?  Probably the same thing
as mTCP and WATTCP.  I remember using ping in DOS to ensure
connectivity to Gateways and DNS, but I wasn't running any servers so
there was little reason to ping the DOS machine.

On Wed, Dec 21, 2022 at 11:23 AM Michael Brutman  wrote:
>
> Read the documentation for whatever networking software you are using.
>
> mTCP in particular is not a "resident" program, so your FreeDOS machine will 
> not respond to ping requests unless an mTCP program is actively running.  
> WATTCP programs have the same behavior.
>
>
> ___
> 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] FreeDOS in proxmox

[Louis Santillan]

Can you ping in the other direction?  It may be that the bridged vmbr0
interface does not pass or there is nothing in the networking stack that
listens for ICMP packets.

See also
https://forum.proxmox.com/threads/solved-cant-ping-windows-vm.65736/


On Mon, Dec 19, 2022 at 2:42 AM Trever Noggle  wrote:

> That worked.  Thank you.  I did discover that I now have network access
> in freedos but it does not respond to ping requests.  There are no
> firewall rules that would prevent this on my lan and I removed the check
> in the firewall box in proxmox for this host. Is there something that
> needs to be set in freedos to allow it to respond to ping requests?
>
> On 12/19/2022 3:41 AM, Louis Santillan wrote:
> > I just setup Proxmox 7.3.3 to do some testing Brett Johnson.  Had no
> > issues installing FD 1.3.  Chose "OS Type" as "Other", switched
> > "Network Device" to "rtl8139" and "Firewall" as "1".  Installed by
> > hand packages "FDNET", "MTCP", "CRYNWR".   There's no option for
> > passthru or private on the "Network Device".
> >
> > Did the following
> > c:\freedos\drivers\crynwr\rtspkt.com 0x60
> > c:\freedos\net\mtcp\dhcp.exe
> >
> > Had an IP from my DHCP server after that.
> >
> > On Sun, Dec 18, 2022 at 7:26 PM Trever Noggle  wrote:
> >> Has anyone been able to get networking to work in proxmox.  No matter
> >> what I try it says that physical networking is not supported at this
> time.
> >>
> >>
> >>
> >> ___
> >> 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] FreeDOS in proxmox

[Louis Santillan]

I just setup Proxmox 7.3.3 to do some testing Brett Johnson.  Had no
issues installing FD 1.3.  Chose "OS Type" as "Other", switched
"Network Device" to "rtl8139" and "Firewall" as "1".  Installed by
hand packages "FDNET", "MTCP", "CRYNWR".   There's no option for
passthru or private on the "Network Device".

Did the following
c:\freedos\drivers\crynwr\rtspkt.com 0x60
c:\freedos\net\mtcp\dhcp.exe

Had an IP from my DHCP server after that.

On Sun, Dec 18, 2022 at 7:26 PM Trever Noggle  wrote:
>
> Has anyone been able to get networking to work in proxmox.  No matter
> what I try it says that physical networking is not supported at this time.
>
>
>
> ___
> 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] memory issue, or something

[Louis Santillan]

Apologies, I confused another thread with this.  But executing ‘mem /c’
would tell someone how their memory is configured and what needs to be done
to make so that there is enough configured for EMS.  The trap 15 error
might be related to the FreeDOS memory managers or might be related to
something the software expects to be handled elsewhere.  ‘mem /c’, and the
contents of autoexec.bat & config.sys would tell us a lot about your system.

On Tue, Nov 29, 2022 at 11:33 AM Tomas By  wrote:

> On Tue, 29 Nov 2022 19:33:34 +0100, Louis Santillan wrote:
> > What does ‘mem /c’ output?
>
>
> No idea. Please read the rest of the thread also.
>
> /Tomas
>
>
> ___
> 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] memory issue, or something

[Louis Santillan]

What does ‘mem /c’ output?

On Tue, Nov 29, 2022 at 4:32 AM Tomas By  wrote:

> On Tue, 29 Nov 2022 05:14:55 +0100, Jeremy Leonard via Freedos-user wrote:
> > Did you use the two disk install from archive.org?
>
> No actually I used the files from
>
> http://id3486.securedata.net/fprado/armorsite/tanks.htm
>
>
> > Here is how I got it to work:
> > 4. Run install from C:\TANKSIN
> > C:
> > CD C:\TANKSIN
> > INSTALL
>
> I tried (after reading the above) to run the program called SINSTALL
> to set up the sound hardware (which did not seem to work but whatever)
> and now I no longer get the strange error, so thank you.
>
> /Tomas
>
>
> ___
> 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] memory issue, or something

[Louis Santillan]

With a 386, you likely have 1MB-16MB.  But you need to have it configured
in the right way for the game, either as Expanded Memory (aka EMS) or
Extended Memory (aka XMS).  MobyGames does not specify how to configure the
2MB RAM requirement.
This website (http://id3486.securedata.net/fprado/armorsite/tanks.htm)
claims you need 600KB of free Conventional Memory just to start.  Maybe
peek at the DOSBox configuration.  Other forums like vogons and vcfed might
have more relevant information.

On Mon, Nov 28, 2022 at 11:29 AM Tomas By  wrote:

> On Mon, 28 Nov 2022 20:03:55 +0100, John Vella wrote:
> > What's the game you're trying to run
>
> https://archive.org/details/msdos_Wargame_Construction_Set_II_-_TANKS_1994
>
>
> > and how much RAM do you have?
>
> More than 640k (1GB?).
>
> /Tomas
>
>
> ___
> 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] How to unload a driver?

[Louis Santillan]

Some drivers might work DDL, DDU as well -
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/ddl/

On Fri, Nov 4, 2022 at 4:06 PM Robert Riebisch  wrote:

> Hi Michał,
>
> > I load drivers for SoundBlaster AWE64 by means of putting CTMM.SYS,
> > CTSB16.SYS and CTCU.EXE in DEVICE= parameters in FDCONFIG.SYS. However,
> > that leaves me with 570KB free. I know that I can free some of that
> > memory if only I can unload the drivers once the card is configured. I
> > need to have 600KB free in order to start some very strange games, like
> > Wolf. No, not Wolfenstein. Wolf
> > https://en.wikipedia.org/wiki/Wolf_(video_game)
>
> You could try UNISOUND instead.
>
> "UNISOUND can be launched without options, with optional command line
> options and with/without a BLASTER/ULTRASND environment variable present
> (before launch). It doesn't consume RAM. It is not a TSR, it doesn't
> require mem extenders, XMS/EMS..."
>
> https://www.vogons.org/viewtopic.php?f=62=72553
>
> (I never tried UNISOUND.)
>
> Cheers,
> Robert
> --
> BTTR Software   https://www.bttr-software.de/
> DOS ain't dead  https://www.bttr-software.de/forum/
>
> ___
> 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] Mail and news for FreeDOS

[Louis Santillan]

Is that using the FreeDOS distributed copy or the work done by AnttiTakala (
https://github.com/AnttiTakala/SSH2DOS/releases/tag/v0.2.1%2BSHA256.1)?
AnttiTakala listed the following changes

The aim was to update the ciphers and protocols to more 2021 standards so
the programs would be usable with current ssh servers without the need to
change the server configuration to allow less secure connection methods.

Changes to original:
diffie-hellman-group1-sha1 -> diffie-hellman-group14-sha256
aes128-cbc -> aes128-ctr
hmac-sha1 -> hmac-sha2-256


On Wed, Sep 21, 2022 at 2:25 PM Karen Lewellen 
wrote:

> The challenge, at least for some, is that ssh2dos has not gotten an update
> allowing  for the current approach to dh keys and the like.
> I personally use ssh2dos  several times a day to reach  the shell service
> I have.  However, I can no longer use ssh2dos  for my workplace Linux
> shell from dreamhost, because openssh stopped supporting public and global
> dh keys.
> Karen
>
>
>
> On Wed, 21 Sep 2022, Louis Santillan wrote:
>
> > Arachne Web Browser also supports email and news protocols.
> >
> > Better solution would be to use ssh2dos to ssh into a linux box to do
> > email/news things.
> >
> > On Wed, Sep 21, 2022 at 12:37 PM Travis Siegel 
> wrote:
> >
> >> I'm fairly certain there's a dos port of pcpine out there somewhere.
> >> I've used it under windows, and it work sfine, but I never used it under
> >> plain dos, (though I know folks who have).  It handles both email and
> >> newsgroups.  Failing that, You could always try one of the various ports
> >> of ka9q, not only does it provide email, but it gives you an entire
> >> tcp/ip suite built in.  It's of course old, but what that runs on dos
> >> isn't? If you're looking specifically for a news reader, you can always
> >> try nettamer.  I don't know if it's still possible to register it, but
> >> honestly, the only thing registration gives you is the ability to remove
> >> taglines generated by the software.
> >>
> >> Hope this helps.
> >>
> >>
> >> On 9/3/2022 2:17 PM, Ralf Wissing wrote:
> >>> Hi everyone,
> >>>
> >>> this is my first post on the list, so i want to apogly in advance
> >>> if i violate any customs.
> >>>
> >>> So... i am searching for a good email solution for DOS, i know there
> >>> is (was?) a mutt port for DOS out there, but it is (at least for me)
> >>> nowhere to be found. As for now i am using Arachne as something of an
> >>> "all in one" solution, but as an spoiled linux user i am missing a few
> >>> things (threaded display of mails, filters...). Another thing i am in
> >>> search of is some form of newsreader, here i was totally out of luck
> >>> so far.
> >>>
> >>> It would be great if someone would have a few suggestions.
> >>>
> >>>
> >>> Greetings
> >>>
> >>> Ralf
> >>> -- This mail was written by a user of the Arachne Browser on FreeDOS  -
> >> http://arachne.cz/
> >>>
> >>>
> >>>
> >>>
> >>> ___
> >>> 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] Mail and news for FreeDOS

[Louis Santillan]

Arachne Web Browser also supports email and news protocols.

Better solution would be to use ssh2dos to ssh into a linux box to do
email/news things.

On Wed, Sep 21, 2022 at 12:37 PM Travis Siegel  wrote:

> I'm fairly certain there's a dos port of pcpine out there somewhere.
> I've used it under windows, and it work sfine, but I never used it under
> plain dos, (though I know folks who have).  It handles both email and
> newsgroups.  Failing that, You could always try one of the various ports
> of ka9q, not only does it provide email, but it gives you an entire
> tcp/ip suite built in.  It's of course old, but what that runs on dos
> isn't? If you're looking specifically for a news reader, you can always
> try nettamer.  I don't know if it's still possible to register it, but
> honestly, the only thing registration gives you is the ability to remove
> taglines generated by the software.
>
> Hope this helps.
>
>
> On 9/3/2022 2:17 PM, Ralf Wissing wrote:
> > Hi everyone,
> >
> > this is my first post on the list, so i want to apogly in advance
> > if i violate any customs.
> >
> > So... i am searching for a good email solution for DOS, i know there
> > is (was?) a mutt port for DOS out there, but it is (at least for me)
> > nowhere to be found. As for now i am using Arachne as something of an
> > "all in one" solution, but as an spoiled linux user i am missing a few
> > things (threaded display of mails, filters...). Another thing i am in
> > search of is some form of newsreader, here i was totally out of luck
> > so far.
> >
> > It would be great if someone would have a few suggestions.
> >
> >
> > Greetings
> >
> > Ralf
> > -- This mail was written by a user of the Arachne Browser on FreeDOS  -
> http://arachne.cz/
> >
> >
> >
> >
> > ___
> > 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] New mTCP available

[Louis Santillan]

It was mentioned recently that ssh2dos was updated last year to include the
newer protocols.


https://github.com/AnttiTakala/SSH2DOS

Would be awesome to see if mTCP improved the networking throughput or
latency.

At some point I’d love sit down and try to get the mTCP ported to djgpp but
the last time I tried I was having issues managing the buffer space in and
out of the lower 1MB.



On Sat, Jul 16, 2022 at 2:49 AM Liam Proven  wrote:

> On Sat, 16 Jul 2022 at 01:13, Michael Brutman 
> wrote:
>
> > Computationally, SSH is not feasible on the 16 bit machines that I
> target for this project.
> > Even with enough compute power, you need to find DOS equivalents of all
> of the libraries.  Which includes the ciphers, key exchanges, etc.  And
> then you need to port those, and what they depend on to DOS.  Without
> introducing security holes.
> > SSH ciphers are a moving target.  What is acceptable today will be
> deprecated in a few years.  It is difficult to keep up.
>
> Agreed. Modern cryptography is one of the relatively few things that uses
> the large amount of bandwidth of modern CPUs.
>
> It's possible to run older versions of OpenBSD on 30+ year old DEC
> minicomputers, for example. It was dropped only because Theo de Raadt
> couldn't get modern VAXstation hardware to compile it on. I tried to
> donate a VAXstation 4000/90 to the project when I emigrated -- Red Hat was
> going to ship it to Canada from the UK for me.
>
> De Raadt changed his mind when he learned it wasn't the fastest model, and
> Red Hat Farnborough lost the machine. 
>
> Anyway, making new SSH keys on a VAX took as much as a couple of *days* in
> some instances.
>
> --
> 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
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] DOS ASM resources

[Louis Santillan]

PCGPE and the VLA Tutorials.
http://bespin.org/~qz/pc-gpe/

On Thu, Jun 30, 2022 at 11:19 AM C. Masloch  wrote:

> On at 2022-06-30 10:00 -0500, Santiago Almenara wrote:
> > Hello!
> >
> > What book or webpage do you recommend to learn some DOS assembler?
> >
> > Thanks in advance
> >
> > Santiago
>
> I learned primarily using these methods:
>
> 1. Read existing code and try to understand it. Even better, start with
> higher-level commentary about code if you can find any. Some
> applications' manuals are good for this, eg DOSLFN.
>
> 2. Have an english-language instruction set reference handy. I used the
> one included with older NASM versions, which I subsequently forked when
> it was dropped from NASM. [1]
>
> 3. Likewise, refer to the Interrupt List for reference as to what a
> particular interrupt service does. Apart from some modern extensions it
> is fairly complete. It can be found in plain-text files (split across a
> lot of them, you can concatenate them to receive a single file) on Ralf
> Brown's pages [2] and can be accessed online, page per page, hosted by
> several different websites such as fd.lod.bz [3].
>
> 4. Try out things in a debugger if unsure, such as when unclear about
> what a particular instruction does, or to trace an existing program and
> try to improve your understanding of its workings. My main project is
> lDebug (with a small "L"), a debugger with a command line interface
> that's based on FreeDOS Debug. [4]
>
> 5. You can also read some of the books that have been written about DOS.
> At home I have the following print books: "FreeDOS Kernel", "DOS
> Internals", "Undocumented DOS (Second Edition)" (UDOS), "Dissecting
> DOS", "Extending DOS", "Advanced MS-DOS Programming", "Writing MS-DOS
> Device Drivers", and a german "DR DOS 6.0" manual. UDOS and the DR DOS
> manual are probably the best among these.
>
> Finally, I wrote a document called Assembly Comments Explained: Guide
> for Advanced Learning and Style [5]. It is intended to clarify
> conventions in my assembly language sources in particular.
>
> Regards,
> ecm
>
>
> [1]: https://pushbx.org/ecm/doc/insref.htm
> [2]: http://www.cs.cmu.edu/~ralf/files.html
> [3]: https://fd.lod.bz/rbil/index.html
> [4]: https://pushbx.org/ecm/web/#projects-ldebug
> [5]: https://pushbx.org/ecm/doc/acegals.htm
>
>
> ___
> 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] Installing GRUB

[Louis Santillan]

Note the first partition starts 1MB from the first sector.  I've seen some
mentions that this sort of thing is standard for multi-boot loaders.  I've
also read that some GPT partitioning schemes are using a BIOS Boot
Partition type (EF02) for that space while most MBR tools don't know or
care about it or expect an unallocated space.  Seems safer to reserve as
long as OSes like FreeDOS, MS-DOS, Windows95/98, etc. respect and support
that well.

On Thu, Jun 30, 2022 at 10:29 AM Louis Santillan  wrote:

> Awesome!  Thanks Tony!
>
> On Wed, Jun 29, 2022 at 4:52 PM Tony Richardson 
> wrote:
>
>> Louis,
>> Sure.  The output is:
>>
>> Device   Boot Start   End Sectors  Size  Id Type
>> /dev/sda1  * 2048 1023999 1021952  499M  e W95 FAT16 (LBA)
>>
>> Regards,
>> Tony
>>
>> On Wed, Jun 29, 2022 at 1:07 AM Louis Santillan 
>> wrote:
>>
>>> Tony,
>>>
>>> In your Linux VM, could you give the output to `fdisk -l /dev/sda`?
>>>
>>> Thanks
>>>
>>> On Sat, Jun 4, 2022 at 7:54 AM Tony Richardson <
>>> richardson.t...@gmail.com> wrote:
>>>
>>>> I wanted to use GRUB to boot FreeDOS.  (I wanted to use it so that I
>>>> could dual-boot FreeDOS and RTEMS, but others may have different reasons.)
>>>> It is a relatively short procedure so I thought I would contribute it to
>>>> the mailing list in case others might be interested. I installed FreeDOS in
>>>> a VirtualBox virtual machine, but the procedure should work on other
>>>> virtual or physical machines. The FreeDOS fdisk does not leave enough space
>>>> before the first partition to install GRUB, so I used a Linux SystemRescue
>>>> CD (system-rescue.org) to partition the (virtual) disk.  This CD has
>>>> all of the tools necessary to partition the drive, format the disk and
>>>> install GRUB.
>>>>
>>>> 1) In VirtualBox create a new 64-bit Linux machine with a 500 MB
>>>> vdi-type drive (FreeDOS.vdi).  Configure the machine to boot off of the
>>>> SystemRescue CD image.  (I had to give the machine 2 GB of memory to boot
>>>> the CD.  The default 512 MB would not allow the machine to boot.)
>>>>
>>>> 2) Boot the new machine and create a new maximum size primary partition
>>>> on the virtual drive (/dev/sda).  Change the partition type to 0x0E (a
>>>> Win95 LBA mapped partition).I use Linux fdisk (enter "fdisk /dev/sda") to
>>>> do this, but you can use any of the other disk partitioning tools on the CD
>>>> (gparted is a graphical partitioning tool).
>>>>
>>>> 3)  Format the new partition by entering "mkfs.msdos   /dev/sda1" (You
>>>> can alternately format the partition as part of the FreeDOS installation.)
>>>>
>>>> 4) Halt the Linux machine.  (Choose the "Power off the machine" option.)
>>>>
>>>> 5) Create a new FreeDOS virtual machine.  Choose to use an existing
>>>> virtual hard disk and attach the FreeDOS.vdi disk.  Boot the machine from
>>>> the FreeDOS live image.  Choose the "Install to Harddisk" option from the
>>>> boot menu.  Install FreeDOS.  You should be able to boot off the harddisk
>>>> into FreeDOS at this point.
>>>>
>>>> 6) Halt the FreeDOS virtual machine.
>>>>
>>>> 7) As part of the installation the FreeDOS master boot loader is
>>>> installed.  We need to rewrite this with GRUB, so restart the Linux 
>>>> machine.
>>>>
>>>> 8) Mount the new partition using "mount   /dev/sda1   /mnt"
>>>>
>>>> 9) Install Grub by entering "grub-install  --boot-directory=/mnt/boot
>>>>  /dev/sda"
>>>>
>>>> 10) Create a file named "grub.cfg" in the /mnt/boot/grub directory with
>>>> the following contents:
>>>> menuentry "FreeDOS" {
>>>>   insmod chain
>>>>   set root=(hd0,1)
>>>>   chainloader +1
>>>> }
>>>>
>>>> 11) Halt the Linux machine.
>>>>
>>>> You should now be able to boot the FreeDOS machine off of the hard
>>>> disk.  You should see the GRUB boot menu first now.  You can modify the
>>>> GRUB menu by editting the grub.cfg file in the C:\boot\grub directory.  You
>>>> can delete the Linx machine, but do not delete the files associated with
>>>> the machine or you will lose your FreeDOS drive.  You can move the
>>>> FreeDOS.vdi file if you want but you will need to play around with the
>>>> VirtualBox Media Manager to make it available to FreeDOS after the move.
>>>>
>>>> Tony Richardson
>>>>
>>>> ___
>>>> 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] Installing GRUB

[Louis Santillan]

Awesome!  Thanks Tony!

On Wed, Jun 29, 2022 at 4:52 PM Tony Richardson 
wrote:

> Louis,
> Sure.  The output is:
>
> Device   Boot Start   End Sectors  Size  Id Type
> /dev/sda1  * 2048 1023999 1021952  499M  e W95 FAT16 (LBA)
>
> Regards,
> Tony
>
> On Wed, Jun 29, 2022 at 1:07 AM Louis Santillan 
> wrote:
>
>> Tony,
>>
>> In your Linux VM, could you give the output to `fdisk -l /dev/sda`?
>>
>> Thanks
>>
>> On Sat, Jun 4, 2022 at 7:54 AM Tony Richardson 
>> wrote:
>>
>>> I wanted to use GRUB to boot FreeDOS.  (I wanted to use it so that I
>>> could dual-boot FreeDOS and RTEMS, but others may have different reasons.)
>>> It is a relatively short procedure so I thought I would contribute it to
>>> the mailing list in case others might be interested. I installed FreeDOS in
>>> a VirtualBox virtual machine, but the procedure should work on other
>>> virtual or physical machines. The FreeDOS fdisk does not leave enough space
>>> before the first partition to install GRUB, so I used a Linux SystemRescue
>>> CD (system-rescue.org) to partition the (virtual) disk.  This CD has
>>> all of the tools necessary to partition the drive, format the disk and
>>> install GRUB.
>>>
>>> 1) In VirtualBox create a new 64-bit Linux machine with a 500 MB
>>> vdi-type drive (FreeDOS.vdi).  Configure the machine to boot off of the
>>> SystemRescue CD image.  (I had to give the machine 2 GB of memory to boot
>>> the CD.  The default 512 MB would not allow the machine to boot.)
>>>
>>> 2) Boot the new machine and create a new maximum size primary partition
>>> on the virtual drive (/dev/sda).  Change the partition type to 0x0E (a
>>> Win95 LBA mapped partition).I use Linux fdisk (enter "fdisk /dev/sda") to
>>> do this, but you can use any of the other disk partitioning tools on the CD
>>> (gparted is a graphical partitioning tool).
>>>
>>> 3)  Format the new partition by entering "mkfs.msdos   /dev/sda1" (You
>>> can alternately format the partition as part of the FreeDOS installation.)
>>>
>>> 4) Halt the Linux machine.  (Choose the "Power off the machine" option.)
>>>
>>> 5) Create a new FreeDOS virtual machine.  Choose to use an existing
>>> virtual hard disk and attach the FreeDOS.vdi disk.  Boot the machine from
>>> the FreeDOS live image.  Choose the "Install to Harddisk" option from the
>>> boot menu.  Install FreeDOS.  You should be able to boot off the harddisk
>>> into FreeDOS at this point.
>>>
>>> 6) Halt the FreeDOS virtual machine.
>>>
>>> 7) As part of the installation the FreeDOS master boot loader is
>>> installed.  We need to rewrite this with GRUB, so restart the Linux machine.
>>>
>>> 8) Mount the new partition using "mount   /dev/sda1   /mnt"
>>>
>>> 9) Install Grub by entering "grub-install  --boot-directory=/mnt/boot
>>>  /dev/sda"
>>>
>>> 10) Create a file named "grub.cfg" in the /mnt/boot/grub directory with
>>> the following contents:
>>> menuentry "FreeDOS" {
>>>   insmod chain
>>>   set root=(hd0,1)
>>>   chainloader +1
>>> }
>>>
>>> 11) Halt the Linux machine.
>>>
>>> You should now be able to boot the FreeDOS machine off of the hard
>>> disk.  You should see the GRUB boot menu first now.  You can modify the
>>> GRUB menu by editting the grub.cfg file in the C:\boot\grub directory.  You
>>> can delete the Linx machine, but do not delete the files associated with
>>> the machine or you will lose your FreeDOS drive.  You can move the
>>> FreeDOS.vdi file if you want but you will need to play around with the
>>> VirtualBox Media Manager to make it available to FreeDOS after the move.
>>>
>>> Tony Richardson
>>>
>>> ___
>>> 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] Installing GRUB

[Louis Santillan]

Tony,

In your Linux VM, could you give the output to `fdisk -l /dev/sda`?

Thanks

On Sat, Jun 4, 2022 at 7:54 AM Tony Richardson 
wrote:

> I wanted to use GRUB to boot FreeDOS.  (I wanted to use it so that I could
> dual-boot FreeDOS and RTEMS, but others may have different reasons.)  It is
> a relatively short procedure so I thought I would contribute it to the
> mailing list in case others might be interested. I installed FreeDOS in a
> VirtualBox virtual machine, but the procedure should work on other
> virtual or physical machines. The FreeDOS fdisk does not leave enough space
> before the first partition to install GRUB, so I used a Linux SystemRescue
> CD (system-rescue.org) to partition the (virtual) disk.  This CD has all
> of the tools necessary to partition the drive, format the disk and install
> GRUB.
>
> 1) In VirtualBox create a new 64-bit Linux machine with a 500 MB vdi-type
> drive (FreeDOS.vdi).  Configure the machine to boot off of the SystemRescue
> CD image.  (I had to give the machine 2 GB of memory to boot the CD.  The
> default 512 MB would not allow the machine to boot.)
>
> 2) Boot the new machine and create a new maximum size primary partition on
> the virtual drive (/dev/sda).  Change the partition type to 0x0E (a Win95
> LBA mapped partition).I use Linux fdisk (enter "fdisk /dev/sda") to do
> this, but you can use any of the other disk partitioning tools on the CD
> (gparted is a graphical partitioning tool).
>
> 3)  Format the new partition by entering "mkfs.msdos   /dev/sda1" (You can
> alternately format the partition as part of the FreeDOS installation.)
>
> 4) Halt the Linux machine.  (Choose the "Power off the machine" option.)
>
> 5) Create a new FreeDOS virtual machine.  Choose to use an existing
> virtual hard disk and attach the FreeDOS.vdi disk.  Boot the machine from
> the FreeDOS live image.  Choose the "Install to Harddisk" option from the
> boot menu.  Install FreeDOS.  You should be able to boot off the harddisk
> into FreeDOS at this point.
>
> 6) Halt the FreeDOS virtual machine.
>
> 7) As part of the installation the FreeDOS master boot loader is
> installed.  We need to rewrite this with GRUB, so restart the Linux machine.
>
> 8) Mount the new partition using "mount   /dev/sda1   /mnt"
>
> 9) Install Grub by entering "grub-install  --boot-directory=/mnt/boot
>  /dev/sda"
>
> 10) Create a file named "grub.cfg" in the /mnt/boot/grub directory with
> the following contents:
> menuentry "FreeDOS" {
>   insmod chain
>   set root=(hd0,1)
>   chainloader +1
> }
>
> 11) Halt the Linux machine.
>
> You should now be able to boot the FreeDOS machine off of the hard disk.
> You should see the GRUB boot menu first now.  You can modify the GRUB menu
> by editting the grub.cfg file in the C:\boot\grub directory.  You can
> delete the Linx machine, but do not delete the files associated with the
> machine or you will lose your FreeDOS drive.  You can move the FreeDOS.vdi
> file if you want but you will need to play around with the VirtualBox Media
> Manager to make it available to FreeDOS after the move.
>
> Tony Richardson
>
> ___
> 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] An idea for silent PC controlled by FreeDOS

[Louis Santillan]

Unfortunately, they’re no longer $9. :(

On Sun, Jun 26, 2022 at 8:36 AM Zbigniew  wrote:

> Stumbled upon this video on YT -- it may be of interest to several
> FreeDOS users:
>
> https://www.youtube.com/watch?v=b0otktPOVRc
>
> "$9 DOS Retro Gaming PC with the HP t5530 Thin Client"
>
>
> ___
> 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] From BTTR: FAT32 ramdisk, SvarCOM shell, Doszip commander

[Louis Santillan]

This is super awesome to hear!  Thanks for linking!

On Wed, Jun 15, 2022 at 1:18 PM Dan Schmidt  wrote:

> Off topic and flagrant necromancy, yet I'll briefly note somebody (kind
> of) did. * (Disclaimer: "correct" loosely defined)*
>
> https://bestofcpp.com/repo/AnttiTakala-SSH2DOS
>
> P.S.  Thanks Eric
>
> On Sun, Mar 13, 2022 at 5:45 PM Karen Lewellen 
> wrote:
>
>> Seems like some fine efforts.
>> Speaking personally, I wish someone would devote time to  upgrading ssh
>> for  dos, so that the  dh key exchange issue was corrected.
>> Kare
>>
>>
>>
>> On Sun, 13 Mar 2022, Eric Auer wrote:
>>
>> >
>> > Hi!
>> >
>> > Today is a day full of announcements on BTTR-SOFTWARE.DE :-)
>> >
>> > https://www.bttr-software.de/forum/forum_entry.php?id=18797
>> >
>> >>  RDRVSX32: FAT32 RAM drive for HimemSX (Announce)
>> >>
>> >>  posted by jadoxa, Queensland, Australia, 13.03.2022, 13:58
>> >>
>> >>  I had a request (via email) to create a RAM drive greater than 4GiB.
>> >>  It sort of works (works on his and mine 8GiB AMD, but has issues with
>> >>  his 32GiB Intel) so if anyone has the time and inclination to test,
>> >>  that'd be great. You will need more than 4GiB RAM (in order to access
>> >>  super-extended memory), preferably more than 8GiB (in order to test
>> >>  accessing beyond 4GiB). Our testing has been simple so far: just copy
>> >>  large files (he was able to create a 28GiB RAM drive, copy hundreds
>> >>  of 64MiB files, but it fails copying a 1GiB file).
>> >
>> > Link: http://shsufdrv.adoxa.vze.com/rdrvsx32.zip
>> >
>> >
>> >
>> > https://www.bttr-software.de/forum/forum_entry.php?id=18799
>> >
>> >>  Doszip Commander version 2.63 available (Announce)
>> >>
>> >>  posted by rr, Berlin, Germany, 13.03.2022, 14:20
>> >>
>> >>  On 02 March 2022 Hjort Nidudsson released a new version.
>> >>
>> >>  Home page: https://github.com/nidud/doszip
>> >>  Download: https://github.com/nidud/doszip/releases/tag/v2.63
>> >>
>> >>  Changes since version 2.55 are:
>> >>  Changes in 2.63 - 2 Mar 2022
>> >>  - extended country-specific date format
>> >>
>> >>  Changes in 2.58 - 15 Feb 2022
>> >>  - added country-specific date format
>> >>
>> >>  Changes in 2.57 - 12 Feb 2022
>> >>  - changed "Jump" to "Skip" in Delete dialog
>> >>  - fixed color issue in Move dialog
>> >>  - fixed issue with pipe command -- unzip -hh | more
>> >
>> >
>> >
>> > https://www.bttr-software.de/forum/forum_entry.php?id=18798
>> >
>> >>  On 13 March 2022 Mateusz Viste released SvarCOM version 2022.3.
>> >>
>> >>  What is SvarCOM?
>> >>
>> >>  Quoting from http://svardos.org/svarcom/:
>> >>  SvarCOM is the SvarDOS command line interpreter, known usually under
>> >>  the name "COMMAND.COM". It is designed and maintained by Mateusz
>> >>  Viste, and distributed under the terms of the MIT license.
>> >>
>> >>  For the time being, it is a work-in-progress project that - although
>> >>  functional - is not entirely polished yet and might miss a few bits
>> >>  and pieces. SvarCOM version 2022.0 must be considered a "preview"
>> >>  version. See the documentation included in the zip file for details.
>> >>
>> >>  SvarCOM is minimalist and I'd like to keep it that way. It aims to be
>> >>  functionaly equivalent to COMMAND.COM from MS-DOS 5.x/6.x. No LFN
>> >>  support.
>> >>
>> >>  As of version 2022.0, SvarCOM's resident footprint is under 2 KiB.
>> >>
>> >>  What is new in version 2022.3?
>> >>
>> >>  Here is his 2022.3 announcement to the SvarDOS mailing list:
>> >>  Hello all,
>> >>
>> >>  SvarCOM 2022.3 has been published right now. It comes with many
>> >>  improvements and bug fixes. Many thanks to Robert Riebisch who
>> dedicated
>> >>  a lot of time to perform extensive tests on SvarCOM and had the
>> strength
>> >>  to annoy me over and over about the various glitches he found.
>> >>
>> >>  The new SvarCOM package is already available on the SvarDOS packages
>> >>  repository. It can also be downloaded from the SvarCOM sub-project
>> page
>> >>  at http://svardos.org/svarcom
>> >>
>> >>  As an experiment I did a SvarDOS build that uses SvarCOM instead of
>> >>  FreeCOM. It is the build 20220312, available in the "files" section of
>> >>  the website: http://svardos.org/?p=files
>> >>
>> >>  If this build proves stable enough, it might become the default
>> download
>> >>  presented on the main page, but for now it needs some testing. There
>> is
>> >>  also still one or two things that needs to be added (like DIR/O
>> support).
>> >>
>> >>  The main advantage of SvarCOM over the legacy FreeCOM is that the
>> former
>> >>  is much lighter (2K of memory footprint), which is esp. important on
>> >>  pre-386 machines.
>> >>
>> >>  An interesting side effect of replacing FreeCOM by SvarCOM is that
>> some
>> >>  of the SvarDOS floppy sets decreased:
>> >>
>> >>  720K set went from 4 floppies to 3 floppies
>> >>  1.2M set went from 3 floppies to 2 floppies
>> >>
>> >>  Other sets remained the same amount of floppies (6x 360K, 2x 1.44M and
>> 

Re: [Freedos-user] virt-install freedos

[Louis Santillan]

You can also use nicscan.exe (
http://www.georgpotthast.de/sioux/packet.htm) or pcinic.com (
http://dunfield.classiccmp.org/dos/index.htm) to verify the nic is
correctly configured in the VM.

On Thu, May 26, 2022 at 6:07 AM Louis Santillan  wrote:

> You also need to provide a ‘model’ on the ‘network’ parameter.  e1000 or
> rtl8139 have DOS packet drivers available.
>
> On Thu, May 26, 2022 at 4:29 AM  wrote:
>
>> Hello everybody. Thanks for the help so far, sorry for the delay in
>> responding.
>>
>> The simplest way for me to create a FreeDOS VM on my server was to
>> install it on a local VM and copy the disk image to the server, once there
>> I created the VM with the following command.
>>
>> virt-install \
>> --name DOS01 \
>> --network bridge=br0 \
>> --ram 32 \
>> --disk /kvm/disk/dos01.img \
>> --graphics=vnc,password=cadeafaca,listen=0.0.0.0,port=5913 \
>> --hvm \
>> --import
>>
>> Almost everything worked.
>> The other VMs (Debian) are happy with the bridge interface but FreeDOS
>> returned the following error.
>>
>> QEMU network detected.
>> Physical hardware networking is not supported at this time.
>>
>> I've tried a few variations trying to use tap interface but still no
>> success. Any idea what to do?
>> Like the other VMs, I want this one to be directly exposed to my internal
>> network, not using NAT.
>>
>> The point with all this is to try to rebuild the old BBS and DOS is not
>> exactly an environment I expect to see networking in. Perhaps a simpler way
>> is to simulate a serial interface and then try to export it to the network.
>>
>> Thanks everyone for the help!
>>
>> Cesar
>>
>> ___
>> 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] virt-install freedos

[Louis Santillan]

You also need to provide a ‘model’ on the ‘network’ parameter.  e1000 or
rtl8139 have DOS packet drivers available.

On Thu, May 26, 2022 at 4:29 AM  wrote:

> Hello everybody. Thanks for the help so far, sorry for the delay in
> responding.
>
> The simplest way for me to create a FreeDOS VM on my server was to install
> it on a local VM and copy the disk image to the server, once there I
> created the VM with the following command.
>
> virt-install \
> --name DOS01 \
> --network bridge=br0 \
> --ram 32 \
> --disk /kvm/disk/dos01.img \
> --graphics=vnc,password=cadeafaca,listen=0.0.0.0,port=5913 \
> --hvm \
> --import
>
> Almost everything worked.
> The other VMs (Debian) are happy with the bridge interface but FreeDOS
> returned the following error.
>
> QEMU network detected.
> Physical hardware networking is not supported at this time.
>
> I've tried a few variations trying to use tap interface but still no
> success. Any idea what to do?
> Like the other VMs, I want this one to be directly exposed to my internal
> network, not using NAT.
>
> The point with all this is to try to rebuild the old BBS and DOS is not
> exactly an environment I expect to see networking in. Perhaps a simpler way
> is to simulate a serial interface and then try to export it to the network.
>
> Thanks everyone for the help!
>
> Cesar
>
> ___
> 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] virt-install freedos

[Louis Santillan]

KVM/qemu as presented by virt-manager/virsh does something funny with the
config of the VM.  After initial boot it’ll “forget” about the CDROM.
Seems like it’s intended for OSes that don’t need to reboot after
formatting the primary drive.  I saw this behavior in RHEL and Fedora using
Cockpit, virt-manager, virsh.

Eventually I was able to install FreeDOS but I had to manually add back the
ISO and also manually fix the boot order.

This seems a lot like the reference I used back then.

https://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administration_Guide/sect-Attaching_and_updating_a_device_with_virsh.html


On Sun, May 22, 2022 at 7:02 PM  wrote:

> Hi!
>
> I'm trying to install FreeDOS in a virtual machine via virt-install, as
> the host machine is remote and doesn't have a graphical environment, so I
> only have access via ssh. Still, I can export the installer screen via VNC.
>
> The installation process loads, and I can get to the part of creating the
> primary partition, but I need to restart the machine after partitioning,
> and I cannot resume the installation from that point forward.
>
> This is the command I'm using.
>
> virt-install \
> --name DOS01 \
> --network bridge=br0 \
> --ram 512 \
> --disk
> /mnt/sd/vmdisk/DOS01.img,device=disk,bus=virtio,size=10,format=qcow2 \
> --graphics=vnc,password=cadeafaca,listen=0.0.0.0,port=5913 \
> --hvm \
> --cdrom /kvm/iso/FD13LIVE.iso \
> --boot cdrom
>
> Does anyone have experience with virt-install + FreeDOS?
>
> It would probably be more straightforward for me to use qemu directly, but
> as I already have several VMs running managed by virt-manager, I wanted to
> keep using it for FreeDOS.
>
> Cesar
>
> ___
> 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] Another good review of 1.3

[Louis Santillan]

Some more input for 8086 considerations

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

Re: [Freedos-user] Installing freedos to virtualbox them copying dice contents to an actual computer

[Louis Santillan]

FreeDOS Edit, SETEdit, vi, pico.  All great basic DoS text editors.

On Wed, Mar 30, 2022 at 4:59 AM John Vella  wrote:

> I'll be honest and say I'm starting to second guess myself here... Reading
> a totally unrelated email at work this morning, I wondered why I'm even
> bothering with wordperfect. I only need a basic text editor. I'm not
> interested in spell check, as I'll do that on the editing machine, so
> bringing it down to the minimum, freedos and whatever text editor is
> included would actually do the job nicely.
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Ré : Installing freedos to virtualbox them copying dice contents to an actual computer

[Louis Santillan]

One thing you can try is to remove the IDE HDD drive from the 486, connect
it to a USB drive adapter, then use VirtualBox/qemu/et al. to install
FreeDOS to it.  You can use an adapter like this one (
https://www.ebay.com/itm/124411032918).  Should have a JMicron chip in it
which all modern OSes will know how to deal with.

On Tue, Mar 29, 2022 at 2:50 PM John Vella  wrote:

> Hi Eric!
>
> I do have the img images for wordperfect, which I have transferred to
> floppy disk. The pc doesn't boot from cd, in fact I can't even get the bios
> to recognise the cd drive, as the hard drive parameters have to be manually
> entered. I have an isa sound Blaster awe 64 value, with ide connector,
> which I believe will allow me to access the drive, although boring from it
> probably won't be possible. Not a problem!
>
> My main problem at this point is that the pc is currently in the living
> room, which is another reason for the original virtual machine plan.
>
> Thinking about it, I could actually have done the complete installation
> from floppy disk by now! I'll have a look tomorrow.
>
>
> On Tue, 29 Mar 2022, 22:36 Eric Auer,  wrote:
>
>>
>> Hi!
>>
>> I think wordperfect for DOS came on floppies, yes.
>> And you can connect ATAPI CD/DVD drives to typical
>> 486  computers. There also are special boot loaders
>> which you can load from floppy to continue booting
>> from CD/DVD in case your BIOS does not yet support
>> direct booting from CD/DVD :-)
>>
>> 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] Issue: FreeDOS on PCem emulating a NE2000

[Louis Santillan]

See - https://gitlab.com/FreeDOS/net/fdnet/-/blob/master/BIN/FDNET.BAT

On Wed, Mar 16, 2022 at 11:15 AM Louis Santillan  wrote:

> "try" is an argument to the fdnet.bat batchfile.
>
> On Wed, Mar 16, 2022 at 11:05 AM dmccunney 
> wrote:
>
>> On Wed, Mar 16, 2022 at 12:18 PM Brandon Taylor
>>  wrote:
>> >
>> > Now, from what I've read in previous posts, it sounds like others have
>> had success by replacing "start" with "try," such that the line now reads
>> "call %dosdir%\bin\fdnet.bat try",
>>
>> Other [psts where?
>>
>> Start is a command. implemented by CMD.EXE in Windows, and can be used
>> to start a new process in a window from the command line. I've used it
>> to do that.  It does nor exist in pure MSDOS batch as implemented by
>> COMMAND.COM
>>
>> Try/Catch is an exception handling routine, present in JavasScript and
>> C# (and I think in Java.)  Just what is supposed to be  handling the
>> try here?
>>
>> I'm not surprised you are getting an error.
>>
>> > Brandon Taylor
>> __
>> Dennis
>>
>>
>> ___
>> 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] Issue: FreeDOS on PCem emulating a NE2000

[Louis Santillan]

"try" is an argument to the fdnet.bat batchfile.

On Wed, Mar 16, 2022 at 11:05 AM dmccunney 
wrote:

> On Wed, Mar 16, 2022 at 12:18 PM Brandon Taylor
>  wrote:
> >
> > Now, from what I've read in previous posts, it sounds like others have
> had success by replacing "start" with "try," such that the line now reads
> "call %dosdir%\bin\fdnet.bat try",
>
> Other [psts where?
>
> Start is a command. implemented by CMD.EXE in Windows, and can be used
> to start a new process in a window from the command line. I've used it
> to do that.  It does nor exist in pure MSDOS batch as implemented by
> COMMAND.COM
>
> Try/Catch is an exception handling routine, present in JavasScript and
> C# (and I think in Java.)  Just what is supposed to be  handling the
> try here?
>
> I'm not surprised you are getting an error.
>
> > Brandon Taylor
> __
> Dennis
>
>
> ___
> 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] How to add AHCICD.sys in the auto check-list for USB BOOT?

[Louis Santillan]

CONFIG.SYS does not work like that.  It looks like a script or batch file
but it mostly isn't.  But it does a have a MENU capability (
http://www.freedos.org/kernel/config.txt).  There's a few examples there as
well as at Phil's Computer Lab (
https://www.philscomputerlab.com/ms-dos-starter-pack.html).


On Fri, Mar 11, 2022 at 8:59 AM richardkolacz...@hotmail.com <
richardkolacz...@hotmail.com> wrote:

> Tom
>
> Thanks for reply.
>
> Any way to do an error check thing instead of always needing to be present
> to accept or reject device AHCICD.sys?
>
> I have not worked out/understand how FreeDOS does it automatically for the
> 4 CD options - be nice to apply this method to my 5th  CD device
> (AHCICD.sys) .
>
> Otherwise for totally automated unattended operation I simply removed the
> AHCICD.sys file and the laptop without optical drive does boot up OK.
>
> Richard
> --
> *From:* tom ehlert 
> *Sent:* Saturday, 12 March 2022 3:27 AM
> *To:* Discussion and general questions about FreeDOS. <
> freedos-user@lists.sourceforge.net>
> *Subject:* Re: [Freedos-user] How to add AHCICD.sys in the auto
> check-list for USB BOOT?
>
> Hallo Herr richardkolacz...@hotmail.com,
>
> am Freitag, 11. März 2022 um 17:23 schrieben Sie:
>
> > I use the ONE USB BOOT stick for two laptops (only one has an optical
> drive).
>
>
> >  I was able to recognize the optical drive by simply putting
> > AHCICD.sys into the \FreeDOS\BIN\ folder (on the USB stick) and for
> > the laptop with the optical drive, the system boots up nicely.
>
>
> >  However, because I want to use the ONE USB stick for both
> > machines, now on the second laptop (without optical drive), on
> > bootup, the computer locks up at the AHCICD.sys stage. When the
> > AHCICD.sys file is simply removed, the usual FreeDOS checking on 4
> > CD possibilities  "errors out" in a controlled manner and allows
> continuation of the BOOT-up.
>
>
> >  So how can I have this 5th CD check (i.e. checking via AHCICD.sys)
> > in the manner of the 4 CD checks already in FreeDOS.
>
> load it like
>
> ?device=AHCIDD.SYS
>
> will ask you if it shall be loaded.
>
> Tom
>
>
>
>
>
>
>
> > Richard
>
>
>
> > From: Robert Riebisch 
> > Sent: Friday, 11 March 2022 7:25 PM
> > To: Discussion and general questions about FreeDOS.
> > 
> > Subject: Re: [Freedos-user] retro gamer review of FreeDOS 1.3
> >
> > Hi Jim,
>
>  >> One program to fix the "runtime error 200" is Robert and Marek's TSR
>  >> tool, which we include in FreeDOS 1.3:
>  >>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/pkg-html/tp7p5fix.html
>
> >  Robert here. I noticed, TP7P5FIX is not working for all software, but I
> >  didn't investigate this.
>
> >  I had good results with
> >  . (Sources:
> >  )
>
> >  Cheers,
> >  Robert
> >  --
> >+++ BTTR Software +++
> >   Home page: https://www.bttr-software.de/
> >  DOS ain't dead: https://www.bttr-software.de/forum/
>
>
> >  ___
> >  Freedos-user mailing list
> >  Freedos-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
>
>
>
> Mit freundlichen Grüßen / with kind regards
> Tom Ehlert
> +49-15151898538
>
>
>
> ___
> 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] Freedos & Arachne

[Louis Santillan]

You might try Links2 Browser in graphics mode. 2.25 is the latest version.

http://links.twibright.com/download/binaries/dos/links-2.25.exe

On Mon, Mar 7, 2022 at 11:02 AM  wrote:

>
>
> Hi!
> I have used Archne for a long time many years ago.
> Currently, both in freedos 1.2 and 1.3, ( no dosbox ) even with the latest
> release of Arachne it is in fact impossible for me to use it.
>  I know of arachne's well known issues with https and jv, but it also
> seems to not recognize the normal wattcp.cfg I use with links, lynx or
> gopherus. In fact I have to manually set my ip address, nameserver, gateway
> and even then it is very slow and often crashes. Even in off-line mode, for
> example as a .jpg viewer, it is very slow and tends to freeze.
>  Are there any underlying incompatibilities with freedos? is the 16 bit
> problem? a recognition problem from my ADSL fast fiber line?
> Yet, I repeat, with my ethernet drivers both links and gopherus are fine
> and fast.
> thanks Andrea
>
>
>
> Voucher MISE per P.IVA e PMI: fino a 2500€ per la Banda Ultralarga.
> https://www.tiscali.it/business/prodotti/voucher/
> 
>
> ___
> 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] Will freedos running in a Virtual box VM recognise a host attached USB security dongle?

[Louis Santillan]

I didn’t miss that.  Licensing software is something I presume Sean and his
company are familiar with in this day and age.  And it is every
individual’s responsibility.  However, my guide wasn’t intended as a lesson
about FOSS.



On Sat, Mar 5, 2022 at 3:24 AM Liam Proven  wrote:

> On Fri, 4 Mar 2022 at 20:09, Louis Santillan  wrote:
> >
> > I wrote a quick guide on how to pass through USB devices to a VirtualBox
> VM.
> >
> >
> https://sites.google.com/view/lpsantil/home/adding-usb-device-to-a-virtualbox-vm
> [...]
> > 5. Pick an appropriate USB spec controller.  Very old devices will
> likely use "USB 1.1 (OHCI) Controller" (super old web cams, scanners,
> keyboards, mice, etc.).  Devices and OSes made in the last 15 years will
> likely be better suited for "USB 2.0 (OHCI + EHCI) Controller".
>
> You are missing a *very* important point in your guide.
>
> VirtualBox is FOSS and can be run without restrictions anywhere. The
> VirtualBox Extension Pack is *not* FOSS and must be licensed. If used
> in a commercial or business setting, you have to pay for it. It's not
> that cheap and for multiple users it can be significant.
>
> USB 2 and higher need the extension pack. Only USB 1 can be used for free.
>
> --
> 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
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Will freedos running in a Virtual box VM recognise a host attached USB security dongle?

[Louis Santillan]

I wrote a quick guide on how to pass through USB devices to a VirtualBox VM.

https://sites.google.com/view/lpsantil/home/adding-usb-device-to-a-virtualbox-vm

It's quite simple to add a USB device to a VirtualBox 6.1 VM.  Elsewhere
you find this called "passing in a device", "device passthru", "device
passthrough" or something similar.  You'll find similar references & guides
for Video Cards, GPUs, Hard drives and Network Cards/NICs.

1. With the USB device plugged in, edit the "Settings" of the VM
2. Choose the "Ports" tab icon
3. Choose the "USB" sub-tab
4. Choose "Enable USB Controller" to enable an emulated USB controller in
your VM.
5. Pick an appropriate USB spec controller.  Very old devices will likely
use "USB 1.1 (OHCI) Controller" (super old web cams, scanners, keyboards,
mice, etc.).  Devices and OSes made in the last 15 years will likely be
better suited for "USB 2.0 (OHCI + EHCI) Controller".  You'll also likely
get better performance.  If you're emulating Windows 8.x, 10, 11, or recent
Linux, you could get the best device performance from "USB 3.0 (xHCI)
Controller".
6. Next click the small USB device icon with a green plus to select your
device.
7. Save and close your VM's "Settings".

On Fri, Mar 4, 2022 at 6:43 AM Sean Warner  wrote:

> Hello,
>
> Before I loose hours trying to get this to work this weekend. Would anyone
> know about getting freedos to recognize USB security dongles?
>
> I use a HASP USB security dongle
> 
>  to
> activate an old software program. I want to run that program from FreeDOS
> running in a Virtualbox VM.
>
> Lets say I connect the USB dongle to my Win 10 host that is running the
> VM. Will the FreeDOS OS (or the OS could maybe be Win 7 instead) running in
> the VM be able to see that HASP USB security dongle and the program running
> in that VM get activated for use?
>
> From my reading it can be done in Virtualbox but not sure if freedos will
> recognize the usb drivers or would I need to install them in the guest as
> well as the host which will be Win 10.
>
> Cheers,
>
> Sean
>
> On Fri 4 Mar 2022, 11:54 tom ehlert,  wrote:
>
>>
>>
>> >> 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?
>>
>> Just because it's true? in MSDOS at least.
>> However I have no idea if that is even implemented in FreeDOS, or
>> DOSEMU.
>>
>> > 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.
>>
>>
>> Tom
>>
>>
>>
>> ___
>> 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] An RPi way to use USB devices on old machines

[Louis Santillan]

Not entirely FreeDOS/DOS related but it might also help folks with
accessibility & old machines where navigating a machine with a
non-traditional device (gamepad or Joystick as a mouse) could be useful.

The RPi+HAT with an addon board for PS/2, Joystick port, and serial output
ports lets you use modern USB devices on machines that may not have the
ability to support USB devices.  This includes machines as old as the
original IBM PC.

https://github.com/dekuNukem/USB4VC
https://www.youtube.com/watch?v=tbHr7ULpusM
https://www.kickstarter.com/projects/dekunukem/usb4vc-usb-inputs-on-retro-computers
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] retro gamer review of FreeDOS 1.3

[Louis Santillan]

Hahaha I was just going to report this as well.

On Fri, Mar 4, 2022 at 9:22 AM Herminio Hernandez, Jr. <
herminio.hernande...@gmail.com> wrote:

> Has anyone watched this review of FreeDOS 1.3 by a Retro Gamer on YouTube.
> I thought it was a pretty good and fair review.
>
> https://www.youtube.com/watch?v=SNeq-F84Lx4
> ___
> 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] Interesting comment by Walter Bright

[Louis Santillan]

He claims "The DMC++ compiler is far and away the best C++ compiler on DOS."

https://news.ycombinator.com/item?id=30127615
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] UDVD2 vs SHSUCDX

[Louis Santillan]

Not sure about the circumstances of your Rayman crash but I’ve read many
posts about issues with that game on DOS. Apps that access the file system
or hardware directly, disk caches can cause certain types of file
corruption.  Whole file system corruption is odd and might indicate other
issues (CPU, RAM, IDE controller, BIOS, drive).

You haven’t provided any details about your hardware.  That said, most
drivers had compatibility with multiple drive makers.  And usually, you
only had to specify the device “/d:xxyyzz”.

There’s a list of popular device drivers here.

https://www.hiren.info/downloads/dos-files

MS used to license OAKCDROM.SYS and CD1.SYS for IDE drives.  You can find
other cd rom drivers at

https://www.allbootdisks.com/disk_contents/98.html


I’d try to find your vendor’s driver disk in archive.org or other vintage
computing sites.



On Sun, Jan 16, 2022 at 5:09 AM Michał Dec  wrote:

> W dniu 16.01.2022 o 13:58, Eric Auer pisze:
> > nothing worse than crashing should happen
> > if you give the wrong answers.
>
> After working with Rayman I am simply traumatized by crashing anything
> under DOS, because any and every crash can mean the destruction of the
> filesystem's integrity.
>
> I'll try and get the OAK driver and let you know what happens next.
>
> Best regards,
>
> Michał
>
>
>
> ___
> 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] Video complains that DOS should not be mantained

[Louis Santillan]

Yes.  In DOS, in Linux, in Mac`links -g` works great for me.

On Mon, Jan 10, 2022 at 8:17 PM Dan Schmidt  wrote:

> Have you tried links -g ?
>
> On Thu, Jan 6, 2022 at 10:11 PM Louis Santillan 
> wrote:
>
>> I haven’t had many crashes in Links2 in normal browsing.  I have been
>> able to make it crash calling out to external programs or by shelling out
>> and trying to return to the browser.
>>
>> On Thu, Jan 6, 2022 at 7:17 AM Dan Schmidt  wrote:
>>
>>> Links and Lynx both do TLS currently on DOS.  Links will even do images,
>>> but it's prone to crash in gui mode.
>>>
>>> On Thu, Dec 30, 2021 at 2:09 AM Louis Santillan 
>>> wrote:
>>>
>>>> Doesn't Links2 do TLS?
>>>>
>>>> On Tue, Dec 28, 2021 at 3:45 PM Jim Hall  wrote:
>>>>
>>>>> On Mon, Dec 27, 2021 at 6:28 PM Jose Senna  wrote:
>>>>> >
>>>>> > Liam Proven said:
>>>>> > > There were DOS email and chat and FTP
>>>>> > > clients; that stuff's fairly easy.
>>>>> >
>>>>> > Were is the right word. Most email
>>>>> > servers nowadays require TLS, which
>>>>> > is not available in DOS email clients.
>>>>> > There are few remaining FTP servers,
>>>>> > and I cannot tell how many also need
>>>>> > TLS.
>>>>>
>>>>>
>>>>> That's why I made sure you can access the FreeDOS website from
>>>>> http://www.freedos.org/ and https://www.freedos.org
>>>>>
>>>>> If you're using a DOS web browser, I don't think any DOS web browser
>>>>> can manage today's SSL, so you need http instead of https.
>>>>>
>>>>> But the links from freedos.org to other websites mostly use https, I
>>>>> think. Because not everyone wants to set up both http and https for a
>>>>> website.
>>>>>
>>>>>
>>>>> Jim
>>>>>
>>>>>
>>>>> ___
>>>>> 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
>>
> ___
> 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] Video complains that DOS should not be mantained

[Louis Santillan]

2.25 is latest version
http://links.twibright.com/download/binaries/dos/


On Thu, Jan 6, 2022 at 3:31 PM Jose Senna  wrote:

> Dan schmidt said:
>
>  | Links and Lynx both do TLS currently on DOS.
>
>  Which versions, please ?
>  There is still the problem of javascript,
> much used in HTTP mail pages nowadays.
>
>
>
>
> ___
> 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] Video complains that DOS should not be mantained

[Louis Santillan]

I haven’t had many crashes in Links2 in normal browsing.  I have been able
to make it crash calling out to external programs or by shelling out and
trying to return to the browser.

On Thu, Jan 6, 2022 at 7:17 AM Dan Schmidt  wrote:

> Links and Lynx both do TLS currently on DOS.  Links will even do images,
> but it's prone to crash in gui mode.
>
> On Thu, Dec 30, 2021 at 2:09 AM Louis Santillan 
> wrote:
>
>> Doesn't Links2 do TLS?
>>
>> On Tue, Dec 28, 2021 at 3:45 PM Jim Hall  wrote:
>>
>>> On Mon, Dec 27, 2021 at 6:28 PM Jose Senna  wrote:
>>> >
>>> > Liam Proven said:
>>> > > There were DOS email and chat and FTP
>>> > > clients; that stuff's fairly easy.
>>> >
>>> > Were is the right word. Most email
>>> > servers nowadays require TLS, which
>>> > is not available in DOS email clients.
>>> > There are few remaining FTP servers,
>>> > and I cannot tell how many also need
>>> > TLS.
>>>
>>>
>>> That's why I made sure you can access the FreeDOS website from
>>> http://www.freedos.org/ and https://www.freedos.org
>>>
>>> If you're using a DOS web browser, I don't think any DOS web browser
>>> can manage today's SSL, so you need http instead of https.
>>>
>>> But the links from freedos.org to other websites mostly use https, I
>>> think. Because not everyone wants to set up both http and https for a
>>> website.
>>>
>>>
>>> Jim
>>>
>>>
>>> ___
>>> 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] state of play

[Louis Santillan]

Advice about win32 apps is fairly off-topic here.  win32 apps that work on
HX that work on FreeDOS doesn't really make this request more on-topic.

You can find a bit of info apps that work at
https://www.japheth.de/HX.html
https://pmwiki.xaver.me/drdoswiki/index.php?n=Main.HX-DOS#toc24



On Sun, Jan 2, 2022 at 1:14 PM Paul Edwards  wrote:

> Hi folks.
>
> Freedos 1.3 RC5 is now good enough for my main need
> which is to do development work using gccwin (similar
> to mingw) to build Win32 executables. (making use of
> HX too).
>
> I am now looking for Freedos to be a viable alternative
> to Windows for the rest of the things I would like to do.
> What I'm looking for is Win32 applications that run
> under both Freedos+HX and Windows 10. In particular
> I want:
>
> 1. Something to display JPEGs. Just one JPEG at a time
> is fine. I actually have some software to do this already
> (public domain C code), but although it works under
> Win10, it produces garbage on Freedos + HX.
>
> 2. Something to play MP3s.
>
> 3. Something to play movies like MP4s.
>
> 4. Something to read and write text email - for this I would
> like a Win32 console mode application using ANSI escape
> sequences. Currently I have "msged" working for Fidonet
> technology messages.
>
> 5. Something to send/receive email to gmail. I am expecting
> this to be DOS-specific rather than a Win32 application, and
> I am expecting to need to use ethernet instead of Wifi, as I
> believe the ethernet spec is open but the Wifi spec is not.
>
> Does such software exist? If Win32 applications are not
> available, I'm interested in DOS alternatives.
>
> Note that I have produced my own Freedos distribution if
> anyone is interested. It is available at http://pdos.org
>
> Thanks. Paul.
>
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com
>
>
>
> ___
> 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] Video complains that DOS should not be mantained

[Louis Santillan]

Doesn't Links2 do TLS?

On Tue, Dec 28, 2021 at 3:45 PM Jim Hall  wrote:

> On Mon, Dec 27, 2021 at 6:28 PM Jose Senna  wrote:
> >
> > Liam Proven said:
> > > There were DOS email and chat and FTP
> > > clients; that stuff's fairly easy.
> >
> > Were is the right word. Most email
> > servers nowadays require TLS, which
> > is not available in DOS email clients.
> > There are few remaining FTP servers,
> > and I cannot tell how many also need
> > TLS.
>
>
> That's why I made sure you can access the FreeDOS website from
> http://www.freedos.org/ and https://www.freedos.org
>
> If you're using a DOS web browser, I don't think any DOS web browser
> can manage today's SSL, so you need http instead of https.
>
> But the links from freedos.org to other websites mostly use https, I
> think. Because not everyone wants to set up both http and https for a
> website.
>
>
> Jim
>
>
> ___
> 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] Now it gets odd Re: FreeDOS workaround for hidden IDE controller?

[Louis Santillan]

I was able to test and MS DOS 6.22 is able to see and format the IDE DOM
drive much like MS DOS 7.  So, I haven't looked at what FD FDISK is doing
differently, and it's likely a relatively small population that is affected
by this.

There seems to be some population of newer or obscure BIOSes that will
misreport IDE drives and BIOS booted HDD formatted USB drives as being non
fixed disks which FD FDISK requires to be able to interact with them.  I'm
willing to do some debugging, data capturing, and testing if there is a
place to report this.  I have a ton of screenshots already.  I'm also
willing to ship a Wyse SX0 if they think it would be necessary and useful.

Any tips of what would be useful to capture and post a bug report to?



On Fri, Dec 24, 2021 at 3:02 PM Louis Santillan  wrote:

> Apologies for the zombie thread revival.
>
> I recently bought 3 of these Wyse SX0 thin clients and I can confirm that
> FreeDOS 1.3-RC5 (and worse!) and FDISK are buggy on it.  I think the
> reality is that BIOS and USB boot code is only partially complete and just
> enough to boot into a more modern OS (ThinOS/Linux, Linux, Windows XPe,
> Windows CE, etc).
>
> The only FreeDOS image this BIOS is able to boot is a converted to RAW
> VMDK image from the LiteUSB zip. FullUSB slowly prints 2 dots but then gets
> seems to get stuck there.
>
> However, MS DOS 7 exhibits the same behavior.  Floppy Images, Bootable ISO
> images do not boot on the Wyse SX0 BIOS.  It is probably more accurate to
> say this BIOS seems to have a heavy preference for HD based booting (USB or
> 44-pin IDE).
>
> As for HD hiding, FreeDOS, FD FDISK, MS DOS 7, MS FDISK are confused by
> what the BIOS presents as the drive info usually found in lower areas of
> memory and/or what is presented via BIOS calls.  When FD boots from the
> VMDK image via USB drive, FDISK will say that there are no fixed disks
> present...which is physically true though as users, we would like the USB
> drive to be treated as a fixed disk.  Worse, Gregg was correct in that 44
> pin IDE DOM HDD is hidden or atleast obscured from being completely visible
> to FDISK.   FDISK still complains there are no fixed disks and the DOM
> should definitely be marked a fixed disk by the BIOS.   And there may be a
> drive enumeration error there when booting off USB with a 44-pin IDE DOM
> HDD together.  USB is mounted as C: while the DOM becomes D:.
>
> I say there is a bug above because while MS DOS 7 and tools like MSD &
> HWiNFO get all kinds of facts about the system incorrect, MS DOS 7 FDISK,
> FORMAT, SYS are still able to complete the tasks of initializing a drive
> partition table, formatting, and transferring a bootable MBR, and then
> transferring the minimal set of files required to boot a system.  You can't
> quite boot & install from USB as a casual DOS user would expect.  Instead,
> you need to initialize the drive, transfer setup files to the new drive,
> reboot w/o USB, then install with a half baked drive.  Having MS DOS 7
> still be able to install with a half working BIOS while FreeDOS (or atleast
> FD FDISK) is not able to is the bug.
>
> I'll do some testing with MS DOS 6.22 and see if it is an LBA vs. BIOS
> partition type thing, or maybe a FAT32 vs. FAT16 thing.
>
>
>
> On Sat, Jan 13, 2018 at 4:08 AM Eric Auer  wrote:
>
>>
>> Hi! As said, I can imagine that the BIOS of your
>> system has problems if the USB stick and DOM both
>> count as harddisks. But you already have bootable
>> DOS installed from floppy now, so I suggest ways
>> which are easier:
>>
>> You can connect the DOM instead of the normal disk
>> to a "bigger" PC with CD-ROM and powerful BIOS and
>> install there, then put the DOM into the small PC
>> again.
>>
>> You can use the ability of FreeDOS drivers to use
>> ISO files instead of physical CD/DVD drives and
>> then run the installer from that virtual CD ROM.
>>
>> Read the SHSU* driver documentation or check the
>> contents of the normal ISO for examples of how to
>> load and configure the drivers.
>>
>> You can use older versions of FreeDOS boot images
>> because those only use FLOPPY type boot areas and
>> avoid the conflict of the current virtual HARDDISK
>> boot image. Then, upgrade to a newer version using
>> the installed version, or just keep things as-is.
>>
>> So there are many ways to have a guilt-free DOS :-)
>>
>> Regards, Eric
>>
>> PS: Yes, you can use USB drives formatted ZIP style
>> to boot from with various - but not all - BIOSes.
>>
>>
>>
>> --
>> Check out the vi

Re: [Freedos-user] Freedos-user Digest, Vol 2142, Issue 5

[Louis Santillan]

I also have HP t5745 thin clients (Intel Atom 1.66GHz 1C/2T, 1GB-4GB RAM,
2GB DOM) and I very much prefer it's BIOS.  You can stick any format USB
drive in it and DOS (FreeDOS or MS DOS 6.22 or 7) will mount it.  And it
has a total of 6 USB ports!  I also bought the expansion module for it that
adds a PCI or PCIe slot w/a fan, a parallel port and a 2nd serial port.
The CPU is obviously much faster than the 365MHz Cyrix/National
Semiconductor Geode LX that is in Wyse SX0 S10.  However, the integrated
Intel GL40/GMA X4500MHD in the HP reports itself as VBE 3.0 compatible and
the Wyse has a Geode GX2 VGA VBE 2.0 compatible card.  The Wyse seems to be
more DOS and Windows 98 friendly though both should also be ok in Windows
XP.  Both also do very well with lightweight Linux distros like
TinyCoreLinux or old Lubuntu 16.04/18.04.  Networking wise, the HP has a
BCM57780 which requires a hard to track down B57 packet driver from Dell!
The Wyse has a Realtek 8139 that works with the same packet drivers that
work in VirtualBox or QEMU.

On Fri, Dec 24, 2021 at 3:35 PM Daniel  wrote:

> I have a Wyse VX0 V10LE and I admit I haven’t tested FreeDOS on it.  If I
> am able to get anothe DOM (Disk On Module), I would love to see if it works
> on the system.
>
> The cpu is 1.2ghz, RAM is 1gb, and the DOM is 16gb.
>
> Originally came with a Windows 98/XP dual boot.  Currently running Windows
> 98 (mainly in DOS), and a vm running OS/2.
>
> Although I am unable to natively install OS/2, Windows 98 and DOS runs
> perfectly and putting a usb stick is available to DOS without needing any
> drivers in DOS which is a plus.  One downside is CD off USB is a big issue
> when trying to install an OS.
>
> On Fri, Dec 24, 2021 at 18:02 
> wrote:
>
>> Send Freedos-user mailing list submissions to
>> freedos-user@lists.sourceforge.net
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> or, via email, send a message with subject or body 'help' to
>> freedos-user-requ...@lists.sourceforge.net
>>
>> You can reach the person managing the list at
>> freedos-user-ow...@lists.sourceforge.net
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Freedos-user digest..."
>>
>>
>> Today's Topics:
>>
>>1. Re: Video complains that DOS should not be maintained (Wengier W)
>>2. Re: Now it gets odd Re: FreeDOS workaround for hidden IDE
>>   controller? (Louis Santillan)
>>
>>
>> --
>>
>> Message: 1
>> Date: Fri, 24 Dec 2021 22:46:34 + (UTC)
>> From: Wengier W 
>> To: "Discussion and general questions about FreeDOS."
>> 
>> Subject: Re: [Freedos-user] Video complains that DOS should not be
>> maintained
>> Message-ID: <1457277452.1987137.1640385994...@mail.yahoo.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>>  I certainly hope to see more people using DOS/FreeDOS as the only (or
>> primary) operating system. However, without things like full support for
>> Internet and modern hardware (modern sound card, USB devices, etc) this
>> cannot occur, unfortunately. IMO, DOS/FreeDOS need to support things just
>> like a typical "modern" OS (e.g. Linux) does, so that the general public
>> won't consider DOS a "legacy" OS, or a system that is limited to very
>> specific uses.
>> Wengier
>> On Friday, December 24, 2021, 05:35:06 p.m. EST, John Vella <
>> john.ve...@gmail.com> wrote:
>>
>>  I'm going to make it my new year project to finish getting the 80486 pc
>> working, and once I've upgraded the memory, (4 Meg isn't going to be
>> enough, is it?) I'll be using freedos as the only operating system for my
>> distraction free writing pc.?
>> On Fri, 24 Dec 2021, 22:00 Jim Hall,  wrote:
>>
>> On Fri, Dec 24, 2021 at 2:11 PM Jon Brase  wrote:
>> > They're not talking about it in the context of log4j itself, they're
>> > talking about it in the context of other open source projects, that
>> > don't have something like the Apache foundation behind them, that
>> > are critical infrastructure, but have one or two maintainers working
>> > on them as a labor of love alongside a day job, and the potential,
>> > as such projects become legacy software, for them to still be
>> > half-maintained (and maybe maintain a significant user base) long
>> > after an institutionally maintained project would have officially
>> >

Re: [Freedos-user] Now it gets odd Re: FreeDOS workaround for hidden IDE controller?

[Louis Santillan]

Apologies for the zombie thread revival.

I recently bought 3 of these Wyse SX0 thin clients and I can confirm that
FreeDOS 1.3-RC5 (and worse!) and FDISK are buggy on it.  I think the
reality is that BIOS and USB boot code is only partially complete and just
enough to boot into a more modern OS (ThinOS/Linux, Linux, Windows XPe,
Windows CE, etc).

The only FreeDOS image this BIOS is able to boot is a converted to RAW VMDK
image from the LiteUSB zip. FullUSB slowly prints 2 dots but then gets
seems to get stuck there.

However, MS DOS 7 exhibits the same behavior.  Floppy Images, Bootable ISO
images do not boot on the Wyse SX0 BIOS.  It is probably more accurate to
say this BIOS seems to have a heavy preference for HD based booting (USB or
44-pin IDE).

As for HD hiding, FreeDOS, FD FDISK, MS DOS 7, MS FDISK are confused by
what the BIOS presents as the drive info usually found in lower areas of
memory and/or what is presented via BIOS calls.  When FD boots from the
VMDK image via USB drive, FDISK will say that there are no fixed disks
present...which is physically true though as users, we would like the USB
drive to be treated as a fixed disk.  Worse, Gregg was correct in that 44
pin IDE DOM HDD is hidden or atleast obscured from being completely visible
to FDISK.   FDISK still complains there are no fixed disks and the DOM
should definitely be marked a fixed disk by the BIOS.   And there may be a
drive enumeration error there when booting off USB with a 44-pin IDE DOM
HDD together.  USB is mounted as C: while the DOM becomes D:.

I say there is a bug above because while MS DOS 7 and tools like MSD &
HWiNFO get all kinds of facts about the system incorrect, MS DOS 7 FDISK,
FORMAT, SYS are still able to complete the tasks of initializing a drive
partition table, formatting, and transferring a bootable MBR, and then
transferring the minimal set of files required to boot a system.  You can't
quite boot & install from USB as a casual DOS user would expect.  Instead,
you need to initialize the drive, transfer setup files to the new drive,
reboot w/o USB, then install with a half baked drive.  Having MS DOS 7
still be able to install with a half working BIOS while FreeDOS (or atleast
FD FDISK) is not able to is the bug.

I'll do some testing with MS DOS 6.22 and see if it is an LBA vs. BIOS
partition type thing, or maybe a FAT32 vs. FAT16 thing.



On Sat, Jan 13, 2018 at 4:08 AM Eric Auer  wrote:

>
> Hi! As said, I can imagine that the BIOS of your
> system has problems if the USB stick and DOM both
> count as harddisks. But you already have bootable
> DOS installed from floppy now, so I suggest ways
> which are easier:
>
> You can connect the DOM instead of the normal disk
> to a "bigger" PC with CD-ROM and powerful BIOS and
> install there, then put the DOM into the small PC
> again.
>
> You can use the ability of FreeDOS drivers to use
> ISO files instead of physical CD/DVD drives and
> then run the installer from that virtual CD ROM.
>
> Read the SHSU* driver documentation or check the
> contents of the normal ISO for examples of how to
> load and configure the drivers.
>
> You can use older versions of FreeDOS boot images
> because those only use FLOPPY type boot areas and
> avoid the conflict of the current virtual HARDDISK
> boot image. Then, upgrade to a newer version using
> the installed version, or just keep things as-is.
>
> So there are many ways to have a guilt-free DOS :-)
>
> Regards, Eric
>
> PS: Yes, you can use USB drives formatted ZIP style
> to boot from with various - but not all - BIOSes.
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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] Video complains that DOS should not be maintained

[Louis Santillan]

And beyond industrial systems, it is sometimes common to see DOS (and
FreeDOS especially) used as part of firmware flashing processes for BIOS,
IDE, SCSI, SATA, SAS, HBA, Ethernet and WiFi controllers especially in
enterprise and network hardware.

On Fri, Dec 24, 2021 at 11:08 AM Travis Siegel  wrote:

> Someone really should tell these guys that dos is still widely used in
> industrial processes today, wonder what they'd say about that. :)
>
>
> On 12/24/2021 12:53 PM, Parodper wrote:
> > O 24/12/21 ás 18:30, Ralf Quint escribiu:
> >> On 12/24/2021 4:48 AM, Bryan Kilgallin wrote:
> >>> The comment against open-source DOS is at the end of this
> >>> discussion. See after 26 minutes.
> >>> https://youtu.be/Opqgwn8TdlM
> >>>
> >> I really wonder how that would effect DOS, after all there is no web
> >> interface, nor any Java in (Free)DOS. So (without having watched this
> >> rather long video yet), any such conclusion seems to be a bit far
> >> fetch IMHO...
> >>
> >> Ralf
> >>
> >
> > They only mention MS-DOS as an example, at the end. Quote from 24:13
> > to 24:50:
> >
> > > [Talking about open source projects being maintained by only one or
> > > two people]
> > > You could see, for example, bits of software that really should be
> > > allowed to die. But, [for example] let's suppose that MS-DOS was open
> > > source. You can guarantee that there would probably be a community of
> > > people still maintaining MS-DOS today. We probably don't want bits of
> > > software like MS-DOS still being maintained. They're interesting
> > > historical curiosities, [but] they're not software that should be used
> > > today. And that's the danger, that the software exists beyond its sell
> > > by date, because anyone can maintain it and it still looks useful.
> >
> >
> >
> >
> >
> > ___
> > 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] Speaking of (tiny) DOS gaming PCs

[Louis Santillan]

And I forgot to mention we also now have Raspberry Pis acting as Virtual
Floppy connected via ISA.

https://www.smbaker.com/raspberry-pi-virtual-floppy-for-isa-pc-xtat-computers

On Tue, Dec 7, 2021 at 4:51 PM Louis Santillan  wrote:

> There seems to be a resurgence of 8088/ISA compatible homebrew computers
> and designs.  Besides NuXT[0], the original Sergey Kiseliev Designs
> [1][2][3][4][5][6], we now have EMM's designs [7][8][9][10][11][12][13],
> some ISA ethernet cards [14][15], some sound cards
> [16][17][18][19][20][21][22][23][24], and a VGA card [25].   Would be
> interesting if they could be shrunk down a bit.  Otherwise, a Raspberry Pi
> Zero W or Zero 2 W is far easier to sneak into a small case.
>
>
> [0]
> https://monotech.fwscart.com/NuXT_v20_MicroATX_Turbo_XT_10MHz_832K_XTIDE_MultiIO_SVGA/p6083514_19777986.aspx
> [1] http://www.malinov.com/Home/sergeys-projects/sergey-s-xt
> [2] https://github.com/skiselev/micro_8088
> [3] https://github.com/skiselev/isa8_backplane
> [4] http://www.malinov.com/Home/sergeys-projects/isa-supervga
> [5] http://www.malinov.com/Home/sergeys-projects/isa-opl2-card
> [6] http://www.malinov.com/Home/sergeys-projects/isa-fdc-and-uart
> [7] https://www.youtube.com/user/elijahmmiller/videos
> [8] https://www.homebrew8088.com/
> [9]
> https://www.homebrew8088.com/home/archived-pages/v40-motherboard-project
> [10] https://www.homebrew8088.com/home/archived-pages/8088-pc-compatible
> [11]
> https://www.homebrew8088.com/home/archived-pages/8088-mother-board-project
> [12] https://www.homebrew8088.com/home/archived-pages/isa-card-lcd-screen
> [13] https://www.homebrew8088.com/home/archived-pages/raspberry-pi
> [14] https://github.com/Manawyrm/ISA8019
> [15] https://github.com/skiselev/isa8_eth
> [16] https://github.com/hkzlab/ES688_ISA8
> [17] https://github.com/hkzlab/ES1868_ISA8
> [18] https://github.com/spark2k06/Internal_ISAOPL3
> [19] https://www.excelvalley.com/product/opl3plt-synth/
> [20] https://github.com/zjuyzj/OPL2LPT-Replica
> [21] https://github.com/yeokm1/pcb-covox
> [22] https://github.com/schlae/snark-barker
> [23] https://github.com/labs-lv/blasterboard
> [24] https://github.com/schlae/graphics-gremlin
> [25] https://github.com/Leshak-pcb/Pine-CL-GD5434
>
>
>
> On Mon, Nov 29, 2021 at 12:14 AM Frantisek Rysanek <
> frantisek.rysa...@post.cz> wrote:
>
>> FreeDOS embedded in the BIOS is certainly a nice touch.
>> Then again, the one thing that speaks in favour of the weeCee is the
>> SB-Pro-compatible audio chip. Unique to the weeCee, of all the
>> Vortex-based machines out there.
>>
>> The Vortex86DX in particular is a "sweet spot" for old-school legacy
>> DOS gaming - that Vortex generation still has native full-fledged ISA
>> bus, can be underclocked below "an equivalent of Pentium 200 MHz"
>> (which is more like 400 Vortex MHz), while at the same time already
>> having an FPU. And the onboard XGI Z9s with 32 MB of dedicated VRAM
>> is also nice (including its VESA option ROM).
>>
>> In other misc hardware, the Vortex86DX has one other potential
>> advantage in the way of "legacy compatibility": the AMI BIOS from
>> ICOP still has configurable options related to ISA IOMEM windows (no
>> particular use for that in the weeCee). On the more modern Vortex
>> generations, this is fading away.
>>
>> Frank
>>
>>
>> On 28 Nov 2021 at 20:00, Ivan Ivanov wrote:
>>
>> > Dennis, thank you for sharing. First of all, if you'd like to get a
>> > Vortex86 CPU-based PC, better to get those which are supported by the
>> > opensource coreboot BIOS, instead of the proprietary closed-source
>> > BIOS. This way, with the help of coreboot's SeaBIOS payload, you'll be
>> > able to - using a simple "cbfstool" command - add a floppy image of
>> > FreeDOS / whatever other floppy OS - to the coreboot.rom BIOS image,
>> > flash it into a BIOS chip, and have a FreeDOS permanently available as
>> > a boot entry! (being able to run it directly from a BIOS chip). If
>> > you're interested, ask questions & I could reply with more info :-)
>> >
>> > , 27 . 2021 .  18:37, dmccunney :
>> > >
>> > >
>> https://www.pcbway.com/project/shareproject/weeCee___Tiny_DOS_Gaming_PC.html
>> > >
>> > > https://www.youtube.com/watch?v=USHvvSbYmJA
>> > > --
>> > > __
>> > > Dennis
>> > >
>> > >
>> > > ___
>> > > Freedos-user mailing list
>> > > Freedos-user@lists.sourceforge.net
>

Re: [Freedos-user] Speaking of (tiny) DOS gaming PCs

[Louis Santillan]

There seems to be a resurgence of 8088/ISA compatible homebrew computers
and designs.  Besides NuXT[0], the original Sergey Kiseliev Designs
[1][2][3][4][5][6], we now have EMM's designs [7][8][9][10][11][12][13],
some ISA ethernet cards [14][15], some sound cards
[16][17][18][19][20][21][22][23][24], and a VGA card [25].   Would be
interesting if they could be shrunk down a bit.  Otherwise, a Raspberry Pi
Zero W or Zero 2 W is far easier to sneak into a small case.


[0]
https://monotech.fwscart.com/NuXT_v20_MicroATX_Turbo_XT_10MHz_832K_XTIDE_MultiIO_SVGA/p6083514_19777986.aspx
[1] http://www.malinov.com/Home/sergeys-projects/sergey-s-xt
[2] https://github.com/skiselev/micro_8088
[3] https://github.com/skiselev/isa8_backplane
[4] http://www.malinov.com/Home/sergeys-projects/isa-supervga
[5] http://www.malinov.com/Home/sergeys-projects/isa-opl2-card
[6] http://www.malinov.com/Home/sergeys-projects/isa-fdc-and-uart
[7] https://www.youtube.com/user/elijahmmiller/videos
[8] https://www.homebrew8088.com/
[9] https://www.homebrew8088.com/home/archived-pages/v40-motherboard-project
[10] https://www.homebrew8088.com/home/archived-pages/8088-pc-compatible
[11]
https://www.homebrew8088.com/home/archived-pages/8088-mother-board-project
[12] https://www.homebrew8088.com/home/archived-pages/isa-card-lcd-screen
[13] https://www.homebrew8088.com/home/archived-pages/raspberry-pi
[14] https://github.com/Manawyrm/ISA8019
[15] https://github.com/skiselev/isa8_eth
[16] https://github.com/hkzlab/ES688_ISA8
[17] https://github.com/hkzlab/ES1868_ISA8
[18] https://github.com/spark2k06/Internal_ISAOPL3
[19] https://www.excelvalley.com/product/opl3plt-synth/
[20] https://github.com/zjuyzj/OPL2LPT-Replica
[21] https://github.com/yeokm1/pcb-covox
[22] https://github.com/schlae/snark-barker
[23] https://github.com/labs-lv/blasterboard
[24] https://github.com/schlae/graphics-gremlin
[25] https://github.com/Leshak-pcb/Pine-CL-GD5434



On Mon, Nov 29, 2021 at 12:14 AM Frantisek Rysanek <
frantisek.rysa...@post.cz> wrote:

> FreeDOS embedded in the BIOS is certainly a nice touch.
> Then again, the one thing that speaks in favour of the weeCee is the
> SB-Pro-compatible audio chip. Unique to the weeCee, of all the
> Vortex-based machines out there.
>
> The Vortex86DX in particular is a "sweet spot" for old-school legacy
> DOS gaming - that Vortex generation still has native full-fledged ISA
> bus, can be underclocked below "an equivalent of Pentium 200 MHz"
> (which is more like 400 Vortex MHz), while at the same time already
> having an FPU. And the onboard XGI Z9s with 32 MB of dedicated VRAM
> is also nice (including its VESA option ROM).
>
> In other misc hardware, the Vortex86DX has one other potential
> advantage in the way of "legacy compatibility": the AMI BIOS from
> ICOP still has configurable options related to ISA IOMEM windows (no
> particular use for that in the weeCee). On the more modern Vortex
> generations, this is fading away.
>
> Frank
>
>
> On 28 Nov 2021 at 20:00, Ivan Ivanov wrote:
>
> > Dennis, thank you for sharing. First of all, if you'd like to get a
> > Vortex86 CPU-based PC, better to get those which are supported by the
> > opensource coreboot BIOS, instead of the proprietary closed-source
> > BIOS. This way, with the help of coreboot's SeaBIOS payload, you'll be
> > able to - using a simple "cbfstool" command - add a floppy image of
> > FreeDOS / whatever other floppy OS - to the coreboot.rom BIOS image,
> > flash it into a BIOS chip, and have a FreeDOS permanently available as
> > a boot entry! (being able to run it directly from a BIOS chip). If
> > you're interested, ask questions & I could reply with more info :-)
> >
> > , 27 . 2021 .  18:37, dmccunney :
> > >
> > >
> https://www.pcbway.com/project/shareproject/weeCee___Tiny_DOS_Gaming_PC.html
> > >
> > > https://www.youtube.com/watch?v=USHvvSbYmJA
> > > --
> > > __
> > > Dennis
> > >
> > >
> > > ___
> > > 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] (no subject)

[Louis Santillan]

It would likely be prudent to get a confirmation statement from Russell
Nelson as well.

Per crynwr.com

nel...@crynwr.com
+1 315 323 1241 voice
Crynwr Software
521 Pleasant Valley Rd.
Potsdam, NY 13676

On Thu, Oct 14, 2021 at 12:19 AM John Vella  wrote:

> Agree!
>
> On Thu, 14 Oct 2021, 07:33 Thomas Mueller,  wrote:
>
>> from Jim Hall:
>>
>>
>> > I don't know why the sources later had an "AMD" statement put on them,
>> > but you cannot claim "proprietary" or "copyright" on something that
>> > was previously released under the GNU General Public License.
>>
>> > It appears that somewhere along the line, someone (at AMD?) had access
>> > to the sources, probably in a larger source tree, and ran a batch job
>> > or script to apply the "AMD" statement to a bunch of source files. And
>> > that happened to catch these GPL and public domain source files. I
>> > believe that was done in error. The original public domain and GPL
>> > declarations trump the latter "AMD" statement.
>>
>>
>> > Resolution:
>>
>>
>> > (1) Let's re-accept the FDNET package into the next FreeDOS
>> distribution.
>>
>> > (2) I'll make a note about this decision in the FreeDOS wiki at
>> > http://wiki.freedos.org/wiki/index.php/Releases/1.3/Packages
>> > (this currently has a red "do not include" note on it .. I'll update
>> > to change it a green "include" message)
>>
>> > (3) To prevent future confusion, I'll create a new version of these
>> > source files that *removes* the "AMD" statement, where a previous GPL
>> > or public domain declaration was already made. (I think that's all of
>> > the files in question.) I'll also create (or update, if it exists) a
>> > README file to note the changes to the source files, and why.
>>
>>
>> > I look forward to including networking support again in the next
>> > distribution, which should be FreeDOS 1.3 RC5.
>>
>>
>> > *If you agree or disagree, I'd appreciate your reply to this email.
>> > Agreement can be simply "agree" or "+1". If you disagree, please
>> > discuss. (But consensus from the last discussion favored including
>> > FDNET, so if no one disagrees now, I'll assume no concerns on this.)
>>
>> Agree
>>
>> Tom
>>
>>
>>
>> ___
>> 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] Netgear LNE100TX

[Louis Santillan]

Try using Georg Potthast's NICSCAN [0][1] or David Dunfield's PCINIC [2][3]
to find the NIC.  I think PCINIC can even suggest a driver from PKTDRV [4].

[0] http://www.georgpotthast.de/sioux/packet.htm
[1] http://www.georgpotthast.de/sioux/pktdrv/nicscan.zip
[2] http://dunfield.classiccmp.org/dos/
[3] http://dunfield.classiccmp.org/dos/pcinic.zip
[4] http://dunfield.classiccmp.org/dos/pktdrv.zip

On Mon, Jul 26, 2021 at 4:03 PM Dan Schmidt  wrote:

> Well, I can tell you this much isn't right:
> >My Ethernet Address Is FF:FF:FF:FF:FF:FF
> That driver doesn't like or can't find your card.
>
>
>
> On Mon, Jul 26, 2021 at 4:25 AM Richard Hoffman <
> richardhoffman2...@gmail.com> wrote:
>
>> Hi,
>>
>> I have been having trouble setting up my ethernet card on my freedos
>> installation.   I am currently attempting to set up this card with the
>> LNE100TX.com packet driver.
>>
>> I run the driver with LNE100TX 0x60  and I get the following
>>
>> Autonegotiation Not Complete
>> Packet Driver Interrupt Number 0X60
>> IO Port 0xDC00
>> Hardware Interrupt Number 11
>> Media Type Is 100baseTX Full Duplex
>> My Ethernet Address Is FF:FF:FF:FF:FF:FF
>> Packet Driver is loaded at segment 3C2
>>
>> I have my network wired from my DSL router to an 8 port 10/100 mbps
>> switch.   From there it goes to my windows 10 pc and my freedos pc.
>>
>> I have tried about every switch option with the packet driver and I keep
>> getting the same result.  Is this a hardware problem with the ethernet card
>> or is it a router issue?
>>
>> Also could this be an IRQ conflict?
>>
>> Thanks.
>> ___
>> 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] Upgrading the BIOS with FreeDOS

[Louis Santillan]

The PE format uses a DOS stub prefix which usually handles DOS execution.

https://en.wikipedia.org/wiki/Portable_Executable#History

On Mon, Jun 28, 2021 at 11:10 AM Paul Dufresne via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> I have an example (from Dell):
>
>
> https://www.dell.com/support/home/en-ca/drivers/driversdetails?driverid=tjgkp=w764=optiplex-3020m-desktop
>
> the page says: "This file format consists of a BIOS executable file. The
> Universal (Windows/MS DOS) format can be used to install from any Windows
> or MS DOS environment." but it is a PE file:
> paul@kasparno:~/Téléchargements$ file
> ~/Téléchargements/OptiPlex_3020M_A15.exe
> /home/paul/Téléchargements/OptiPlex_3020M_A15.exe: PE32 executable (GUI)
> Intel 80386, for MS Windows
>
>
>
> ___
> 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] Crynwr package contains PCNTPK.COM

[Louis Santillan]

I don't get what the issue with PCNTPK.COM packet driver is?

Per the amdpd.zip file at http://crynwr.com/drivers/00index.html , it is
copyright Russell Nelson 1990 w/a GPLv1 license in 1990 and copyright AMD
1993 w/a pseudo Public Domain-ish license (PCNTPK.ASM).  While not packaged
the way we expect of GPL v2 or v3 code, I think the 1990 copyright and GPL
v1 license would supersede AMD's, but IANAL.  Russell Nelson wrote many of
the drivers and/or skeletons in his collection.

If this driver from Crynwr doesn't suit you, I think many of the vendors
(IBM, HP, Compaq, Dell, etc.) in the past have had compatible drivers.
Check their driver lists and/or FTP archives.  The driver has been packaged
dozens and maybe hundreds of times.  I think AMD would sue various people &
companies if they had an issue.


On Thu, Jun 3, 2021 at 9:08 PM David Calman <
alt.people.davidcal...@gmail.com> wrote:

> Does this mean it will be pulled from the distribution? Or does it
> mean we'll actually try and address this issue head-on, because now it
> affects two packages?
>
> I think FDNET is pretty mission-critical, given it's in the default
> FDAUTO.BAT. The problem with that, if what I read on the wiki is
> correct, is that AMD tried to pull some shenanigans after releasing
> PCNTPK to the public. The Crynwr package also has this problem because
> it contains PCNTPK.COM.
>
> Do we simply drop support for AMD network interface cards? Is that the
> solution here?
>
>
> ___
> 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] What it was all about for some of us

[Louis Santillan]

While empathize with the yearning for the simpler time in computing, taking
it from Ted Campbell [0], the Verda Spell passage seems like it was
intended as a humorous invocation of a muse.  Much like Homer did in the
Iliad and Odyssey [1][2].

[0] https://sourceforge.net/p/bwbasic/bugs/7/#a62d
[1] https://en.wikipedia.org/wiki/Muses#In_literature
[2]
https://classical-inquiries.chs.harvard.edu/a-re-invocation-of-the-muse-for-the-homeric-iliad/

On Fri, Apr 30, 2021 at 11:55 PM Bryan Kilgallin 
wrote:

> Thanks, Alvah:
>
> > I wish I could articulate the
> > valid things that are surrendered with the demise of computing at that
> > level. Fortunately, people who invest time and energy into the use of
> > FREEDOS understand what  it is that I am unable to convey.
>
> There's a sense of understanding, and hence control. I am not
> forking-out on expensive licences for proprietary software. That is so
> complex that my friends don't understand half of it!
> --
> members.iinet.net.au/~kilgallin/
>
>
> ___
> 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] DOS on (very) small form factor PCs?

[Louis Santillan]

Phil’s Computer Lab has covered lots of DOS compatible Thin Clients.  I
personally have 5 fanless HP t5745.   Atom N280 (single core, dual thread)
CPUs, mine have 1GB-4GB RAM, 2GB IDE DOM, 10/100/1000 Ethernet by Broadcom,
serial port, PS/2 ports, Intel GL40 VGA & DisplayPort, will USB boot
FreeDOS and others.  Fairly small, about the size of a DVD-ROM drive.  I
even bought the expansion bays to allow you to fit a PCI or PCI-E card
(also adds a quiet fan) and a parallel port.  Still sell on eBay for $25.

https://m.youtube.com/playlist?list=PL5T8bmLxd_T3xTjY3fpBdT3zpZfHPtbDJ

https://www.parkytowers.me.uk/thin/hp/t5740/




On Wed, Apr 28, 2021 at 3:05 PM Eric Auer  wrote:

>
> Hi Tom,
>
> >> ...the board format does not matter much.
> >> It's the CPU model/generation that matters.
> >
> > NOT. AT. ALL.
> >
> > each Intel/AMD CPU produced the last 20 years is able
> > to execute the same way that the previous versions did.
>
> The point is that everything which is remotely
> similar to a Raspberry Pi uses ARM style CPU,
> but the SIZE and COST of Raspberry Pi (Thomas
> has mentioned Asus Tinker Board as example) are
> obviously tempting. It would be nice to have a
> non-ARM, x86 compatible hardware in that range.
>
> So I would like to hear whether single board
> computers in similar size and price (not PC/104
> price level) with x86 compatible CPU exist and
> which of them can be recommended by people here.
>
> Of course we can always buy x86 Mini-ITX with
> even a single normal size PCIe or PCI slot and
> many good old interfaces, but that would be a
> LOT larger than Raspberry style. With Nano- or
> Pico-ITX, even SATA becomes less common. Might
> not be a problem if the on-board M.2 or mSATA
> slot of other boards is what you want, but if
> you want to recycle existing 2.5 inch drives,
> SATA would be nice. I could name a number of
> other interfaces, but I am mainly interested
> to hear what YOU people have been using in the
> category of tiny, affordable x86 computers :-)
>
> Cheers, Eric
>
> PS: While Thomas does not want sound, of course
> I am also interested about variants with sound,
> maybe even ISA Sound Blaster compatible sound.
>
> > Ah, thanks, Frank. I don’t need sound, I actually don’t WANT sound
> > (and no fans)
> >
> > Th.
> >
>
>
> ___
> 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] Recovery of a file on a non booting Windows computer

[Louis Santillan]

Jim,

DOS & HW basic like the above might make good 5 minute "FD Shorts" on
youtube.

On Wed, Apr 14, 2021 at 9:45 AM Ralf Quint  wrote:

> On 4/14/2021 5:19 AM, Stephanos wrote:
> > Dear All
> >
> > I want to boot to freeDOS using a CD ROM.  Then I want to insert a
> > memory stick into the computer and copy a file from the Windows HDD onto
> > the memory stick.  Is this possible and if so which version of freeDOS
> > do I use?
>
> If you are talking about any Windows newer than Windows ME, simply
> forget about this route.
>
> Use a Linux Live CD (I personally would recommend Linux Mint 20.1 Mate)
> and use that one instead...
>
> 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
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] networking/wifi

[Louis Santillan]

IMO, ISA is a better option for truly vintage machines.  I think if someone
combined the ideas PiModem/Wifi232, Pi Virtual Floppy [0], and ISA8019 [2]
(which is an NE2000!), then that would be the ideal.  An ISA card powered
by a Pi Zero W that could emulate a Floppy/HDD/CD-ROM/DVD-ROM and provide
1000BaseT Ethernet and/or WiFi would be a super card.  Doing BaseT or WiFi
transparently in SW like Dr. Baker did showed could be done in the Pi
Virtual Floppy would be awesome.

[0]
https://www.smbaker.com/raspberry-pi-virtual-floppy-for-isa-pc-xtat-computers
[1] https://github.com/Manawyrm/ISA8019

On Fri, Mar 19, 2021 at 2:03 PM  wrote:

> Hi! Eric
> as for the wi-fi I have solved the problem in an empirical way: I have
> long bought
>
>  a TP-Link TPL-MR3020 mini router which detects available wireless
> networks and which
>
>  has an ethernet port to which I can connect my laptop .
>
> It also has the possibility to connect - on the move - an internet key.
>
> The only problem is that to configure it and to detect the networks I need
> a win or linux browser because with LINKS - which I use in dos -it is
> obviously not possible.
>
> regards
> andrea
>
> Il 18.03.2021 13:55 Eric Auer ha scritto:
>
> Hi!
>
> Am just wondering if this is the current status, or some old comment:
> "Wireless devices connected via USB can not yet be used with FreeDOS." (
> http://freedos.sourceforge.net/wiki/index.php/WiFi)
>
> This meant "USB dongles which serve as WiFi or Bluetooth modems
> have no DOS drivers" and is still the case as far as I know:
>
> In rare cases, DOS drivers for PCMCIA WiFi modems have existed.
> For current computers, the recommended workaround would be to
> use an external WiFi to LAN converter, as it is much easier to
> find LAN style wired network drivers for DOS.
>
> Similarily, I would expect Bluetooth to serial port converter
> modules to work reasonably well with DOS: Those tend to have a
> modem-style command system to control them and actually serial
> interfaces between microcontrollers and Bluetooth modules are
> widespread. It is slow enough to be useful even if not connected
> by for example a faster SPI bus. Of course you would still need
> a converter for RS232 signal levels. Combined products may exist.
> Also, DOS users tend to have modem command skills and dialup tools.
>
> Maybe people here could talk about their experiences with specific
> brands of WiFi LAN gateways or Bluetooth RS232 adapters in DOS :-)
>
> Regards, Eric
>
>
>
> ___
> Freedos-user mailing 
> listFreedos-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
>
>
> Con Tiscali Mobile Smart 30 4G hai minuti illimitati, 100 SMS e 30 Giga in
> 4G a soli 8,99€ al mese. http://tisca.li/smart30
>
> ___
> 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] networking/wifi

[Louis Santillan]

DOS did networking a lot better with ISA and some PCI NICS.  WiFi came
after DOS was no longer being developed.  There might be some 900MHz
WaveLAN things that work for DOS if the point is to make a machine
connected wirelessly.

If the machine has serial you might consider a Wifi232[0] or one of the Pi
Zero W[1][2] based options.



[0] http://biosrhythm.com/?page_id=1453
[1] http://podsix.org/articles/pimodem/
[2]
https://mygpslostitself.blogspot.com/2017/07/raspberry-pi-zero-w-serial-modem.html

On Thu, Mar 18, 2021 at 6:41 AM Eric Auer  wrote:

>
> Hi! To do some additional name-dropping on the DOS WiFi topic here:
>
>
> https://www.olimex.com/Products/IoT/ESP32/ESP32-GATEWAY/open-source-hardware
>
>
> https://www.hackster.io/techbase_group/arduino-esp32-serial-port-to-tcp-converter-via-wifi-66d341
>
> https://github.com/martin-ger/esp_wifi_repeater/blob/master/README.md
>
> In short, you can do interesting things with cheap WiFi (and Bluetooth)
> enabled controller modules, including things which involve LAN or RS232,
> so there might be some "turn some modules for a total of 10-25 USD into
> a connector between WiFi and LAN or serial port" project out there for
> those who prefer tinkering over ready to use brand devices :-)
>
> ESP32 are 4 USD 2-core controller modules with WiFi, Bluetooth and more
> interfaces, 520 kB RAM, more compute power than your 386 PC. But just
> marketed as wireless controller, less as microcontroller. "ESP8266++"
> Maybe fast enough to simulate a PC XT, with MDA graphics, in software.
>
> Cheers, 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] Invalid opcode - where do I even begin?

[Louis Santillan]

I think those are binary instructions.  Not actual addresses.  You could
try disassembling here [0] but a quick cut & paste gave an instruction
sequence that is non-obvious to me.  If Contra is a debugger/mod, then that
makes a little more sense.  The full message might also help clear things
up.  Also, noting what memory managers, drivers, and other software
versions are running also helps.

[0] https://defuse.ca/online-x86-assembler.htm#disassembly2

On Thu, Mar 4, 2021 at 12:37 PM Michał Dec  wrote:

> Hello,
>
> I've run some software on Pentium 3 Tualatin S on FreeDOS and it's
> getting an invalid opcode error. The error precisely says "Invalid
> opcode at ..." where ... is a bunch of 16 bit variables. Saying "at" is
> really misleading and doesn't make any sense, since such a high address
> like let's say 628a  3002 206f 2b43 202b 202d 6f43 7970 6972 6867
> 2074 3931 is well within the realm of ZFS storage, not protected mode
> address space :D
>
> If anyone's wondering, the offending software is Contra and Quake 1.08
> (software renderer). For what it's worth, the above hex string is
> exactly what Quake blurted out.
>
> Where do I even begin with understanding this message? Is this a series
> of opcodes the CPU failed to run, or is this an address, or is it
> something else? I could recompile Quake, but Contra will probably
> require me to patch the binary with the help of reverse engineering tools.
>
> Best regards,
>
> Michał
>
>
>
> ___
> 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] Booting from USB Issue

[Louis Santillan]

Not sure what the "Client" is.  I just used FreeDOS to run sas2flash on my
Dell R7610 servers.  However, I instead used the FD12FULL.zip usb image,
`dd` the image to an old 1GB flash drive, and then wiped out all the FD
packages to make room for the firmware softwares.

Maybe your USB drive is corrupted or maybe you chose the wrong image for
your server.

On Fri, Feb 19, 2021 at 8:55 AM bobby 
wrote:

> I am trying to use FreeDOS to update drivers on a Dell Rack Server.  I
> used Unetbootin on Win10 to create the bootable USB.  But when I try to
> boot from it, the client freezes up.  I tried the USB on my server and my
> client laptop, and the same results.  What could this mean?
> ___
> 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] Dillo Web browser

[Louis Santillan]

That's one thing that has troubled me about Links2.  I've been able to
compile it for Mac and Linux but not DOS.

On Mon, Dec 7, 2020 at 2:35 PM Jamie Le Tual  wrote:
>
> I would be curious to know which tool chain they used to compile it
>
> On Mon, 7 Dec 2020 at 16:26, Jose Senna  wrote:
>>
>>  The only Web browsers for DOS with TLS support I
>> know of are recent versions of Links.
>>
>>
>>
>> ___
>> 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] Serial port WiFi modems - was: MS-DOS 7.1

[Louis Santillan]

The various Wifi232 variants seem to run about $45-$100USD.  I think
the PiModems w/a $10-$15USD PiZeroW could be made cheaper but no one
seems to be producing prebuilt versions.

On Mon, Dec 7, 2020 at 12:04 PM Eric Auer  wrote:
>
>
> Hi DOS people,
>
> those links from Louis are really interesting!
>
> For example the Guru Modem is a device based on the
> tiny ESP32 WROOM computer (actually sold as controller
> for WiFi and Bluetooth, but has plenty of CPU power)
> which has a serial port to connect it to your PC
> and has some modem simulation software installed.
>
> For the PC, it will look like a classic serial
> RS232 dial-up modem, but it will use your WiFi
> to connect to the internet, instead of actually
> connecting your computer to any phone line :-)
>
> As Louis has suggested a whole collection of links
> to various similar products, I wonder which of them
> are pre-assembled and which have to be assembled by
> those who buy them? Also, what are the prices? Have
> DOS users already tested the products? Which ones
> would you recommend? The general idea is very cool,
> although LAN is of course much faster than RS232.
>
> Regards, Eric
>
> PS: I guess 5 Volt from your USB port should have
> enough power for the Guru Modem? Or use a charger.
>
>
>
>
> ___
> 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] MS-DOS 7.1

[Louis Santillan]

If you're a little handy with soldering you could make yourself a
Wifi232 or PiModem.  Alternatively, you can buy Wifi232 or WiModem232
or Gurumodem.  Works like a dialup modem on


Buy
http://biosrhythm.com/?page_id=1453
https://www.cbmstuff.com/proddetail.php?prod=WiModem232
https://electronicsisfun.com/gurumodem
https://www.ebay.com/itm/GuruModem-RS-232-Wifi-Modem/224174229752
https://www.ebay.com/itm/ArcaneByte-RS232-WiFi-Wireless-Modem-for-Vintage-Computers/203207668237

Build
https://github.com/stardot/esp8266_modem
http://podsix.org/articles/pimodem/
https://magpi.raspberrypi.org/articles/add-internet-access-to-a-vintage-computer-using-raspberry-pi
https://www.reddit.com/r/retrobattlestations/comments/7oep2j/instead_of_buying_a_wifi232_i_built_my_own_into_a/
https://www.insentricity.com/a.cl/215/putting-your-retro-computer-on-the-line
https://www.raspberrypi.org/blog/raspberry-pi-dial-up-server/
https://lunduke.com/posts/2020-04-20-a/

On Mon, Dec 7, 2020 at 1:24 AM Karen Lewellen  wrote:
>
> When my engineer is next able to list everything after a visit, I will
> share.
> Post pandemic restrictions most likely.
> We really would like to put freedos on a laptop, I have a thinkpad p3 that
> we considered using, but I could never find a  modem card that would work.
> add  the lack of firm networking included, and we found Nothing that
> freedos provided  that made it worth the test at the time.
>
>
>
> On Mon, 7 Dec 2020, Mateusz Viste wrote:
>
> > On 06/12/2020 22:31, Karen Lewellen wrote:
> >>  Its terrific, have been using it exclusively for years.
> >
> > That's cool and all, but in what way exactly is it better than FreeDOS?
> > That's a honest question.
> >
> > BTW, MS-DOS 2.0 appears to be libre (MIT) nowadays - that could also be a
> > good fit to some, given how small footprint (much smaller than FreeDOS) it
> > has.
> >
> > Mateusz
> >
> >
> > ___
> > 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] Modern add-ons for ancient PC

[Louis Santillan]

Agreed.  I haven't seen [0] Monotech go out of its way to communicate
that it mostly integrated other people's designs into a MicroATX
solution [1][2].  But they still seem to release their schematics and
changes.

[0] https://www.vogons.org/viewtopic.php?f=46=67424
[1] https://github.com/monotech/NuXT
[2] https://github.com/monotech/NuXTv2

On Sat, Oct 3, 2020 at 9:23 AM Michael Brutman  wrote:
>
> One important note - buyer beware.
>
> Most of these are open source projects.  And in a lot of cases people are 
> taking the designs and not providing credit to the original designers, or 
> making design changes that the original designers have quality concerns 
> about.  Monotech was one of those.
>
>
>
> ___
> 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] Modern add-ons for ancient PC

[Louis Santillan]

You mean like these? [0][1][2][3][4]

Personally, while I think real hardware is great, I've resolved to
mostly using emulation.  I mean, if I had access to USB, WiFi, Flash,
SSD, NVMe, SATA 30 years ago, I would have used it.  So, why shouldn't
I use it now to run old software better than I could have imagined
back then?

[0] https://github.com/tjmnmk/gadget_cdrom
[1] https://magpi.raspberrypi.org/articles/pi-zero-w-smart-usb-flash-drive
[2] https://www.raspberrypi.org/forums/viewtopic.php?t=213309
[3] 
https://www.insentricity.com/a.cl/244/adding-a-hard-drive-to-an-original-ibm-pc-using-a-raspberry-pi
[4] https://hackaday.io/project/20774-netpi-ide

On Fri, Oct 2, 2020 at 10:57 PM Jon Brase  wrote:
>
> One thing I'd really like to see is a single board computer that plugs into a 
> USB and/or SATA cable on one end and a pair of PATA cables and a floppy cable 
> on the other. You put a multi-terabyte hard drive or SSD (or several of them) 
> at the USB/SATA end, and an old PC at the PATA end, then stuff the hard drive 
> full of disk images. You then have software on the SBC that can receive ATAPI 
> commands over the PATA cable to set which images get presented on the ATA and 
> floppy cables, and some management software whatever operating systems you 
> want to run on the PC that can issue those commands (or maybe a bootloader 
> that can switch images). That way, if you're multi-booting, you don't have to 
> worry about finding space to fit everything on an 8 GIB drive if one of your 
> OSes (or your BIOS) can't handle anything larger: you just give each such OS 
> its own 8 GiB image, which the SBC presents to the PC as a hard drive.
>
> I've seen similar floppy-only projects that allowed the user to select a 
> floppy image on a USB stick with a pair of next image / previous image 
> buttons, but never something on as grand a scale as described above, where 
> the goal is to serve all of an old PC's storage interfaces with images stored 
> on a single modern drive.
>
>
>  Original message 
> From: Michael Brutman 
> Date: 10/2/2020 21:38 (GMT-06:00)
> To: "Discussion and general questions about FreeDOS." 
> 
> Subject: Re: [Freedos-user] Modern add-ons for ancient PC
>
> The retrocomputing crowd has a lot of these projects now, and they generally 
> work.  Most are based on open source designs so the quality will vary from 
> vendor to vendor.
>
> The 8 bit IDE cards for example are based on a project called XT-IDE that I 
> was part of back in 2008/2009. (See the genesis of the project at 
> http://www.vcfed.org/forum/showthread.php?12359-8-Bit-IDE-Controller .  The 
> original version of the card had the traces optimized on my work laptop while 
> it was idling.)
>
> If I were buying an XT-IDE I would be getting it from 
> https://www.glitchwrks.com/xt-ide.  I haven't purchased any of the recent 
> variants; all mine are gen 1 from the first production run.  And I've not 
> tried out memory boards but they are generally known to work; they are not 
> particularly complicated.
>
>
> Mike
>
>
> On Thu, Oct 1, 2020 at 4:34 AM Eric Auer  wrote:
>>
>>
>> Hi! Mentioned in a video mentioned by Rugxulo on BTTR,
>> I noticed that there is a shop where you can get some
>> circuit boards to do-it-yourself 8-bit ISA extension
>> cards for your ancient computers for features such as
>> more RAM, IDE or Compact Flash interfaces or even USB
>> interfaces which are bootable. Interesting technical
>> detail: They use EEPROMS which you can program without
>> using a programmer, just with magic write sequences.
>>
>> Has anybody tried any of those products? Are they okay
>> for the task at hand? Note that the shop usually has
>> only the PCB, not the pre-built devices, so you have
>> to get the components elsewhere and solder yourself in
>> most cases. They also have a few ready to use products.
>>
>> https://www.lo-tech.co.uk/product-category/retro-ibm-pc/
>>
>> Cheers, 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] Modern add-ons for ancient PC

[Louis Santillan]

Some of the Lo-tech boards and other replicas end up on eBay and are
sometimes less expensive (at least in the US).

Another small time maker, Monotech [0], has also produced boards.  I
sort of consider them semi-expensive.  Especially considering that
they don't seem to be original designs.  They do seem to have some
optimizations, bug fixes, etc.  They also went through the effort of
integrating several designs into an MicroATX form factor, 8088
XT-compatible board including IDE, SVGA [0].  Other original designs
are here [2][3][4][5][6][7][8].

[0] https://monotech.fwscart.com/category/cards
[1] 
https://monotech.fwscart.com/NuXT_v20_MicroATX_Turbo_XT_10MHz_832K_XTIDE_MultiIO_SVGA/p6083514_19777986.aspx
[2] http://www.malinov.com/Home/sergeys-projects/xi-8088
[3] http://www.malinov.com/Home/sergeys-projects/isa-fdc-and-uart
[4] http://www.malinov.com/Home/sergeys-projects/xt-cf-lite
[5] http://www.malinov.com/Home/sergeys-projects/isa-supervga
[6] http://www.malinov.com/Home/sergeys-projects/sergey-s-xt
[7] https://github.com/skiselev/micro_8088
[8] https://github.com/skiselev/isa8_backplane

On Fri, Oct 2, 2020 at 7:40 PM Michael Brutman  wrote:
>
> The retrocomputing crowd has a lot of these projects now, and they generally 
> work.  Most are based on open source designs so the quality will vary from 
> vendor to vendor.
>
> The 8 bit IDE cards for example are based on a project called XT-IDE that I 
> was part of back in 2008/2009. (See the genesis of the project at 
> http://www.vcfed.org/forum/showthread.php?12359-8-Bit-IDE-Controller .  The 
> original version of the card had the traces optimized on my work laptop while 
> it was idling.)
>
> If I were buying an XT-IDE I would be getting it from 
> https://www.glitchwrks.com/xt-ide.  I haven't purchased any of the recent 
> variants; all mine are gen 1 from the first production run.  And I've not 
> tried out memory boards but they are generally known to work; they are not 
> particularly complicated.
>
>
> Mike
>
>
> On Thu, Oct 1, 2020 at 4:34 AM Eric Auer  wrote:
>>
>>
>> Hi! Mentioned in a video mentioned by Rugxulo on BTTR,
>> I noticed that there is a shop where you can get some
>> circuit boards to do-it-yourself 8-bit ISA extension
>> cards for your ancient computers for features such as
>> more RAM, IDE or Compact Flash interfaces or even USB
>> interfaces which are bootable. Interesting technical
>> detail: They use EEPROMS which you can program without
>> using a programmer, just with magic write sequences.
>>
>> Has anybody tried any of those products? Are they okay
>> for the task at hand? Note that the shop usually has
>> only the PCB, not the pre-built devices, so you have
>> to get the components elsewhere and solder yourself in
>> most cases. They also have a few ready to use products.
>>
>> https://www.lo-tech.co.uk/product-category/retro-ibm-pc/
>>
>> Cheers, 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] Run Linux & Linux binaries on DOS

[Louis Santillan]

I've documented my process for getting doslinux working on real
hardware [0].  Not too bad.

`ftpget`, `wget`, and `httpd` applets are included [1] in busybox. I
think with a little more work, static binary versions of many apps
would work.  Shouldn't be that hard to statically build in the
networking drivers, even other drivers.  I think that many apps from
suckless [2] sbase [3], ubase[4], toybox [5], asmutils [6] should work
well too.

[0] https://sites.google.com/view/doslinux-on-real-hardware
[1] https://github.com/charliesome/doslinux/blob/master/busybox-config#L841-L994
[2] https://suckless.org/rocks/
[3] https://git.suckless.org/sbase/file/README.html
[4] https://git.suckless.org/ubase/files.html
[5] http://www.landley.net/code/toybox/status.html
[6] http://asm.sourceforge.net/asmutils.html

On Tue, Sep 29, 2020 at 10:50 AM Mercury Thirteen via Freedos-user
 wrote:
>
> "Does DSL allow you to, say, install apt (or another package manager), gcc, 
> make, etc.,"
>
> No.
>
>
> "or does it only allow you to run the common linux commands shown on the 
> BusyBox website?"
>
> Yes.
>
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, September 29, 2020 12:33 PM, Jason Pittman 
>  wrote:
>
> I know nothing about BusyBox, so I'm going to ask a dumb question. Does DSL 
> allow you to, say, install apt (or another package manager), gcc, make, etc., 
> or does it only allow you to run the common linux commands shown on the 
> BusyBox website?
>
> (And on a side note, has anyone actually gotten it to work? I'd already know 
> the answer to my question above if I could get it to do something other than 
> crash the VM when I run "dsl.com")
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, September 23, 2020 11:33 AM, Jim Hall  wrote:
>
> After poking around the GitHub project, this is actually a very clever thing. 
> Looks like he's using VM86 mode (requires '386 or later CPU) to instantiate a 
> dedicated Linux kernel with BusyBox to run the Linux commands. This is not 
> bringing up a full Linux installation in a VM - this is only the kernel + 
> BusyBox. So that keeps it small.
>
> Now, what would you *do* with this? Why would you need DSL under FreeDOS? I'm 
> not sure. But it's a neat idea that is well done. Good job!
>
> On Wed, Sep 23, 2020 at 10:41 AM Louis Santillan  wrote:
>>
>> The author freely admits running DOS & Linux side-by-side this way is
>> a fragile coordination [0].  I doubt that redirection would work as
>> one might desire.  The recently updated ascii demo [1] shows calling
>> various DOS and Linux commands, and, shows creating a text file with
>> `dsl vi hello.txt` and then later opening that same file with `edit
>> hello.txt`.  Interestingly, the file appears written to the filesystem
>> as `HELLO.TXT`, as MS-DOS 6.22 is case insensitive (w/o a LFN driver).
>> I wonder what would happen if an LFN driver was added to the mix.
>>
>> [0] https://news.ycombinator.com/item?id=24556801
>> [1] 
>> https://camo.githubusercontent.com/deb8f6b6cc59686ba91a3758daeb047fccdf05dd/68747470733a2f2f636861726c69652e73752f7265636f7264696e672d61633565396166353936613931382e676966
>>
>> On Wed, Sep 23, 2020 at 4:39 AM Eric Auer  wrote:
>> >
>> >
>> > Hi everybody,
>> >
>> > I would predict doslinux to be a variant of a Linux loader,
>> > so my questions here are: Can Linux safely write to the DOS
>> > partition while running? What are the limitations to return
>> > to DOS after using Linux? Is it possible to switch between
>> > DOS and Linux without having to reboot Linux each time? Are
>> > direct interactions possible, e.g. run single apps and pipe
>> > their output from Linux to DOS or from DOS to Linux?
>> >
>> > As Jim writes about modifications to make doslinux work with
>> > FreeDOS, it can probably do more than just load Linux, but I
>> > would be happy to read more about the details here on the list.
>> >
>> > Thanks :-) 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] (no subject)

[Louis Santillan]

You can use JEMMEX to provide EMS.  Command docs are here
(https://web.archive.org/web/20200205000957/http://help.fdos.org/en/hhstndrd/base/jemmex.htm).

You need a line like
```
DEVICE=C:\FDOS\BIN\JEMM386.EXE RAM
```
in your fdconfig.sys.

See (https://www.philscomputerlab.com/ms-dos-starter-pack.html) for more info.

On Wed, Sep 30, 2020 at 4:45 AM Leo Kerr  wrote:
>
> does freedos support ems and if so, how would i go about enabling it?
> ___
> 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] Run Linux & Linux binaries on DOS

[Louis Santillan]

The author freely admits running DOS & Linux side-by-side this way is
a fragile coordination [0].  I doubt that redirection would work as
one might desire.  The recently updated ascii demo [1] shows calling
various DOS and Linux commands, and, shows creating a text file with
`dsl vi hello.txt` and then later opening that same file with `edit
hello.txt`.  Interestingly, the file appears written to the filesystem
as `HELLO.TXT`, as MS-DOS 6.22 is case insensitive (w/o a LFN driver).
I wonder what would happen if an LFN driver was added to the mix.

[0] https://news.ycombinator.com/item?id=24556801
[1] 
https://camo.githubusercontent.com/deb8f6b6cc59686ba91a3758daeb047fccdf05dd/68747470733a2f2f636861726c69652e73752f7265636f7264696e672d61633565396166353936613931382e676966

On Wed, Sep 23, 2020 at 4:39 AM Eric Auer  wrote:
>
>
> Hi everybody,
>
> I would predict doslinux to be a variant of a Linux loader,
> so my questions here are: Can Linux safely write to the DOS
> partition while running? What are the limitations to return
> to DOS after using Linux? Is it possible to switch between
> DOS and Linux without having to reboot Linux each time? Are
> direct interactions possible, e.g. run single apps and pipe
> their output from Linux to DOS or from DOS to Linux?
>
> As Jim writes about modifications to make doslinux work with
> FreeDOS, it can probably do more than just load Linux, but I
> would be happy to read more about the details here on the list.
>
> Thanks :-) 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] Run Linux & Linux binaries on DOS

[Louis Santillan]

If "doslinux" can boot enough of Linux to enable drivers or access to
devices or software that FreeDOS or BIOS has no interfaces for (USB,
NVMe, SMP, NFS, FUSE, newer NICs such as 1GbE+ or WiFI networking), I
think it makes for some interesting possibilities.  And, it
potentially opens up FreeDOS to machines that have gone obsolete in
the last 10-15 years while still not losing compatibility.

For a while now, I've wanted to see FreeDOS be able to self-host from
scratch.  Bootable FreeDOS to bootable FreeDOS USB/ISO/HDD/FDD
installer image, a "FreeDOS from Scratch" if you will.  I think this
is one of those technologies that could greatly help.

On Tue, Sep 22, 2020 at 3:01 PM Jim Hall  wrote:
>
> I had a brief twitter conversation with him when he originally announced it 
> on twitter. The first announcement used MS-DOS, but he was able to get this 
> to work with FreeDOS too.
>
> Once he confirmed it worked with FreeDOS, I posted a tweet on it:
> https://twitter.com/FreeDOS_Project/status/1308382845883289600
>
>
> I'm not sure I'll make a news item about this on the website. It's not really 
> the kind of project to announce there, since it's not really about FreeDOS. 
> But it's a really interesting idea for anyone booting FreeDOS from Linux.
>
> Jim
>
>
> On Tue, Sep 22, 2020 at 3:29 PM Louis Santillan  wrote:
>>
>> Ohand it runs in UnReal Mode?!?! [0][1]  Super interesting.
>>
>>
>> [0] 
>> https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L239-L247
>> [1] https://en.wikipedia.org/wiki/Unreal_mode
>>
>> On Tue, Sep 22, 2020 at 1:24 PM Louis Santillan  wrote:
>> >
>> > In case you missed it, DOS Subsystem for Linux [0][1] was announced on
>> > HackerNews.  Think of it something like WINE, or, something like
>> > DPMILD32/HXRT/HXGUI Japeth's HX DOS Extender, but for Linux on top of
>> > DOS.  A couple interesting things to note: 1) It needs to run w/o XMS
>> > [2], 2) It seems to actually boot Linux's bzImage kernel image [3].
>> >
>> >
>> > I think DINE (DINE Is Not an Emulator), LID (Linux in DOS) might have
>> > been more descriptive names for the project.  Reminiscent of the old
>> > UMSDOS Linux Distros but maybe not full fledged boot into Linux.
>> > Interesting nonetheless.
>> >
>> > [0] https://news.ycombinator.com/item?id=24555689
>> > [1] https://github.com/charliesome/doslinux
>> > [2] https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L5-L15
>> > [3] 
>> > https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L45-L220
>>
>>
>> ___
>> 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] Run Linux & Linux binaries on DOS

[Louis Santillan]

Ohand it runs in UnReal Mode?!?! [0][1]  Super interesting.


[0] https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L239-L247
[1] https://en.wikipedia.org/wiki/Unreal_mode

On Tue, Sep 22, 2020 at 1:24 PM Louis Santillan  wrote:
>
> In case you missed it, DOS Subsystem for Linux [0][1] was announced on
> HackerNews.  Think of it something like WINE, or, something like
> DPMILD32/HXRT/HXGUI Japeth's HX DOS Extender, but for Linux on top of
> DOS.  A couple interesting things to note: 1) It needs to run w/o XMS
> [2], 2) It seems to actually boot Linux's bzImage kernel image [3].
>
>
> I think DINE (DINE Is Not an Emulator), LID (Linux in DOS) might have
> been more descriptive names for the project.  Reminiscent of the old
> UMSDOS Linux Distros but maybe not full fledged boot into Linux.
> Interesting nonetheless.
>
> [0] https://news.ycombinator.com/item?id=24555689
> [1] https://github.com/charliesome/doslinux
> [2] https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L5-L15
> [3] https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L45-L220


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

[Freedos-user] Run Linux & Linux binaries on DOS

[Louis Santillan]

In case you missed it, DOS Subsystem for Linux [0][1] was announced on
HackerNews.  Think of it something like WINE, or, something like
DPMILD32/HXRT/HXGUI Japeth's HX DOS Extender, but for Linux on top of
DOS.  A couple interesting things to note: 1) It needs to run w/o XMS
[2], 2) It seems to actually boot Linux's bzImage kernel image [3].


I think DINE (DINE Is Not an Emulator), LID (Linux in DOS) might have
been more descriptive names for the project.  Reminiscent of the old
UMSDOS Linux Distros but maybe not full fledged boot into Linux.
Interesting nonetheless.

[0] https://news.ycombinator.com/item?id=24555689
[1] https://github.com/charliesome/doslinux
[2] https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L5-L15
[3] https://github.com/charliesome/doslinux/blob/master/doslinux.asm#L45-L220


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

Re: [Freedos-user] Microsoft Open-Sources GW-BASIC

[Louis Santillan]

I think you're wrong dpirate. I haven't had time to test, but, I would
expect [0] to be able to use MASM & LINK from MS-DOS 2.0 [1] to build
this.  I plan to throw some cycles at this.


[0] https://news.ycombinator.com/item?id=23269345
[1] https://github.com/microsoft/MS-DOS/tree/master/v2.0/bin

On Fri, May 22, 2020 at 7:08 AM Andy Stamp  wrote:
>
> It looked like this was the x86 output of the meta compiler.  I'm going to 
> try to coax the Watcom Assembler into building it this evening.
>
> On Fri, May 22, 2020 at 8:38 AM Deposite Pirate  
> wrote:
>>
>> This cannot be compiled to machine code because it's some kind of meta 
>> assembler to generate assembler for various processor architectures and this 
>> meta assembler is apparently not available. So unless someone goes through 
>> the pain of reverse engineering this meta assembler this is pretty much 
>> useless shit, just like MS-DOS 1.x and 2.x.
>>
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
>
> --
> --Andy
> ___
> 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] SHSUCDX Updated to 3.07

[Louis Santillan]

SHSUCDX was updated to 3.07 recent it looks like.  See
http://adoxa.altervista.org/shsucdx/index.html


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

Re: [Freedos-user] DOSBOX Isn´t for everyone (off-topic remark)

[Louis Santillan]

These days, it several MBs more than 8MB, but, TinyCoreLinux [0][1] is
a RAMDisk based Linux that requires less than 48MB.Earlier
versions ran on far less and even offered network connected, command
line versions running in under 16MB of RAM on i486DX or better [2].
Even a mildly loaded i486DX or Pentium will have 24MB or more.

Linux kernels older than 3.0 were far less memory hungry than they are today.

[0] http://tinycorelinux.net/faq.html#req
[1] 
https://www.makeuseof.com/tag/tiny-core-linux-is-your-smallest-choice-for-an-operating-system/
[2] https://en.wikipedia.org/w/index.php?title=Tiny_Core_Linux=422419994

On Wed, Mar 25, 2020 at 11:57 AM  wrote:
>
> On Mar 25 2020 18:51, Jose Antonio Senna wrote:
> > Today userbeit...@abwesend.de (Robinson West ?) said:
> >
> >> Afaik there is no Linux that will run with only 8 MB of RAM.
> >   About 1998 I did run (plod was a better description)
> >  Red Hat 5.0 (kernel 2.0.32) in a 486 DX-50 with 4 MB
> >  of RAM, but in text mode only. The machine and the
> >  installation CD are still here. I used DR-DOS 5 and
> >  loadlin to boot, because the machine could not boot
> >  from CD.
>
>
> Sorry, yes, old Linux version will work. I also still have a box of SuSE
> Linux 4.2 laying around somewhere, and a quite old version of Debian on
> a CD or DVD. Since the 486 does not have a working optical drive, I
> would have to install it on my current desktop using something like
> VirtualBox or QEMU, forcing it to reflect a 486, and then transfer the
> installation.
>
>
> I was referring to a current system. I think, not even the kernel will
> boot on a system with only 8 MB memory. A 2.4 kernel might, but I am not
> even sure about a 2.6 kernel.
>
>
> I also have DR DOS 5 laying around, an original version. I might play
> with that, but I was curious about FreeDOS, because it is somewhat more
> recent in some respects than old DOSes and old Linuxes. But I might be
> wrong...
>
>
> A.
>
>
>
> ___
> 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] FreeDOS is slow in Raspberry 4

[Louis Santillan]

Something to note in the original bug report is that CFLAGS chosen are
not optimal for performance (`make 'CFLAGS=-Wall -g -O2 -w'`).
Specifically, the `-g` and `-O2`  flags should probably be changed.

`-g` [0] adds debugging info which will make the QEMU binary larger,
and produce code & data to allow instrumenting and debugging at
runtime.  This will blow cache performance since more code & data
overflow the cache.  I recommend removing this all together.

`-O2` [1] instructs the compiler to enable all performance options
that do not involve a space-time tradeoff.  Generally `-O3` is
considered to produce the most "optimal" code, `-Os` is beneficial for
CPUs with small caches and `-Ofast` can enable further performance
potentially at the cost of program execution correctness.

I recommend trying `-O3` or `-Ofast` without `-g` and retesting/rebenchmarking.


[0] https://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html
[1] https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#Optimize-Options

On Wed, Mar 18, 2020 at 1:48 PM Jim Hall  wrote:
>
>
>
> On Wed, Mar 18, 2020 at 3:00 PM Eric Auer  wrote:
>>
>>
>> Hi Ralf,
>>
>> >> How about first installing to a directory or diskimage stored
>> >> in a ramdisk on the host OS, then copying that to mass storage?
>>
>> > This would be a bit like the old chicken and egg problem. The time you
>> > would spend to copy the contents of the FreeDOS distro from the SD card
>> > to a RAM disk on the RPi is likely not much faster...
>>
>> I expect it to be much faster because: You only read from the
>> slow SD card and you read fewer, larger files. The bad parts,
>> writing many small files, would be on the fast ramdisk side.
>> Also, you can start from a FreeDOS ISO on the SD card, which
>> again is only one big file to copy from the web to the card.
>> When done, you copy one big file, the diskimage, once from
>> the ramdisk to the SD card :-)
>> [..]
>
>
> Someone had suggested that option to me - install FreeDOS to a HD image in a 
> RAM drive, then copy the HD image back to storage.
>
> But I didn't want to explain those extra steps in my article. And really, 
> installing FreeDOS on QEMU+RPi takes longer, but it's not "all day" long. 
> It's more like "start the install, and make a cup of coffee while the install 
> finishes." For a one-time thing, it's not too bad.
>
>
> ___
> 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