Re: [Freedos-user] Feelings on lfn

On Nov 8 2022, 17:40, Ralf Quint wrote: On 11/8/2022 2:55 AM, userbeit...@abwesend.de wrote: On Nov 8, 2022, 01:58, Ralf Quint wrote: But I only use this feature sparingly, as there are a lot of older software that can't handle them. And the mapping to some xyz~1.abc is actually losing two

Re: [Freedos-user] Feelings on lfn

On Nov 8, 2022, 01:58, Ralf Quint wrote: But I only use this feature sparingly, as there are a lot of older software that can't handle them. And the mapping to some xyz~1.abc is actually losing two significant characters of those 8 available for generally usable filenames. On Linux, you can

Re: [Freedos-user] Feelings on lfn

Am 07.11.22 um 14:07 schrieb Joseph Norton: Hi listers: I’m just curious about how you all feel about the use of lfn in FreeDOS (or any real DOS). Before you read on: FreeDOS 1.1 was the last version I actually used... (Didn't find the time...) For FreeDOS I think that LFN should be in the

Re: [Freedos-user] "The very weird Hewlett Packard FreeDOS option"

On 18 May 2022, 11:09, Aitor Santamaría wrote: Some months ago we discussed about this very precise topic. I particularly favoured for something like this: let Linux do the job to adapt to new hardware and FreeDOS live in a emulated 16-bit environment that real hardware no longer provides. I am

Re: [Freedos-user] "The very weird Hewlett Packard FreeDOS option"

On 17 May 2022, 18:21, perditi...@gmail.com wrote: So yes there is work in the pipeline, but nothing coming soon or guaranteed to be useful. Jeremy That is great to hear, as FreeDOS will otherwise be drifting away forever on real hardware, even more as it was before (when there still were

Re: [Freedos-user] "The very weird Hewlett Packard FreeDOS option"

Hi! Just out of curiosity... Jim Hall wrote on 16 May 2022, 19:07: FreeDOS pre-installed. But it's UEFI only (no BIOS) and any DOS requires a BIOS. Is there a way to load a BIOS from an UEFI that lacks a CSM? SeaBIOS comes to mind... By loading something like a "BIOSEMU.EFI"

Re: [Freedos-user] ECHO vs @ECHO

On 26 Feb 2022, 02:54, Bret Johnson wrote: I've tried creating an ECHO environment variable. With older versions of DOS: SET ECHO=ECHO OFF and with newer versions of DOS: SET ECHO=@ECHO OFF then at the beginning of all batch files I put a: %ECHO% That works with older versions of

Re: [Freedos-user] Old BIOS issue

ZB wrote on 17th of October 2020: I found some basic information here: https://www.daqarta.com/y2kure.htm (I mean "BACKGROUND" paragraph), but when possible I'd like simply to modify BIOS and resolve the problem "once for always" Wow! Thanks for the link to Y2kure! This is the fix I absolutely

Re: [Freedos-user] 4DOS - license issue, not included in FreeDOS 1.3?

Am 27.03.20 um 23:29 schrieb Jim Hall: > Yes, as I said in my other email, the 4DOS license was a mistake and I > should not have suggested that extra term to Rex. This is unfortunate. You might not have got the sources for 4DOS without those additional terms, since Rex Conn was worried that

Re: [Freedos-user] 4DOS - license issue, not included in FreeDOS 1.3?

On Mar 27 2020 23:53, Random Liegh wrote via Freedos-user: > The important question isn't "why would I", the question is "can I". > > Any reason someone would want to port software from dos to another OS > valid. Any reason. But in the case of 4dos they can't because of the > license. While that

Re: [Freedos-user] 4DOS - license issue, not included in FreeDOS 1.3?

On Mar 27 2020 23:34, Jim Hall wrote: > I didn't want to put FreeDOS in the position of having a "non-free" > package > group like some Linux distributions. That's going to make things > really confusing, and possibly make things harder. As I said, I think > 4DOS can fix it by removing term 2 from

Re: [Freedos-user] 4DOS - license issue, not included in FreeDOS 1.3?

On Mar 27 2020 23:02, Jim Hall wrote: > Yes, the 4DOS license was my mistake and I feel really bad about it. Don't. IMO it's an okay license. And I am forever greatful for it, otherwise we might have never gotten the 4DOS sources like we did. My astonishment is that something exclusively free

Re: [Freedos-user] 4DOS - license issue, not included in FreeDOS 1.3?

On Mar 27 2020 22:21 geneb wrote: >> learn to live with it. >> > Nah, you just ignore it. ;) Exactly. But why not include it [as an option] in the FreeDOS distribution? It's not like it's a mandatory part or a requirement to run FreeDOS, so it's all about user choice. A.

Re: [Freedos-user] 4DOS - license issue, not included in FreeDOS 1.3?

On Mar 27 2020 22:13, Random Liegh wrote via Freedos-user: > The problem is that while it's free to use and to modify on FreeDOS, > it's restricted to FreeDOS (officially speaking; rumour has it that > you're allowed to use it on any DOS based OS unofficially[1]). > > You can't (for example) port

[Freedos-user] 4DOS - license issue, not included in FreeDOS 1.3?

Hi! I just read through http://wiki.freedos.org/wiki/index.php/Releases/1.3/Packages. In Section Utilities 4DOS is marked as "no not include" for FreeDOS 1.3. ?!?!?! I thought that 4DOS was specifically free to use with FreeDOS. Wasn't this the ONLY limitation of the license? Shouldn't it

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

On Mar 27 2020 11:37, Mateusz Viste wrote: > On 27/03/2020 11:25, userbeit...@abwesend.de wrote: >> Yes, FreeDOS tends to be growing, which makes sense. For old computers, >> original to that time, EDR-DOS might be a better choice. > > Or you might try some minimalistic FreeDOS distribution

Re: [Freedos-user] DOSBOX isn't for everyone...

Hi! On Mar 27 2020 04:57, Rugxulo wrote: > XP is dead as a doornail (since 2014), so is even Win7 nowadays. No > more security fixes. Those old cpus (and even modern ones) all have > vulnerabilities and various software workarounds, plus microcode > updates, which each have different costs

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

Hi! On Mar 27 2020 05:14, Rugxulo wrote: > I only have DR-DOS 7.03, but AFAIK, DR-DOS 5 was compatible to MS-DOS > 3.3, DR 6 was their 5, and 7 was (of course) 6 compatible (though it > pretended to be PC-DOS, technically, unless you specifically asked > elsewhere). > > So, yes, FreeDOS should be

Re: [Freedos-user] DOSBOX isn't for everyone...

On Mar 27 2020 04:49, Rugxulo wrote: > Niklaus Wirth wrote "A Plea for Lean Software" back in 1995. He > obviously was referring to his [quasi open source] OberonOS with > compiler and tools. I don't think most people took his advice. He has > had a lot of good ideas over the years, but as even he

Re: [Freedos-user] DOSBOX isn't for everyone...

On Mar 25 2020 18:21, andrew fabbro wrote: > Of course, you're comparing a 20-year-old distro with a 30-year-old > "distro" of DOS :-) > > You get more functionality in a mid-90s Linux than a late-80s DOS. Actually, DOS had a lot to offer. On such a machine it was quite fast, compared to a Unix

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

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

Re: [Freedos-user] DOSBOX isn't for everyone...

On Mar 25 2020 01:36, Rugxulo wrote: > I heard that XP was designed to get to the desktop in 30 secs. Not > necessarily responsive nor able to be used just yet, but at least it > would show up (in optimal conditions). Of course, that was P3/P4 > (single core) era. > > Of course, nowadays we have

Re: [Freedos-user] DOSBOX isn't for everyone...

Hi! On Mar 25 2020 at 01:28, andrew fabbro wrote: > On Mon, Mar 23, 2020 at 8:52 PM wrote: > >> Just a thought, some of us have old computers that we want to run freedos >> on. Running Linux on a Pentium 4 and trying to run Dosbox on top of that is >> going to be pretty have for that machine.

Re: [Freedos-user] Can't boot Freedos from Lenovo B590

On 17th of June, 2019, 10:00hrs, Thomas Mueller wrote: > Excerpt from userbeit...@abwesend.de: > >> Sorry, you're right off course. > > > Did you mean "of course" or "off course"? Sorry. My bad. I meant "of course"... > I have a problem in FreeBSD with support for my ethernet and wireless > >

Re: [Freedos-user] Can't boot Freedos from Lenovo B590

On the 16th of June 2019, 22:28, Thomas Mueller wrote: > Excerpt from userbeit...@abwesend.de: > >> * UEFI replaced the BIOS. >> * FreeDOS needs a PC with BIOS. >> * UEFI, in its transitional period, supported emulating the BIOS, which >> it calls CSM. >> * CSM stands for "compatiblity support

Re: [Freedos-user] Can't boot Freedos from Lenovo B590 [follow-up]

Follow-up: I forgot, it's important that "Secure Boot", should it be turned on, is set to off, otherwise the CSM will be disabled automatically since it essentially defeats the purpose. Also, I found something that illustrates what happens when the CSM is loaded but not "started":

Re: [Freedos-user] *** GMX Spamverdacht *** Can't boot Freedos from Lenovo B590

Hello! It should work. The reason for this is that Windows 7 needs the CSM to be enabled anyway. https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/Unable-to-Install-Windows-7-without-CSM-support-enabled-in-BIOS/ta-p/1038089 I looked your laptop up and it originally shipped with Windows

Re: [Freedos-user] Some driver updates

On 2017-11-05 19:32, Mateusz Viste wrote: On Sun, 05 Nov 2017 17:58:54 +0100, userbeitrag wrote: The truth is I don't have the time nor the resources. Sorry. For someone with no time you sure write awfully long mails. Might be time better spent doing actual stuff. I type fast

Re: [Freedos-user] Some driver updates

Am 2017-11-05 um 16:55 schrieb Mateusz Viste: On Sun, 05 Nov 2017 16:48:00 +0100, userbeitrag wrote: What I'm saying is that you might consider allowing additional software, either in the main distribution, or - which would be even better: to allow the addition of easy to set-up additional

Re: [Freedos-user] Some driver updates

Hi! On 2017-11-05 00:48, Jim Hall wrote: On Sat, 04 Nov 2017 20:09:48 +0100, userbeitrag wrote: I'm also thinking that FreeDOS should include a not-so-free and even a non-free section of software. The only limit should be restriction of redistribution. On Sat, Nov 4, 2017 at 2:27 PM, Mateusz

Re: [Freedos-user] Some driver updates

On 2017-11-05 01:48, geneb wrote: On Sat, 4 Nov 2017, userbeit...@abwesend.de wrote: Isn't that exactly what JPSoftware did with 4DOS? And speaking of it, 4DOS isn't free - it is specifically restricted to FreeDOS, which makes it non-free. Which is basically nonsense because the person that

Re: [Freedos-user] Some driver updates

On 2017-11-04 21:47, Eric Auer wrote: Hi Rugxulo, if umbpci and xmgr run more stable than jemm386, in particular regarding umb range autodetection, then it is no surprise that Dimitris is happy about those :-) And you remember how long ago Japheth stopped maintenance and support for jemm386 and

Re: [Freedos-user] Some driver updates

On 2017-11-04 21:23, Ralf Quint wrote: On 11/4/2017 12:06 PM, userbeit...@abwesend.de wrote: I did install a couple of software too. What good is DOS without programs, right? But even deselecting the compilers and the GUI it didn't fit. I wanted to select only really relevant packages next, but

[Freedos-user] ZANSI.SYS

Hi! I tried to find ZANSI.SYS but found that it is nowerdays really hard to get... Finally I found it there: https://stuff.mit.edu/afs/net/user/tytso/msdos/screen/ So, ZANSI Version 1.2 is from Thomas Hanlin III, who used NANSI 2.2 from Daniel Kegel as a basis. The source code is included.

Re: [Freedos-user] Some driver updates

Hello! On 2017-11-04 16:02, Dale E Sterner wrote: I don't believe that freedos should be restricted to only open software but should promote anything that improves dos, like QV which is closed but great dos software. DOS is on the edge of extinction and needs all the help it can get. Owner of

Re: [Freedos-user] Some driver updates

Hi! On 2017-11-04 18:02, Ralf Quint wrote: On 11/4/2017 4:58 AM, userbeit...@abwesend.de wrote: I too have a couple of old 486 systems and recently also two 286 laptops (yeah!) but I wasn't yet able to install FreeDOS on them. The first reason being that my first project, a desktop 486,

Re: [Freedos-user] Some driver updates

Hi! On 2017-11-04, 11:41, Dimitris Zilaskos wrote: Hi, There some bad heated past definitely which hopefully will be cooled down by time but ultimately like I said, there is a number of dos era systems that people like myself may want to use with FreeDOS and Jack's drivers are an option to do

Re: [Freedos-user] New FreeDOSers Monthly Reminder

Yes, please! At most, a yearly reminder would make sense. A monthly reminder just annoys people. A. Am 2017-11-01 um 12:04 schrieb Tom Ehlert: Hallo Herr John Price, can we please have this monthly remainder stopped? it is just unnecessary Tom am Mittwoch, 1. November 2017 um 07:00

Re: [Freedos-user] boot floppy disk image too big for a disk

k! I hope you will figure it out! (As I hope to find the time to make my 486 run FreeDOS eventually... I didn't find the time since after the New Years holidays...) Userbeitrag. The answer from Dennis is correct: > On Thu, Mar 23, 2017 at 9:32 PM, Dennis Fenton <dwf...@gmail.com>

Re: [Freedos-user] OT: USB floppy cannot read medium on modern PC and Linux.

On 2017-01-02 02:53, dmccunney wrote: > Take a variable out of the equation. Start with a fresh, new floppy > disk. Don't try to reuse an ancient one that may be failing due to > age. > > Floppies are still made and should be findable. Will do. Takes tim

Re: [Freedos-user] OT: USB floppy cannot read medium on modern PC and Linux.

sometimes. It's also prooven that some disks give access errors all the way unter Linux. Honestly, I have no idea. Userbeitrag. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Sla

Re: [Freedos-user] Preload and start installer from installation target?

ould have been FreeDOS, but I am sure this one if from the BIOS _before_ it executes the MBR boot code. Maybe the next time I will try only one partition first... Anyway: again, I've come to a halt for now. I appreciated your help. Happy 2017. Userbeitrag. --

[Freedos-user] HIMEMX.EXE - Invalid Opcode

Skipping HIMEMX.EXE lets me continue with installation. Just reporting... Userbeitrag. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http

Re: [Freedos-user] Preload and start installer from installation target?

drive back in your 486. I thought about that as well, but I really think that would be even worse than the other real PC I could use. I used direct access to physical drives and partitions, so I know the procedure. Anyway, thanks very much for your help! userbeitrag. -

Re: [Freedos-user] Preload and start installer from installation target?

tion stuff from the USB image 1:1 to the third partition. I should then be able to start the installer on the 486-PC from that partition. Thank you very much, userbeitrag. -- Check out the vibrant tech community on one of the

Re: [Freedos-user] Preload and start installer from installation target?

work. I don't know if the floppy drive or the floppies are broken. Anyway, I would prefer another solution: the HDD works in this more modern PC, so I really think that I should install it from USB or CD-ROM there and then transfer the HDD to the 486-PC. T

[Freedos-user] Preload and start installer from installation target?

the installer from there, to create all necessary CONFIG.SYS and AUTOEXEC.BAT entries and to select the software to be installed. The installer files may remain as capacity is not a factor on this HDD anyhow. Has this been done before? And how would I do it? Help highly appreciated! Thanks, userbeitrag

Re: [Freedos-user] Installation on a ThinkPad 340?

think this is how DOSBox does support sound. If you do find a practical solution though -- I would be interested too! Cheers, userbeitrag On 2016-12-18 23:58, Thomas Mueller wrote: > Do such programs to init the sound hardware work with all sound hardware? > I have on-motherboard Inte

Re: [Freedos-user] Cannot boot FreeDOS on 8086-based IBM PS/2 -- any ideas?

Hi! Isnt't FreeDOS dependant on 80286+? Not sure, but pure 8086 isn't very easy to handle these days. Did you try to boot without any device drivers at all? On original 8086 hardware you should try an old version of MS-DOS or DR DOS. That's what I would do. Good luck! userbeitrag

Re: [Freedos-user] Mounting VirtualBox FreeDOS images in Windows

ly available. I didn't test if those versions work under Windows 7, 8/8.1 or 10 though, but if they do this would be great news. Virtual PC 2004 SP1: http://www.microsoft.com/en-US/download/details.aspx?id=3243 Virtual PC 2007 SP1: http://www.microsoft.com/en-US/download/detai

Re: [Freedos-user] Games

BTW, I fear that VirtualBox does not have guest additions, and VMware Tools are also not available for DOS. Cheers, userbeitrag -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutti

Re: [Freedos-user] Games

] QEMU One checked, three remaining... Cheers, userbeitrag -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present

Re: [Freedos-user] Games

ers set up sometimes is hard work, because you have to find those drivers first. Including them as an installation package would be sufficiently easy for uses IMHO. Just my 2¢. Cheers, userbeitrag Original message from Don Flowers, 2016-06-20 20:45: > That would be awesome! >

Re: [Freedos-user] Games

imilar strategy as for DOSEMU > is probably easier: Ship FreeDOS as a directory ready to be > dropped in a shared directory C: "drive" for DOSBox? This is the first time I hear about running actual DOS (the kernel) or its tools inside DOSBox. Most of this s

Re: [Freedos-user] Games

hing: it must be checked if the guest integration drivers are redistributable or not. I don't think DOSBox requires a virtual hard disk image at all. Cheers, userbeitrag -- What NetFlow Analyzer can do for you? Mo

Re: [Freedos-user] Games

r will be. It's not viable to invest in compatibility anyway, given the great alternatives. Cheers, userbeitrag -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reve

Re: [Freedos-user] Games

quirement of the to-be-used (legacy) software. IMHO, for games lack of sound and mouse/joystick support really is the fun-killer. > Cheers, Eric Cheers as well, the anonymous userbeitrag. -- What NetFlow Analyzer can do for

Re: [Freedos-user] Games

Running FreeDOS on real hardware can be challenging. If you only want to play Lure of the Temptress, on a mordern computer you have two options: * DOSBox * ScummVM I would recommend to use ScummVM for playing old (and by ScummVM supported) click-and-point adventures. It integrates very well

Re: [Freedos-user] entering into the command-line as fast as possible

On Fri, Sep 18 2015 at 10:54pm, dmccunney wrote: > On Fri, Sep 18, 2015 at 3:47 PM, Jim Hall wrote: >> But 3(b) in the GNU GPL says source code should be available up to >> three years after they download the binary, upon request. > The problem is that this is generally taken

Re: [Freedos-user] For what architectures is FreeDOS designed?

On 2014-11-23 20:57, Dennis Holierhoek wrote: Hello everybody, I was wondering about two things: For what architectures is FreeDOS designed? For what architectures must programs be designed to run on FreeDOS? Dennis As far as I can tell, QDOS i.e. Quick and Dirty Operating System was a

Re: [Freedos-user] Partition magic anyone?

-- Original message -- Subject: Re: [Freedos-user] Partition magic anyone? Date:Friday, 05. October 2012 From:Santiago Almenara almen...@gmail.com To: Discussion and general questions about FreeDOS. freedos- u...@lists.sourceforge.net On Thu, Oct 4, 2012 at 11:53

Re: [Freedos-user] FreeDOS packaging rules / paths

Hi! Long time no see. I’d like to mention my POV anyways. Why use a Unix-like structure? In DOS, everything is where you want to put it. Configuration files traditionally reside in the same directory where the actual program that uses it is located. If not, it has its own structure (like

Re: [Freedos-user] 387 emulator

charles wrote on Wednesday 24th of November 2010: I have recently installed freedos 1.0 on my 486sx laptop. I am now looking for a math coprocessor emulator that won't kill emm386. Any suggestions? No. I do know there was one in the old days (late 80's), and as far as I remember it was

Re: [Freedos-user] PC-MOS/386 - a GPLed Multitasking DOS alternative (MS-DOS 5.0 compatible)

Oups... Sorry, I was wrong - the source code is NOT yet available. And it is uncertain, which license it will end up with. Andreas. Original message: Hi! I wonder if anyone ever heard of PC-MOS/386? Since its code is now under the GPLv2 it should be considered as an option to the

[Freedos-user] PC-MOS/386 - a GPLed Multitasking DOS alternative (MS-DOS 5.0 compatible)

Hi! I wonder if anyone ever heard of PC-MOS/386? Since its code is now under the GPLv2 it should be considered as an option to the existing FreeDOS distribution or (for developers) as a new source of improvement (code exchange) to FreeDOS itself. http://code.google.com/p/pcmos386/ Greetings,