Hi,
On Mon, Jun 25, 2012 at 4:53 PM, Mateusz Viste mate...@viste-family.net wrote:
I do agree with Rugxulo. Just adding my 2cts regarding FDUpdate (I'm the one
responsible for creating the monster).
BTW, I knew you'd read this, so no disrespect intended (obviously),
your work is always
Hi,
On Mon, Jun 25, 2012 at 11:46 PM, Marco Achury marcoach...@gmail.com wrote:
I think official freedos release must be just 2 or 3 floppies, as MSDOS
was
Boot system + basic drivers and tools (and both, cdrom and floppy image are
required).
Well, depends on how simplistic you want to
From: Rugxulo rugx...@gmail.com
To: freedos-user@lists.sourceforge.net
Sent: Thursday, June 28, 2012 12:31 PM
Subject: Re: [Freedos-user] fdupdate
Hi,
On Mon, Jun 25, 2012 at 11:46 PM, Marco Achury marcoach...@gmail.com wrote:
I think official freedos release must be just
I have been blissfully unaware of the packaging requirements for
FreeDOS. I update mTCP a few times a year, and I know that is a lot of
work to get right. Is there a FAQ or notes on how FreeDOS manages
packages? If I can make the mTCP updates easier I will.
Mike
Hello,
I do agree with Rugxulo. Just adding my 2cts regarding FDUpdate (I'm the one
responsible for creating the monster).
Since I too often don't have networking in native DOS, I've never
relied on FDupdate. Presumably it can (or could) do so, but I don't
know the specifics. I don't know if
I think official freedos release must be just 2 or 3 floppies, as
MSDOS was
Boot system + basic drivers and tools (and both, cdrom and floppy image
are required).
No package manager needed for this base system
Aditional to this, the community or any interested user can release
cdroms with
Hi,
let's continue where I stopped a year ago. ;)
I tried fdupdate to update my 1.1 installation.
But, the DOS PC is still offline. I don't have a spare network cable. Is
there any way to tell fdupdate/fdpkg where to find the files locally?
I believe there are a lot of packages that are not
On Sat, 2009-04-25 at 16:35 +0200, Eric Auer wrote:
Hi,
Has anyone gotten fdupdate to work with a 486? I lost the link to
fdupdate v0.55 and the instructions on how to use it in fdupdate
v0.54. If using a 486 is the problem because of a bug in the math
coprocessor or something
Hi,
Has anyone gotten fdupdate to work with a 486? I lost the link to
fdupdate v0.55 and the instructions on how to use it in fdupdate
v0.54. If using a 486 is the problem because of a bug in the math
coprocessor or something similar, that would be nice to know.
I've noticed that I get
On Monday 20 April 2009 00:08 (CEST), Michael Robinson wrote:
Has anyone gotten fdupdate to work with a 486? I lost the link to
fdupdate v0.55 and the instructions on how to use it
Hi,
You didn't lose it, it simply never existed :)
I sent you a beta FDUPDATE version with support for the
Has anyone gotten fdupdate to work with a 486? I lost the link to
fdupdate v0.55 and the instructions on how to use it in fdupdate
v0.54. If using a 486 is the problem because of a bug in the math
coprocessor or something similar, that would be nice to know.
I've noticed that I get a C prompt
Hello,
2009/4/9 Eric Auer e.a...@jpberlin.de:
MS DOS 6.22 has a tool that graphically shows a representation of
memory, I think it was called msd. Is there an equivalent for freedos?
There are various tools for that, a nice one
is Quarterdeck MFT Manifest which is now
freeware.
Oops, just sent an empty reply...
and more than 2 near fnodes does not tell me what crashed.
It might mean you use an old kernel which leaves
file handles open when access is aborted due to
an error...
I do not think your RAM config is a problem.
Maybe your copy of FDUPDATE or WGET is
I was wrong about wget not crashing, it just took it a long time to
crash running it on it's own. Is the kernel going to be reworked
anytime soon to remove this fnode concept?
--
On Fri, 2009-04-03 at 17:12 +0200, Mateusz Viste wrote:
On Friday 03 April 2009 16:08, Michael Robinson wrote:
When I run fdupdate, it crashes with a 2 near fnodes error.
Hi,
Please define the crash. When exactly is it happening? When FDUPDATE is
starting itself, or when it run wget to
I'm not certain about what is crashing. Changing to curl makes no
difference at all. This works on my Pentium 4, so I suspect there is
something specific to my 486 that is causing the problem. I wish the
crash message was more descriptive. A dump of the processor's registers
and more than
I have a DTK 486 with a very simple AMI bios and on
it a Dlink DE220PT nic on IRQ 12 IO 0x240. Arachne
works fine, but fdupdate crashes. It crashes
regardless of whether or not I choose to update a
package. I'm using the crynwr packet collection
ne2000 driver. I get an error about 2 near
I could get it to work under vmware with wget believe it or not,
but I haven't gotten it to work on real hardware even with curl.
Another problem I've noticed is that fdupdate doesn't seem to
record the new version of a package that it has updated.
My 486 is passing memtest with flying colors.
On Fri, 2008-02-15 at 21:00 +0100, Mateusz Viste wrote:
On Friday 15 February 2008, robinson-west user wrote:
I could get it to work under vmware with wget believe it or not,
but I haven't gotten it to work on real hardware even with curl.
Do your real hardware can run anything more than
Hi Michael,
Do you tried using the tested wget binary?
(http://mateusz.viste.free.fr/fdupdate/wgetx.zip)
Why wouldn't the copy of wget packaged with freedos 1.0 work?
It is just a piece of the puzzle: If using another
version of wget solves the problem, we know more.
machine. I'm not
Hi!
FDUPDATE v0.53 is out!
What's new in v0.53 [14 Feb 2008]:
- Added configuration for the download command (was hardcoded to wget),
- FDUPDATE doesn't switches to the %TEMP% directory anymore,
- Changed the configuration file format,
- Added german translation.
ulimit(fdupdate.tab) EIO error input/output error...
My freedos update locks up and I've noticed something similar to the
above error. Is there supposed to be a ulimit executable? Is there
supposed to be an installation of djgpp for wget to work?
On Wednesday 13 February 2008, robinson-west user wrote:
ulimit(fdupdate.tab) EIO error input/output error...
Wow, that's an error I've never seen...
My freedos update locks up and I've noticed something similar to the
above error. Is there supposed to be a ulimit executable?
No, there's
I'm on a 486 DX2 66 EISA bus, no VLB. 20 megs of SIMM ram, 30 pin.
Is there a copy of memtest86+ for freedos, it would be silly if this
turned out to be a bad memory problem.
autoexec.bat:
---
@echo off
if not %config% == 4
On Friday 28 December 2007, someone wrote:
I am running freedos on a DTK 486 DX2-66 board with AMI bios.
It crashes when I type y to apply any update.
gs: sel=00bf base= limit=0010
ss: sel=0033 invalid
App stack: [000f06c8..000706cc] Exceptn stack: [000705f8..0006e6b8]
Sorry
I am running freedos on a DTK 486 DX2-66 board with AMI bios.
It crashes when I type y to apply any update.
gs: sel=00bf base= limit=0010
ss: sel=0033 invalid
App stack: [000f06c8..000706cc] Exceptn stack: [000705f8..0006e6b8]
Call frame traceback EIPS:
0xad0f
0x0001ce94
26 matches
Mail list logo
