Re: [Freedos-user] Forwarding and commenting a FreeDOS 1.3rc3 critical review

> First, the amount of RAM available varies greatly making it an all or nothing > prospect. > Second, unzip requires DMPI and wants HD swap. Unless the binary is > somehow modified at boot, it will complain about no C drive swap. > Also with no swap and limited RAM constraints, it is potential

Re: [Freedos-user] DOS on (very) small form factor PCs?

> ...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. (with the exception that there might be CPU sepcific microcode updates

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

Hallo Herr tom ehlert, am Samstag, 17. April 2021 um 11:20 schrieben Sie: > BTW: your original statement was > 'Remember that in effect MS-DOS was an unlicensed copy of Digital >Research's CP/M and particularly CP/M-86.' > by TK Chia's remark, CP/M-86 didn't even exist yet w

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

BTW: your original statement was 'Remember that in effect MS-DOS was an unlicensed copy of Digital Research's CP/M and particularly CP/M-86.' by TK Chia's remark, CP/M-86 didn't even exist yet when he wrote QDOS. and QDOS couldn't compete with CP/M as CP/M doesn't run on 8088. > I still

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

Hallo Herr Liam Proven, am Freitag, 16. April 2021 um 13:44 schrieben Sie: > On Thu, 15 Apr 2021 at 19:48, tom ehlert wrote: >> >> that is simply not true. to start this sentence with 'Remember' >> as in 'as everyone knows' is bullshit conspiracy tactics. > I stand by

Re: [Freedos-user] DOS was dead...

> I will note that Windows 95 *could* use DOS drivers. I/O > performance suffered horribly since DOS drivers weren't thread safe, > but there was a copy of DOS in the system VM for this purpose, even > if it had nothing to do under normal circumstances. > But to some degree this is a

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

I basically agree with what you write, but > Remember that in effect MS-DOS was an unlicensed copy of Digital > Research's CP/M and particularly CP/M-86. that is simply not true. to start this sentence with 'Remember' as in 'as everyone knows' is bullshit conspiracy tactics. Tom

Re: [Freedos-user] Using a USB stick and an optical drive

Liam, >> it's not. I know. but it's a file format that can transport both a DOS >> and Windows executable in the same file. > This is not correct. In fact this tech was possible before Windows 3.0 > even launched; it was called a "family app" or "family mode". probabaly it's a bit of hair

Re: [Freedos-user] Using a USB stick and an optical drive

Liam, >> It is safe but will not solve your problem. The BIOS updater .EXE is a >> Windows program, and will only run on Windows. > Tom, do not guess. Check, be sure, before you post. > Here is the BIOS update: >

Re: [Freedos-user] Using a USB stick and an optical drive

Hallo Herr Eric Auer, am Freitag, 9. April 2021 um 18:04 schrieben Sie: > Hi Stephanos, >> 1) I have WINE on my laptop and run several MS applications.  Is it safe >> to treat the BIOS upgrade file as an application and run it in WINE? > That will not help. Wine can run Windows apps, but you

Re: [Freedos-user] GNU General Public License...

> I can be a part of a healthy conversation, > otherwise I have to respectfully withdraw. excellent idea Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] GNU General Public License...

> The license MUST be viral. Folks, anyone who complains about it > being viral doesn't understand it at all. that's nonsense. there are a lot of free licenses out there that are not viral, starting with LGPL, but also Apache, MIT, and many others. > Google is a monopoly. > Google doesn't

[Freedos-user] FSF

https://arstechnica.com/gadgets/2021/03/red-hat-withdraws-from-the-stallman-led-free-software-foundation/ maybe it's time to show the FSF the middle finger, too? Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net

Re: [Freedos-user] Latex / long filenames

> Am trying to use Latex (from DJGPP) in Freedos, and get errors > seemingly having to do with long file names. always try to be a little bit more precise then 'getting errors' > The "dir" command only shows 8+3, try DIR /LFN ... > and when I manually rename using > "move", the name

Re: [Freedos-user] COWGOL programming language

Hallo Herr TK Chia, am Mittwoch, 17. März 2021 um 13:19 schrieben Sie: > Hello Bruce, hello Dennis, >> No recursion and no floating point will be blockers users need to keep >> in mind, but being able to build for 8bit micros like the 8080, Z-80, >> and 6502 is a definite plus.. > The Cowgol

Re: [Freedos-user] BIOS weirdness with SATA/IDE adapter

"Evolution as taught in public schools, like religion, is based on faith, not on science." either give us a pointer why you think you must annoy us with that, or please stop with that (mostly religious) nonsense. Tom ___ Freedos-user

Re: [Freedos-user] 1.3RC3 Installation woes (was Re: FDISK 1.3.3)

> ERROR: Unable to initialize CD-ROM drive > after trying to load UDVD2 (3-05-2015). of course it would be cool to read the error message form UDVD2 itself, otherwise "ERROR:bla" is not very helpful ;<<< > This is on a Dell Latitude, so not just some obscure 3rd party Chinese > knock-off...

Re: [Freedos-user] Proposal to add "unzip16.exe" to FreeDOS Disk Image

Hallo Herr Jerome Shidel, am Mittwoch, 10. Februar 2021 um 16:08 schrieben Sie: > Hi Eric, > On Feb 10, 2021, at 8:40 AM, Eric Auer wrote: > [..] > PS: Thanks Tom et al for improving FDISK!! Time to get > the new version packaged into the distro repositories? > That was done soon after

Re: [Freedos-user] FYI: I'm speaking at FOSDEM'21 this weekend

> I want to get "1.3" finally wrapped up, and I'd like to have a > "2.0" someday. The NightDOS folks are working english is not my first language so i could missread this. but doesn't 'folks are working' suggest a plurality of human being, opposed to the reality of a single guy who ever

Re: [Freedos-user] FYI: I'm speaking at FOSDEM'21 this weekend

> (and a future "2.0" someday). I am a bit surprised by this. any news that we all are not aware of? Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Windows 95

>>> **Win95 is an operative system (no comment). **There is no DOS. >> Win95 is a desktop environment that lives on top of a MS-DOS 7.0 foundation. >> Win98SE is a desktop environment that lives on top of a MS-DOS 7.1 >> foundation. >> WinME " " " " " "

Re: [Freedos-user] Windows 95

>> **Win95 is an operative system (no comment). **There is no DOS. > Win95 is a desktop environment that lives on top of a MS-DOS 7.0 foundation. nope. starting with Windows 3.11 for workgroups, most work is done by Windows. Win95: Only if necessary work would be delegated to the 16Bit DOS

Re: [Freedos-user] Which C compiler for targeting DOS?

> * I would like to be able to automate the build process as much as >possible, avoiding complex install requirements as are often the >case with cross compilers. This means automatically downloading the >compiler would be great, so it knocks out something like Borland >Turbo C

Re: [Freedos-user] Context out of memory

> {If this error persists, consider to increase some internal buffer, such > as history, directory stack, etc.} > I do not know how to do this. I seriously recommend using a different operating system. alternatively, please use a different mailing list. thanks Tom

Re: [Freedos-user] IDE <-> CF adapters

>> 1. This is bad idea - use flash cards for swap or more modern os (like all >> windows). I had experience with 16 TF cards, which die after 1 year (rewrite >> limit). All 16 cards work in non-overloaded machines. > My CF card is used as "HDD" 3rd month - we'll see in 9 months will it survive.

Re: [Freedos-user] Package discussion

>> TPPATCH is both small and really useful (runtime error fixer for >> Borland compiled binaries which crash on too fast CPU, I believe?) > But its license is unclear, because so far we didn't find a way to > contact the author Andreas Bauer. googling TPPATCH easily leads to

Re: [Freedos-user] AMB, Ancient Machine Book format and FreeDOS Help

> Don't forget ftp:, mailto:, gopher:, telnet:, news:, file:, ... > () > What about scheme-less URLs, e.g., or ? not THAT complicated. www. --> http://www. ftp. --> ftp://ftp blabla@ --> mailto:blabla file: is local anyway, not

Re: [Freedos-user] Make sure your opinion is heard

> Are you happy with what software is included with FreeDOS? you are mixing up "FreeDOS" with "FreeDOS setup 1.x" there was a lot of FreeDOS going on before this (IMO insane) FreeDOS 1.0 release. xyzDOS used to be mostly equivalent to be our "BASE" with few additions. at some point, someone

Re: [Freedos-user] CDROM Driver

> Remember that it was normal that CDROM drives shipped with > DOS drivers in the past. this is true. and each manufacturer took care to only support it's own drives. until later someone showed that IDE-CDROM drivers are inherently universal. UDVD and vide-cdd.sys

Re: [Freedos-user] Multi-Boot with Windows 2000 and FreeDOS

> Hey Tom - do you think Windows 2000 boot.ini is the best way to go > for my particular setup? If you do, I'll give it another try and report my > errors/messages.  multibooting Windows NT/2000/XP with DOS was a 'no problem' problem in ~1995-2005, using any of multiple (boot.ini, GRUB,

Re: [Freedos-user] Multi-Boot with Windows 2000 and FreeDOS

th my FreeDOS setup? At this point, I feel lucky that both > operating systems still boot and run ok by swapping drives in my BIOS! Hallo Herr FreeDOS., Mit freundlichen Grüßen / with kind regards Tom Ehlert +49-241-79886 ___ Freedos-u

Re: [Freedos-user] PCI Express Network Adapter Board for FreeDos

> Can anyone suggest a PCIe network adapter for FreeDos? One that I > can get a packet driver or NDIS driver for. My FreeDos computer > doesn't have a regular PCI slot and I've given up trying to get the onboard > network adapter to work. while it's MSDOS based, this

Re: [Freedos-user] PCI Express Network Adapter Board for FreeDos

> Can anyone suggest a PCIe network adapter for FreeDos? One that I > can get a packet driver or NDIS driver for. My FreeDos computer > doesn't have a regular PCI slot and I've given up trying to get the onboard > network adapter to work. Realtek 8139 has NDIS drivers, E1000 both packet and

Re: [Freedos-user] installation/partitions

> Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Hallo Herr FreeDOS., Mit freundlichen Grüßen / with kind regards Tom Ehlert +49-241-79886 _

Re: [Freedos-user] Is there such a thing as an add-on SATA host controller that works with DOS?

Hallo Herr Deposite Pirate, am Samstag, 24. Oktober 2020 um 10:14 schrieben Sie: > Hi, > I have a bunch of SATA mechanical hard drives with perfect health > that I've swapped out for SSDs in various laptops. I installed a > 160Gb one with a Silicon Image 3512a SATALink host controller in my >

Re: [Freedos-user] Is there such a thing as an add-on SATA host controller that works with DOS?

Hallo Herr ZB, am Samstag, 24. Oktober 2020 um 13:19 schrieben Sie: > On Sat, Oct 24, 2020 at 08:14:44AM +, Deposite Pirate wrote: >> Considering how late FAT32 support came to the >> DOS family of OSes I would understand why no manufacturer of SATA add-on >> host controller bothered with

Re: [Freedos-user] A few suggestions to improve debug

> And as there aren't many tools where ZB's idea would make > sense in his opinion, it seems a bit like brewing up a tempest in a > teacup... ;-) +1 > And another reason why this might not be in general a good idea is if we > take compatibility with old(er) DOS software/environments serious,

Re: [Freedos-user] Bexome Endorsed By The FSF! Opportunity

Hallo Herr Ralf Quint, am Sonntag, 23. August 2020 um 09:01 schrieben Sie: > On 8/22/2020 3:17 PM, haytam.fr--- via Freedos-user wrote: >> Hey, >> I want to inform you about something kind of interesting , >> http://www.gnu.org/distros/free-non-gnu-distros.html visit this >> website , make

Re: [Freedos-user] Moving beyond FAT

>> ... would this have any effect on existing DOS software? at least a bit. to transfer data between BIOS, DOS programs and your driver you need a buffer in the precious 640KB space. whatever size you select (due to performance over resource usage), you are hurting real mode programs, more or

Re: [Freedos-user] Benchmark volunteers wanted

> indeed the FreeDOS kernel is about 2* slower then necessary >> *on rotating rust disks* ; the reason is known (1) > Because I/O is split to avoid 64 kB DMA boundaries, > into 2, at most 3 transfers, even when only floppy > would need it, according to your footnote (1). > If your diagnosis is

Re: [Freedos-user] Benchmark volunteers wanted

Hallo Herr Eric Auer, > As FreeDOS has the reputation of having slow disk I/O, 'reputation' meaning that Jack told you so... but indeed the FreeDOS kernel is about 2* slower then necessary *on rotating rust disks*; the reason is known (1), hasn't been fixed for the last few years, and given

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

DJGPP) in 2017 for simple 2D games. > It's not that dire. Anybody interested could clean up and fix some of > these. I might even do it myself, but it's not pressing. There's > always more to do. > Sorry for the ramble, it's just a minefield of tools out there. Still fun! > _

Re: [Freedos-user] SATA...

> Or if that fails, disable AHCI in the SATA controller. DOS is fine with > drives talking in IDE mode. for disk drives, your disk should be supported by the BIOS. it usually is, otherwise it could not boot from it. it doesn't matter at all if it's SATA, PATA/IDE, RAID, SCSI, SAS, MFM, RLL or

Re: [Freedos-user] Backslash key on UK keyboard not recognised

> Thank you for the pointer. I checked my autoexec.bat, and as set up when > I installed FreeDOS it loaded mkeyb UK in conventional memory. as I understand your backslash key doesn't produce any character at all. whatever the reason, mkeyb has a debug mode mkeyb uk /T here it will show you

Re: [Freedos-user] paint programs for DOS - was 4DOS...

Hallo Herr Ralf Quint, am Montag, 13. April 2020 um 21:22 schrieben Sie: > On 4/13/2020 10:28 AM, tom ehlert wrote: >> >>>> So the task would be to translate 5000 snippets of >>>> French, are there any GrafX2 fans who feel in the >>>>

Re: [Freedos-user] paint programs for DOS - was 4DOS...

>> So the task would be to translate 5000 snippets of >> French, are there any GrafX2 fans who feel in the >> mood to help FreeDOS as source "interpreters"? :-) a) this sounds like a job for something like grep ... | sed ... | awk ...| translate.google.com | sed ... unfortunately I

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

Hallo Herr userbeit...@abwesend.de, am Freitag, 27. März 2020 um 21:07 schrieben Sie: > 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

Re: [Freedos-user] USB floppy saga...

> I'm working with an EVOC brand SBC on a PICMG 1.0 backplane. > I have not been able to get floppy disk support in Freedos 1.3, period. as far as I understand it, you have been working with MSDOS 6.x for the last 25 years. I recommend another 20 years. the alternative would have been to

Re: [Freedos-user] Can't install FreeDOS

> Regrettably, I ran into another problem: apparently the CD I burned was > roughed up too badly for the installation to complete.  It died while > trying to install UDVD2, due to a read error.  And that was my last > CD-R.  as you don't describe in detail what you did we can only guess :<<

Re: [Freedos-user] floppy drive won't format disk...

the PCI bus. > The only format I have achieved is with a Teac USB floppy drive in > Windows Millenium, the ISA card not installed at all. > Can someone shed light some light on Error 136 and DMA troubles? Hallo Herr FreeDOS., Mit freundlichen Grüßen / with kind regards Tom Ehl

Re: [Freedos-user] DOS version control

> On 16/02/2020 22:54, tom ehlert wrote: >> doing programming *on* DOS in 2020 is just stupid. > Why would that be more stupid than programming *for* DOS in 2020? > A hobby is a hobby. ok. replace 'stupid' by 'inefficient' in the sense that there are easier ways to get usef

Re: [Freedos-user] DOS version control

> I've starting working on a game and some small dual monitor (VGA + > MDA) utilities but have run into issues where the code used to work > and now it doesn't.  We use subversion, cvs, and git at work and I > was wondering what options are available for dos-based systems besides dated > zip

Re: [Freedos-user] Freedos 1.3 and Windows 9x...

> MS DOS 6.x was not the end of MS-DOS. Windows 9x releases added a > strange protected mode, but unlike NT, these versions of Windows still ran on > top of MS-DOS. > There is no support for DOS based Windows any longer and the > ReactOS project essentially abandoned it. However, there are >

Re: [Freedos-user] "Test." -- does that come from FreeDOS?

Hallo Herr Jack Browning, am Montag, 6. Januar 2020 um 19:32 schrieben Sie: > I've been trying to update the BIOS on my wife's Dell Inspiron 17 > 5721 laptop using FreeDOS. I've tried to do this with FreeDOS 1.0, > 1.1, 1.2, and 1.3rc2, each time with the same result. > What happens is this:

Re: [Freedos-user] Debian 9 64b / QEMU 2.8.1 / FreeDOS 1.3rc2 as a guest: DHCP requests end up zero-padded

>> in short: when debugging network problems, avoid EMM386/JEMMEX. >> >> HIMEM and friends should be fine, though. >> > Okay, I'll try to figure out my way through this... > I definitely do need something to load all the resident drivers > "high" wherever possible, otherwise I'm out of

Re: [Freedos-user] Debian 9 64b / QEMU 2.8.1 / FreeDOS 1.3rc2 as a guest: DHCP requests end up zero-padded

Hi Frank, > So in that context, in the Debian-based host OS, I've tried sniffing > the traffic coming out of tap0 with tcpdump. And, I'm seeing > something interesting. > In perfect correlation with the DOS guest's DHCP client starting up, > I can see a "packet of all zeroes" every now and

Re: [Freedos-user] MODE not changing RTS or DTR of serial ports

Hi! ECHO TEST>COM1 >>> good idea. unfortunately this only works with proper >>> DTR/CTS/RTS/... status lines connected. > Unless you select a no-handshake mode. MODE might be able to suggest to a partner 'I am ready to receive'. there is no such thing ( for MODE) as 'ignore status lines.

Re: [Freedos-user] MODE not changing RTS or DTR of serial ports

> MODE COM1:BAUD=9600 DATA=8 STOP=1 PARITY=N DTR=OFF RTS=OFF MODE (for anyDOS) does nothing sensible about DTR/RTS. (it might set the status line outputs, I don't know. there is no way to change the input of status line behaviour. > I suspect that DTR/RTS being on is the reason why I cannot

Re: [Freedos-user] Freedos 1.2 move, copy & xcopy

Hallo Herr Ralf Quint, am Montag, 25. November 2019 um 18:43 schrieben Sie: > On 11/25/2019 8:36 AM, TK Chia wrote: >>> One problem here is what I mentioned a lot of times in the past but >>> always got scoffed at is that these are highly technical apps but do not >>> have any proper technical

Re: [Freedos-user] Quick FreeDOS 1.3 Live CD Poll

>> After you booted DOS from CD: >> >> - insert floppy >> - type "format a:/s" >> - ...done. You've got "FreeDOS LiveFloppy". You can then transfer needed >> programs/data to that floppy > What to do if I don't have a physical floppy or physical floppy drive > anywhere? (so can't do it "format

Re: [Freedos-user] Quick FreeDOS 1.3 Live CD Poll

Hallo Herr Felix Miata, am Donnerstag, 14. November 2019 um 17:38 schrieben Sie: > Jerome Shidel composed on 2019-11-14 10:27 (UTC-0500): >> I’m just looking to do quick poll on you thoughts and opinion. >> When FreeDOS 1.3 is booted as a Live environment from the CD-ROM, should it >> be

Re: [Freedos-user] Freedos 1.2 move, copy & xcopy

>I have 2gigs of drive space used. It seems that move for >some reason thinks the drive is full. > > >I tried the copy command today and it worked. I don't understand it. as said before: unless you tell us the exact command that failed, you are just producing noise. COPY *.* NEW will work.

Re: [Freedos-user] Freedos 1.2 move, copy & xcopy

> copy on MS-DOS wasn't really meant for copying more than one file > at a time bullshit. COPY can copy multiple files. both on MSDOS and FreeDOS. > (which is why xcopy exists), no. XCOPY /S is one of the reasons for it's existence. multiple files not. Tom

Re: [Freedos-user] Freedos 1.2 move, copy & xcopy

Hallo Herr Dale E Sterner, am Dienstag, 12. November 2019 um 17:38 schrieben Sie: > I tried to move post.mp4 - a 3.5.meg file. - got insufficient memory > error with move, copy & xcopy. The copy command sometimes > has trouble with wildcard "*". I tried copy *.* new\*.* the correct command

Re: [Freedos-user] Freedos 1.2 move, copy & xcopy

> Have you noticed that move, copy & xcopy refuse > to work on files bigger than 3 meg. No. And it's extremely unlikely that copy & xcopy fail in similar ways (they are entirely unrelated). > I tried to relocate > an mp4 file and they all said "out of memory" or > was it "disk space"; it

Re: [Freedos-user] DOS Frotz 2.50 beta1 is out

> Yesterday I tagged and released the first beta test of DOS Frotz 2.50. > Most of the work that went into the DOS interface focus on improving > stablity. I think I've corrected the two outstanding problems with DOS > Frotz: locking up upon exit and crashing with a "dos mem corrupt" error. >

Re: [Freedos-user] freedos 1.2 | creating modified ISO image with mkisofs

Hi, > I am new to FreeDOS and would like to ask for any helpful hint how > to create an modified ISO image from the actual FreeDOS version 1.2. > My "aim" is simple - based on the FD12LGCY.iso image to create a > bootable DOS ISO image with BIOS firmware upgrade software (DOS based). creating a

Re: [Freedos-user] Source code to Windows 9x and ME...

> The comment that a pick and place machine designed around MS-DOS 6.22 > and Windows 9x/ME is a funny machine is a little disingenuous. > Freedos didn't exist in a useable form back then and Windows 9x/ME in > it's day was dominant. I surely didn't want to insult your amazing machine;

Re: [Freedos-user] Source code to Windows 9x and ME...

> Freedos should be capable of supporting Windows 3.1, at least in > standard mode. AFAIK it does (not that it was ever important for the developers). > Wouldn't it be great if freedos could support that better and 3.11 as well > along with a lot of programs from that era? just organize your

Re: [Freedos-user] bugs in XDEL command included with 1.3 RC1

> Example of the exact command that failed was "xdel /s *.uni\*.de": I located the original 22 may 2002 from original author even this can't XDEL /d *.uni and xdel /s *.uni\*.de > Definitely broken command, seems like. exactly. should be fixed by someone with more motivation then

Re: [Freedos-user] bugs in XDEL command included with 1.3 RC1

> I assume these are known problems with the XDEL command in version > 1.3 RC1, but this regards two situations: not at all. at least some of these problems seem to be introduced during port Borland C --> Watcm C (in 2005; XDEL seems to be not so intensly used) > 1) where you want to delete

Re: [Freedos-user] HP laptop touchpad

> I agree about trackpads, they’re awful. The only port this thing > has is a USB port and a usb mouse didn’t really fare any better than > the trackpad, and I don’t think cutemouse supports usb mice either. most likely your trackpad is connected to the motherboard via an internal USB port,

Re: [Freedos-user] why isn't anyone answering my question?

> On 7/17/2019 4:41 AM, kaye n wrote: >> My apologies.  Wrong choice of words.  I am aware that this is not a >> paid support line. >> >> Anyway, here's my question. >> >> I have a desktop computer running a Linux distro. In this LInux distro >> I have installed VirtualBox, and in this

Re: [Freedos-user] Find command and a drive

Hallo Herr Jim Hall, am 25. Juni 2019 um 22:16 schrieben Sie: > I don't see this bug reported in the bug database, so you seem to > be the first person to discover this bug? That's pretty amazing, > since the bug appears to have been in there since at least 2007 (latest > version). >

Re: [Freedos-user] New FreeDOSers Monthly Reminder

__ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Windows 2000 fat32 and freedos...

> The two aren't currently compatible. Any chance of lfndos getting > the bugs ironed out? lfndos is known to be buggy. use doslfn http://sta.c64.org/dosprg/doslfn.zip instead. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net

Re: [Freedos-user] Windows 2000 fat32 and freedos...

> FreeDOS began as an effort to create an open source version of 16 bit > DOS, compatible with what Microsoft issued. It largely succeeded in > that effort. exactly. > Providing the support you want is serious system level programming. > The folks who *can* do that get *paid* for it. Tell me

Re: [Freedos-user] Agilent e5061a and e5071b...

Hi, > The Agilent e5061a belongs to the company I'm working for and is > only two channel. this mailing list is about FreeDOS, and not the Agilent e5061a or Windows 2000 support group. you may help him, but please do so on private channels; the FreeDOS community is not going to learn anything

Re: [Freedos-user] Using a timer with an ISR in watcom

> Just out of curiosity, if I write something for a DOS4GW 32bit > environment, would I choose the same way for having a timer or are there > better ways for having a timer callback function? the idea will be the same, the routines to use are different. > For a later experiment project I want to

[Freedos-user] MKEYB 0.43 has been updated

MKEYB has been updated, the slovenian keyboard has been corrected and verified by Fritz. http://www.drivesnapshot.de/freedos/mkeyb.htm Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net

Re: [Freedos-user] Updates to FreeDOS wiki

Hi Eric, >> I took the time to look into what the night dos kernel... >> what they describe as goal is some sort of OS/2, WINDOWS 3.11 > While their goals are noble, I doubt that they will achieve good > compatibility with most DOS stuff. And I agree that they should > use more C in their code

Re: [Freedos-user] Updates to FreeDOS wiki

> Not sure how to fold in the "16bit v 32bit" section or the "UEFI" > section, but I may add a section at the bottom of "Releases" that > talks about this (probably "Features" or "Assumptions") just to have > everything in one page. "16bit v 32bit": I took the time to look into what the night

Re: [Freedos-user] FreeDOS on SSD

>> Trim sounds like the old standard "defrag program" which should >> be unneeded for flash since all bits get accessed at the same speed. >> No spinning disk to move around on. wrong. > Trim is used for equal usage of memory-cells. It is a mechanism to > support round-robin usage of those

Re: [Freedos-user] FreeDOS on SSD

For some > applications DOS is far faster than the pixel-mapped systems. You > don't need a luxurious Mercedes to move a box of chocolates down the > road. Thank you for your comments. FDISKto create an active partition reboot FORMAT C: SYS C: Tom > De : Tom Ehlert > Envoyé

Re: [Freedos-user] FreeDOS on SSD

>> Can anyone recommend an IDIOT-proof method of installing FreeDOS 1.2 on >> a fixed SSD drive (with no OS) via one of several USB ports ? 1st, a fixed SSD behaves *exactly* like a ((fast) rotating disk. 2nd, I have no idea how much IDIOT you are, but most likely ANYDOS is not your best

Re: [Freedos-user] MS-DOS 1.1 and 2.0 ...now open source?

>> IIRC, the FreeDOS kernel is written largely in C, so the ASM source >> isn't directly usable. It may be useful to go spelunking for the >> algorithms used and how corner cases were handled. > It certainly can help to deal with issues that arise out of undocumented > features/bugs/issues, which

Re: [Freedos-user] Memmaker

Hi Eric, >>   0aa5 10,464   (10K)    IBMDSS14    device driver >> installed DEVICE=IBMDSS14 >>   0d34 25,824   (25K)    IBMDOSCS    device driver >> installed DEVICE=IBMDOSCS > What is the purpose of

Re: [Freedos-user] SLIP packet driver

Hallo Herr David McMackins, am Mittwoch, 1. August 2018 um 03:48 schrieben Sie: > Ah, it appears I should've looked past my nose. FreeDOS's own Crynwr > package has a SLIP driver. > Is using it as simple as just running SLIP8250.COM? If you don't know how to use a SLIP driver you most likely

Re: [Freedos-user] [Announce]E100PKT 0.2 (stable)

Hallo Herr Seth Simon, am Donnerstag, 14. Juni 2018 um 03:27 schrieben Sie: > I've released version 0.2, which I consider stable, of E100PKT. > This version uses less memory, supports interrupt sharing, and > fixes many bugs. If you plan to upgrade from 0.1, please note > that version 0.2 cannot

Re: [Freedos-user] (no subject)

> DOSEMU2 (Linux-hosted) is still being worked upon, and there have been > efforts to port the current FreeDOS kernel to GCC (with 16-bit support > patches). Since that (also) works on x64, the latest efforts should > again continue to prolong the lifetime of DOS programs, which is good > since

Re: [Freedos-user] Trying to run a Dell bios update exe in FreeDOS 1.2

Hallo Herr Jim Hall, am Dienstag, 16. Januar 2018 um 22:17 schrieben Sie: > On Tue, Jan 16, 2018 at 3:10 PM, Mario Menezes wrote: >> >> I've to say that using a Windows PE iso (got from here >> https://toolslib.net/downloads/viewdownload/255-winpese-x64/) and LiveUSB >>

Re: [Freedos-user] Trying to run a Dell bios update exe in FreeDOS 1.2

> Hi, >   I'm trying to run a Dell bios update file for my Inspiron 7520. >   I've created the FreeDOS usb stick, copy the bios update file to > it, can boot into it, return to DOS Prompt without installing, but > when I try to run the exe file all I get is (reproducing the FreeDOS screen >

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

> I used CloneDisk to rip a RAW image of the booting DOM with > FreeDOS. Mounted that with Qemu. Booted Qemu with the FreeDOS > install image and installed FreeDOS to the image copied from the > DOM. Then I used CloneDisk to write that image back to the DOM. "Missing > Operating System". I just

Re: [Freedos-user] Would you use a native 32/64-bit FreeDOS/BIOS system?

> There already is FD32 which puts FreeDOS and > a 32-bit DOS extender into the same file, I missed this. If you mean FreeDOS-32, they put 'FreeDOS and a 32-bit DOS extender' in the project name, but the source is unrelated to FreeDOS. If I'm wrong, please correct me. > but the improvements >

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

> I used CloneDisk to rip a RAW image of the booting DOM with > FreeDOS. Mounted that with Qemu. Booted Qemu with the FreeDOS > install image and installed FreeDOS to the image copied from the > DOM. Then I used CloneDisk to write that image back to the DOM. "Missing > Operating System". forget

Re: [Freedos-user] You think BETA testing means you're brave?

> It's not FOSS but source is available here [0][1][2] for IMD. > [0] http://www.classiccmp.org/dunfield/dos/index.htm > [1] http://www.classiccmp.org/dunfield/dos/imd.zip > [2] http://www.classiccmp.org/dunfield/dos/imdsrc.zip besides other restrictions, this does not allow distribution. so

Re: [Freedos-user] SSH - unsupported remote protocol version

> We did talk at length about it almost exactly a year ago.  The tldr > version is that you would need ssh2d386 and you have to have access > to modify the ssh config on the server to support older ciphers.  there are GOOD reasons to not allow outdated protocols to be used. on what planet have

Re: [Freedos-user] SSH - unsupported remote protocol version

> On 12/31/2017 10:47 AM, Robert Riebisch wrote: >> From SSHDOS source code: >> ### >>if(remote_major != 1 && remote_minor == 0) >> fatal("Unsupported remote protocol version\n"); >> ### > What a weird check. So version 2.1 would work? Shouldn't the check be not only a weird and

Re: [Freedos-user] counterproductive UPX usage for loadhigh display /maybe other drivers also/?

Hi, > Hi, I just tried to 'lh display', but it always ends in conventional > memory (code, codepages are perhaps in XMS): ... > I myself explain this that the UPX-ed program is probably going to UMB, > but after its decompression, its resident part will no longer fit there > for some reason and

Re: [Freedos-user] Some driver updates

> What do these "Jack's Drivers" actually do? nothing as they no longer work on FreeDOS. btw: NEVER fullquote. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!

<    1   2   3   4   >