Hi Jerome,
> At present, the RBE is not setup to include 2 branches from the same GitLab
> project.
>
> It would require a separate GitLab project (with a different name, like
> watcomv2). I think having two different watcom C packages could cause user
> confusion on which one to install. It
+1 - Open Watcom 1.9 is stable and safe. I think those factors make it the
default for inclusion in a distribution.
Something actively under development and in between releases sounds like a
bad idea.
On Sat, Mar 18, 2023 at 5:42 AM wrote:
> Hi Bernd,
>
> > On Mar 17, 2023, at 2:12 PM, Bernd B
Hi Bernd,
> On Mar 17, 2023, at 2:12 PM, Bernd Boeckmann via Freedos-devel
> wrote:
>
> IDLEHALT=1 works for my machines and reduces the CPU load under VirtualBox to
> nearly zero at the command prompt.
>
>> Am 17.03.2023 um 15:25 schrieb jer...@shidel.net:
>>
>> On a side note… Why run the
Hello Rugxulo,
This is interesting --- thanks! For my part, I found that `wcl' with
`-l=com' does indeed work on my machine.
Apparently `wcl -l=com' will actually pass `system com' (instead of
`format dos com') to `wlink'. I am not sure how `format dos com' works
(if it is supposed to work
> I'm trying to link a program as a COM executable, but when I add the
> "format DOS COM" directive to the linker, it complains that libraries
> aren't available (such as clibs.lib). It works fine and produces an EXE
> if I leave out this directive. What's really happening?
just don't use .COM f
Hi,
On Wed, Jul 11, 2018, 6:29 AM David McMackins wrote:
> I'm trying to link a program as a COM executable, but when I add the
> "format DOS COM" directive to the linker, it complains that libraries
> aren't available (such as clibs.lib). It works fine and produces an EXE
> if I leave out this
I'm trying to link a program as a COM executable, but when I add the
"format DOS COM" directive to the linker, it complains that libraries
aren't available (such as clibs.lib). It works fine and produces an EXE
if I leave out this directive. What's really happening?
Happy Hacking,
David E. McMack
Hi,
On 7/8/11, Jim Michaels wrote:
>
> they are available here.
> http://www.rahul.net/dkaufman/index.html
I've never used cURL, but apparently latest is 7.21.7. I blindly
wonder if it'll still compile with DJGPP + WATT-32 (too preoccupied to
personally try right now, doh).
Anyways, here's link
cURL has no problem with ftp:// it handles LOTS of protocols
>
>From: Michael B. Brutman
>To: freedos-devel@lists.sourceforge.net
>Sent: Wednesday, July 6, 2011 4:32 PM
>Subject: Re: [Freedos-devel] watcom tcp
>
>
> On 7/6/2011 6:0
they are available here.
http://www.rahul.net/dkaufman/index.html
>
>From: Bernd Blaauw
>To: freedos-devel@lists.sourceforge.net
>Sent: Wednesday, July 6, 2011 4:02 PM
>Subject: Re: [Freedos-devel] watcom tcp
>
>Op 3-7-2011 4:26, Micha
s measured in MiB and GiB.
>
>From: Bernd Blaauw
>To: freedos-devel@lists.sourceforge.net
>Sent: Wednesday, July 6, 2011 4:27 AM
>Subject: Re: [Freedos-devel] watcom tcp
>
>Op 6-7-2011 6:22, Steve Nickolas schreef:
>> On Tue, 5 Jul 2011, Jim Michaels
Op 7-7-2011 15:37, Steve Nickolas schreef:
> On Thu, 7 Jul 2011, Bernd Blaauw wrote:
>
> I think the RTL-8139 chipset does and it's still quite common.
>
And there I was, wanting high-performant low-CPU network cards (with
also packet drivers):
* Intel Gigabit PCI-card (10/100Mbit fallback)
* In
On Thu, 7 Jul 2011, Bernd Blaauw wrote:
> I'm happy with whatever I can get. My real hardware has an Nvidia
> chipset network driver for which no packet drivers exist, so sticking to
> virtual machines. I wonder if any PCI (or even PCI-express or onboard)
> network cards still support packet drive
Hi Bernd,
> I'm happy with whatever I can get. My real hardware has an Nvidia
> chipset network driver for which no packet drivers exist, so sticking to
> virtual machines. I wonder if any PCI (or even PCI-express or onboard)
> network cards still support packet drivers.
You probably can stil
Op 7-7-2011 1:32, Michael B. Brutman schreef:
> mTCP FTP compares poorly to the native stack and FireFox there, but FTP
> is working in a very limited environment:
>
> * The TCP/IP socket receive buffer is tiny compared to the native
> network stack
> * You are doing filesystem writes 8KB
On 7/6/2011 6:02 PM, Bernd Blaauw wrote:
ftp://ftp.xs4all.nl/pub/test/10mb.bin :
1) 2.0 to 2.5MByte/second ( around 20Mbit/s, 25Mbit ISP subscription)
2) N/A , WGET not working
3) 500Kbyte/second ( around 4Mbit/s)
mTCP FTP compares poorly to the native stack and FireFox there, but FTP
is worki
Op 3-7-2011 4:26, Michael B. Brutman schreef:
> The second parameter is optional and allows you to do the rename. This
> is similar to Unix command line clients.
Tested tonight, works like a charm :)
Confusingly, I've now got trouble getting WGET working, as I had the
intention of downloading fr
Op 6-7-2011 6:22, Steve Nickolas schreef:
> On Tue, 5 Jul 2011, Jim Michaels wrote:
>
>> how on earth shall I expect to build a bootable ISO image with mkisofs?
>
> Put a boot floppy image in the folder and use
> mkisofs -b filename.144 -o filename.iso path/
And isolinux as bootloader, instea
On Tue, 5 Jul 2011, Jim Michaels wrote:
> how on earth shall I expect to build a bootable ISO image with mkisofs?
Put a boot floppy image in the folder and use
mkisofs -b filename.144 -o filename.iso path/
--
All of t
how on earth shall I expect to build a bootable ISO image with mkisofs?
>
>From: Rugxulo
>To: freedos-devel@lists.sourceforge.net
>Sent: Tuesday, July 5, 2011 1:23 AM
>Subject: Re: [Freedos-devel] watcom tcp
>
>Hi,
>
>On 7/2/11, B
DOS version of cURL can be obtained from
http://www.rahul.net/dkaufman/index.html
>
>From: Bernd Blaauw
>To: freedos-devel@lists.sourceforge.net
>Sent: Saturday, July 2, 2011 5:42 PM
>Subject: Re: [Freedos-devel] watcom tcp
>
>Op 3-7-2011
Le mardi 05 juillet 2011 à 15:17 -0500, Rugxulo a écrit :
> > http://www.torlus.com/floppy/
>
> Good to know (SD card reader / USB floppy emulator hardware), but
> there's still probably some drawbacks.
>
> I've got a USB floppy drive, and it works with FreeDOS, but other
> non-BIOS-using OSes ne
Hi,
On 7/5/11, François Revol wrote:
> Le mardi 05 juillet 2011 à 03:23 -0500, Rugxulo a écrit :
>>
>> > That's not helping a "hey
>> > let's boot from floppy, configure internet access and install from
>> > downloaded/mounted ISO file"
>>
>> Floppies just don't hold enough. Add to that the fact
Le mardi 05 juillet 2011 à 03:23 -0500, Rugxulo a écrit :
>
> > That's not helping a "hey
> > let's boot from floppy, configure internet access and install from
> > downloaded/mounted ISO file"
>
> Floppies just don't hold enough. Add to that the fact that they fail
> semi-frequently, and you hav
Hi,
On 7/2/11, Bernd Blaauw wrote:
> Op 3-7-2011 2:59, Rugxulo schreef:
>> I guess you mean Mike plans to write something like this one day. We
>> do already have a port of WGET (via DJGPP), but I've not heavily
>> tested it. (Or did you mean one with IPv6 support?? Dunno ...)
>>
>> http://www.ib
On 7/2/2011 8:25 PM, Bernd Blaauw wrote:
> Ah good news.
> Basicly FTP.EXE already suffices, except for the following:
> * FTP-only, no http/https
> * requires entering commands or external script as input
> * no renaming for storing (www.mysite.com/somelongfilename.zip -->
> c:\short.zip)
mTCP FT
Op 3-7-2011 2:59, Rugxulo schreef:
> I guess you mean Mike plans to write something like this one day. We
> do already have a port of WGET (via DJGPP), but I've not heavily
> tested it. (Or did you mean one with IPv6 support?? Dunno ...)
>
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/n
Op 3-7-2011 3:03, Michael B. Brutman schreef:
> [1] A fully featured wget will be difficult to get into the memory
> space. I have plans for a simple version that does not recurse, does
> not support Unicode, etc.
Ah good news.
Basicly FTP.EXE already suffices, except for the following:
* FTP-onl
On 7/2/2011 7:42 PM, Bernd Blaauw wrote:
> Op 3-7-2011 1:54, François Revol schreef:
>> Any of those two supports IPv6 ? So FreeDOS can survive the IPcalypse :D
> Don't think so.
>
> Stuff I can think of which is missing:
> 1) WGET/CURL
> 2) WOL-client to wake up machines in the network by sending
Hi,
On Sat, Jul 2, 2011 at 7:42 PM, Bernd Blaauw wrote:
> Op 3-7-2011 1:54, François Revol schreef:
>
>> Any of those two supports IPv6 ? So FreeDOS can survive the IPcalypse :D
>
> Don't think so.
>
> Stuff I can think of which is missing:
> 1) WGET/CURL
I guess you mean Mike plans to write som
Op 3-7-2011 1:54, François Revol schreef:
> Any of those two supports IPv6 ? So FreeDOS can survive the IPcalypse :D
Don't think so.
Stuff I can think of which is missing:
1) WGET/CURL
2) WOL-client to wake up machines in the network by sending magic packet
3) IP v6
4) Jumboframes (9000 bytes I t
Le samedi 02 juillet 2011 à 09:32 -0500, Michael B. Brutman a écrit :
> Thanks for the plugs for mTCP - I am buried in work and away from email
> for a good part of the day.
>
> There are a lot more WATTCP apps out there because WATTCP has been
> around a lot longer, and there is a benefit to th
Thanks for the plugs for mTCP - I am buried in work and away from email
for a good part of the day.
There are a lot more WATTCP apps out there because WATTCP has been
around a lot longer, and there is a benefit to that long term
stability. I think that I have covered the more popular applicat
Op 1-7-2011 23:53, Rugxulo schreef:
> Hi, quick reply, (others know way more than I do here),
http://www.crynwr.com/
should do the trick for packet drivers.
Loading method:
* find correct packet driver for your network interface card
* load it (usually type its name, sometimes specific options
Hello I am trying to find watcom tcpip drivers and utils to connect a 286
running dos 5 to the internet I have an 3c509 card packet driver and neeed
watcom tcp where can I get watcom tcp? Thanks ed
--
All of the data gen
Hi, quick reply, (others know way more than I do here),
On Fri, Jul 1, 2011 at 4:49 PM, Edwin Rhodes wrote:
>
> Hello I am trying to find watcom tcpip drivers and utils to connect a 286
> running dos 5 to the internet I have an 3c509 card packet driver and neeed
> watcom tcp where can I get watco
What version of WATCOM is the most recommended one ?
Almost 1 year elapsed since 1.8 release, there were some complaints by
Japheth about "JWASM doesn't compile with 1.8 anymore" in the past,
but latest releases report to compile fine with both 1.7a and 1.8,
although nothing has been fixed in WATC
On Sun, 8 Feb 2004, Arkady V.Belousov wrote:
> Steffen, I found, that for RTL sources also need bld/lib_misc
> directory. May you prepare (and resend) it too?
You will find it here:
http://www2.inf.fh-bonn-rhein-sieg.de/~skaise2a/ska/ow/lib_misc.tar.bz2
Bye,
--
Steffen Kaiser
-
Hi!
Steffen, I found, that for RTL sources also need bld/lib_misc
directory. May you prepare (and resend) it too?
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the
Hi!
4-Фев-2004 10:48 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
>> - WHELP doesn't support fast search (by first typed letters).
LG> It does - press S and then type - it searches as you type.
`S' searches only in list, which (somewhat) equal to index. It doesn't
searc
On Wed, 4 Feb 2004 08:35:55 +0300 (MSK), Arkady V.Belousov wrote:
- WHELP doesn't lists help files (in current and/or startup directory).
- WHELP doesn't shows help file header (for example, "Open Watcom C/C++
Getting Started") in Contents.
- WHELP doesn't remembers last position in Contents.
-
Hi!
Well, I summarize my first impressions with Watcom in (short) list:
__O\_/_\_/O__
OpenWatcom wishes, issues, troubles and bugs
Distributive:
- no descriptions for archives and files in
On Wed, 4 Feb 2004, Arkady V.Belousov wrote:
> 3-æÅ×-2004 15:17 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
> [EMAIL PROTECTED]:
>
> LG> "_emit" can be replaced by "db",
>
> __emit__ (was) allow to point variable names (including local). Though,
> I don't use this feature and now replace s
Hi!
3-Фев-2004 15:17 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG> "_emit" can be replaced by "db",
__emit__ (was) allow to point variable names (including local). Though,
I don't use this feature and now replace some __emit__ occurences by
explicit inline asm. BTW,
On Tue, 3 Feb 2004 05:06:41 +0300 (MSK), Arkady V.Belousov <[EMAIL PROTECTED]> wrote:
But there remains unrecoverable errors, because Watcom doesn't knows
register pseudo-variables (_AX, etc) and __emit__. Unforunately, there are
places, where inline asm is required. Fortunately, Watcom knows pre
Hi!
First try is negative. :) :( I try to compile my MEM with Watcom, but
without (full) success. There was some small things, which I correct to make
WPP happy:
- to remove warnings about truncation, I add some castings. (Strange, that
without casting WPP gives this warning for "SYS.OS.fl
46 matches
Mail list logo
