Re: [Freedos-user] help troubleshooting a time / date issue?

2024-08-03 Thread Daniel Essin via Freedos-user

Time for a new cmos battery?

On 8/3/2024 8:57 AM, Karen Lewellen via Freedos-user wrote:

Hi all,
At the most basic level, what helps a computer keep time / date?
I have a situation where mine is skipping time / date, often within 
seconds, even when set back.

My computer is not over heating, fan running quite cool to the touch.
Was working just fine until late last night when I turned it off.
basic ideas?
for the record, I only run dos on this machine.
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] Unexpected results from DIR command

2024-06-03 Thread Daniel Essin via Freedos-user
Look at python for dos - http://www.caddit.net/pythond/
If it has the os module,  I'll bet you could do it. 

On Sun, Jun 2, 2024, at 11:19 PM, hms--- via Freedos-user wrote:
> Hi
> I am looking for files named Q and not directories named Q. In my case I 
> have thousands of assembler text files without filename extensions. It 
> comes from early days starting out with TSC Flex and Uniflex followed by 
> the Mark Williams Coherent operating systems.
> John
>
> On 2024/06/02 22:29, tsie...@softcon.com wrote:
>>  Don't know if it helps, but I've found that if you want *just* 
>> directory names, and you don't have a directory program that allows 
>> you to set flags, so it only shows directories, then the best way to 
>> get them is to do something like:
>>
>> dir *.
>>
>> Since most directory names don't have extensions, this only picks out 
>> the directory names (and of course, any files without extensions, but 
>> those are rare), so that should find the q directory for you with 
>> little to no trouble.
>>
>>
>> On 6/2/2024 5:34 PM, hms--- via Freedos-user wrote:
>>> Hi All
>>> It appears that if a directory exists with the same name as the file 
>>> one is searching for, the directory listing is terminated early 
>>> without error.
>>> I was searching for a files named "Q" with no extension. I used the 
>>> commands "DIR Q /S /B" and "DIR Q. /S /B", but it only revealed files 
>>> in a directory named "Q".
>>> An example directory structure is shown  below. Note that most of the 
>>> file names below do not have extensions. The file named "Q" appears 
>>> in all the subdirectories.
>>> I was puzzled and decided to dig a little further. Is this correct 
>>> behaviour for the DIR command or a misunderstanding on my part about 
>>> file name matching? Perhaps an anomaly or a bug? I have tried various 
>>> DOS's with the same result, the DIR command being an internal one. I 
>>> have also tried XCOPY and XXCOPY with the "/L" option and it also 
>>> only finds the files in the "Q" directory. Any thoughts as to what's 
>>> going on?
>>> John
>>>
>>>
>>> Directory of  f:\a12\*.*
>>> [.] [..]    [J] [Q] [Q.A]
>>> [Q1]    [TS]
>>>
>>> Directory of  f:\a12\j\*.*
>>> [.] [..]    Q
>>>
>>> Directory of  f:\a12\q\*.*
>>> [.] [..]    Q   Q.A Q.ASM
>>> Q1  Q12
>>>
>>> Directory of  f:\a12\q.a\*.*
>>> [.] [..]    Q   Q.A
>>>
>>> Directory of  f:\a12\q1\*.*
>>> [.] [..]    Q   Q.A Q99
>>>
>>> Directory of  f:\a12\ts\*.*
>>> [.] [..]    Q   Q.A Q.ASM
>>>
>>> Entering the command below gives the following result.
>>> F:\>DIR Q /S /B
>>> f:\a12\q\Q
>>> f:\a12\q\Q.A
>>> f:\a12\q\Q.ASM
>>> f:\a12\q\Q1
>>> f:\a12\q\Q12
>>>
>>> The Q file is only found in the Q directory.
>>>
>>> Same result as above with:-
>>> F:\>DIR Q. /S /B
>>>
>>> Typing command:
>>> F:\>DIR Q.? /S /B
>>> Gives this result.
>>> f:\a12\Q
>>> f:\a12\Q.A
>>> f:\a12\j\Q
>>> f:\a12\q\Q
>>> f:\a12\q\Q.A
>>> f:\a12\q.a\Q
>>> f:\a12\q.a\Q.A
>>> f:\a12\q1\Q
>>> f:\a12\q1\Q.A
>>> f:\a12\ts\Q
>>> f:\a12\ts\Q.A
>>>
>>> The Q file is now found in all the subdirectories.
>>>
>>>
>>>
>>>
>>> ___
>>> 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] VICTORY! How I got networking operational in 86Box

2024-06-02 Thread Daniel Essin via Freedos-user
Excellect work! 

On Sun, Jun 2, 2024, at 5:35 PM, Brandon Taylor via Freedos-user wrote:
> I've been agonizing over the question of why I can't connect an 86Box virtual 
> machine powered by FreeDOS to the Internet. But now, it seems, I have found a 
> fix, or at least a preliminary one.
> 
> Using a fine-toothed comb (as it were), I went over the FDAUTO.BAT file and 
> found that it referenced another batch file that handled all of the 
> networking stuff, namely, C:\FREEDOS\BIN\FDNET.BAT. So, going over THAT, I 
> arrived at what I figured was a critical line in the second batch file, which 
> was `vinfo /m`. Typing this into the command line didn't seem to do anything, 
> but when I typed `vinfo /m | echo %errorlevel%`, lo and behold, FreeDOS 
> returned the number 5. So, going back into FDNET.BAT, I eventually arrived at 
> this piece of code:
> ```
> :hw086
> :hw186
> :hw286
> :hw386
> :hw486
> :hw586
> :hw686
> :NoHardware
> vecho /t %_FDNET.LANG% ERROR.HARDWARE
> goto End
> ```
> and that's why it told me that `Physical hardware networking is not supported 
> at this time.`
> 
> Well...
> 
> Not willing to admit defeat, I continued going through FDNET.BAT to find out 
> what it was about VirtualBox and VMware that made the network go...
> 
> ...and both of them branched to `:vmGeneric`.
> 
> From THERE, I discovered that FreeDOS supports three network card families: 
> AMD PCnet, Realtek RTL8139, and NE2000-compatibles – the same ones used by 
> VirtualBox, VMware, and (though I haven't used FreeDOS on this) QEMU!
> 
> So, going back to the physical hardware section of the batch file, I simply 
> added a branching line after `:hw686`, so that the code block now reads:
> ```
> :hw086
> :hw186
> :hw286
> :hw386
> :hw486
> :hw586
> :hw686
> goto vmGeneric
> 
> :NoHardware
> vecho /t %_FDNET.LANG% ERROR.HARDWARE
> goto End
> ```
> and opened the 86Box configuration to install an AMD PCnet-FAST III into an 
> emulated PCI slot, which triggered a hard reset.
> 
> And wouldn't you know? The network worked!
> 
> I was able to `ping www.google.com` and get a pong sent back to me. I'm kinda 
> having a little bit of difficulty with `fdnpkg` though, so maybe there are 
> still some kinks to work out. But for right now, I can declare at least a 
> preliminary victory!
> 
> Brandon Taylor
> 
> ___
> 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] PCI parlallel port card....

2024-05-18 Thread Daniel Essin via Freedos-user

https://www.startech.com/en-us/cards-adapters/pci1pm

On 5/18/2024 12:54 PM, Roderick Klein via Freedos-user wrote:

Hello,

Are there any PCI cards that live at IO adress 378 so they are 
compatible with DOS ?


Thanks,

Roderick


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

2024-05-08 Thread Daniel Essin via Freedos-user

Try it in a VM

On 5/8/24 6:21 PM, Travis Siegel via Freedos-user wrote:
I found my copy of PTS DOS Source, and was digging through them to see 
some of the differences between that and opendos, for which I also 
have the sources, and I ran across the dos navigator menuing system 
(at least I'm pretty sure it's a menu system, don't currently have a 
dos machine setup anywhere, so can't run it). But, interestingly 
enough, it's opensource as well, and I was curious if free dos would 
be willing to include it, there's a lot of traffic on the list at 
times looking for a decent menuing system, dos navigator could be the 
answer.  PTS DOS uses it, so why not?


It can be found at: https://www.ritlabs.com/en/products/dn/

just in case anyone is interested in taking a look.




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

2023-07-26 Thread Daniel Essin via Freedos-user
Re: the Compaq, in the late 80's, with the bus expander and a multi-port serial 
card, we ran a 6-user Pick system application using wyse-60 terminals. Also ran 
a 10-user version on an AT. Tasks that could be completed in seconds now take 
minutes in Windows. This is a major cause of physician burn-out with electronic 
health records. 

On Wed, Jul 26, 2023, at 5:47 AM, Bryan Kilgallin via Freedos-user wrote:
> Hey Dan:
>
>> That's great info! I glad to see so many getting use ouf of old 
>> hardware. I, myself, have a whole load of old hardware.
>
> If it still works, or can be made to work, there's no need to chuck it!
>
>> In particular I have 
>> a T40 and, perhaps more interesting, A Compaq Portable III.
>
> Get them going, then.
>
>> I even have, in a flip-top jewel case, a 5-1/4" floppy + manual for a 
>> strange little app called Microsoft Access.
>
> I used to design databases in that!
> -- 
> 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?

2023-07-25 Thread Daniel Essin via Freedos-user
I have a box full of PCMCIA ethernet cards. If anyone could use one, I 
could search them out and post a list.


Dan

On 7/24/23 6:13 PM, Ralf Quint via Freedos-user wrote:

On 7/24/2023 6:06 PM, Karen Lewellen via Freedos-user wrote:

Hi folks,
Too many layers in the process for me to try the install.
That and the thinkpad, which is a thinkpad 600x is not in condition 
for the work it seems.
I do wonder though if the freedos networking options would have 
functioned with the on-board Ethernet structure? 


Does your 600x include an Ethernet port "on-board", AFAIK, they didn't 
and you needed (as it was pre-USB days) an PCMCIA/CardBus adapter and 
that's where the soft  brown matter hits the fast rotating appliance...




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

2023-07-25 Thread Daniel Essin via Freedos-user
That's great info! I glad to see so many getting use ouf of old 
hardware. I, myself, have a whole load of old hardware. You all have 
given me the stimulus to see what I can do with it. In particular I have 
a T40 and, perhaps more interesting, A Compaq Portable III.


I even have, in a flip-top jewel case, a 5-1/4" floppy + manual for a 
strange little app called Microsoft Access. It's not much use now 
because it was an app to use your 300 baud modem to make airline 
reservations. I guess MS (the evil empire) liked the name :)


Thank you all for satisfying my curiosity

Dan

On 7/24/23 7:37 PM, Bryan Kilgallin via Freedos-user wrote:

Hi Dan:

What are others using freedos for: business, curiosity, running retro 
games and apps for fun, to avoid total dependence on the evil empire, 
or something else?


I have an ancient heart rate monitor. Its computer interface uses DOS 
software via a serial port!



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


[Freedos-user] My curiosity

2023-07-24 Thread Daniel Essin via Freedos-user

Hello,

I'm following this list and find it very interesting. I found it when I 
was trying to prepare myself to help a friend whose business in built 
around a DOS app. It's clear that many/most/all? have access to other 
computers and OSes. This would be obvious if only because one needs 
access to the internet even if only to get this list. This has made me 
curious.


What are others using freedos for: business, curiosity, running retro 
games and apps for fun, to avoid total dependence on the evil empire, or 
something else?


Dan



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


Re: [Freedos-user] Confusing details about SET and redirection inFreeCOM

2023-06-22 Thread Daniel Essin via Freedos-user
Maybe put in quotes? 

On Thu, Jun 22, 2023, at 10:07 AM, Bret Johnson wrote:
>> Hi fellow users :-)
>>
>> I have been wondering which chars are special in SET
>> in FreeCOM and whether they can be escaped or similar.
>
> I don't know specifically about FreeCOM, but I know in some versions of 
> DOS an environment variable can't contain an equals sign.  For example, 
> in some DOS versions you can't do this while in others you can:
>
>   SET ParameterList=Var1=1,Var2=2
>
> This has caused me some grief in the past when I try to allow the user 
> to enter option parameters either from the command-line or from an 
> environment variable.  For example, if the program I'm trying to run is 
> called PROGRAM I allow the user to set an environment variable named 
> PROGRAM that contains the "default" command-line parameters:
>
>   SET PROGRAM=Option1=Yes, Option2=No
>
> I want that to work the same way as if the user had done this:
>
>   PROGRAM Option1=Yes, Option2=No
>
> Sometimes it works and sometimes it doesn't, depending on which version 
> of DOS I am using.  And I'm not even sure it is consistent across all 
> different DOS versions from the same manufacturer.  BTW, the way I get 
> around this problem is to allow the user to either enter an equals (=) 
> or a colon (:) as the separator character and explain the situation in 
> the documentation..
>
> The reason I bring this up is that in a recent post there was some 
> discussion over whether or not FreeDOS should fix all the bugs in 
> MS-DOS (essentially, improving MS-DOS) or duplicate the bugs, and the 
> consensus seemed to be to duplicate the bugs.  I don't know if allowing 
> an equals sign in an environment variable would be considered a bug or 
> a feature, but I would classify it as a bug, and I don't remember 
> specifically how MS-DOS handles 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] TASM under an emulator?

2023-03-28 Thread Daniel Essin via Freedos-user

off topic but interesting?

https://yeokhengmeng.com/2023/03/building-a-dos-chatgpt-client-in-2023/

On 3/23/2023 12:44 PM, Rugxulo wrote:

Hi again,

On Thu, Mar 23, 2023 at 12:53 PM Alvah Whealton  wrote:

Thanks for providing me with better direction. I'm already pursuing some of 
your recommendations.

Just to reiterate, the official recommendation of FreeDOS is to use
OpenWatcom and NASM.

(OW's whelp.exe is their documentation reader. For something like
DJGPP it would be Texinfo, e.g. "info libc a printf" although other
Info readers exist.) But a lot of other assemblers are incompatible,
and old source code (e.g. 80xxx snippets) will mostly be in other
dialects. YMMV, caveat emptor, etc.

* 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/asm/nasm/0.98.39/8086host/

* https://pushbx.org/ecm/doc/insref.htm

* https://www.nasm.us/pub/nasm/releasebuilds/2.16.01/dos/ (latest
32-bit DJGPP build)
* https://www.nasm.us/pub/nasm/releasebuilds/2.16.01/doc/html/

* 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/ambread.html
(see OSDN's samples, e.g. 8086 reference)

Just for completeness, although not directly DOS-related, I also want
to tell you about Ray Seyfarth's x64 .PDF book, it's very cheap ($5),
and I think it uses YASM. He has some helpful tools (e.g. his EBE
IDE).

* https://www.rayseyfarth.com/asm/


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

2023-03-02 Thread Daniel Essin via Freedos-user
There hasn't been much discussion of running dos in a virtual machine. I 
know it depends on why you want to run dos at all but a vm is an option 
that avoids the bios/uefi issues and the need for extra hardware.


FreeDOS on VMWare Player | Agnoiologist 



Installing DOS 6.22 in VMware Player 



Installing DOS 6.22 in a VM « Virtualised Reality 




On 3/2/2023 1:55 AM, Ivan Ivanov wrote:

Well, coreboot opensource x86 firmware will help you! The default
coreboot's payload is SeaBIOS - a modern legacy-style BIOS written on
C, without any UEFI crap. In addition, thanks to opensource - you can
finally trust that your BIOS doesn't have the backdoors / holes /
broken code hastily written for a bowl of rice by the lowest bidder.

Of course, not every hardware is suitable for coreboot, so you'll have
to buy anyways. Personally, I can recommend the AMD boards without a
PSP hardware backdoor: Lenovo G505S laptop with A10-5750M, ASUS
A88XM-E desktop with A10-6700 / A10-6800K, and ASUS AM1I-A mini-ITX
micro-desktop with Athlon 5370 - which may be a close match for your
single-board-computer requirement (it has LPT, COM, etc.)

More information can be found on the Internet (i.e. the manuals on
DangerousPrototypes website), or you can just ask me.


чт, 2 мар. 2023 г. в 00:47, Ben Hutchinson:

What legacy OS Either DOS or directly on bare metal. It needs to start in 16bit 
real mode though for either of these to work. UEFI I think starts in 32bit 
protected mode (likely in ring3, so you never really can get hardware level 
access to the computer). This is why it needs legacy BIOS support, so it starts 
in 16bit real mode.

On Wed, Mar 1, 2023 at 12:11 PM John Vella  wrote:

I don't know if this is any help but I am currently installing FreeDOS using 
PCem, on an Atom based Stick PC.

What are you planning on using the legacy os for?

On Wed, 1 Mar 2023, 19:20 Ben Hutchinson,  wrote:

I found what seemed to be a good Intel x86 based SBC over 
athttps://up-shop.org/up-squared-series.html  but there was one problem. It 
mentioned only a UEFI firmware. Nothing about supporting legacy BIOS. I know my 
laptop can switch between UEFI and BIOS by changing the firmware settings (go 
into the firmware menu by pressing F2 at bootup). But the lack of mention of 
legacy BIOS support worried me. So I emailed them and asked. And unfortunately, 
as I was worried, this was their answer:
"For the product now it’s all supported with UEFI BIOS. No legacy BIOS 
supported."

So, I would like to run DOS on an SBC, but with a UEFI only system, that's not 
possible.
___
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] Greetings

2023-03-01 Thread Daniel Essin via Freedos-user
https://archive.org/details/msdos_manual_622
https://archive.org/details/microsoft-programmers-reference-manual-msdos-2.0
https://archive.org/details/msdos_5_User_Guide_completehttps://archive.org/details/msdos_5_User_Guide_complete
 

On Wed, Mar 1, 2023, at 2:22 PM, usul wrote:
> This is awesome, thank you.
> 
> 
> 
> On Wed, Mar 1, 2023 at 3:18 PM Rugxulo  wrote:
>> Hi,
>> 
>> On Wed, Mar 1, 2023 at 11:57 AM usul  wrote:
>> >
>> > So I was digging through my old "stuff" and found some of my old cds and 
>> > my Dell Latitude D520 laptop. And I got all nostalgic . I got my start 
>> > with a 486 DX 8 mgs of Ram.
>> > I mostly did Visual Basic 3.0 programming to start after I finished 
>> > college. VBA/ MS Access then to Dot Net.  I can read C / C++ but never 
>> > really did anything with it.
>> 
>> FreeBASIC might be for you, then. It does have a DJGPP build.
>> 
>> * https://freebasic.net/
>> * https://www.freebasic.net/wiki/DocToc
>> 
>> > So I thought it would be cool to mess around with it again
>> >
>> > So I plan to multiboot on the laptop
>> > Linux
>> > Dos 6.22 / Windows 3.11
>> > and FreeDos
>> > Is there an 'Order that this would need to be done in? Any Recommendations?
>> 
>> You already mentioned ZipSlack (Slackware 11.0), and that was 2006-ish
>> using UMSDOS running atop FAT.
>> 
>> * https://mirrors.slackware.com/mirrorlist/
>> * https://mirrors.dotsrc.org/slackware/slackware-11.0/zipslack/
>> 
>> > I found on those old cds copies of
>> > desQview/X 2.1 and XAppeal (and if they could port it I might be able to)
>> > and DragonLinux which runs on UMSDOS so install on the same partition.
>> > Borland C++ 3.0, so much other fun stuff.
>> 
>> The Desqview/X SDK was DJGPP v1 (though I never used it), it's still on 
>> mirrors.
>> 
>> * https://www.delorie.com/djgpp/getting.html
>> * http://www.delorie.com/pub/djgpp/deleted/v1tk/00_index.txt
>> 
>> > Anyway I am having some problems, and I really don't remember my 
>> > autoexec.bat/config.sys stuff anymore but I remember getting all the dos 
>> > and stuff loaded to high memory or something like that.
>> 
>> I personally wouldn't bother with EMM386 (JEMM) just yet. Try sticking
>> to XMS only (HIMEMX), for now.
>> 
>> > The only options that seem to work are 4 & 5. .  Where can I get all the 
>> > info to relearn all of that?  Is there a website / documentation or an old 
>> > dos book I can buy that would still be relevant to FreeDos.  It sees all 
>> > of the memory on the laptop 4gigs just
>> 
>> * https://help.fdos.org/en/index.htm
>> 
>> > I have not tried anything that needs 32 bit protected mode. but  
>> > eventually once I get it figured out I will need it to do stuff in djgpp.
>> 
>> * https://delorie.com/pub/djgpp/current/v2/readme.1st
>> * https://delorie.com/pub/djgpp/current/v2misc/csdpmi7b.zip
>> 
>> There's also OpenWatcom:
>> 
>> * 
>> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/c/openwatcom/1.9/
>> 
>> A lot of us also like HX / HDPMI32:
>> 
>> * https://github.com/Baron-von-Riedesel/HX/releases/tag/v2.20
>> 
>> > I'm not really good with mailing lists, too  much overload. LOL Do we have 
>> > a Discord server or something along those lines? Web based forum etc.  If 
>> > not, I'll re-adapt.
>> 
>> * http://www.bttr-software.de/forum/board.php
>> 
>> 
>> ___
>> 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] Anyone want to write an article about FreeDOS?

2023-02-07 Thread Daniel Essin via Freedos-user
I think we're all here out of interest. i have a neighbor who "needs" yo run a 
dos app for his nusiness. He's the only one I know who "needs" to run dos. 
Everyone else does it out of interest who still has an ibm-pc or xt as their 
only computer?

That said, if someone "wants" to write dos programs, why not? And if you're 
looking for a retro experience, why a 20meg hard drive (I have one in my compaq 
portable III), why not dual floppies?

And, does anyone remember when Microsoft Access was a program to go online with 
your 300 baud modem to make airline reservations? I have that too, on 5.25 
flop;y. Works great in the compaq except there is no one to call with it 
anymore.

On Tue, Feb 7, 2023, at 10:25 AM, tom ehlert wrote:
>>> programming *on* DOS in the year 2023 is like self flagellation. you
>>> are absolutely allowed to do it; it's just not recommended.
>> Why not? It worked just fine for all intends and purposes for two 
>> decades, so why would that not be "recommended" to do so in 2023?
>
> because programming can be MUCH more productive when you have multiple
> windows open, each much better then 25*80, can google stuff while editing,
> look at your source while debugging and much more.
>
> it worked - yes. like a hand drill, and hand saw, or other late 1800 stuff.
> whatever you do - you are probably using electric stuff these days.
> unless you are an archeologist, trying to rebuild a medivial castel
> with medivial tools only.
>
>
>> That is the part that I think is the true fallacy that too many people
>> perpetrate these days, when claiming to be interested in (Free)DOS.
>
> when 'interested' in DOS, you should use edlin and a XT machine with a
> big 20 MB disk for the real experience.
>
> 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