> More detail:
> The rs232 port Com1: is connected via a Null modem cable to an Adam 232 to
> 485 converter.
> In the Bios I have Com2 to 3 disabled.
> An IRQ clash is possible if Cutemouse uses IRQ4 from Com1.
> My next step is to try different mouse drivers, unless I get more
> suggestions.
th
> The serial port is opened in FreeBasic with :
> Open Com "COM1:38400,n,8,1,cs0,ds0,cd0,rs" For Random As #CP
FreeBasic doesn't support FIFO, and most likely no IRQ.
try
Open Com "COM1:600,n,8,1,cs0,ds0,cd0,rs" For Random As #CP
and see if that changes your problem.
Tom
> FreeBasic doesn't support FIFO, and most likely no IRQ.
> try
> Open Com "COM1:600,n,8,1,cs0,ds0,cd0,rs" For Random As #CP
> and see if that changes your problem.
sorry, not true.
FreeBasic seems to use IRQ, but not FIFO.
anyway, try
Open Com "COM1:600,n,8,1,cs0,ds0,cd0,r
> DOS might have problems with SATA drive. DOS reads from the harddrive a
> lot.
> Since SATA is serial (just one bit at a time) The data ransfer rate might
> be too slow for DOS to live with. I know I can't get it to run on a SD card
> because one bit at a time is just too slow.
back in the good
> I've released alphas and beta versions of the game.
> http://www.mediafire.com/download/36t9ql7z19x14i8/SN0_1.ZIP: tech demo.
> http://www.mediafire.com/download/ddem9tk51xdaidu/SN0_3.ZIP: alpha 0.3
> http://www.mediafire.com/download/u7hdsdtevhv4omt/SN0_6.ZIP: alpha 0.6
> http://www.mediafire.c
> Is it safe to load UIDE in FDAUTO.BAT with DEVLOAD.COM, instead
> of loading it in FDCONFIG.SYS as recommended in the
> instructions?
yes, this is save.
Tom
--
Dive into the World of Parallel Programming! The Go Paral
> Now the new multi-TB hard drives have 4096-byte physical sectors,
> at least some of them try to act as if sector size were 512 bytes.
virtually ALL disks act as having 512 byte sectors, even if they have
internally 4096 byte ('advanced format').
search for '4K native' drives, and you will see
> Ability to run Windows 3.1 in 386 enhanced mode.
has been discussed multiple times. conclusion: forget it
Tom
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitorin
> On Mon, May 18, 2015 at 8:32 PM, Rugxulo wrote:
> Hi,
>
> On Mon, May 18, 2015 at 4:42 AM, Tom Ehlert wrote:
>>
>>> Ability to run Windows 3.1 in 386 enhanced mode.
>>
>> has been discussed multiple times. conclusion: forget it
>
> Okay, but
> On 6/8/2015 7:27 AM, Dale E Sterner wrote:
>> For printers its usually easy to find the control commands but
>> for cd units I've never seen them made available to the public.
>> Is there a command list published anywhere for cds.
>>
> Yes, it's called ATAPI and there exist a lot of different do
edos-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
--
Monitor 25 network device
I recommend to ignore this thread.
Tom
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your
Hallo Herr John Hupp,
am 16. Juli 2015 um 01:48 schrieben Sie:
> For a US layout keyboard and the default BIOS keyboard driver: I brought
> this issue up a long time ago and learned that by design R-Alt is a dead
> key and does not duplicate the functionality of L-Alt.
> I have always found it t
Hello Mateusz,
a) you forgot to publish the source for picotcpl.lib and
picodosl.lib
b) the only provided example program PING.EXE is HUGE (120K/63K when
compressed) when compared to mTCP ping.exe (40K/28K compressed)
what exactly is the advantage of 'pico'TCP?
Tom
am 19. November 2015 um
> I am concerned by this statement from Jack's email: "Take a look at
> the sources for Microsoft HIMEM or EMM386, as I have…" This is the
> first I was aware that Jack had reviewed any source code from
> Microsoft.
Microsoft made the source for HIMEM.SYS available to programmers in
1988.
"Febru
>> Just want to know if FreeDOS can run interlink.exe and intersrv.exe
>> If FreeDOS is compatible with interlink, then what steps should follow?
interlink/intersrv are part of msdos. this should work in theorie,
but you are probably the first to test this on FreeDOS.
> As far as I remember, tho
Bret,
> Eric/Tom:
> I used to use INTERxxx a lot many years ago using the special
> parallel cables designed for that purpose (I think I still have a
> couple of those cables in my "spare cable box"). Parallel is MUCH
> faster than serial (null modem) cables.
I also used it *A LOT*. in times whe
ly tested this with
softice
himem
interlnk
what is your crashing configuration?
Mit freundlichen Grüßen/Kind regards
Tom Ehlert
+49-241-79886
--
Site24x7 APM Insight: Get Deep Visibility into Application
> The patched version of ITERLNK leads to problems if I still have a line
> version=3.31
version=3.31 is lying about location and size of a couple DOS
datastructures. don't do this, or expect trouble.
use /low or a new kernel to run interlnk.
tom
--
> CRYNWR - Unknown License, Dropped.
> GCDROM - Listed as GPL, No Sources, Based on XCDROM, Removed.
GCDROM sources are available.
> UIDE - Free for non-commercial, Removed.
> UMBPCI - Listed as free, No sources, Dropped.
> XCDROM - Removed.
an operati
>> Without DOSLFN, no support at all for long filenames?
> Correct. Although, I hear the was another very buggy one that was
> around before DOSLFN. I don’t know the name.
THIS.IS.RIDICULOUS.
one of the worst manifestations of Stallmanitis ever.
bye
Tom.
-
>> an operating system without CDROM and network drivers doesn't sound
>> very useful to me, even if everything has the correct license. YMMV.
> I think that the key is to perceive FreeDOS as a replacement to MSDOS,
> nothing else (that is, "BASE").
after 10+ years advertising that FreeDOS is bet
ad.doubleclick.net/ddm/clk/304595813;131938128;j
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
M
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-
> I'm building the new website. I'll update the notice to encourage new
> users to install FreeDOS in a virtual machine.
any reason why we don't provide ready to run virtual machines as .VHD
images?
Tom
--
What NetFlow
>> I'm building the new website. I'll update the notice to encourage new
>> users to install FreeDOS in a virtual machine.
>
> any reason why we don't provide ready to run virtual machines as .VHD
> images?
>
> Tom
> Hmm... I don't know why we haven't. I don't know anything about VHD
> though
__
> 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
---
>> Has anyone tried "Installhigh=C:\FDOS\COMMAND.COM"
>> I have that working for a few apps (including DP and so far no issues, also
>> am loading CDROM drivers earlier in autoexec.bat and I can cram nealy
>> everything into upper memory.
> No, I never use INSTALL, though I'm vaguely aware of it.
> On 22/07/2016 10:34, Tom Ehlert wrote:
>>> (Honestly, FreeCOM needs to be better optimized for size and then we
>>> wouldn't have to worry at all. That is one of our weakest links.)
>>
>> seriously: command.com has ~3 K resident size. what are you
>>
ce, and I recommend to
remove KPDOS from future releases of FreeDOS
> I don't need it now anymore it seems. But still wondering if it's really
> not available from anywhere.
>> Viel Spass!
> Gleichfalls, von Berlin nach Berlin :-)
> Kai
instead I recommend
http://ww
Hallo Herr Kai Schaetzl,
am 18. August 2016 um 15:31 schrieben Sie:
> Tom Ehlert wrote on Mon, 15 Aug 2016 16:00:55 +0200:
>> an amazing amount of effort to get a german keyboard driver
> Not really once you know that you don't need the .kl file.
> According to
>
> I keep getting the error dma crosses 64k boundary when using tools
> like rawrite3 or hard drive manufacturers tools floppy creation
> software. I need to boot from Windows 98 bootdisk to get rid of it.
> Please let me know if there is a way to get rid of this problem under FreeDOS.
MSDOS redir
imem.exe version 3.26, Aug 25 2006
> 15201 USBUHCI.OVL overlay for usbuhci
> 16799 emm386.exe version 2.26, Aug 25 2006
> 20776 USBUHCI.COM version 0.14, apparently 2010
> 30250 country.sys data file for nlsfunc country specific settings
> Maybe the others have additional comments on the used file versions!
> On physical machine any of keyboard layouts not work. In Virtualbox every
> keyboard layout is working.
>
> We think real machine memory side has a problem with loading keyb.exe.
there is a tool called MEM.EXE where you can detect if KEYB is loaded
or not.
it may be as well that MEM gets loa
Hello Salih,
did you try to boot your image on real, but different hardware, like a
standard PC?
Tom
--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https:
as usual.
urgent problem.
even 'Solver of this problem will be rewarded with 500$.'
a lot of more or less helpful messages exchanged.
then all of sudden the original poster vanishes, without any feedback
if all the given advice helped, or not, and how he solved his problem
(or not).
after wast
Hi,
to reproduce this FIND problem, I tried to setup a new FD1.2 machine.
what I did:
download FD12LGC.ISO
create a new virtual box machine with 512 MB disk
use FD12LGC.ISO to boot the machine.
boot machine.
'Unfortunately, this method of installation is not supported on this
hardware platfor
I could reproduce this.
it happens in/after findnext()
this error is related to the compiler.
if the source is compiled using TurboC 2.01 the error occures.
compiling the exact same source with TCPP the error is gone.
try www.drivesnapshot.de/freedos/findtcpp.com and
www.drivesnapshot.de/free
Originally to: ALL
I could reproduce this.
it happens in/after findnext()
this error is related to the compiler.
if the source is compiled using TurboC 2.01 the error occures.
compiling the exact same source with TCPP the error is gone.
try www.drivesnapshot.de/freedos/findtcpp.com and
www.
Originally to: ALL
Hi,
to reproduce this FIND problem, I tried to setup a new FD1.2 machine.
what I did:
download FD12LGC.ISO
create a new virtual box machine with 512 MB disk
use FD12LGC.ISO to boot the machine.
boot machine.
'Unfortunately, this method of installation is not supported on
in the APPINFO directory, the LSM files are formatted UNIX style LF,
and not DOS style CR LF
btw: I'm no longer able to locate FreeDOS sources for FIND and it's
maintainer from freedos.org.
Tom
--
Check out the vibran
>> Am 16.01.2017 um 13:12 schrieb BlameTroi :
>> I got this after a FIND command.
>>
>> C:\ELVIS\DOC>find /i "env" e*.htm
>> file list ...
>> Error reading from drive A: DOS area: general failure
>>
>> I've triple checked and I have nothing in my autoexec or config that
>> points to drive A
__
> 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
--
Check out the vib
Hello again,
> Do you want to load FreeDOS High, UMB?
there is no good reason (for normal use) to have ever
DOS=HIGH,UMB
disabled. if no HIGH or UMB memory is found, it is silently ignored.
Tom
--
Check out the
ck 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
>
>>> Unless I'm mistaken, conditional jumps on 8086 don't go beyond -128 ..
>>> 127 (signed) byte range. Hence the billions of workarounds (TASM
>>> "jumps", MASM "option ljmp", etc).
right.
>> I won't argue about what opcode is or is not available on 8086, since I
>> did not bother decoding their
From: Tom Ehlert
> On physical machine any of keyboard layouts not work. In Virtualbox every
keyboard layout is working.
>
> We think real machine memory side has a problem with loading keyb.exe.
there is a tool called MEM.EXE where you can detect if KEYB is loaded
or not.
it may b
From: Tom Ehlert
Hello Salih,
did you try to boot your image on real, but different hardware, like a
standard PC?
Tom
--
___
Freedos-user mailing list
Freedos-user
From: Tom Ehlert
as usual.
urgent problem.
even 'Solver of this problem will be rewarded with 500$.'
a lot of more or less helpful messages exchanged.
then all of sudden the original poster vanishes, without any feedback
if all the given advice helped, or not, and how he solved h
From: Tom Ehlert
Dear Eric Auer,
could concentrate ONCE on the problem at hand, and not on all this
blablabla about file versions?
the problem seems to be that this freedos.img, booted in VirtualBox,
is able to generate funny characters (i without dot, C with hook, ...)
and not on real
From: Tom Ehlert
Kai,
an amazing amount of effort to get a german keyboard driver :<<
> Hi Eric,
> thanks for the quick reply. In the meantime I found out that I can load a
> German layout with just "keyb gr", just not the layout file itself or the
> /E swit
From: Tom Ehlert
Hallo Herr Kai Schaetzl,
am 18. August 2016 um 15:31 schrieben Sie:
> Tom Ehlert wrote on Mon, 15 Aug 2016 16:00:55 +0200:
>> an amazing amount of effort to get a german keyboard driver
> Not really once you know that you don't need the .kl file.
>
From: Tom Ehlert
> I keep getting the error-adma crosses 64k boundary when using tools
> like rawrite3 or hard drive manufacturers tools floppy creation
> software. I need to boot from Windows 98 bootdisk to get rid of it.
> Please let me know if there is a way to get rid of this p
From: Tom Ehlert
Hi,
to reproduce this FIND problem, I tried to setup a new FD1.2 machine.
what I did:
download FD12LGC.ISO
create a new virtual box machine with 512 MB disk
use FD12LGC.ISO to boot the machine.
boot machine.
'Unfortunately, this method of installation is not support
From: Tom Ehlert
I could reproduce this.
it happens in/after findnext()
this error is related to the compiler.
if the source is compiled using TurboC 2.01 the error occures.
compiling the exact same source with TCPP the error is gone.
try www.drivesnapshot.de/freedos/findtcpp.com and
From: Tom Ehlert
> Why not use the CHOICE option-a to let the user decide?
because 99,9 % of all user have no need for SHARE.
> I have a
> menu system which is designed to be used on a network and requires share to
be loaded
are really multiple machines accessing the same files at
From: Tom Ehlert
Hello again,
> Do you want to load FreeDOS High, UMB?
there is no good reason (for normal use) to have ever
DOS=HIGH,UMB
disabled. if no HIGH or UMB memory is found, it is silently ignored.
From: Tom Ehlert
Mateusz,
really cool.
unfortunately I don't have a linux machine around, so testing must
wait.
may I suggest to use UDP/IP instead of raw packets?
UDP/IP requires just a few bytes set up in the right way, and the
calculation of the IP checksum; shouldn't be too
From: Tom Ehlert
>>> Unless I'm mistaken, conditional jumps on 8086 don't go beyond -128 ..
>>> 127 (signed) byte range. Hence the billions of workarounds (TASM
>>> "jumps", MASM "option ljmp", etc).
right.
>> I won't argue
> It's more possible than ever [0] to compile the kernel with GCC.
'This part of DJGPP is dedicated to the 16-bit tools that have been developed
to assist in using DJGPP.
Note: I lost interest in these projects before I completed them.'
> Yes, it would be a large under taking but maybe a long t
>> Hi Jerome,
>> I've just tried your veach.com utility and it looks like it shall really
>> come in handy! I was missing a program capable of appending a command to a
>> sorted list (like a | in Unix ) .
>> Nice job, and thanks for your effort
> Thank you.
> Just like you, I would find mysel
> 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@list
Dear Eric,
> Hi :-) Quick news from Jack's drivers: He has a closed
> source update for XMGR (more fail-safe 386 XMS move)
> and UHDD: The new UHDD has the interesting feature of
> read-ahead for cache sizes of at least 20 MB. It is
> a simplified version without I/O overlap and DOS RAM
> search
> Also, did you know that UMBPCI is actively maintained
> and more reliable in finding out which areas can be
> used for UMB etc. than JEMM / JEMM386? So it can be
> a good idea to use explicit EMM options based on what
> UMBPCI detected: This avoids more conflicts than the
> easier method of letti
during the time that all these responses were written AND READ, competent
programmers could
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_
during the time that all the contributions in this thread were
written AND READ, competent programmers could have ported the kernel
to GCC, with some time left to save the planet, and fight for peace on
earth.
just my 2 cents.
Tom
--
> 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!
> 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 buggy
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 i
> 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 yo
> 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 thi
> 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
> 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
> c
> 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
> 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
> belo
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
>> tool (http://live.lear
> 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 eve
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
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 do
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 those
>> 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
>> 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 option
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
> E
>> 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 cells.
> 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 d
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 t
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
https://lists.sourceforge.net/lists/listinfo/
> 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
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
> 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 w
> 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
h
__
> 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
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).
> https://sou
> 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 VirtualBo
> 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, jus
> 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
> 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 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
> 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; sorry.
1 - 100 of 447 matches
Mail list logo
