On 26 Apr 2004 07:56:43 -0400, you wrote:
Hi Patrick,
>This is with Intel PRO/1000 hardware, not 3com hardware. I strongly
>suspect you and I are seeing independent problems.
But Tom's advise did work on my system, that means you may have the
same problem later (when you fix this).
Rgds,
Joh
On Mon, 26 Apr 2004 09:27:31 +0200, you wrote:
Hello Tom,
>try
> LH /L: NET INIT
>
>to force loading of network driver into low memory.
Thank you Tom, now the MSCLIENT work, you are really a genius :-)
Rgds,
Johnson.
---
This SF.net email
On Mon, 26 Apr 2004, tom ehlert wrote:
> BO> MSDOS 7.10 does move the EBDA though. What MSDOS are we looking at now --
> BO> the FAT16 kernel says 5.0, and the FAT32 says 7.10 ?
>
> MSDOS 7.1 doesn't move it on F5 (or ctrl-F5 ? should this depend on
> the kernel version ?), but seems to move in h
At 05:00 PM 4/26/2004 -0400, Patrick J. LoPresti wrote:
>Michael Devore <[EMAIL PROTECTED]> writes:
>
>> First thing to look at is the register values, which are across the
>> top line. We need those values. Then look at the failing CPU
>> instruction line which is highlighted in the main window.
Michael Devore <[EMAIL PROTECTED]> writes:
> First thing to look at is the register values, which are across the
> top line. We need those values. Then look at the failing CPU
> instruction line which is highlighted in the main window. That
> together with the register values should give the im
At 04:03 PM 4/26/2004 -0400, Patrick J. LoPresti wrote:
>Michael Devore <[EMAIL PROTECTED]> writes:
>
>> Is X=TEST really necessary? Unfortunately yes, at least for some
>> machines. There exist PC's which place ROM code in the upper memory
>> area, but without the standard ROM signature of 55h A
"Erwin Veermans" <[EMAIL PROTECTED]> writes:
> Wild guess:
>
> Did you try "switches=/E" in config.sys?
> Some people were reporting issues with latest kernel that
> could be reverted with the /E-switch. Browse this list
> for more info ...
No effect. Also, this happens with both the 2.0.33 and
Michael Devore <[EMAIL PROTECTED]> writes:
> Is X=TEST really necessary? Unfortunately yes, at least for some
> machines. There exist PC's which place ROM code in the upper memory
> area, but without the standard ROM signature of 55h AAh. These
> aren't old moldy machines either. In a small te
Uploaded to ftp://ftp.devoresoftware.com/downloads are emm386.zip (uncompressed
executable) and emm386sr.zip (source) with several changes related to UMBs, EMS, and
rebooting. The ZIP files are dated April 26, 2004, actual files dated April 25.
EMM386 performs a warm boot upon a Ctrl-Alt-Del ke
Hello Bart,
>> Checking MSDOS 6.2, the kernel doesn't move the EBDA if no UMB is
>> found.
BO> MSDOS 7.10 does move the EBDA though. What MSDOS are we looking at now --
BO> the FAT16 kernel says 5.0, and the FAT32 says 7.10 ?
it's not a matter of reported kernel version - and I don't care about
On Mon, 26 Apr 2004, tom ehlert wrote:
> Checking MSDOS 6.2, the kernel doesn't move the EBDA if no UMB is
> found.
MSDOS 7.10 does move the EBDA though. What MSDOS are we looking at now --
the FAT16 kernel says 5.0, and the FAT32 says 7.10 ?
> in the default setting, moving the EBDA doesn't sav
Alain escribió:
Just one question: How much does MODE grow with Zlib?
And one more: What about an install program that extracts needed
information from a standard .zip file specific for that user's needs?
I'd support that, but requires work:
(1) either to create the packs
(2) or to make the prog
Just one question: How much does MODE grow with Zlib?
And one more: What about an install program that extracts needed
information from a standard .zip file specific for that user's needs?
Alain
right now on updated ODIN bootdisk the CPI files take almost 600KB (10
* 60KB),
which is nearly half
Checking MSDOS 6.2, the kernel doesn't move the EBDA if no UMB is
found.
moving the EBDA makes most sense anyway, if it's moved to upper (UMB)
memory)
So I would recommend to disable move EBDA by default, or to move it
only if UMB space can be allocated for it.
in the default setting, moving the
> With FreeDOS (ke2034_32), it crashes as I described: The driver loads,
> but when tinyrfc.exe tries to obtain a DHCP lease, it gets an invalid
> opcode.
Wild guess:
Did you try "switches=/E" in config.sys?
Some people were reporting issues with latest kernel that
could be reverted with the /E-s
Johnson Lam <[EMAIL PROTECTED]> writes:
> You report faster than me.
>
> I got the same problem when trying MSCLIENT, it does work under
> FDXXMS+UMBPCI (try it), but fail with HIMEM+EMM386. I'm quite sure the
> memory manager and hardware not so compatible especially Network
> Interface Card.
I
Hi,
I have not had success with dial-up in FreeDOS, but in case I had, I
have recently discovered that there's a version of PegasusMail for DOS,
so perhaps that's a start for an email client for DOS...
Aitor
david lowe escribió:
Is there an equivalent of Dialup Networking in the FreeDOS system
At Mon, 26 Apr 2004 9:59am +0100, Bart Oldeman wrote:
> On Sun, 25 Apr 2004, Steve Nickolas - Using Windoze wrote:
>
> > I only wish we had ADSL and cable-modem dialers. :(
>
> these are *way* too complicated with the limited resources we have.
>
> My ADSL modem alone needs more firmware downlo
On Sun, 25 Apr 2004, Steve Nickolas - Using Windoze wrote:
> I only wish we had ADSL and cable-modem dialers. :(
these are *way* too complicated with the limited resources we have.
My ADSL modem alone needs more firmware downloaded (770K) into it
everytime it starts than what DOS was designed fo
Hello Johnson,
JL> I got the same problem when trying MSCLIENT, it does work under
JL> FDXXMS+UMBPCI (try it), but fail with HIMEM+EMM386. I'm quite sure the
JL> memory manager and hardware not so compatible especially Network
JL> Interface Card.
Freedos EMM386 doesn't support VDS yet, and NET.EXE
Johnson Lam schreef:
I got the same problem when trying MSCLIENT, it does work under
FDXXMS+UMBPCI (try it), but fail with HIMEM+EMM386. I'm quite sure the
memory manager and hardware not so compatible especially Network
Interface Card.
try HIMEM + UMBPCI (there's even a 3.57beta7 version at the UM
On Mon, 26 Apr 2004 13:31:34 +0800, you wrote:
Sorry everyone,
>I monitored with a RS232 break-out box, DTR raise when BAUDHARD=1.
I type the wrong number!
When setting the speed (e.g. BAUDHARD=96) DTR will raise, BAUDHARD=1
only shows the status and DTR
Rgds,
Johnson.
22 matches
Mail list logo
