At 05:53 PM 4/25/2004 +0400, Arkady V.Belousov wrote:
Hi!
24-áÐÒ-2004 21:51 [EMAIL PROTECTED] (Michael Devore) wrote to
[EMAIL PROTECTED]:
I thought ram by itself meant dynamic EMS allocation as opposed to
allocating a fixed amount (at least, this is what the docs day), that's
how I use ram in
In the last major release of my project
(http://unattended.sourceforge.net/), I changed my network boot disk
to use FreeDOS instead of MS-DOS.
Now, my users are reporting that the boot disk no longer works on
machines which have Intel gigabit (PRO/1000) networking hardware.
I have one machine
On Sun, 25 Apr 2004, Aitor Santamaría Merino wrote:
Bernd Blaauw escribió:
right now on updated ODIN bootdisk the CPI files take almost 600KB (10
* 60KB),
which is nearly half the disk! (and makes creating 720KB more difficult).
Perhaps it's a question to check the CPI files, perhaps
At 11:36 PM 4/25/2004 +0400, Arkady V.Belousov wrote:
Hi!
25-áÐÒ-2004 11:02 [EMAIL PROTECTED] (Michael Devore) wrote to
[EMAIL PROTECTED]:
I thought ram by itself meant dynamic EMS allocation as opposed to
MD It's not documented that way on any EMM386 docs I see, including
EMM386 may be able to
help-files are already collected in a zipfile, Rob worked on that.
I suggested compressing the CPI-files to Eric using Gzip,
but that would add Zlib to MODE.
Eric likes another less efficient but smaller to implement compression
algorythm/program.
he said it reduces CPI from 58 (60) to 19KB
Hi!
25--2004 15:36 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA X-Spam-Report: Spam detection software, running on the system
externalmx-1.sourceforge.net, has
EA identified this incoming email as possible spam. The original message
EA has been attached to this so you
Ooops...
Aitor Santamaría Merino escribió:
Bernd Blaauw escribió:
right now on updated ODIN bootdisk the CPI files take almost 600KB
(10 * 60KB),
which is nearly half the disk! (and makes creating 720KB more
difficult).
Perhaps it's a question to check the CPI files, perhaps for MOST of
Hi,
Eric Auer escribió:
RAM= assume that there already IS RAM at this place, so leave it mapped 1:1
and put UMB or EMS page frame there
Do not mess with terms:
RAM= scanable area: scan it, and if found empty, map, and have into
account any X=, I=
X=unconditionally excluded for
Michael Devore [EMAIL PROTECTED] writes:
Since you're failing without HIMEM or EMM386 loaded, you have to be
hitting a kernel compatibility, agreed? It can't be a UMB conflict
or a p-mode conflict or something failing in EMS/XMS/VCPI/DPMI
calls. That actually narrows the field of suspects
Title: Bestec_FT4U-Finishing Equipment
We trade stock ultrasonic cleaning, metal finishing plant and equipment.
Ask details
First a few updates...
My considering converting to FreeDOS was because of some recent problems
with my system, some of which were problems in Windoze. Eventually (over
the course of this weekend) I had to reformat my hard drive. Now that that's
over with, I have a few more questions:
What
On Sun, 2004-04-25 at 22:33, Steve Nickolas - Using Windoze wrote:
david lowe wrote:
SNIP
What utilities are recommended for download management, internet
browser, virus/trojan/worm
detection removal?
I have yet to find them, although I have heard Arachne works well as a
browser.
At 07:08 PM 4/25/2004 -0400, Patrick J. LoPresti wrote:
Michael Devore [EMAIL PROTECTED] writes:
I don't do kernel work, but depending on how much you want to dig in
the guts of the problem, you might want to grab the 386SWAT debugger
and load it immediately after the driver, with nothing
Hi Eric,
I monitored with a RS232 break-out box, DTR raise when BAUDHARD=1.
But when it's low, it shows DTR=AUTO. That seems a bit confusing.
Rgds,
Johnson.
---
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a
Michael Devore [EMAIL PROTECTED] writes:
I don't do kernel work, but depending on how much you want to dig in
the guts of the problem, you might want to grab the 386SWAT debugger
and load it immediately after the driver, with nothing else. It
should catch the exception and throw you into the
At 07:08 PM 4/25/2004 -0400, Patrick J. LoPresti wrote:
Michael Devore [EMAIL PROTECTED] writes:
I don't do kernel work, but depending on how much you want to dig in
the guts of the problem, you might want to grab the 386SWAT debugger
and load it immediately after the driver, with nothing
On 25 Apr 2004 18:10:17 -0400, you wrote:
Hi Patrick,
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.
You report faster than me.
I got the same problem when trying MSCLIENT, it does work under
17 matches
Mail list logo